Azure-docs: Downloaded file has the wrong filename and this doesn't seem to work for personal apps?

[mol]

If downloading the file the filename is set to:
'microsoft-identity-configuration.json'
While the info says it should be named:
'microsoft-identity-association.json'

Additionally, this verification does not seem to work for (old) personal apps despite it being an option under Branding and with the exact json link working in a browser.

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

---

Document Details

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

• ID: 61edea45-b5d6-05b3-33c3-2265ef8cb309
• Version Independent ID: c7d5813c-5cf1-44c3-88ff-3c194d3e44ad
• Content: Configure an application's publisher domain
• Content Source: articles/active-directory/develop/howto-configure-publisher-domain.md
• Service: active-directory
• Sub-service: develop
• GitHub Login: @rwike77
• Microsoft Alias: ryanwi

[SaurabhSharma-MSFT]

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

[mol]

Thanks @SaurabhSharma-MSFT! Let me know if you guys need anything, like the app id or something else :)

[FrankHu-MSFT]

Hey @mol can you provide some more context around the error? In your issue it says :
_If downloading the file the filename is set to:
'microsoft-identity-configuration.json'
While the info says it should be named:
'microsoft-identity-association.json'_

I don't believe the article references downloading anything.

And in regards to the old apps section of your question.
Can you please provide a screenshot of what you're referring to and what you mean by old apps?
There is a section that refers to grandfathered apps : https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-configure-publisher-domain#grandfathered-applications

[mol]

Sure, I've made this image to illustrate both issues.

The downloaded file I'm referring to is there's button on the page with the json content text, that one can click to download a "ready-made" json file - to avoid having to create the file manually and copy/pasting the json into it. But the file has the wrong name. Probably a leftover from the old system of registering apps? In the image you can see the name of the file in Explorer and the name the page says it should have (neither name works as far as the other issue is concerned btw).

The other issue of the verification not working is illustrated by a browser pointing to the file and showing the correct json but the verification still fails. I'm thinking because it's a personal app, or maybe because yes it was grandfathered. It's not a big deal but it would be nice to get it verified since we can.

I'd also love to move the app to a directory to avoid it being a personal app, but as far as I know it's not possible?

[Removed the image as suggested. Can provide it again on request]

[FrankHu-MSFT]

Thanks for the information! We are currently looking into this with the product team and will get back to you as soon as possible,

[mol]

And here's the app listing in Azure, to explain what I mean about an old app. I masked the email because public forum :)

[Removed the image as suggested. Can provide it again on request]

Again, I'd love to move it to the directory but I don't think it's possible - and since it's a live app I don't want to delete it and create another and lose all the authentications.

[FrankHu-MSFT]

Great thank you for that, I have the image, you might want to delete the picture because alot of your app id is showing.

[mol]

As I understand it the app id is not a secret, but you're still suggesting me to remove the images? If you have both and it's fine then I can remove them.

EDIT: I removed them for now.

[FrankHu-MSFT]

@mol I'm following up on this issue, this should be resolved within the next two weeks. Please let me know if this is not resolved within that time period. Also my suggestion would be to submit a support ticket and escalate this issue that way accordingly. If there's any issues with the support ticket, please let me know the support ticket number and I can follow up accordingly. Also please reopen this git issue.

Is there anything else you would like addressed within the scope of this git thread? If not, I will be going ahead and closing this github issue.

[mol]

Thanks @FrankHu-MSFT sounds good, go ahead and close it.