###Update on 28th November 2018
The Engineering team has fixed the issue and Identified the Preliminary issue.
According to the official Azure Status site the reason was "a DNS issue triggered a large number of sign-in requests to fail, which resulted in backend infrastructure becoming unhealthy. "
MS also told that they have fixed the issue and observed a decrease in the MFA failure count. We are still waiting for the RCA..
==========================================
27th November 2018
Azure MFA is failing again today 27th November 2018 with the Error message " Sorry, we're having trouble with verifying your account. Please try again"
{no Sno SMS sent, no push notification to the app, TOTP code doesn’t work)MS sent, no push notification to the app, TOTP code doesn’t work}
Azure Site says all the regions of America, APAC, and Europe is affected.
Outage details in Azure Site :
Starting at 14:25 UTC on 27 Nov 2018 a subset of customers using Multi-Factor Authentication may experience intermittent issues signing into Azure resources, such as Azure Active Directory, when Multi-Factor Authentication is required by policy. Impacted customers may encounter timeout errors. Engineers are aware of this issue and are actively investigating mitigation options. The next update will be provided in 60 minutes, or as events warrant.
The MS team is working on this.
The regions that are affected are,
Oregon
North Virginia
Dublin
Tokyo
Tokyo
BrazilNorth EuropeSouth East AsiaWest Europe SydneyDallasTXHong KongHong KongSouth Central USEast US2SingaporeNorth Central USFrankfurtNorth CaliforniaChicagoSydneyNorth VirginiaEast JapanSouth India
we are following the MS Internal Sites. An Incident with Priority has been raised and MS team is working on this.
============================================
###Update on 28th November 2018
The Engineering team has fixed the issue and Identified the Preliminary issue.
According to the official Azure Status site the reason was "a DNS issue triggered a large number of sign-in requests to fail, which resulted in backend infrastructure becoming unhealthy. "
MS also told that they have fixed the issue and observed a decrease in the MFA failure count. We are still waiting for the RCA..
============================================
###Update on 28th November 2018
The Engineering team has fixed the issue and Identified the Preliminary issue.
According to the official Azure Status site the reason was "a DNS issue triggered a large number of sign-in requests to fail, which resulted in backend infrastructure becoming unhealthy. "
MS also told that they have fixed the issue and observed a decrease in the MFA failure count. We are still waiting for the RCA..
No comments:
Post a Comment