@David Hautbois Thanks for the update, The issue you’re experiencing might be due to the deployment mode of your ARM template. If you’re using the “Complete” deployment mode, it will delete resources that exist in the resource group but are not specified in the template. This could be why your existing API connection resource is being deleted.
To resolve this, you can change the deployment mode to “Incremental”. This mode will only add or update the resources specified in the template, without deleting any existing resources.
Here’s an example of how you can deploy the template with Azure CLI using the “Incremental” mode:
az deployment group create --resource-group <resource-group-name> --template-file <template-file-path> --mode Incremental
Replace <resource-group-name> with the name of your resource group, and <template-file-path> with the path to your template file.
If you’re deploying the template through the Azure portal, you can select the “Incremental” mode in the “Custom deployment” blade.
Please try this and let me know if it helps.