I have entered the DNS information exactly right, and tried multiple different settings and configurations, given over 2 weeks for propagation each time, tried all forms of the URL (with 'www', without www, with https, http, etc.). And attempted all troubleshooting tips from the Support Documentation. The Custom Domain Name still fails verification inside the Azure Portal. What is the next step to try? Thank you,

Hi Jon, First, precisely which service(s) are you attempting to use in Azure? I ask because, you tagged your question with Azure App Service, however, your screenshot shows Microsoft Entra ID. These are two different services, and each has its own procedure for verifying custom domains. Verifying your custom domain for Entra ID would be for the case where you want users to be able to sign in to Azure portal/Microsoft 365/etc. using username@yourcustomdomain.com instead of username@yourcustomdomain.onmicrosoft.com Verifying your custom domain for Azure App Service is used for the case where you want to host your website/webapp in Azure and have people be able to navigate to it using yourcustomdomain.com (or [www.yourcustomdomain.com]) instead of yourcustomdomain.azurewebsites.net. To verify your domain for App Service you need to navigate to your web app in the Azure portal -- Settings -- Custom domains blade, add your domain, add DNS record to verify, etc. I checked your DNS records and you don't have correct record in place for verifying [www.yourdomain.com]. Normally you would NOT verify [www.yourdomain.com] with Entra ID. You do have correct record in place to verify yourdomain.com with Entra ID, however, based on your screenshot you are not attempting to verify that. Additionally, it appears you do not have the correct DNS records in place to verify your custom domain on App Service. Please reply back with information requested above and I'll assist you further. I'm familiar with your registrar so can help you with instructions there if needed. Thanks. -TP

Hi, I have prepared a detailed document showing the procedure ' How to configure a custom domain for an Azure Web Application ' in my blog Please cross check, if you have followed the right steps in your setup Hope this helps. --please don't forget to upvote and Accept as answer if the reply is helpful--

Why won't the custom domain name verify?

Accepted answer

TP 98,176 Reputation points

2024-07-29T22:07:03.1666667+00:00

Hi Jon,

First, precisely which service(s) are you attempting to use in Azure? I ask because, you tagged your question with Azure App Service, however, your screenshot shows Microsoft Entra ID. These are two different services, and each has its own procedure for verifying custom domains.

Verifying your custom domain for Entra ID would be for the case where you want users to be able to sign in to Azure portal/Microsoft 365/etc. using username@yourcustomdomain.com instead of username@yourcustomdomain.onmicrosoft.com

Verifying your custom domain for Azure App Service is used for the case where you want to host your website/webapp in Azure and have people be able to navigate to it using yourcustomdomain.com (or [www.yourcustomdomain.com]) instead of yourcustomdomain.azurewebsites.net.

To verify your domain for App Service you need to navigate to your web app in the Azure portal -- Settings -- Custom domains blade, add your domain, add DNS record to verify, etc. I checked your DNS records and you don't have correct record in place for verifying [www.yourdomain.com]. Normally you would NOT verify [www.yourdomain.com] with Entra ID. You do have correct record in place to verify yourdomain.com with Entra ID, however, based on your screenshot you are not attempting to verify that.

Additionally, it appears you do not have the correct DNS records in place to verify your custom domain on App Service.

Please reply back with information requested above and I'll assist you further. I'm familiar with your registrar so can help you with instructions there if needed.

Thanks.

-TP
Please sign in to rate this answer.
Srinud 2,610 Reputation points Microsoft Vendor

2024-07-31T10:57:44.1166667+00:00

Hi Jon Kidwell,

Just checking in to see if you have got a chance to see the answer posted by TP in resolving the issue.

If it was helpful, please click "Upvote and Accept Answer" on his post to let us know.

We're here to help, so if you have any further questions, don't hesitate to ask.

Thank You.

Jon Kidwell 20 Reputation points

2024-07-31T22:34:22.97+00:00

Hi TP,

Thank you for the probing questions to create clarity, and the outline of the two services, Azure App Service and Entra ID. Everyone's engagement is greatly appreciated.

What we are attempting to do, (and perhaps it is misguided), is achieve having this portion of the login process when a user accesses our SaaS at leadwellplus,.com, using a Microsoft OAuth login, show "Verified" instead of the "unverified" message - and we believed getting our domain name correctly verified within our Azure App Registration, was the first step to that (here is an example login using one of our personal Office365 retail accounts to login with):

So based on your explanation of Azure Web App and EntraID, where do I need to navigate to within portal.azure.com, to remove that unverified message? (Is that purely related to being a Verified Publisher with a Verified Publisher Domain?)

And we should not be concerned with this screen below, (for the purposes of how we are represented when having users be able to successfully log into our SaaS platform, using their personal or enterprise Microsoft account logins)?

Thank you again.

Jon

TP 98,176 Reputation points

2024-07-31T23:07:59.23+00:00

Hi Jon,

I'm guessing you want your publisher domain to be www.leadwellplus.com and not leadwellplus.com? Currently you have your app set to www.leadwellplus.com.

I would think most people would go with simply leadwellplus.com, however, this is more of a cosmetic/industry pattern.

You need to verify the custom domain you are going to use as publisher in Entra ID custom domains. This is the easy/quick part. I know it seems hard to you at the moment since you tried already and had an issue, but we can fix that by having you create correct DNS entry. When I checked your DNS records it appeared that you already had proper DNS record to verify leadwellplus.com, you just need to enter it in custom domains.

The more difficult part is to get your account properly set up in Cloud Partner Program (aka Microsoft Partner Network) and then once all that is done you can go to the Branding & properties blade of your app as shown in your screenshot and add the partner ID.

Publisher verification

https://learn.microsoft.com/en-us/entra/identity-platform/publisher-verification-overview

The other thing for you to consider/test is how the above will affect your existing users that have already consented. For example, let's say you think about it and decide you prefer the publisher to be leadwellplus.com Seems straightforward to change it on the application properties, however, will your users have to re-consent since the publisher url changed?

I'm not saying the above potential consent prompt should stop you. In my experience before rolling out changes to SaaS users you have to test and think of all these "minor" details and have a plan ready so that users can be notified and support is ready to handle tickets.

Jon Kidwell 20 Reputation points

2024-07-31T23:17:16.5233333+00:00

Entra Custom Domains looks the same as the Azure page. Am I missing something?

As you noted, the DNS records are already correct, with the @ TXT matching the data inputs provided by Microsoft.

TP 98,176 Reputation points

2024-07-31T23:30:46.73+00:00

Click Add custom domain and enter leadwellplus.com . Since you already have the DNS TXT record in place you should be able to verify it quickly. I believe once you do that, www.leadwellplus.com should show up as verified as well.

I've added a sub custom domain (similar to www in your case) after the apex domain and it was automatically verified since the apex was already verified, however, I've not done it in reverse sequence as you are attempting.

Again as I mentioned above, this is the "easy" part. Getting the partner network stuff is what takes some time.

Jon Kidwell 20 Reputation points

2024-07-31T23:44:42.0466667+00:00

That will require another separate DNS entry, with the new values:

I attempted this before, multiple times over the course of months. (creating a leadwellplus.com custom domain, adding the DNS entries, waiting for propagation, attempting verification, failing. Adding www.leadwellplus.com, repeating again a second time, etc., etc.). It failed every time.

TP 98,176 Reputation points

2024-08-01T00:02:42.7733333+00:00

Now that you have the leadwellplus.com custom domain there, jump over to Namecheap and edit the existing TXT record so that it is MS=ms15537505 and save the change. If you have TTL set to 60 minutes like Microsoft requested you should be able to verify it in about an hour.

Jon Kidwell 20 Reputation points

2024-08-01T16:20:29.9766667+00:00

That seems to have worked this time, TP, thank you! Apparently the Entra admin portal functions differently than the Azure Admin portal?

I would consider that a bug, though, with it not working in the Azure portal. Given the steps that were taken, and the "Custom Domain" user menus and screens, are identical.

Srinud 2,610 Reputation points Microsoft Vendor

2024-08-05T03:46:51.6+00:00

Hi Jon Kidwell,

We are really glad to know that the issue is resolved for you.

If the issue persists, please contact us, and we'll be glad to assist you further.

Thank you.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Why won't the custom domain name verify?

1 additional answer

Your answer