search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.13k stars 21.21k forks source link

App Registration - Publisher Domain Registration cannot connect to domain #35934

Closed RobusXLR closed 4 years ago

RobusXLR commented 5 years ago

Reference documentation: How to: Configure an application's publisher domain

To Reproduce:

  1. Navigate: Azure Portal > Azure Active Directory > App Registrations > Branding > Publisher Domain >Verify a new domain
  2. Set the publisher domain e.g: https://example.azurewebsites.net
  3. Download the "microsoft-identity-association.json" file using the download link
  4. Host the file eg: https://example.azurewebsites.net/.well-known/microsoft-identity-association.json
  5. Verify file is reachable using a browser
  6. Click the "Verify and save domain" button

Behaviour: "Verification of publisher domain failed. Unable to connect to /.well-known/microsoft-identity-association. [tncdR]"

Expected Behaviour: Validate the domain

Previous issue #32862 suggested the downloaded file name was incorrect.

I've tried adding a copy of the file with name "microsoft-identity-configuration.json" but this does not work.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

MarileeTurscak-MSFT commented 5 years ago

@RobusXLR Thanks for your feedback! We will investigate and update as appropriate.

frankhu-2021 commented 5 years ago

@RobusXLR I'm following up on this the previous issue suggested that the name was wrong, but the one you downloaded is now correct. i.e. microsoft-identity-association.json is correct.

Did you replace the application id per step 1? https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-configure-publisher-domain#to-verify-a-new-domain-for-your-app

Zhang-lujia commented 4 years ago

Hi guys, I've came into the same problem with "Verification of publisher domain failed. The application was not found". I've checked the applicationId in json file is corrent, and I can use curl to fetch the content hosted in the server. I can provide the file path and appId if necessary. Thanks.

frankhu-2021 commented 4 years ago

Hey @Zhang-lujia it looks like this is happening for multiple people. We're currently looking into the issue and will get back to you a response as soon as possible.

Thanks,

frankhu-2021 commented 4 years ago

@zhang-lujia are can you also share the whole error text? was there anymore text at the end of your error?

frankhu-2021 commented 4 years ago

@Zhang-lujia I'm following up on this issue, can you please respond in regards to the previous replies on this thread? Thanks, - Frank

Also, as this seems to be a reoccurring issue, I can enable a onetime free support ticket for issues related to this publisher domain registration cannot connect to domain issue.

if you're still experiencing this issue, @RobusXLR Please send an email to AzCommunity[at]microsoft[dot]com with a reference to this thread and also your Azure Subscription GUID.

Thanks!

Zhang-lujia commented 4 years ago

@FrankHu-MSFT the error text are "Verification of publisher domain failed. The application was not found. If the application was just created, wait a few minutes and refresh the page. [eZJ1g]"

nhvu1988 commented 4 years ago

I also got the same error text but the last [suffix] string is different. This is on mine

"Verification of publisher domain failed. The application was not found. If the application was just created, wait a few minutes and refresh the page. [feRDf]"

frankhu-2021 commented 4 years ago

Hello, if you are experiencing this issue, please email Please send an email to AzCommunity[at]microsoft[dot]com with a reference to this thread and also your Azure Subscription GUID.

I will enable a one-time free support ticket for issues related to this.

That being said I will be closing out this issue now as the git doc issues are meant for issues with the docs.

Thanks!

frankhu-2021 commented 4 years ago

for future reference, a note has been added to the docs here in regards to this issue : The expected 'Content-Type' header that should be returned is application/json. You may get an error as mentioned below if you use anything else like application/json; charset=utf-8

"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. "

veler commented 4 years ago

Hi @FrankHu-MSFT, I'm facing the same issue. Postman and Chome indicates the content type is "application/json". I tried creating a new user in the portal as you suggested but that doesn't fix the issue. My file is hosted on a Apache server.

shehryar-azam commented 3 years ago

hi @FrankHu-MSFT i am facing Verification of publisher domain failed. Unable to connect to {my-domain}.well-known/microsoft-identity-association. [D90xsMhA4X4+34GCcIXmaz]. but microsoft-identity-association.json is accessible in the browser

mraipsec-mra commented 3 years ago

hi @FrankHu-MSFT i am facing Verification of publisher domain failed. Unable to connect to {my-domain}.well-known/microsoft-identity-association. [D90xsMhA4X4+34GCcIXmaz]. but microsoft-identity-association.json is accessible in the browser

+1

mraipsec-mra commented 3 years ago

@FrankHu-MSFT any workaround available and this is for Azure AD B2C custom domain.

shehryar-azam commented 3 years ago

I was trying to verify the subdomain, after verifying the root domain every thing was fine.

3c71 commented 3 years ago

I tried a year ago and got OP error (Unable to connect). Still getting the same issue today, even though I verified the domain with Azure Active Directory and added TXT record to my DNS entry for the dmain...

Sent an email to suggested support email in hope to resolve this.

ha-sante commented 1 year ago

Sending this here for possible solutions and to any further visitors.

You can see this play out when you use curl to request the file

Hope this helps someone.