-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Azure Firewall with Virtual Hub deployment fails as unable to set Public IP #219
Comments
Hey @chris5287, Thanks for raising this. Aware we are speaking on Friday on a call. However, I have just tested this and it worked for me (also we test all PRs so had me a little concerned how may of this one slipped by 😁): Can you share some more info around any customizations you made and what the error is/was? Thanks Jack |
The issue occurs on the 2nd deployment, as the initial deployment seems to ignore the value provided. If you check your deployment you should see the Public IP against the Azure Firewall does not match the one that was provisioned? |
Thanks will investigate in the morning 👍 |
Thanks @chris5287 you are indeed correct about the 2nd deployment and the public IP not being used. I am working on a fix for this as we speak and hope to get out soon 👍 |
ALZ-Bicep/infra-as-code/bicep/modules/vwanConnectivity/vwanConnectivity.bicep
Line 169 in efa2529
This does not work with Virtual Hubs, it appears the Public IP is a read only resource that gets randomly allocated?
The text was updated successfully, but these errors were encountered: