--- title: Microsoft’s 3 major incidents in 10 days, where did they go wrong? description: Microsoft’s 3 major incidents in 10 days, where did they go wrong? image: https://blog.exigence.io/hubfs/stress-1331259_640.jpg --- ![CORRECT LOGO FOR BLOG](https://blog.exigence.io/hs-fs/hubfs/CORRECT%20LOGO%20FOR%20BLOG.png?width=143&name=CORRECT%20LOGO%20FOR%20BLOG.png "CORRECT LOGO FOR BLOG") - [Home](https://www.exigence.io/) - Solution - [Enterprise IT ops and security](https://www.exigence.io/enterprise-it-ops-security) - [Incident Response Firms](https://www.exigence.io/incident-response-firms) - [MSPs & MSSPs](https://www.exigence.io/msps-mssps) - [Platform](https://www.exigence.io/platform) - [Case Studies](https://www.exigence.io/case-studies) - [McGraw Hill](https://www.exigence.io/case-study-mhe) - [Software Giant](https://www.exigence.io/case-study-software-company) - [Thales](https://www.exigence.io/case-study-thales) - [Financial Solutions Provider](https://www.exigence.io/case-study-financial-solutions-provider) - [DataScan](https://www.exigence.io/case-study-datascan) - Company - [About Us](https://www.exigence.io/about-us) - [Careers](https://www.exigence.io/careers) - [Blog](https://blog.exigence.io/) - [Get in touch](https://www.exigence.io/contact-us) # Blog ![](https://blog.exigence.io/hubfs/Exigence_March2019/image/Blog%20ListingPage-Image.png) - [All Posts](https://blog.exigence.io) - [Tech Ops](https://www.exigence.io/blog/tag/tech-ops) - [Critical Incident Management](https://www.exigence.io/blog/tag/critical-incident-management) # [All Posts](https://blog.exigence.io) Sign Up - [All Posts](https://blog.exigence.io) - [Critical Incident Management](https://blog.exigence.io/tag/critical-incident-management) - [CyberSecurity Incident Response](https://blog.exigence.io/tag/cybersecurity-incident-response) - [Automating Critical Incident Management](https://blog.exigence.io/tag/automating-critical-incident-management) Share Post Share Link Cancel Copy Link ![Noam Morginstin](https://blog.exigence.io/hubfs/Noam%20Pic.jpg) Noam Morginstin Admin Oct 15 5 min read Share Post # Microsoft’s 3 major incidents in 10 days, where did they go wrong? [![stress-1331259_640](https://blog.exigence.io/hs-fs/hubfs/stress-1331259_640.jpg?width=640&name=stress-1331259_640.jpg)](https://blog.exigence.io/)   # **How to aggravate millions of users** Just in case you haven’t heard, last week Microsoft experienced a huge outage that prevented users from accessing its Office 365 cloud-based subscription service which serves [200 million](https://www.zdnet.com/article/microsoft-says-more-than-25-percent-of-office-365-licenses-now-sold-through-microsoft-365/) active monthly users. This latest outage was the third in ten days, causing the company to receive a deluge of customer complaints about a 'something went wrong' message that popped up when they tried to access their accounts. [Downdetector.com](https://downdetector.com/), provider of real-time updates on issues and outages, showed that user reports had spiked at 14:26. And many users even published on various social media platforms the great anger and frustration they have over continued Office 365 outages. *“Microsoft users vented their frustrations on social media as the outage left them unable to send and receive important emails.”* ([CNBC](https://www.cnbc.com/2020/10/01/microsoft-outlook-experiencing-problems-worldwide-.html)) It was only at 14:48, more than twenty minutes later that the Microsoft 365 Status Twitter account even acknowledged the issue. And only at 19:05, four and a half hours since the peak of complaints did the company announce that affected services were back up and running. As noted, unfortunately for Microsoft and users of Office 365, this was the third time in ten days that the service was rendered inaccessible for several hours at a time. Both on September 28th and on October 1st, similar issues had occurred.   # **Three strikes and you’re out?** Needless to say, no company wants to be in this situation, where your service is down for several hours. Clearly, the implications are dire. For, regardless of the cause, whether it’s due to putting [new code into production](https://lightrun.com/debugging/debugging-microservices-in-production-an-overview/), a cyberattack, or an increase in usage – the damage from an outage can be tremendous, impacting customer satisfaction and loyalty, revenues, compliance, and brand equity. When it comes to customer satisfaction, as the stats show, when something goes wrong, your customers will blame you. According to one survey, [66%](https://www.uctoday.com/unified-communications/how-much-would-a-cloud-outage-cost-your-business/) of respondents believe that it’s the responsibility of the service provider to deal with the issue. And if the problem is not dealt with swiftly frustration and risk of attrition will rise. As for cost, in another survey it was found that one hour of downtime can [cost](https://itic-corp.com/blog/2019/05/hourly-downtime-costs-rise-86-of-firms-say-one-hour-of-downtime-costs-300000-34-of-companies-say-one-hour-of-downtime-tops-1million/) most businesses at least $100,000, and for some even between $1- $5million. [![EBOOKDOWNLOAD](https://blog.exigence.io/hs-fs/hubfs/EBOOKDOWNLOAD.png?width=317&name=EBOOKDOWNLOAD.png)](https://info.exigence.io/the-7-key-capabilities-for-gaining-control-command-of-critical-incidents)   # **Acceleration is the name of the game** So, what can organizations and their IT teams do about this? Well, for one – they can’t bank on 100% prevention. Outages are inevitable. There will always be network failures, sudden increases in system and app usage, human error, and software malfunctions. But, whereas incidents are not avoidable, lengthy incident resolution certainly is. In the Microsoft case, even with three incidents in less than two weeks – the way to mitigate the risk and reduce losses is to profoundly accelerate incident resolution. This strategic need becomes all the more critical when we consider that outages are more likely and more frequent today than ever due to the massive mobilization of the workforce to the home following Covid-driven work from home directives. In fact, internet outages have reached an all-time high during the pandemic, with downtime increasing by an astounding [63%](https://www.itpro.co.uk/infrastructure/network-internet/356663/march-saw-more-internet-outages-than-ever-before-says) just in March.   # **Don’t forget to add a good measure of cyberattacks** Though Covid has not only accelerated the rates of outages. It has also prompted a dramatic increase in cyberattacks, with a [50% increase](https://blog.checkpoint.com/2020/10/06/study-global-rise-in-ransomware-attacks/) in the daily average of ransomware attacks, for example, during Q3-2020, compared with the first half of the year. Among the [cybercrime trends](https://www.firstpoint-mg.com/blog/mobile-threats-and-risks-2021-what-mnos-can-do/) that have been noted are a great increase in the proliferation of malware attacks that leverage social engineering to exploit a global pre-occupation with the virus. Furthermore, cybercriminals are also leveraging the [increased](https://blog.checkpoint.com/2020/03/30/covid-19-impact-cyber-criminals-target-zoom-domains/) use of Zoom video conferencing during lockdown to launch phishing attacks.  So, no matter how you look at it – whether through the lens of outages, or through the prism of cyberattacks, no organization can allow itself *not* to expedite as much as possible the resolution of a major incident. This is why it has never been more important to make sure that incident resolution capabilities, processes, and tools are at the top of their game. [![Virtual War Room](https://no-cache.hubspot.com/cta/default/5278914/a7395683-2a53-4a74-a3a7-d684d6e9f07d.png)](https://cta-redirect.hubspot.com/cta/redirect/5278914/a7395683-2a53-4a74-a3a7-d684d6e9f07d)   # **How Exigence can help** Exigence offers a platform for automated incident management and orchestration for profoundly improving resolution capabilities and processes. This platform empowers incident responders with complete command and control and oversight of critical incidents, whether for technology operations, security, or drills, and business continuity tests as well. It enables them with a structured framework for a typically unstructured process, enabling them to orchestrate stakeholders and tools and ensure that everyone is always on the same page and fully up to speed. Exigence automatically notifies and onboards all incident stakeholders, informing them of what type of incident has occurred, which systems have been impacted, and what their role is in the resolution effort. It also automatically opens a conf. call bridge and collaboration channel, so no time is wasted in getting everyone aligned. Then, throughout the incident resolution journey, it automatically updates stakeholders about each status change in accordance with their stake in the incident. And once the incident is resolved the team is notified of incident closure automatically, and incident summaries and root cause analysis reports can be created just by clicking a button.   # **In closing** The mandate to resolve incidents faster than ever is here to stay. However, with automated incident management and orchestration, the burden of speed, clarity, and efficiency can be lifted off the shoulders of those charged with the ever more important job of resolving major incidents. To learn more about how Exigence can help your team profoundly increase the speed and efficacy of incident resolution, we invite you to reach out to us at [info@exigence.io](mailto:info@exigence.io). [![New call-to-action](https://no-cache.hubspot.com/cta/default/5278914/3bca5d96-909f-4490-9cda-2a4b47505f83.png)](https://cta-redirect.hubspot.com/cta/redirect/5278914/3bca5d96-909f-4490-9cda-2a4b47505f83) [Critical Incident Management](https://blog.exigence.io/tag/critical-incident-management)• [major incident management](https://blog.exigence.io/tag/major-incident-management)• [CyberSecurity Incident Response](https://blog.exigence.io/tag/cybersecurity-incident-response)• [Automating Critical Incident Management](https://blog.exigence.io/tag/automating-critical-incident-management) [Critical Incident Management](https://blog.exigence.io/tag/critical-incident-management)• [major incident management](https://blog.exigence.io/tag/major-incident-management)• [CyberSecurity Incident Response](https://blog.exigence.io/tag/cybersecurity-incident-response)• [Automating Critical Incident Management](https://blog.exigence.io/tag/automating-critical-incident-management) Share Link Cancel Copy Link ### Recent Posts [See All](https://blog.exigence.io) [![Global Industrial Leader Coordinates Severity 1 Incidents with Clarity and Speed](https://blog.exigence.io/hubfs/Gemini_Generated_Image_ocux07ocux07ocux.png "Global Industrial Leader Coordinates Severity 1 Incidents with Clarity and Speed")](https://blog.exigence.io/https/www.exigence.io/global-industry-giant) ## [Global Industrial Leader Coordinates Severity 1 Incidents with Clarity and Speed](https://blog.exigence.io/https/www.exigence.io/global-industry-giant) [![From plan to practice to prevail: my conversation with Chris Johnson, host of the MSSP 1337 podcast](https://blog.exigence.io/hubfs/Podcast%20blog%20post%20and%20Linkedin%20image.jpg "From plan to practice to prevail: my conversation with Chris Johnson, host of the MSSP 1337 podcast")](https://blog.exigence.io/from-plan-to-practice-to-prevail-my-conversation-with-chris-johnson-host-of-the-mssp-1337-podcast) ## [From plan to practice to prevail: my conversation with Chris Johnson, host of the MSSP 1337 podcast](https://blog.exigence.io/from-plan-to-practice-to-prevail-my-conversation-with-chris-johnson-host-of-the-mssp-1337-podcast) [![The 6th DORA requirement no one told you about](https://blog.exigence.io/hubfs/DORA.png "The 6th DORA requirement no one told you about")](https://blog.exigence.io/the-6th-dora-requirement-no-one-told-you-about) ## [The 6th DORA requirement no one told you about](https://blog.exigence.io/the-6th-dora-requirement-no-one-told-you-about) ### Take control of your critical incidents Get in touch and get started! [Schedule a Demo](https://calendly.com/exigence/60min?back=1) - © 2017-2020 by Exigence Ltd. - [info@exigence.io](mailto:info@exigence.io?subject=Hey%20there!%20(from%20the%20site)) - [US: +1-877-422-3833](tel:+1-877-422-3833) - [Privacy Policy](https://www.exigence.io/privacy-policy) - [![Twitter](https://blog.exigence.io/hubfs/Exigence_March2019/image/Twitter.png)](https://twitter.com/exigence_ltd) - [![Linkedin](https://blog.exigence.io/hubfs/Exigence_March2019/image/Linkedin.png)](https://www.linkedin.com/company/exigence-ltd-?trk=biz-companies-cym) - [![Twitter](https://blog.exigence.io/hubfs/Exigence_March2019/image/Twitter.png)](https://twitter.com/exigence_ltd) - [![Linkedin](https://blog.exigence.io/hubfs/Exigence_March2019/image/Linkedin.png)](https://www.linkedin.com/company/exigence-ltd-?trk=biz-companies-cym) - [Privacy Policy](https://www.exigence.io/privacy-policy) - [info@exigence.io](mailto:info@exigence.io?subject=Hey%20there!%20(from%20the%20site)) - [US: +1-877-422-3833](tel:+1-877-422-3833) - © 2017-2020 by Exigence Ltd.