You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bicep version
Bicep CLI version 0.30.23 (ec3612efc7)
Describe the bug
As far as I know it is impossible to add apex domain to the frontdoor via bicep. But it is possible to add them manually. Earlier if the domain was somedomain.com, the resource name was somedomain-com. I noticed that Microsoft changed this behaviour and adds some random string to the name like this: somedomain-com-ad5e
Is there any way to refer to the manually added apex domain without hardcoding the name with suffix?
To Reproduce
Create Azure Frontdoor
Add apex domain to the custom domains
Try to refer to apex domain by its name like in this example
resourceCDN'Microsoft.Cdn/profiles@2022-11-01-preview'existing = {
name: profileNameresourcecustomDomain'customDomains' = {
name: replace(zone, '.', '-')
properties: {
hostName: zonetlsSettings: {
certificateType: 'ManagedCertificate'minimumTlsVersion: 'TLS12'
}
azureDnsZone: {
id: DNS.id//<-- based on th docs you might want to add this value as well.
}
}
}
}
Additional context
I need to associate rules with this domain using bicep
The text was updated successfully, but these errors were encountered:
Bicep version
Bicep CLI version 0.30.23 (ec3612efc7)
Describe the bug
As far as I know it is impossible to add apex domain to the frontdoor via bicep. But it is possible to add them manually. Earlier if the domain was somedomain.com, the resource name was somedomain-com. I noticed that Microsoft changed this behaviour and adds some random string to the name like this: somedomain-com-ad5e
Is there any way to refer to the manually added apex domain without hardcoding the name with suffix?
To Reproduce
Additional context
I need to associate rules with this domain using bicep
The text was updated successfully, but these errors were encountered: