Experiencing errors in registering for Microsoft Insights Resource Provider- 01/25 - Resolved

Published Jan 24 2021 09:41 PM 1,552 Views
Final Update: Monday, 25 January 2021 05:33 UTC

We've confirmed that all systems are back to normal with no customer impact as of 01/25, 04:40 UTC. Our logs show the incident started on 01/22, 00:00 UTC and that during the 3 days, 4 hours and 40 minutes that it took to resolve the issue some of customers using Azure Monitor service may have experienced errors when registering subscriptions with the Microsoft Insights Resource Provider, with the state stuck on "Registering". Retries may have been successful.
  • Root Cause:  The failure was due to an issue in one of our dependent services.
  • Incident Timeline: 3 Days, 4 Hours & 40 minutes - 01/22, 00:00 UTC through 01/25, 04:40 UTC
We understand that customers rely on Azure Monitor as a critical service and apologize for any impact this incident caused.

-Anmol

%3CLINGO-SUB%20id%3D%22lingo-sub-2092751%22%20slang%3D%22en-US%22%3EExperiencing%20errors%20in%20registering%20for%20Microsoft%20Insights%20Resource%20Provider-%2001%2F25%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2092751%22%20slang%3D%22en-US%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Monday%2C%2025%20January%202021%2005%3A33%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2001%2F25%2C%2004%3A40%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2001%2F22%2C%2000%3A00%20UTC%20and%20that%20during%20the%203%20days%2C%204%20hours%20and%2040%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20customers%20using%20Azure%20Monitor%20service%20may%20have%20experienced%20errors%20when%20registering%20subscriptions%20with%20the%20Microsoft%20Insights%20Resource%20Provider%2C%20with%20the%20state%20stuck%20on%20%22Registering%22.%20Retries%20may%20have%20been%20successful.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20%26nbsp%3BThe%20failure%20was%20due%20to%20an%20issue%20in%20one%20of%20our%20dependent%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%203%20Days%2C%204%20Hours%20%26amp%3B%2040%20minutes%20-%2001%2F22%2C%2000%3A00%20UTC%20through%2001%2F25%2C%2004%3A40%20UTC%3CBR%20%2F%3E%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Monitor%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Anmol%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2092751%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Jan 24 2021 09:41 PM
Updated by: