No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

I am also having trouble to find the equivalent of `ApplicationInsights` . Is there a guide or an explanation somewhere that I can use to map from the old names to the ones in `nextgen` ?

It’s a module called `Insights` and resource `Component`. Unfortunately, there’s no doc that maps the old names (hand-crafted by us) to new names (auto generated), at the moment. Also, the mapping is often not 1:1.

<https://www.pulumi.com/docs/reference/pkg/azure-nextgen/insights/component/>

On the bright side, you can pretty much use Azure docs for ARM templates and map them to Pulumi.

So if I create a `Component` I should see `ApplicatoinInsights` in the Azure Portal?

Wow I didn't expect such inconsistency in Azure's own stuff

<https://docs.microsoft.com/en-us/azure/templates/microsoft.insights/components>

I guess older services that went through several marketing waves suffer from that more

Yeah... I am just trying to find my way as a beginner and it is confusing that the GUI doesn't match the API

Thanks again for you help :slightly_smiling_face: