Microsoft.ApiManagement/service - Slow when updating

[cmptscpeacock]

Hi

I've deployed an API Management Service (APIMS). It takes anywhere from 10 mins-1 hour to deploy. Then, as I want a private connection I deploy that using the Resource ID of the APIMS. This then updates the APIMS so more waiting is needed.

However, I also found an issue in that if you want to set publicNetworkAccess to "Disabled" you can only do this if you first deploy the APIMS with publicNetworkAccess to "Enabled", then deploy the private connection, then you can update the APIMS to publicNetworkAccess to "Disabled". You cannot set publicNetworkAccess to "Disabled" unless there is a private connection in place.

Any suggestions on how to deploy the APIMS in a more efficient way without having to update it (and wait) each time?

[Shriharsh-Deshmukh]

To streamline APIMS deployment:

1. Deploy with Private Endpoint from Start:

   • Instead of first deploying with publicNetworkAccess enabled, deploy APIMS directly with the private endpoint configured. This reduces the need for subsequent updates.

2. Use ARM Templates:

   • Utilize ARM templates to automate the deployment and configuration. Define both public and private network settings in the same deployment template.

3. Check Deployment Templates:

   • Ensure your deployment templates include both publicNetworkAccess settings and private endpoints from the initial setup.

4. Leverage Azure CLI or PowerShell:

   • Use Azure CLI or PowerShell scripts for a more efficient deployment process:

     az apim update --resource-group <group> --name <apim-name> --set publicNetworkAccess=Disabled

This approach avoids unnecessary updates and reduces deployment time.