Import function via Powershell Az Module

[PhilipAnthonyMurray]

A previous question asks around programmatically importing a HTTP Trigger Function App which was never truly resolved. We have our Function Apps hosted within an Isolated tier App Service Plan on a private App Service Environment and at the moment I am unable to expose the OpenAPI specification using the Function App API Definition.

In this particular use case I can manually register a Function App endpoint within APIM but this is not possible on our Pre-Production and Production environments as we have no access. We need a mechanism of completing this task via Powershell and the Az library.

Any assistance would be useful.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: a0b38af1-81e7-341a-d7bf-e471ea7585e5
• Version Independent ID: 6d16fd43-249e-5afc-062a-2e019eade30e
• Content: Import an Azure Function App as an API in API Management - Azure API Management
• Content Source: articles/api-management/import-function-app-as-api.md
• Service: api-management
• GitHub Login: @mikebudzynski
• Microsoft Alias: apimpm

[PhilipAnthonyMurray]

I used the Dev tools to understand the REST calls in achieving this and there is a chain of 22 calls. This is absolutely not maintainable in a DevOps pipeline.

[mike-urnun-msft]

@PhilipAnthonyMurray Thank you for your feedback! We will review and update as appropriate.

[PhilipAnthonyMurray]

@mike-urnun-msft Any update on this functionality?

[mike-urnun-msft]

Hello @PhilipAnthonyMurray - Sorry for the delay in response. I have reached out to the APIM team internally regarding this issue and received confirmation that there isn't a backend endpoint available for this operation at this time around (Portal does it with Javascript on the frontend hence the 22 calls).

As the next step, please consider submitting a feature request on the Azure UserVoice (or upvote an existing one if it exists) for the APIM team to review its priority for the product roadmap.

We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

[nnnvvvcv]

@PhilipAnthonyMurray did you ever get anywhere with this? I'm looking to do something similar.

[PhilipAnthonyMurray]

@nnnvvvcv
We exported the API definition of the Function App as a YAML file then utilised the below Powershell snippet to import into APIM

$apiMgmtContext = New-AzApiManagementContext -ResourceGroupName $ApimResourceGroup -ServiceName $ApiManagementInstanceName

cd $PSScriptRoot
$api = Import-AzApiManagementApi -Context $apiMgmtContext -SpecificationFormat OpenApi -SpecificationPath '.\myYAML.yaml' -Path "myAPIPath" -Protocol Https -ServiceUrl $ServiceUrl

Add-AzApiManagementApiToProduct -Context $apiMgmtContext -ProductId "myProductId" -ApiId $api.ApiId  | Out-Null

[nnnvvvcv]

@PhilipAnthonyMurray thanks for that. Can I just ask what you used to generate the YAML? Was this part of your build pipeline too? I've been looking at the Azure Webjobs OpenAPI library to generate a document but that is generated at runtime rather than buildtime.

I guess we could build the function-app, deploy the function-app, extract the YAML from the running instance and then provision APIM...

[PhilipAnthonyMurray]

@nnnvvvcv

Not entirely sure, I got the development lead to generate it as a one off. He either had it from the initial spec or generated it from the Swagger editor.