Region constraints needed for app insights?

[pamelafox]

I got an error when I first tried to deploy, where I selected westcentralus:

Apparently app insights components aren't supported there. I assume something is supported there, given it shows up in the list? Or should azd be hiding that region always? @vhvb1989 Do you know?

[vhvb1989]

When it comes to listing locations to deploy, azd doesn't check the type of resources from the deployment. Azd gets all the locations from user's subscription.
The only way to make azd to filter locations is by using the @allowed() annotation in bicep for the location parameter.

[lilyjma]

thanks for the pointer @vhvb1989 . Sounds like the only way to restrict the regions now is to update the @allowed() annotation in bicep so I'll make that change

[pamelafox]

Okay, yeah, just wanted to check that it wasnt an issue that "westcentralus" should never be shown to anyone. (We once had that issue with test region names, I think).

It'll be a long list but at least prevent folks from choosing the more obscure regions like I did.

[mullaneai]

I am getting similar error , trying to install to "West Europe" as "North Europe" is not offered as a option

[lilyjma]

@mullaneai yes, could you try West Europe please?

[mullaneai]

@lilyjma thanks for coming back to me quickly

I just tried West Europe again and got similar error.
Attached is a screenshot of the Deployment error from the Azure portal

api-flex-consumption
There was an unexpected InternalServerError. Please try again later

api
The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.

[pamelafox]

@mullaneai Have you ever successfully deployed a Flex Consumption Function? It's possible that the Flex RP isn't registered for you for some reason - you could try register Microsoft.App

[mullaneai]

@pamelafox Microsoft.App was not registered. Once I registered it the Deployment worked. Thanks Pamela

[lilyjma]

Looks like bicep doesn't support registering RP yet. I've added a CLI command to help with that at the moment.

Thanks for trying out the sample and reporting the issue @mullaneai!