Final Update: Wednesday, 04 December 2019 11:17 UTC
We've confirmed that all systems are back to normal with no customer impact as of 12/04, 11:15 UTC. Our logs show the incident started on 11/26, 09:45 UTC and that during the 8 days, 1 hour and 30 minutes that it took to resolve the issue minimal set of customers may have experienced failure in resource movement between subscriptions.
- Root Cause: The failure was due to a potential bug which got introduced due to recent deployment.
- Incident Timeline: 8 days, 1 Hour & 30 minutes - 11/26, 09:45 UTC through 12/04, 11:15 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.
-Rama
Update: Monday, 02 December 2019 10:34 UTC
Root cause has been isolated to a potential bug which got introduced due to recent deployment which is impacting resource movement from One subscription to another. To address this issue, we have come up with a fix which needs to be updated in the service responsible and also in the downstream systems for the fix to work. We have already tested the fix in our non-production environment and it is working as expected. Now we are moving the fix to production environment which needs to be deployed in all Geo Locations. Only minimal set of customers may experience failure in resource movement between subscriptions and all existing features will work as expected. The expected ETA to fix this issue is 3rd Dec 2019.
- Work Around: None
- Next Update: Before 12/03 11:00 UTC
-Rama
Update: Tuesday, 26 November 2019 19:56 UTCCustomers may not be able to move Application Insights resources from one subscription to another and may not be able to move resources from one resource group to another. We are working hard to fix this issue. We apologize for any inconvenience this may cause. -Ian
