Microsoft Outage History

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.

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.

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

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.

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.

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

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

We have observed recovery for a portion of the infrastructure affected by this issue within the Southeast Asia region. While many impacted services and resources have recovered, a subset of customers may continue to experience connectivity issues or service degradation for dependent Azure services. Engineers are actively working to restore the remaining impacted infrastructure and validate full service recovery.More information will be provided as it becomes available.

We are aware of an issue affecting access to the Azure portal in the Australia regions. Our engineers are actively investigating the cause and impact. Further updates will be provided as more information becomes available.

User impact: Users may be unable to send new messages in Microsoft Teams Free. Current status: We're reviewing scenario telemetry logs to determine why users may be unable to send messages after a recipient of a new chat request accepts in Microsoft Teams Free. Next update by: Tuesday, July 28, 2026, at 6:30 PM UTC

User impact: Users may be unable to send new messages in Microsoft Teams Free. Current status: We've identified that the process which should occur when a user accepts a new chat isn't trigger as expected. We're continuing to review the scenario telemetry logs to identify why this process isn't completing to determine the root cause and a strategy that remediates impact. Next update by: Tuesday, July 28, 2026, at 8:30 PM UTC

User impact: Users may be unable to send new messages in Microsoft Teams Free. Current status: Our review of the scenario telemetry logs is taking longer than anticipated, but we're continuing to make progress in understanding the root cause and developing a strategy that remediates impact. Next update by: Wednesday, July 29, 2026, at 1:00 AM UTC

User impact: Users may be unable to send new messages in Microsoft Teams Free. Current status: Current status: We’ve made changes to improve background processing and confirmed through internal monitoring that the impacted scenario is recovering. We’re continuing to monitor the recovery progress to confirm the issue is fully resolved. Next update by: Wednesday, July 29, 2026, at 10:00 AM UTC

We are investigating a networking issue affecting connectivity to Azure services in the West US region. Impacted customers may experience intermittent connectivity failures, increased latency, or difficulty accessing Azure services. Customers with traffic traversing the West US region may also experience downstream impact. We are exploring mitigation options on affected network devices. Early indications suggest the issue is related to network traffic flow through the impacted infrastructure; however our analysis remains ongoing. We are closely monitoring traffic while continuing our investigation. We will provide additional information as it becomes available.

GitHub Enterprise Cloud with Data Residency is experiencing a service outage impacting all services, issue identified and mitigation in progress. For details please go here: : https://us.githubstatus.com/posts/details/PBJ0QTY

User impact: Users are experiencing issues in the service. Current status: We're investigating a potential issue with the Microsoft Copilot for Microsoft 365 and are checking for impact to your organization. We'll provide an update within 30 minutes.

User impact: Users may be unable to access or sign in to Microsoft Teams Free on iOS devices. Current status: We're investigating a potential Microsoft Teams Free issue in which users may be unable to access or sign in to the service on iOS devices and will provide an update in 30 minutes.

User impact: Users may be unable to access or sign in to Microsoft Teams Free on iOS or Android mobile devices. Current status: We've determined that this issue is due to a recent change that included a reference to a deprecated token for mobile devices. We're reverting this offending change to mitigate impact. Start time: Thursday, June 25, 2026, at 7:00 PM UTC Next update by: Saturday, June 27, 2026, at 1:30 AM UTC

Impact Statement: Starting at 21:45 UTC on 15 June 2026, a subset of Azure customers leveraging services which depend upon MCR (Microsoft Container Registry) for storing images may experience 401 authentication errors for requests attempting to pull Microsoft images from mcr.microsoft.com.Current Status: We detected this issue via internal service monitoring upon identifying a spike of 401 errors. We’ve identified a potential underlying factor to be a recent update which introduced a code regression, and we've completed roll out of a hotfix to address the code regression and mitigate impact for affected customers. We are closely monitoring internal telemetry to validate full mitigation and prevent further occurrences. The next update will be provided within 60 minutes, or as events warrant.

We are actively investigating customer alerts of 401 authentication errors when pulling images from mcr.microsoft.com. We’ve identified a potential underlying factor related to a recent update made to a backed service and we are actively working on determining mitigation workstreams. More information will be provided shortly.

User impact: We don't have details on impact yet. We're seeing an increase in user reported issues above our alerting threshold. Current status: We are reviewing service telemetry and available information to determine if there is an issue happening and we'll update this message shortly with our latest findings. This communication serves as a preliminary notification about a potential issue affecting your service.