[ad_1]
Microsoft said that an incident occurred during a DNS migration was causing an interruption of nearly two hours Azure on May 2, between 19:43 and 22:35 UTC.
The global incident has affected a range of Microsoft cloud services, which has resulted in connection issues for major services such as Azure, multiple services under the umbrella Microsoft 365, Dynamics and DevOps.
The incident had repercussions on Azure computing, storage, App Service, Azure AD identity services, and the SQL database.
Microsoft was migrating its legacy domain name system (DNS) to its own hosted Azure DNS, when "some domains for Microsoft services were updated incorrectly," he explains on the page. 39 Azure status history.
Microsoft has updated the page several times during the incident and as the services are being restored.
The company assures customers that none of their DNS records were affected during the event and that the Azure DNS remained in place throughout.
"The problem was only with Microsoft service records," he said, pointing out that it was due to a "name server delegation problem."
One reason for slower than expected recovery time is that affected Microsoft applications and services may have cached the wrong domain registrations, according to Microsoft. These would have been restored when cached information has expired.
The company plans to release a detailed root cause analysis in the next 72 hours.
The state of integrity of the Microsoft 365 service currently reports no problem. However, according to The Register, it was stated yesterday that the relevant services included SharePoint Online, OneDrive for Business, Microsoft Teams, Feed, Power BI, Planner, Forms, PowerApps, Dynamics 365, Intune and Office Licenses.
DNS issues were also causing Azure's global outage in January that had affected the Office 365, Azure and Dynamics 365 services. Microsoft pinned the problem on the managed DNS service of Level 3. And at the end of last year, Azure AD multifactor authentication crash prevented Office 365 users worldwide from connecting to their accounts.
An altogether different global DNS problem also hit Windows 10 users in February. A data corruption issue at an external DNS provider resulted in incorrect DNS entries for Windows Update, preventing Windows 10 users from downloading software and security updates through Windows Update for several days.
The latest Azure crash arrives a few days before the big Microsoft Build Conference for developers, where the main topic should be Azure and AI.
More information about Microsoft and cloud services
[ad_2]
Source link