This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Update: Friday, 17 June 2022 01:55 UTC
We have identified a recent change in the dependent backend service as the underlying cause and are currently rolling out a hotfix to mitigate the issue. The next update will be provided in 4 hours or as events warrant.
We have identified a recent change in the dependent backend service as the underlying cause and are currently rolling out a hotfix to mitigate the issue. The next update will be provided in 4 hours or as events warrant.
- Work Around: Creating a sub-resource (e.g., web test) in the impacted Application Insights component might fix the issue for the whole subscription. If the issue persists, try refreshing the page or opening the impacted blade in a new browser. That sub-resource (e.g., web test) could be deleted immediately once the issue goes away.
- Next Update: Before 06/17 06:00 UTC
Initial Update: Thursday, 16 June 2022 23:30 UTC
We are aware of issues within Application Insights and are actively investigating. Some customers when using subscriptions that don't have any existing Application Insights resources will see failures when creating a new Application Insights resource via Terraform. For customers using Azure portal, the "Usage and estimated costs" page of the Application Insights resource may not show the daily cap information.
We are aware of issues within Application Insights and are actively investigating. Some customers when using subscriptions that don't have any existing Application Insights resources will see failures when creating a new Application Insights resource via Terraform. For customers using Azure portal, the "Usage and estimated costs" page of the Application Insights resource may not show the daily cap information.
- Next Update: Before 06/17 03:30 UTC
-Robin Paul