"A policy change unintentionally applied to a subset of Microsoft-managed storage accounts, including those used to host virtual machine extension packages, led to this outage. The change blocked public read access that disrupted scenarios such as virtual machine extension package downloads, according to Microsoft's status history. Logged under tracking ID FNJ8-VQZ, some customers experienced failures when deploying or scaling virtual machines, including errors during provisioning and lifecycle operations."
"Azure Kubernetes Service users experienced failures in node provisioning and extension installation, while Azure DevOps and GitHub Actions users faced pipeline failures when tasks required virtual machine extensions or related packages. Operations that required downloading extension packages from Microsoft-managed storage accounts also saw degraded performance. Although an initial mitigation was deployed within about two hours, it triggered a second platform issue involving Managed Identities for Azure Resources."
An unintentional policy change applied to some Microsoft-managed storage accounts blocked public read access and prevented virtual machine extension package downloads. The outage began at 19:46 UTC and lasted over ten hours, resolving at 06:05 UTC. Customers experienced failures deploying or scaling virtual machines, including provisioning and lifecycle errors. Azure Kubernetes Service node provisioning and extension installation failed. Azure DevOps and GitHub Actions pipelines that required VM extensions or related packages failed or degraded. An initial mitigation deployed within about two hours triggered a secondary platform issue affecting Managed Identities for Azure Resources and token acquisition for resource operations.
Read at InfoWorld
Unable to calculate read time
Collection
[
|
...
]