Azure status

Note: During this incident, as a result of a delay in azure status exactly which customer subscriptions were impacted, we chose to communicate via the public Azure Status page. As described in our documentation, public PIR postings on this page are reserved for 'scenario 1' incidents - typically broadly impacting incidents across entire zones or regions, azure status, or even multiple zones or regions.

Note: During this incident, as a result of a delay in determining exactly which customer subscriptions were impacted, we chose to communicate via the public Azure Status page. As described in our documentation, public PIR postings on this page are reserved for 'scenario 1' incidents - typically broadly impacting incidents across entire zones or regions, or even multiple zones or regions. Summary of Impact: Between and UTC on 07 Feb first occurrence , customers attempting to view their resources through the Azure Portal may have experienced latency and delays. Subsequently, impact was experienced between and UTC on 08 Feb second occurrence , the issue re-occurred with impact experienced in customer locations across Europe leveraging Azure services. Preliminary Root Cause: External reports alerted us to higher-than-expected latency and delays in the Azure Portal.

Azure status

.

Mitigation: During the first occurrence, we initially suspected an issue with Azure Resource Graph ARG and reverted a recent deployment as this was a potential root cause, azure status.

.

Impact Statement: Starting as early as UTC on 07 Feb , customers accessing their resources through the Azure Portal may experience latency and delays viewing their resources. Impact would be mostly seen in West Europe. Current Status: We identified a potential issue with Azure Resource Graph which has now been mitigated. We are now monitoring the health of our resources to validate recovery. The next update will be provided in 60 minutes, or as events warrant. This message was last updated at UTC on 07 February Update - Mitigation is being applied and customers may start to notice service recovery. Sweden Central region is fully recovered. We are expecting full recovery in approximately an hour. Also, the downstream impact to Purview service is completely recovered across all impacted regions.

Azure status

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. We respond quickly during performance slowdowns and stability issues. Our top priority is to communicate the incident status and our next steps to mitigate the issue. Check the status of our services through the Azure DevOps Services status portal. Our Customer Impact Assessment CIA is modeled after our availability model, which measures real customer experiences representing both reliability and performance. Many of the events we post are based on the CIA.

Waxing studio near me

Completed Our Key Vault team has fixed the code that resulted in applications crashing when they were unable to refresh their RBAC caches. How are we making incidents like this less likely or less impactful? Completed We are gradually rolling out a change to proceed with node restart when a tenant-specific call fails. Completed Our Entra team improved the rollout of that type of per-tenant configuration change to wait for multiple input signals, including from canary regions. How did we respond? Estimated completion: February Our ARM team will audit dependencies in role startup logic to de-risk scenarios like this one. How did we respond? While impact for the first occurrence was focused on West Europe, the second occurrence was reported across European regions including West Europe. Please try refreshing the page. We mitigated by making a configuration change to disable the feature.

Note: During this incident, as a result of a delay in determining exactly which customer subscriptions were impacted, we chose to communicate via the public Azure Status page. As described in our documentation, public PIR postings on this page are reserved for 'scenario 1' incidents - typically broadly impacting incidents across entire zones or regions, or even multiple zones or regions. Summary of Impact: Between and UTC on 07 Feb first occurrence , customers attempting to view their resources through the Azure Portal may have experienced latency and delays.

Sorry for the inconvenience, but something went wrong. Unbeknownst to us, this preview feature of the ARM CAE implementation contained a latent code defect that caused issues when authentication to Entra failed. At UTC, our monitoring detected a decrease in availability, and we began an investigation. Estimated completion: March This page contains root cause analyses RCAs of previous service issues, each retained for 5 years. Because most of this traffic originated from trusted internal systems, by default we allowed it to bypass throughput restrictions which would have normally throttled such traffic. At UTC, our monitoring detected a decrease in availability, and we began an investigation. Please try refreshing the page. Estimated completion: February Finally, our Key Vault team are adding better fault injection tests and detection logic for RBAC downstream dependencies. Note: During this incident, as a result of a delay in determining exactly which customer subscriptions were impacted, we chose to communicate via the public Azure Status page.