Azure status

Note: During this incident, azure status, as a result of a delay in determining exactly which customer subscriptions were impacted, we chose to communicate via the public Azure Status page.

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. After further investigation, we determined that an issue impacting the Azure Resource Manager ARM service resulted in downstream impact for various Azure services.

Azure status

.

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. On 21 Januaryazure status, an internal maintenance process made azure status configuration change to an internal tenant which was enrolled in this preview.

.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. This article describes the information you can find on the Status Page and how you can subscribe to service notifications. You can easily view the status of a specific service by viewing the status page. You can also subscribe to status updates on individual service components. This sends an alert whenever the status of the service you are subscribed to changes. The status page is broken down by Azure region. Select one of the four main geos Americas , Europe , Asia Pacific , or Middle East and Africa to display all of the active regions in the selected geo.

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

Hometalk com

Estimated completion: February We are improving monitoring signals on role crashes for reduced time spent on identifying the cause s , and for earlier detection of availability impact. 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. Status History. Customer impact started to subside and ARG calls were successfully passing updated resource information. Eventually this led to an overwhelming of the remaining ARM nodes, which created a negative feedback loop increased load resulted in increased timeouts, leading to increased retries and a corresponding further increase in load and led to a rapid drop in availability. 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. 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. Estimated completion: March From June 1, , this includes RCAs for broad issues as described in our documentation. 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. Unbeknownst to us, this preview feature of the ARM CAE implementation contained a latent code defect that caused issues when authentication to Entra failed. Estimated completion: February Our ARM team will audit dependencies in role startup logic to de-risk scenarios like this one. How did we respond?

The Hybrid Connection Debug utility is provided to perform captures and troubleshooting of issues with the Hybrid Connection Manager.

January Status History. 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. Completed We have offboarded all tenants from the CAE private preview, as a precaution. ARM nodes restart periodically by design, to account for automated recovery from transient changes in the underlying platform, and to protect against accidental resource exhaustion such as memory leaks. On 21 January , an internal maintenance process made a configuration change to an internal tenant which was enrolled in this preview. In addition, several internal offerings depend on ARM to support on-demand capacity and configuration changes, leading to degradation and failure when ARM was unable to process their requests. On 21 January , an internal maintenance process made a configuration change to an internal tenant which was enrolled in this preview. This feature is to support continuous access evaluation for ARM, and was only enabled for a small set of tenants and private preview customers. Sorry for the inconvenience, but something went wrong.