%3CLINGO-SUB%20id%3D%22lingo-sub-353398%22%20slang%3D%22en-US%22%3EExperiencing%20issue%20while%20redirecting%20to%20Azure%20Portal%20from%20alert%20emails-%2001%2F23%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-353398%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3E%20First%20published%20on%20MSDN%20on%20Jan%2023%2C%202019%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CDIV%3E%0A%20%20%20%3CDIV%3EFinal%20Update%3A%20Wednesday%2C%2023%20January%202019%2006%3A54%20UTC%20%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2001%2F23%2C%2007%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2001%2F18%2C%2023%3A00%20UTC%20and%20that%20during%20the%204%20days%20and%208%20hours%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20would%20have%20experienced%20issues%20while%20redirecting%20to%20azure%20portal%20from%20alert%20email%20links.%20%3CBR%20%2F%3E%3CUL%3E%0A%20%20%20%20%20%3CLI%3ERoot%20Cause%3A%20The%20failure%20was%20due%20to%20version%20compatibility%20issue%20in%20one%20of%20our%20backend%20service.%3C%2FLI%3E%0A%20%20%20%20%20%3CLI%3EIncident%20Timeline%3A%204%20Days%20%26amp%3B%208%20Hours%20-%2001%2F18%2C%2023%3A00%20UTC%20through%2001%2F23%2C%2007%3A00%20UTC%20%3CBR%20%2F%3E%3C%2FLI%3E%0A%20%20%20%20%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Application%20Insights%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20-Mohini%20%3CBR%20%2F%3E%3C%2FDIV%3E%0A%20%20%20%3CDIV%3E%0A%20%20%20%20%3CDIV%3EUpdate%3A%20Wednesday%2C%2023%20January%202019%2006%3A44%20UTC%20%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Application%20Insights.%20Some%20customers%20continue%20to%20experience%20issue%20while%20redirecting%20to%20portal%20from%20alert%20emails.%26nbsp%3BWe%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2C%20initial%20findings%20indicate%20that%20the%20problem%20began%20at%2001%2F18%20~23%3A00%20UTC.%20%3CBR%20%2F%3E%3CUL%3E%0A%20%20%20%20%20%20%3CLI%3EWork%20Around%3A%20None%3C%2FLI%3E%0A%20%20%20%20%20%20%3CLI%3ENext%20Update%3A%20Before%2001%2F23%2011%3A00%20UTC%3C%2FLI%3E%0A%20%20%20%20%20%3C%2FUL%3E-Mohini%20%3CBR%20%2F%3E%3C%2FDIV%3E%0A%20%20%20%20%3CDIV%3E%0A%20%20%20%20%20%3CDIV%3EInitial%20Update%3A%20Wednesday%2C%2023%20January%202019%2004%3A34%20UTC%20%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Application%20Insights%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20issue%20while%20redirecting%20to%20portal%20from%20alert%20emails.%20%3CBR%20%2F%3E%3CUL%3E%0A%20%20%20%20%20%20%20%3CLI%3EWork%20Around%3A%20None%3C%2FLI%3E%0A%20%20%20%20%20%20%20%3CLI%3ENext%20Update%3A%20Before%2001%2F23%2007%3A00%20UTC%3C%2FLI%3E%0A%20%20%20%20%20%20%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%20%3CBR%20%2F%3E%20-Mohini%3C%2FDIV%3E%0A%20%20%20%20%3C%2FDIV%3E%0A%20%20%20%3C%2FDIV%3E%0A%20%20%3C%2FDIV%3E%0A%20%0A%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-353398%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20MSDN%20on%20Jan%2023%2C%202019%20Final%20Update%3A%20Wednesday%2C%2023%20January%202019%2006%3A54%20UTCWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2001%2F23%2C%2007%3A00%20UTC.%3C%2FLINGO-TEASER%3E
First published on MSDN on Jan 23, 2019
Final Update: Wednesday, 23 January 2019 06:54 UTC

We've confirmed that all systems are back to normal with no customer impact as of 01/23, 07:00 UTC. Our logs show the incident started on 01/18, 23:00 UTC and that during the 4 days and 8 hours that it took to resolve the issue some customers would have experienced issues while redirecting to azure portal from alert email links.
  • Root Cause: The failure was due to version compatibility issue in one of our backend service.
  • Incident Timeline: 4 Days & 8 Hours - 01/18, 23:00 UTC through 01/23, 07:00 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Mohini
Update: Wednesday, 23 January 2019 06:44 UTC

We continue to investigate issues within Application Insights. Some customers continue to experience issue while redirecting to portal from alert emails. We are working to establish the start time for the issue, initial findings indicate that the problem began at 01/18 ~23:00 UTC.
  • Work Around: None
  • Next Update: Before 01/23 11:00 UTC
-Mohini
Initial Update: Wednesday, 23 January 2019 04:34 UTC

We are aware of issues within Application Insights and are actively investigating. Some customers may experience issue while redirecting to portal from alert emails.
  • Work Around: None
  • Next Update: Before 01/23 07:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Mohini