Recover orphaned Azure AD Tenant

Robert Dolca 0 Reputation points
2023-05-14T04:19:10.92+00:00

I have two Azure AD tenants (let's call them A and B). The user john@A was a guest of B and the only Global Administrator of B. While testing I deleted permanently john@A which left B in an orphaned state where I cannot access the AAD tenant anymore. What is the best way to recover and get access to the AAD?

Azure Active Directory
Azure Active Directory
An Azure enterprise identity service that provides single sign-on and multi-factor authentication.
14,623 questions
Azure
Azure
A cloud computing platform and infrastructure for building, deploying and managing applications and services through a worldwide network of Microsoft-managed datacenters.
379 questions
{count} votes

2 answers

Sort by: Most helpful
  1. VasimTamboli 2,170 Reputation points
    2023-05-14T10:53:24.21+00:00

    Recovering an orphaned Azure AD tenant can be a complex process, but there are steps you can take to regain access. Here are some recommendations:

    Contact Microsoft Support: Reach out to Microsoft Support as soon as possible. Explain your situation and provide them with the details of the orphaned Azure AD tenant (Tenant B). They will guide you through the recovery process and assist you in regaining access.

    Provide necessary information: Microsoft Support may ask for various details to verify your identity and ownership of the tenant. Be prepared to provide information such as the tenant name, associated email addresses, subscription details, and any other relevant information to prove your ownership.

    Verify your identity: Microsoft Support will likely require you to verify your identity as the owner of the orphaned tenant. This could involve providing identification documents or answering security questions associated with the tenant.

    Follow Microsoft's guidance: Microsoft Support will provide you with specific instructions on how to proceed with the recovery process. This may involve validating your ownership, re-establishing administrator privileges, or transferring the tenant to a new account.

    Consider legal or contractual implications: If the orphaned tenant is associated with any legal or contractual agreements, it's advisable to consult with legal professionals or review the terms of those agreements. This will help ensure compliance and address any specific requirements related to the recovery process.

    It's important to note that recovering an orphaned Azure AD tenant can take time, and the exact process may vary based on your specific situation. Working closely with Microsoft Support will be crucial in resolving the issue and regaining access to your Azure AD tenant (Tenant B).


  2. Sandeep G-MSFT 7,041 Reputation points Microsoft Employee
    2023-05-15T08:08:59.7766667+00:00

    @Robert Dolca

    In this situation you cannot login to your tenant without help of Microsoft support team.

    There is a dedicated support team who handles these situations.

    If you are the only global admin on the account and are blocked entirely, you can reach out to the Azure Data Protection team to restore access. 866-807-5850

    Also, for the future, you can create an emergency access account (break glass) in Azure AD. This account will help prevent being accidentally locked out of your Azure Active Directory (Azure AD) organization because you can't sign in for any reason.

    https://docs.microsoft.com/en-us/azure/active-directory/roles/security-emergency-access

    Some other support option include;

    AzureSupport

    https://support.microsoft.com/en-us/topic/global-customer-service-phone-numbers-c0389ade-5640-e588-8b0e-28de8afeb3f2

    azcommunity@microsoft.com

    or creating a ticket through a different account:  https://learn.microsoft.com/en-us/microsoft-365/admin/get-help-support?view=o365-worldwide#phone-support

    Let me know if you have any further questions on this.

    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

    0 comments No comments