Can't verify publisher domain for web app

Question

Asking on behalf of the user dataportabiltiy who originally posted on: https://social.msdn.microsoft.com/Forums/en-US/ef2e2ed8-1377-448e-97f8-c5156526ec38/cant-verify-publisher-domain-for-web-app?forum=AzureStack

On our web app, under Publisher Domain for the Branding it says unverified. The instructions to configure the domain say

To verify a publisher domain for {0}
Create a file named microsoft-identity-association.json and paste in the following content. Or, use the link provided to download the content.

{
"associatedApplications": [
{
"applicationId": ""
}
]
}

Download

Host the file at:
https://EXAMPLE.COM/.well-known/microsoft-identity-association.json
Click 'Verify and save domain' below.

When we visit the url, our application id is there, but when we click "Verify and save domain" we get this error:

"Verification of publisher domain failed. Error getting JSON file from https:///.well-known/microsoft-identity-association. The server returned an unexpected content type header value. [gS599]"

The host link returns the right results but it looks like its returning HTML instead of the raw json? Inspecting via a browser shows that the content type response header is: content-type: application/json; charset=utf-8 According to a support page that i'm unable to link, it looks like it needs to be just application/json. Unfortunately, we use an open source library and the only MediaType available is the one we set. It would be non trivial to update this.

Is there anyway to get a manual verification?

Answer 1

Is there any other way to verify our publisher domain?

Webflow says "The /.well-known folder slug, is reserved for hidden files that are stored in this folder to be used for site metadata. It is not possible to name a folder or page this URL in Webflow."

IONOS said talk to Webflow.

Webflow said talk to Microsoft.

Stuck in this crazy loop where neither Microsoft, IONOS, Nylas or Webflow can help. Our whole app is getting held up. Insane.

Answer 2

In my case i discovered the problem was related to a redirect of the base url. eg: mydomain.com --> www.mydomain.com

removing the redirect solved the issue.

Answer 3

This document will help you guys for solving the problem.
https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/add-custom-domain

Answer 4

Hi All,

For fixing this issue, kindly go through the below steps.

1. Verify your custom domain in AAD Directory (Make it primary optional)
2. Follow the branding steps in app your AAD app.
3. Update the file and verify the domain.

Hope this will works.

Thanks
Azad Desai

Answer 5

Posting this here for folks who spent hours, searching different threads of the same issue.
I found this deep into one thread, instead of fighting this issue there is an entirely different way to verify domains.
https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/add-custom-domain Add a custom domain and just update the TXT or MX records in your DNS and Azure will verify the domain that way instantly.
This was simpler and has worked for 3 domains so far.