Unable to add eo-nz.org to Microsoft 365 due to unmanaged Entra directory – error 715-456280

Sandra 0 Reputation points
2026-08-06T03:42:51.97+00:00

We are trying to add the custom domain eo-nz.org to our existing managed Microsoft 365 / Microsoft Entra tenant.

We own and control the domain through Wix and have added the TXT verification record requested by Microsoft. However, domain verification repeatedly fails with error code 715-456280.

Microsoft Support has confirmed that eo-nz.org was previously used for a Microsoft self-service sign-up, which created an unmanaged Microsoft Entra directory.

We need to use eo-nz.org in our existing managed tenant so that we can create ******@eo-nz.org.

Could someone please advise:

  1. What is the correct process to release eo-nz.org from the unmanaged Entra directory?
  2. Should we use an external admin takeover or an internal admin takeover?
  3. Can the takeover be completed directly from our existing managed tenant?
  4. How can we check whether the unmanaged directory contains any Power BI, Power Apps, Power Automate, or other user data before it is removed?
  5. Which Microsoft support team or Azure Portal support category handles unmanaged directory and custom-domain takeover issues?

We have already tried the Microsoft 365 support channel, but the case was redirected to Azure support. The Azure / Entra support request form does not show a suitable Custom Domain, Domain Management, or Unmanaged Directory category.

We control the DNS and can add any additional TXT verification record required.

Microsoft Security | Microsoft Entra | Microsoft Entra ID
0 comments No comments

1 answer

Sort by: Most helpful
  1. Jerald Felix 18,200 Reputation points Volunteer Moderator
    2026-08-07T01:52:07.21+00:00

    Hello Sandra,

    Greetings! Thanks for raising this question in Q&A forum.

    Based on your description, the domain eo-nz.org appears to be associated with an unmanaged Microsoft Entra directory that was created through a self-service signup. When a domain is attached to another directory, even an unmanaged one, it cannot be added to your existing Microsoft 365 tenant until ownership is transferred or the domain is released.

    1. Since you already control the DNS records and Microsoft Support has confirmed the existence of an unmanaged directory, the appropriate path is typically an Admin Takeover of the unmanaged directory.
    2. Before proceeding, review Microsoft's guidance for unmanaged directory takeover and domain management to understand the impact on any existing users or services that may be associated with the domain.
    3. If you need to determine whether the unmanaged directory contains Power BI, Power Apps, Power Automate, or other user data, this generally requires Microsoft support assistance because forum moderators do not have visibility into tenant contents.
    4. Open a support request with Microsoft Entra / Microsoft 365 support and provide:
    • The domain name (eo-nz.org)
    • The verification details proving domain ownership
    • The error code 715-456280
    • Your existing managed tenant ID
      • A request to review the unmanaged tenant and assist with domain takeover or domain release.
    1. If the support portal does not present a suitable category, select the closest Microsoft Entra ID or Domain Management option and request escalation to the team responsible for unmanaged directory and domain ownership investigations.

    The next action is with Microsoft Support, as they can validate domain ownership, review the unmanaged directory, and guide or perform the required backend actions to release or transfer the domain. The forum cannot directly access or modify tenant ownership records.

    If this answer helps you kindly accept the answer which will help others who have similar questions

    Best Regards,

    Jerald Felix.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.