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.
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