"email-verified tenant" error when attempting to mark app as publisher verified

jg2 1 Reputation point
2021-02-25T23:11:13.48+00:00

Hi all, Many many thanks for your help. I have a verified MPN account and am attempting to mark a public app as verified using the documentation here. The publisher domain of the app matches the domain of the email address used during the verification process for my MPN account, but when I attempt to add the MPN ID to the app, I get this error:

"This capability is not supported in an email-verified tenant"

Any ideas for how to resolve this? Thanks again!

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
19,561 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. OEC 26 Reputation points
    2022-11-12T01:44:30.9+00:00

    I think I solved this problem. Under the partner.microsoft.com - I had to go to "User Management" and then click a link to become administrator and owner. Once I did that, it presented a screen with the TXT value for DNS entry and after I added it and it converted the account into "Account admin, Referrals admin, MPN partner admin, Owner"

    Then I was able to add verified MPN ID to the application created in the portal.azure.com and now it shows verified badge.

    No answer is needed for this any more at least for me, but this process could certainly be much easier than it is, it is very unintuitive as it is IMHO.

    1 person found this answer helpful.
    0 comments No comments

  2. Vasil Michev 95,581 Reputation points MVP
    2021-02-26T07:24:49.377+00:00

    You probably need to verify the domain using a "traditional" method such as adding the TXT record.

    0 comments No comments

  3. OEC 26 Reputation points
    2022-11-10T19:49:54.943+00:00

    Can you please clarify how this is done, when the MPN ID is already created and the domain shows as "verified" under Azure AD?

    I have the exact same error and I cannot find any obvious place where I can continue verification of the domain, because it already shows as "verified" and the verification was done by uploading a file with a code to ".well-known" folder on the web server.

    0 comments No comments