Forum Discussion

tutumon79's avatar
tutumon79
Copper Contributor
May 11, 2025

Bicep Error While Integration API Management with Function App

Team, We are trying to automate the deployment of Azure Function App with Azure API Management so that when there is a schema change, we dont have to manually update the APIM with the functionApp s...
devops
Jamony's avatar
Jamony
MCT
Jun 26, 2026

The portal "Import Function App" experience does more than create an APIM API. It discovers HTTP-triggered functions, creates or uses a host key, stores that key as an APIM named value, and wires the backend/API operation details. In Bicep you usually need to model those pieces explicitly.

The safer automation pattern is:

  1. Expose an OpenAPI definition from the Function App, or generate one during build.
  2. Deploy/import the APIM API from that OpenAPI document.
  3. Create a backend or named value for the Function host key.
  4. Add an APIM policy to send the function key, unless you are using managed identity/EasyAuth instead.
  5. If APIM and Function App are in different resource groups, use existing resources with the correct scope in Bicep.

If the Bicep error is around listKeys() or resource scope, check that the module/resource is scoped to the Function App resource group and that the API version supports the key operation you are calling.

Useful docs:
https://learn.microsoft.com/azure/api-management/import-function-app-as-api
https://learn.microsoft.com/azure/api-management/import-api-from-oas
https://learn.microsoft.com/azure/azure-functions/functions-openapi-definition