Final Update: Sunday, 14 February 2021 23:46 UTC
We've confirmed that all systems are back to normal with no customer impact as of 02/14, 23:32 UTC. Our logs show the incident started on 01/24 and that during the ~ 21 days that it took to resolve the issue <1% of global customers experienced an error when trying to create a scope configuration within Log Analytics Portal indicating "Failed to create scope configuration resource."
-Jayadev
We've confirmed that all systems are back to normal with no customer impact as of 02/14, 23:32 UTC. Our logs show the incident started on 01/24 and that during the ~ 21 days that it took to resolve the issue <1% of global customers experienced an error when trying to create a scope configuration within Log Analytics Portal indicating "Failed to create scope configuration resource."
- Root Cause: The failure was due to a code change that happened to one of the backend services.
- Incident Timeline: 21 days - 01/24 UTC through 02/14, 23:32 UTC
-Jayadev
Update: Sunday, 14 February 2021 20:57 UTC
Root cause has been isolated to a code related issue which was impacting customers to create a scope configuration change within the Log Analytics Portal. To address this issue we are rolling back the changes to previous working code. We estimate the rollout to complete in about ~ 4 hours.
Root cause has been isolated to a code related issue which was impacting customers to create a scope configuration change within the Log Analytics Portal. To address this issue we are rolling back the changes to previous working code. We estimate the rollout to complete in about ~ 4 hours.
- Next Update: Before 02/15 01:00 UTC
Initial Update: Sunday, 14 February 2021 17:06 UTC
We are aware of issues within the Log Analytics portal with scope configuration changes and are actively investigating. Some customers may experience an error when trying to create a scope configuration indicating "Failed to create scope configuration resource."
Next Update: Before 02/14 21:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jeff
Updated Feb 14, 2021
Version 4.0