Viser mobilvisning Computervisning
|Web og mobil|
|Data og lager|
|Administrationsportal til SQL-database|
|SQL Data Warehouse|
|Data Lake Store|
|Data Lake Analytics|
|Medier og CDN|
|Live og on-demand-streaming|
|Identitets- og adgangsstyring|
|Azure Active Directory|
|Azure AD Domain Services|
|Azure Active Directory B2C|
|Access Control Service|
|Visual Studio Team Services|
|Build & Deployment/Build (XAML)|
|Visual Studio Application Insights|
|Azure DevTest Labs|
|Azure Resource Manager|
|Microsoft Azure Preview-portal|
SUMMARY OF IMPACT: Between 20:40 to 21:00 UTC on 24 November, 2015 a subset of customers may have experienced an error when attempting to log into their Management Portal through https://portal.azure.com. PRELIMINARY ROOT CAUSE: At this stage we do not have a definitive root cause. MITIGATION: The issue was self-healed. NEXT STEPS: Investigate the underlying root cause of this issue and develop a solution to prevent reoccurrences.
SUMMARY OF IMPACT: Between 17:05 and 21:30 UTC on 24 November, 2015 a subset of customers who logged into their Visual Studio account using Azure Active Directory (AAD) credentials may have experienced slow sign-in or may have encountered an error. PRELIMINARY ROOT CAUSE: At this stage we do not have a definitive root cause. MITIGATION: We failed over the impacted authentication front-end servers and that mitigated the latency. NEXT STEPS: Continue to investigate the underlying root cause of this issue and develop a solution to prevent reoccurrences.
We have concluded our investigation of a reported issue for Active Directory and confirmed that all services are healthy, and a service incident did not occur.
SUMMARY OF IMPACT: Between 17:36 to 17:44 UTC on 24 November, 2015 customers using Compute and Storage resources in the Australia East region may have experienced a brief network interruption of up to 9 minutes. PRELIMINARY ROOT CAUSE: Preliminary investigations indicate that this incident was caused by an interruption to our Network Infrastructure. MITIGATION: Network health normalized after engineers replaced a faulty control board on a network device. NEXT STEPS: Continue to investigate the underlying root cause of this issue and develop a solution to prevent reoccurrences.
SUMMARY OF IMPACT: From 24 Nov 2015, 10:21 to 17:03 UTC a subset of customers using Visual Studio Online in West Europe may have experienced longer than usual build queue times. Customers were advised that they should not have cancelled their builds or attempt to resubmit these. Customers were advised to wait for their builds to complete as cancelling the job and resubmitting will may have pushed their jobs to the back to the queue. PRELIMINARY ROOT CAUSE: A recent deployment resulted in an alteration of a system setting. This change resulted in some jobs that were waiting to be processed, to be stuck in a bottleneck. MITIGATION: Engineers had to wait for the bottleneck to be cleared before applying a mitigation hotfix. NEXT STEPS: Investigate the underlying root cause of this issue and develop a solution to prevent reoccurrences.
SUMMARY OF IMPACT: Between 05:01 and 06:54 on 24 Nov, 2015 UTC customers using Network Infrastructure in West Europe experienced issues accessing networking services. Multiple other Azure services were also impacted. PRELIMINARY ROOT CAUSE: A misconfiguration on a networking device caused a loss of connectivity for the West Europe Regions. Service were still running, but were unreachable for customers during this period. MITIGATION: Engineers revised the configuration and system thresholds to prevent a reoccurrence of this issue . NEXT STEPS: Engineers will continue to investigate to determine the underlying cause.
Between 05:01 and 06:54 on 24 Nov, 2015 UTC, Multiple services in Europe were impacted by an underlying Networking issue. Impacted services included: SQL Database, API Management, Media Services, Azure Search, App Service \ Web App, Service Bus, Event Hubs, Azure Active Directory B2C, Operational Insights, Key Vault, Virtual Machines, Data Catalog, Azure Active Directory and Stream Analytics. The Networking issue was resolved at 06:54, and additionally impacted services are now also recovered.
SUMMARY OF IMPACT: Starting at 24 Nov, 2015 05:01 to 06:54 UTC a subset of customers using Virtual Machines or SQL Database in North Europe may have experienced their Virtual Machines or SQL Databases move into an unresponsive state. PRELIMINARY ROOT CAUSE: Due to an underlying Network Infrastructure issue, a subset of Virtual Machines and SQL Databases in North Europe moved into an unresponsive state. Most impacted customers would have noticed an instant recovery, however some customers would have experienced some delay before recovery. MITIGATION: Engineers manually recycled the affected Virtual Machines to bring them back online. NEXT STEPS: Investigate the underlying Networking infrastructure issue .
Starting at 24 Nov, 2015 05:01 Virtual Machines are impacted by an ongoing networking issue in West Europe. Details on impact to Virtual Machines will be posted under the main Networking Incident, and this thread will be closed.
SUMMARY OF IMPACT: Between 17:40 and 19:12 on 23 NOV 2015 UTC a subset of customers using Visual Studio Application Insights in multiple regions may have experienced failures and/or random timeouts when attempting to view or query their data. Up to 18% of Application Insights customers may have been impacted by this issue. Impacted customers were unable to create new alerts. Existing alerts were not impacted, however alerts would fire without a metric display name. Additional updates and root cause can be found on the Application Insights blog: http://blogs.msdn.com/b/applicationinsights-status/archive/2015/11/23/experiencing-data-access-issue-in-azure-portal-for-many-data-types-11-23-investigating.aspx . PRELIMINARY ROOT CAUSE: At this stage we do not have a definitive root cause. MITIGATION: The issue was self-healed and engineers restarted processes to speed up recovery. NEXT STEPS: Investigate the underlying root cause of this issue and develop a solution to prevent reoccurrences.