Puzzle Technology
Back to all services
MA

Microsoft Azure

Microsoft · Cloud

OK
Status Page
https://status.azure.com/

View Microsoft Status History & Stats

Last 30 Days
2 incidents

Current state: Operational

Recent incidents

    • resolved

      Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

    • investigating

      We are aware of an issue affecting Azure Data Factory in UK South, where a subset of customers may experience failures, delays, or timeouts with pipeline and activity runs, integration runtime management, or authoring operations. Our engineers are actively working to determine the cause and impact. As a workaround, customers are advised to cancel and retry affected runs that fail, time out, or remain in progress longer than expected.

    • investigating

      We are aware of an issue affecting Azure Data Factory in UK South, where a subset of customers may experience failures, delays, or timeouts with pipeline and activity runs, integration runtime management, or authoring operations. Our engineers are actively working to determine the cause and impact.As a workaround, customers are advised to cancel and retry affected runs that fail, time out, or remain in progress longer than expected

    • investigating

      We are aware of an issue affecting Azure Data Factory in UK South, where a subset of customers may experience failures, delays, or timeouts when running pipelines and activities, managing integration runtimes, or performing authoring operations. Our engineers are actively investigating the cause and impact . Workaround: Customers are advised to cancel and retry affected pipeline or activity runs that fail, time out, or remain in progress longer than expected. Further updates will be provided as more information becomes available.

    • resolved

      Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

    • investigating

      We are aware of an issue affecting Azure Data Factory in UK South, where a subset of customers may experience failures, delays, or timeouts when running pipelines and activities, managing integration runtimes, or performing authoring operations. Our engineers are actively investigating the cause and impact . Workaround: Customers are advised to cancel and retry affected pipeline or activity runs that fail, time out, or remain in progress longer than expected. Further updates will be provided as more information becomes available.

    • investigating

      Azure Data Factory issues in UK SouthWe are aware of an issue affecting Azure Data Factory in UK South, where a subset of customers may experience failures, delays, or timeouts when running pipelines and activities, managing integration runtimes, or performing authoring operations. Our engineers are actively investigating the cause and impact.Workaround: Customers are advised to cancel and retry affected pipeline or activity runs that fail, time out, or remain in progress longer than expected.Further updates will be provided as more information becomes available.

  3. Active - Azure ExpressRoute Gateway service impacting event in multiple Azure Regions

    Major · 30 Sept 2026, 21:30 · resolved about 1 month ago

    • resolved

      Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

    • investigating

      We are investigating an alert for Azure ExpressRoute Gateway in multiple Azure regions, also affecting dependent services. We will provide more information as it becomes available.

    • investigating

      We are investigating an alert for Azure ExpressRoute Gateway in multiple Azure regions. We will provide more information as it becomes available.

  4. Active - Multiple services experiencing connectivity issues in multiple regions

    Major · 30 Sept 2026, 21:30 · resolved about 1 month ago

    • resolved

      Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

    • investigating

      Starting at 20:30 UTC on 30 September 2026, customers using gateway services may be experiencing degraded or interrupted network connectivity. Customers may see gateways failing to load in the Azure Portal, and may also be experiencing failures or delays with network management operations across the following impacted services: ExpressRoute Gateways Azure Firewall Application Gateways / Web Application Firewall VPN Gateways Azure VMWare Solution (AVS) Current status: The vast majority of previously-impacted regions are showing signs of recovery, we are working to apply configuration changes that were successful in other regions to the remaining five regions: France Central, North Europe, Southeast Asia, UK South, and UK West. Our investigation has identified a correlation between the timing of this incident and infrastructure operating system servicing activity, which has since been paused. The underlying failure mechanism has not yet been confirmed, and we continue to investigate why network service instances became unhealthy and why recovery behavior differed across services. We continue to validate recovery - region by region, and service by service. We will provide additional information within the next 60 minutes, or sooner if events warrant.

    • investigating

      Starting at 20:30 UTC on 30 September 2026, customers using ExpressRoute and VPN Gateway may have experienced degraded or interrupted network connectivity. Customers may also experience failures or delays with network management operations across impacted services. Azure Firewall data-plane traffic is not currently known to be impacted. However, customers in affected regions may experience failures or delays when performing service management operations, including creating or updating Azure Firewall resources and updating firewall rules. As of 22:35 UTC on 30 September 2026, ExpressRoute gateways are showing significant recovery, and we continue to monitor service health to validate that recovery is sustained. We have paused infrastructure servicing activity associated with the onset of this event, preventing additional resources from entering the affected workflow. Some supporting network management components have not recovered automatically and continue to affect management operations and the recovery of dependent resources in some regions. Engineering teams have paused the infrastructure servicing activity associated with the onset of this event. We are restoring the affected network management components, reducing load to stabilize the service, and addressing constraints affecting our ability to add resources. We continue to validate recovery region by region and service by service. Our investigation has identified a correlation between the timing of this event and infrastructure operating system servicing activity. The underlying failure mechanism has not yet been confirmed, and we continue to investigate why network service instances became unhealthy and why recovery behavior differed across services. We will provide additional information within the next 30 minutes, or sooner if events warrant.

    • investigating

      Starting at 20:30 UTC on 30 September 2026, customers using ExpressRoute and VPN Gateway may have experienced degraded or interrupted network connectivity. Customers may also experience failures or delays with some network management operations. Current status: ExpressRoute gateways are showing significant recovery as of 22:35 UTC, and we continue to monitor service health to validate that recovery is sustained. We have paused infrastructure servicing activity associated with the onset of this event, preventing additional resources from entering the affected workflow. For VPN Gateway, some affected gateways experienced reduced redundancy or loss of connectivity, and recovery continues to be monitored. Some supporting network management components have not recovered automatically and continue to contribute to management operation failures in affected regions. Engineering teams are actively restoring these components using healthy instances where available. Our investigation has identified a correlation between the timing of this event and infrastructure operating system servicing activity. The underlying failure mechanism has not yet been confirmed, and we continue to investigate why some network service instances became unhealthy and why recovery behavior differed across services. We will provide additional information within the next 30 minutes, or sooner if events warrant.

    • investigating

      Starting at 20:30 UTC on 30 September 2026, customers using ExpressRoute and/or VPN Gateway may experience degraded or interrupted network connectivity. Customers may also experience failures or delays when performing some network management operations. Current status: We have paused the infrastructure servicing activity associated with the onset of this event, preventing additional resources from entering the affected servicing workflow. We are seeing continued recovery across impacted ExpressRoute gateways and are monitoring this recovery to confirm that it remains durable. For VPN Gateway, some affected gateways have experienced reduced redundancy rather than a complete loss of connectivity. Recovery continues to be monitored. Some supporting network management components have not recovered automatically and are contributing to management operation failures in a subset of affected regions. Engineering teams are actively restoring these components using alternate healthy instances where available. Our investigation continues to show a correlation between this event and infrastructure operating system servicing activity. However, the underlying failure mechanism has not yet been confirmed. We are investigating why some network service instances became unhealthy and why recovery behavior has differed between services. We will provide additional information within the next 30 minutes, or sooner if events warrant.

    • resolved

      Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

    • investigating

      Impact statement: Starting at 20:30 UTC on 30 September 2026, customers using ExpressRoute and/or VPN Gateway may experience degraded or interrupted connectivity. We are also seeing impact to components responsible for managing network gateways, which may affect some management operations. Current status: Our investigation has identified a correlation between the onset of impact and infrastructure operating system servicing activity. During this activity, some network gateway instances became unhealthy or temporarily unavailable. We have paused the associated operating system servicing activity, preventing additional resources from entering the affected servicing workflow. Since taking this action, we are seeing mitigation progress across affected resources, including recovery of impacted ExpressRoute gateways. Affected resources may require time to recover from servicing activity that was already in progress when the pause was applied. Based on the recovery observed so far, we expect recovery to continue and to be durable as the remaining affected resources complete this process. Some supporting network management components are recovering differently, and our engineering teams are continuing targeted restoration work for resources that have not recovered automatically. Our current working hypothesis remains that infrastructure operating system servicing triggered an unexpected condition in some network service instances. We have not yet confirmed the underlying failure mechanism and are continuing to investigate why affected instances became unhealthy and why recovery behavior differs between services. We are closely monitoring recovery across the affected services and regions, validating that recovery is sustained, and taking additional restoration actions where necessary. We will provide additional information within the next 30 minutes or as events warrant.

    • investigating

      Starting at 20:30 UTC on 30 September 2026, customers using ExpressRoute and/or Azure VPN Gateway may experience degraded or interrupted connectivity. We are also seeing impact to components responsible for managing network gateways, which may affect some management operations. Our investigation has identified a correlation between the onset of impact and infrastructure ‘operating system’ servicing activity. During this activity, some network gateway instances became unhealthy or temporarily unavailable. We have observed different recovery behavior across the affected services. Many impacted ExpressRoute gateways are recovering as the servicing operation completes. However, some supporting management components have not recovered automatically, and we are actively working to restore those components. Our current working hypothesis is that infrastructure operating system servicing is triggering an unexpected condition in some network service instances. We have not yet confirmed the underlying failure mechanism and are continuing to investigate why affected instances became unhealthy and why recovery behavior differs between services. We have paused further operating system servicing associated with this activity to prevent new instances from entering the affected servicing workflow. In parallel, our engineering teams are restoring network management components that have not recovered automatically as well as evaluating additional recovery actions for resources that remain unhealthy. We are continuing to monitor recovery across the affected services and will provide additional information within the next 30 minutes or as events warrant.

    • resolved

      Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

    • investigating

      We are investigating an issue affecting Azure OpenAI and Foundry agent services in the Sweden Central region. Impacted customers may experience intermittent errors when making service requests. We are investigating the underlying issue and exploring mitigation options to restore normal service performance. Our analysis remains ongoing, and we are closely monitoring service health while continuing our investigation. We will provide additional information as it becomes available.

    • resolved

      Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

    • investigating

      Impact Statement: Starting at 10:00 UTC on 29 September 2026, a subset of customers using OpenAI Service, Foundry Agent Service, Foundry Models, and Cognitive Services, in Sweden Central may experience intermittent request failures, increased latency, and HTTP 5XX error codes when submitting requests to affected models and APIs hosted in this region. Current Status: Currently we are monitoring improvements in the overall experience. Initial findings indicate that a backend service which is relied on to retrieve metadata information when managing requests for this region, was experiencing timeouts when reading from dependent database and caching layers. Additionally, some instances for this backend service became unhealthy and experienced restarts. As a result, requests that depend on these processes were delayed or failed intermittently. We have taken steps to further scale instances for the backend service, and reconfigured system processes as mitigation steps. Queued requests have been processed for a period of time to confirm improvements to overall service health. We are continuing to investigate the health of supporting platform infrastructure and system processes that may have impacted these requests and the backend service. The next update will be provided within 60 minutes, or as events warrant.

    • investigating

      Impact Statement: Starting at 10:00 UTC on 29 September 2026, a subset of customers using OpenAI Service, Foundry Agent Service, Foundry Models, and Cognitive Services, in Sweden Central may experience intermittent request failures, increased latency, and HTTP 5XX error codes when submitting requests to affected models and APIs hosted in this region. Current Status: Currently we are monitoring improvements in the overall experience. Initial findings indicate that a backend service which is relied on to retrieve metadata information when managing requests for this region, was experiencing timeouts when reading from dependent database and caching layers. As a result, requests that depend on these processes were delayed or failed intermittently. Queued requests are being processed. We are continuing to investigate the health of supporting platform infrastructure or system processes that may impact these requests. The next update will be provided within 60 minutes, or as events warrant.

    • resolved

      Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

    • investigating

      Impact Statement: Starting at 10:00 UTC on 29 September 2026, a subset of customers using OpenAI Service, Foundry Agent Service, Foundry Models, and Cognitive Services, in Sweden Central may experience intermittent request failures, increased latency, and HTTP 5XX error codes when submitting requests to affected models and APIs hosted in this region. Current Status: Currently we are monitoring improvements in the overall experience. Initial findings indicate that a backend service which is relied on to retrieve metadata information when managing requests for this region, was experiencing timeouts when reading from dependent database and caching layers. As a result, requests that depend on these processes were delayed or failed intermittently. Queued requests are being processed. We are continuing to investigate the health of supporting platform infrastructure or system processes that may impact these requests. The next update will be provided within 60 minutes, or as events warrant.

    • investigating

      Impact Statement: Starting at 10:00 UTC on 29 September 2026, a subset of customers using OpenAI Service, Foundry Agent Service, Foundry Models, and Cognitive Services, in Sweden Central may experience intermittent request failures, increased latency, and HTTP 5XX error codes when submitting requests to affected models and APIs hosted in this region. Current Status: Currently we are monitoring improvements in the overall experience. Our investigation is focused on observed instability and dependency connectivity timeouts for backend services that are relied on. Multiple mitigation workstreams are underway, and we are closely monitoring service health to assess their effectiveness and determine the most effective path toward full recovery. The next update will be provided within 60 minutes, or sooner if significant developments occur.

    • investigating

      We continue to investigate intermittent request failures, increased latency, and HTTP 5XX error codes affecting a subset of customers using Azure OpenAI Service, Azure AI Foundry Agent Service, Azure AI Foundry Models, and Azure AI Cognitive Services in Sweden Central. Our investigation is focused on the observed service instability and dependency connectivity timeouts. Multiple mitigation workstreams are underway, and we are closely monitoring service health to assess their effectiveness and determine the most effective path toward full recovery. We will provide additional information as it becomes available.

    • investigating

      We are investigating an issue affecting Azure OpenAI Service, Azure AI Foundry Agent Service, Azure AI Foundry Models, and Azure AI Cognitive Services in the Sweden Central region. Impacted customers may experience intermittent request failures, increased latency and HTTP 5XX error codes when making service requests. We are investigating the underlying issue and exploring mitigation options to restore normal service performance. Our analysis remains ongoing, and we are closely monitoring service health while continuing our investigation. We will provide additional information as it becomes available.

  9. Active - Network Infrastructure impacting event in East US

    Major · 3 Sept 2026, 11:03 · resolved 2 months ago

    • resolved

      Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

    • investigating

      We are investigating an issue affecting a subset of infrastructure within the East US region. Customers may experience service degradation for dependent Azure services. Our teams are actively investigating the cause and working to restore normal operations. More information will be provided as it becomes available.

  10. Active -Multiple Service impacted affecting West US Regions

    Major · 28 Aug 2026, 07:19 · resolved 2 months ago

    • resolved

      Auto-resolved by the status page: the vendor stopped reporting this incident in their feed.

    • investigating

      We are investigating an issue impacting multiple Azure services in the West US regions. Engineering teams are actively assessing the scope and working to mitigate customer impact. Further updates will be shared as they become available