If you havent obfuscated that domain name, it's li...
# azure
w
If you havent obfuscated that domain name, it's likely doing some checking on the tld as it isn't valid. I'd check that it's cnamed properly too. Azure normally checks the routing before it will allow you to add custom domains.
m
the domain name is obfuscated
but I figured out the actual problem, The CustomDomainName is quite misleading, but apparently that cannot be a domain, just a name
t
Aren’t you able to leave out this property and let it auto-generate?
m
it said it was required
t
m
but Pulumi actually errored out saying it was missing
t
Oh, odd, that doesn’t sound right
m
no, but thats what I got.
anyways it seems like CustomDomain does not support ssl, but ADFCustomDomain does