![microsoft word print comments only microsoft word print comments only](http://photos.demandstudios.com/getty/article/129/135/87700197_XS.jpg)
"Outages sit alongside unpredictable billing, complex services, and other issues that shackle users," Boost said. He suggested that the cloud services industries could do a lot better than they have been doing on a number of fronts. "The assumption that brand familiarity and scale alone are enough to maintain uptime is continually challenged by outages of this kind."īoost added that complexity just increases with hyperscale cloud service providers, such as Microsoft, "where the deployment of a storage device caused services used by billions across the globe to be unusable." "Last night's major Microsoft 365 and Teams outage is a reminder of the fallibility of even the largest cloud providers," Boost said. Microsoft's service outage elicited a comment from Mark Boost, CEO of Civo, a U.K.-based provider of managed Kubernetes services, who suggested via e-mail that big cloud service providers, such as Microsoft, don't offer organizations any better assurances of stability.
![microsoft word print comments only microsoft word print comments only](https://howtech.tv/wp-content/images/001496/2.jpg)
Moreover, they have to apply for the service credit, as it's not automatically applied. Based on it, organizations can only get a service-time credit in compensation for any downtime. Microsoft does have a nuanced service level agreement associated with its cloud services.
![microsoft word print comments only microsoft word print comments only](https://mac-cdn.softpedia.com/screenshots/Word-Document-Writer-Pro_3.jpg)
Places such as Hong Kong and Eastern Australia also may have been affected by the Teams outage, based on comments found in Microsoft's Twitter announcement. Heatmap of the Microsoft Teams outage on July 20 (source: ). users in Los Angeles, Dallas and New York City (see chart): Figure 2. However, per, it seems to have mostly affected U.S. Microsoft didn't indicate in its public Twitter announcements where the outages took place. Graph of complaints about the Microsoft Teams service on July 20 (source: ). on July 20, which tapered toward zero at around 11:00 p.m. It's based on complaints recorded by, which showed a spike in Microsoft Teams complaints starting at about 6:00 p.m. The time estimate of six hours of downtime for Teams and other services is just a guess, as Microsoft didn't offer a chronology. The inability for administrators to see information about service downtimes has been a recurring issue associated with Microsoft services over the years, and it continued in this case. Even those IT pros may have been thwarted, as Microsoft also admitted that "some users have reported that they are unable to access the admin center to view updates." Both venues, though, are just accessible to IT administrators of Microsoft 365 services. Microsoft referred people seeking further information on the outage to its Office status portal ( ), or to messages in its Message Center. The July 20 outage was briefly addressed publicly by Microsoft in this Twitter post series, which suggested that it occurred because of "a broken connection to an internal storage service." The outage affected "multiple Microsoft 365 services with Teams integration, such as Microsoft Word, Office Online and SharePoint Online."
#Microsoft word print comments only update
Update 7/22:Įxoprise, a company that offers performance-monitoring solutions to detect service outages, estimated that the July 20 Microsoft Teams outage lasted three hours, per Microsoft Teams and other Microsoft 365 apps went down for some users on Wednesday night, lasting maybe six hours.