This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 62%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERC%3C/text%3E%3C/svg%3E)
I have setup CMG with configuration Manager v2107 using CSP subscriptions and virtual machine scale set, I used Service Name + Deployment name same as xxxx.xxSOUTH.CLOUDAPP.AZURE.COM. do we need any public DNS or CN Name for this method? as i could see clients and ConfigMgr are start communicating without any DNS info? is it a recommend way? or something I'm missing. all my clients are windows 10 Azure Hybrid Joined. MP communication settings is enhanced HTTP.
Please advise
Thank You
Rck
If you are using azure deployment name then you don’t need a CNAME as it is owned by Microsoft and publicly routable.
Edit: This is as per Microsoft’s official technical documentation. Personally, I would create a CNAME.
If you are using azure deployment name the you don’t need a CNAME as it is owned by Microsoft and publicly routable.
While technically true (and supported even) this is a BAD idea. ALWAYS use a CName and always use a cert from a public CA for your CMG.
Thanks @Jason Sandys ....We already setup with azure deployment name. so, can we modify the configurations? or we have to rebuild the cloud service from the scratch? if we rebuild can we get /or used the same cloud domain like xxxx.xxSOUTH.CLOUDAPP.AZURE.COM as its already created? also what could be the impact if we are continue without CName?
Unfortunately, your question is far too ambiguous to answer. I have no idea what you currently have configured so can't tell you what you can or should do. The CMG service name always starts with and is based on the name in your server certificate. What subject name is in your certificate?
I used the certificate name , service name and deployment name same as 'xxxx.xxSOUTH.CLOUDAPP.AZURE.COM' . as discussed It is working without any external domain or CName but as you suggested this is not the good idea. may i know the impact if we continue the same setup?
So if we need to rout with CName then we have to create new certificate with our domain name right? i.e. the service name going to change as per new certificate in that case can we still use our CMG deployment name same as xxxx.xxSOUTH.CLOUDAPP.AZURE.COM' i.e. the existing one? what is the best way to sort it out this matter.
Thank You
So if we need to rout with CName then we have to create new certificate with our domain name right?
Correct.
in that case can we still use our CMG deployment name same as xxxx.xxSOUTH.CLOUDAPP.AZURE.COM' i.e. the existing one?
Yes, you can use the same name although I don't think you'll be able to use the exact same deployment as there's no direct way (to my knowledge) to swap out the cert if the subject name in the cert doesn't match. I can't say I've ever tried doing this though so could be wrong.
Thanks Jason, so what is the best way to sort it out this matter? if there is any issues if I continue the same setup?
please advise
(sorry, missed replying to this earlier)
I'm not sure what else you need here. You are stuck to my knowledge and need to recreate the CMG. Always use a CName. Full Stop. That would have avoided this issue.