Warn

Azure

Impact Statement: As early as 22:00 UTC on 08 Jan 2025, we noticed a partial impact to some of the Azure Services in East US 2 due to a configuration change in a regional networking service. This configuration change caused an inconsistent service state. This may have resulted in intermittent Virtual Machine connectivity issues, failures in allocating resources or communicating with resources in the region. The services impacted include Azure Databricks, Azure Container Apps, Azure Function Apps, Azure App Service, SQL Managed Instances, Azure Data Factory, Azure Container Instances, PowerBI, VMSS, PostgreSQL flexible servers, and additional services. Customers using resources with Private Endpoint Network Security Groups communicating with other services would also be impacted. The impact is limited to a single zone in the East US 2 region. No other regions are impacted by this issue. Current Status: As early as 22:00 UTC on 08 Jan 2025, service monitoring alerted us to a networking issue in East US 2 impacting multiple services. As part of the investigation, it was identified that a network configuration issue in one of the zones resulted in three of the Storage partitions going unhealthy. As an immediate remediation measure, traffic was re-routed away from the impacted zone, which brought some relief to the non-zonal services, and helped with newer allocations.  Please also be aware that services that sent zonal requests to the impacted zone remained unhealthy. Some of the impacted services initiated their own Disaster Recovery options to help mitigate some of the impact being seen. Additional workstreams to rehydrate the impacted zone by bringing the impacted partitions back to a healthy state are continuing. While we encountered some challenges which required more time than expected to step through the validation process of this fix, the mitigation workstream is progressing as expected. Two of the three impacted partitions are back online. We will continue to monitor the health of these partitions, in parallel to bringing the final partition back to a healthy state. For customers impacted due to Private Link, a patch was applied, and we confirm dependent services should be available. We will continue to share more details on our progress in the next update. We continue to advise customers to execute Disaster Recovery to expedite recovery of their impacted services. Customers that have already failed out of the region should not fail back until this incident is fully mitigated. The next update will be provided in 1 hour, or as events warrant. This message was last updated at 14:36 UTC on 10 January 2025

Last update on Jan 10, 2025 5:23 PM

Warn

Microsoft Teams

Title: Some users may be unable to launch Microsoft Teams on Mac devices post auto-update User impact: Users may be unable to launch Microsoft Teams on Mac devices post auto-update. More info: Some users may receive a popup stating "The application bundle is corrupted". Users can run the application directly from the applications folder and ignore this popup to avoid this issue. Users can also delete the application bundle from the applications folder and install Microsoft Teams again to also resolve impact. Impact is specific to Microsoft Teams for Mac OS versions 13.7.2, 14.7.2, and 15.2. Current status: Our automated monitoring services notified us of an issue where users on Microsoft Teams for Mac OS versions 13.7.2, 14.7.2, and 15.2 may be unable to launch the desktop client. We've determined that a third-party update contains a code error that's resulting in auto-updates to Microsoft Teams for Mac to become corrupted. We're working with our third-party partners to resolve the issue, along with pausing all updates for Mac users to prevent the issue from propagating further. Scope of impact: This issue can potentially affect any user who was automatically updated to Microsoft Teams for Mac OS versions 13.7.2, 14.7.2, and 15.2. Start time: Wednesday, December 11, 2024, at 12:00 AM UTC Root cause: A third-party update contains a code error that’s resulting in auto-updates to Microsoft Teams for Mac to become corrupted. Next update by: Thursday, January 9, 2025, at 10:00 AM UTC

Last update on Jan 10, 2025 5:23 PM

Warn

Red Canary

Identified - We are tracking an outage with Broadcom Carbon Black Cloud (CbC) that is affecting alert ingest and correlation of alerts to endpoint data.https://status.broadcom.com/services/carbon-black/notices/kcjrp2fn7pniepsu-carbon-black-cloud-alerts-page-search-degraded-performance Jan 10, 2025 - 17:24 UTC

Last update on Jan 10, 2025 5:26 PM