Hello!
I have been setting up a template for Api dashboards in our company, and have been using the Tile; Application Insights Availability. Suddenly today the tile is not working, giving the error: ComponentId is Required. The tile has been working fine for the past few weeks.
Did you remove the tile completely, or is this an error which will be fixed?
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@daneri-norkart Thanks for reaching out! Could you please include a screenshot having the error you see?
I am able to see the Availability Test Summary Application Insights tile as under:

If possible, could you please try removing and reconfiguring the tile, and check if that helps?
1 = how the tile has looked before.
2, 3 = the error I'm getting right now.
4 = how the tile you are referencing looks. It seems to be a new addition which can't be scaled down to fit the size I'm working with.
the problem with removing the tile and adding it again is that the tile I was using is no longer in the tile gallery.

thanks for the quick response, btw :)
@daneri-norkart Sure, thanks for the addtional details.

You can then resize the tile as you see fit. :)
oh yeah, I see :)
What I'm working on is releasing multiple APIs in one dashboard, based on a Arm Template. Do you know why the tile was removed from the tile gallery? and if this happens often?
The name of the part has now changed from
Extension/AppInsightsExtension/PartType/AvailabilityNavButtonPart to Extension/AppInsightsExtension/PartType/WebTestsPinnedPart when working with the json parts. So it would be nice to have at least some consistency over a period of time where we dont have to update the arm template for every team. Or some notice of which tiles will not be available through the tile gallery.
@daneri-norkart Glad you could surface the component type. I'll try and check why this is so and get back once I get an update. Also, thanks for the feedback, and suggestion. I'll cascade this to our internal Teams.
On a side note, I'd like to let you know that this channel (the Azure Docs repository) is only for driving improvements related to the Azure documentation. The best place for specific answers about implementations are going to be the MSDN and Stack Overflow forums. We actively look through posts in the forums, and will do our best to get you going in the right direction!
At this point, it appears that there are no edits or updates needed to the document in question. Hence closing this issue for now. If there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation. Thanks again for reaching out!