The recent D365 outage had a ripple effect on global Microsoft services, causing disruptions to many businesses and organizations.
Microsoft's Dynamics 365 service was experiencing issues, affecting users worldwide.
The outage started on a Tuesday morning and lasted for several hours, impacting many customers.
Many businesses rely on Dynamics 365 for their daily operations, making the outage particularly inconvenient.
Microsoft's status page reported the outage, providing updates to affected customers.
The company's support team worked to resolve the issue as quickly as possible.
Microsoft's Dynamics 365 service provides a range of business applications, including customer service and sales tools.
These applications are used by businesses of all sizes, making the outage a significant concern.
A fresh viewpoint: Rate Making
Causes and Prevention
Microsoft's own chatbot, Copilot, recommends treating configuration changes with the same rigor as code deployments. This means a misstep can cause outages, security vulnerabilities, or performance degradation.
A local or staging environment validation is a crucial step before deploying a configuration change to production. Microsoft's chatbot suggests this as a best practice.
Recommended read: Configuration Odoo
The company has a history of configuration changes causing problems, including breaking the web version of Outlook earlier this year. This incident highlights the importance of thorough testing and validation.
Microsoft has acknowledged the need to review and improve its testing and validation processes. The company's "Next steps" include further reviewing these processes to prevent similar incidents in the future.
A configuration change was made that caused an outage, affecting North American users' access to Microsoft 365. The company has not responded to questions about the specific change made.
For more insights, see: Software Testing Outsourcing
Impact and History
The d365 outage has had a significant impact on businesses that rely on the platform. In 2020, Microsoft reported a global outage that affected thousands of customers, causing estimated losses of over $1 billion.
The d365 outage has a long history, with the first reported outage occurring in 2018. This incident lasted for several hours and affected users in multiple regions.
Worth a look: The Importer Reported a Generic Error
Microsoft has made efforts to improve the reliability of d365, but outages still occur. According to a 2020 report, the average duration of a d365 outage is around 2 hours.
The d365 outage has also led to changes in Microsoft's maintenance policies. The company now provides more advance notice of scheduled maintenance, allowing customers to prepare for potential outages.
Microsoft's efforts to improve d365's reliability have been ongoing for years. In 2019, the company announced plans to invest $1 billion in improving the platform's performance and availability.
Recommended read: Does Insurance Cover Power Outage
Global Microsoft Outage Disrupts Services
A global Microsoft outage disrupted services on July 30, 2024, affecting millions of users worldwide. This was the second major outage in two weeks, causing concerns about the reliability of Microsoft's infrastructure.
The nine-hour outage was caused by a distributed denial-of-service (DDoS) attack, which triggered an error in Microsoft's defense mechanisms, amplifying the impact. This was not the initial reason given by Microsoft, which blamed an "unexpected usage spike" for the issue.
Microsoft Entra, some Microsoft 365, and Microsoft Purview services, as well as various Azure services, were impacted by the outage. Users experienced difficulties accessing emails and issues with scheduled calendar invitations.
The company implemented networking configuration changes to support their DDoS protection efforts and performed failovers to alternate networking paths to restore services. By 2:54 PM ET on July 30, the vast majority of services were fully restored.
Featured Images: pexels.com
