Wrong DNS zone creation in government cloud deployment #35
Description
A customer reported that deploying SCEPman in a GCC High environment will lead to a unconnected key vault:
https://c4a8.freshdesk.com/a/tickets/136895
In the following line we are creating the private dns zone for privatelink.vaultcore.azure.net while the correct zone should be privatelink.vaultcore.usgovcloudapi.net for GCC High:
https://github.com/scepman/install/blob/b0479c39beb845c8fe16721f2f7ba47af27d9e84/nestedtemplates/vault.bicep#L62
If we adjust the deployment generally to use service endpoints instead of private endpoints, this issue would vanish automatically. A dedicated I can think of would be to modify this zone for the gcchigh branch before releasing.