Possible to verify a custom domain on the azure portal when using Microsoft social connection?

[Ralphie]

So I have a custom domain and are using the windowslive/microsoft social connection. This works fine but when going though the login flow, it shows up as “Publisher unverified”.

To fix this you need to host a file and verify your domain:

https: //DOMAIN /.well-known/microsoft-identity-association.json

But, domain is my custom domain which I set to Auth0 using a CNAME, so I can’t host this myself. Is there any way to fix this?

[remus.ivan]

Hi @Ralphie,

Welcome to the Auth0 Community!

In order to avoid this error you’ll have to Become a verified publisher on Microsoft’s end.

Our documentation on Connect Your App to Microsoft Azure AD comes with a section that specifies how to Remove the unverified label :

If you’re using a custom domain, the application consent prompt for Azure AD login may label your domain as “unverified”. To remove the unverified label:

1. Verify the domain for the Auth0 application: Add your custom domain name using the Azure Active Directory portal.

2. Assign the verified domain to the Auth0 application: How to: Configure an application’s publisher domain.

I hope this helps!

Thanks,

Remus

[Ralphie]

Ah, found it, thanks.

I am using the social connection rather than the enterprise AD one, so didn’t look at that documentation, and when adding a new domain as the publisher domain on the azure side it only offers a https challenge rather than the DNS one, so missed that.