Change in template throwing errors on deployment.

[YSongCloud]

Deployment attempts fail with this error - The template output reference to "" requires an API version when using with an already existing PublicIP in the same resource group.

If you choose to deploy the template using new PIPs for the 3 instead of existing, and you select "BASIC" for all 3, PIP3 always deploys with the SKU type set to Standard, thereby causing the deployment to fail due to incompatible configurations of IPs as the Cluster PIP SKU would be basic and the FGT-B mgmt PIP SKU would be Standard.

I have successfully deployed this template in the past, but since the last commit it is failing.

[jvhoof]

Hi,

Thanks for reaching out. Which template did you try to deploy? That way I can do some specific tests.

Joeri

[YSongCloud]

Joeri,

I was deploying the Active-Passive with SDN template. I also edited my original post to provide more details as I have been troubleshooting the deployment failures most of the day today. I am able to consistently recreate this, but am testing a workaround.

[jvhoof]

Hi,

Can you try again? I found the typo on the pip3 sku naming in the template. This didn't get caught in my tests.

In the next version we will be removing the option for a basic sku public IP. Microsoft will be retiring the basic sku in 2025 and recommends standard SKU public IPs already for production workloads. Check the link below for more information:

https://azure.microsoft.com/en-us/updates/upgrade-to-standard-sku-public-ip-addresses-in-azure-by-30-september-2025-basic-sku-will-be-retired/

Joeri