First published on MSDN on Apr 04, 2018
Final Update: Wednesday, 04 April 2018 04:00 UTC

We've confirmed that all systems are back to normal with no customer impact as of 04/04, 04:00 UTC. Our logs show the incident started on 04/02, 13:00 UTC and that during the 39 hours that it took to resolve the issue, customers who attempted to create new Log Analytics work spaces through Azure portal in the subscriptions created after 13:00 UTC 04/02, experienced errors and work space creation failed.

  • Root Cause: While creating new work space, Azure Portal failed to identify the new subscriptions due to latest configuration changes to one of our backend services, resulting in work space creation failures in new subscriptions.
  • Incident Timeline: 39 Hours - 04/02, 13:00 UTC through 04/04, 04:00 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Sapna
Update: Tuesday, 03 April 2018 03:05 UTC

Fix for the issue has been identified and is being deployed globally region by region. It will take upto 24 hours for the update to be available across all regions.

  • Work Around: If customers have the ability to deploy through an ARM template, specifying the "pergb2018" pricing tier instead of one of the pricing tiers displayed in the portal will unblock the user.
  • Next Update: Before 04/04 03:00 UTC
-Sapna
Update: Monday, 02 April 2018 21:00 UTC

Root cause has been isolated to a configuration change in one of our back-end services, which failed to identify new subscriptions correctly, impacting creation of work spaces under the new subscriptions only.  To address this issue we are working on the configuration updates across all the regions. Initial findings indicate that the problem began at 04/02 ~13:00 UTC and may take few more hours to resolve the issue.

  • Work Around: If customers have the ability to deploy through an ARM template, specifying the "pergb2018" pricing tier instead of one of the pricing tiers displayed in the portal will unblock the user.
  • Next Update: Before 04/03 03:00 UTC
-Sapna
Initial Update: Monday, 02 April 2018 18:00 UTC

We are aware of issues within Azure Log Analytics and are actively investigating. Some customers who attempt to create new Log Analytics work spaces through Azure portal in the subscriptions created after 13:00 UTC,will see an error and the work space creation will fail.

  • Work Around: If customers have the ability to deploy through an ARM template, specifying the "pergb2018" pricing tier instead of one of the pricing tiers displayed in the portal will unblock the user.
  • Next Update: Before 04/02 21:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.

-Sapna