News

Microsoft Azure and Office 365 Services Go Down in Texas Service Area

Microsoft's datacenters in the South Central U.S. region were affected by a lightning strike on Sept. 4, disabling Microsoft Azure and Office 365 services.

The lightning strike on a San Antonio, Texas datacenter temporarily knocked out the power, leading to service outages that have affected many regional South Central U.S. Azure and Office 365 services, as well as nonregional Azure Active Directory services. Power to the affected datacenter has since been restored, but Microsoft still listed multiple Azure services that are out for customers in that region, according to its Azure Status page.

The DownDetector.com site, which tracks service outages, offered this heat map, showing that Azure service outages appear to be mostly located in the Texas region:

[Click on image for larger view.] Heat map from DownDetector.com showing Microsoft Azure service outage on the afternoon of Sept. 4, 2018.

Office 365 services were also affected for customers using hosting services from Microsoft's San Antonio datacenter. The kinds of problems Office 365 users might encounter were listed as follows, according to this Office 365 announcement:

  • Exchange -- Some users may be unable to access Outlook on the web. Email access through other protocols may be unaffected.
  • Power BI -- Users may receive a 'Server unavailable' error or may be unable to log in.
  • SharePoint -- Most impact has been mitigated, but a subset of users may be unable to make or save changes and may experience stale search results. Further details on SharePoint mitigation can be found under service incident SP147560.
  • Microsoft Teams -- Users may be unable to access Office documents within Teams.
  • Intune -- Affected users may be unable access the Intune portal or other functionality.
  • Education -- Affected users may be seeing issues with services including School Data Sync.

The start time for the problems was listed as occurring at 9:09 a.m. UTC, which is about 2:09 a.m. PST.

The outage has affected developers using Microsoft's Visual Studio Team Services, causing them to be unable to access their accounts, and reporting dashboards won't load, according to a VSTS announcement. That announcement also specifically mentioned that the underlying issue was "a datacenter cooling outage in South Central US which is impacting all services in a specific part of the datacenter."

The outage also affected users of Azure Active Directory, Microsoft Dynamics Finance and Operations and Lifecycle Services, according to a Microsoft Dynamics announcement.

So far, there are no workarounds for affected customers. At press time, Microsoft had not indicated when there might be a resolution.

Many of Microsoft's services come with service-level agreements, typically assuring 99.9 percent uptime availability. Organizations can get a service credit if they apply for the downtime. However, these customers have to have had no other service options to claim the credit.

About the Author

Kurt Mackie is senior news producer for 1105 Media's Converge360 group.

Featured

  • Microsoft Starting To Roll Out New Excel Connected Data Types

    Microsoft on Thursday announced some Excel and Power BI enhancements that add "connected data types" on top of the standard strings and numbers options.

  • Windows 10 Users Getting New Process for Finding Optional Driver Updates

    Accessing Windows 10 drivers classified as "optional updates" will be more of a manual seek-and-install type of experience, starting on Nov. 5, 2020, Microsoft explained in a Wednesday announcement.

  • Microsoft Changes Privacy Platform Name to SmartNoise

    Microsoft Research has changed the name of its "differential privacy" platform from "WhiteNoise" to "SmartNoise," according to a Wednesday announcement.

  • Why Restarting a Failed SCVMM Job Might Be a Bad Idea

    Occasionally, restarting a failed System Center Virtual Machine Manager job can leave your virtualization infrastructure in an unknown state. Here's how to avoid that.

comments powered by Disqus