partially provisioned tanent

abdo elbarbary 70 Reputation points
2026-03-12T08:56:06.0533333+00:00

During the provisioning process for a newly purchased Microsoft 365 product, an error occurred that appears to have interrupted the tenant creation. As a result, the provisioning seems to have only partially completed and did not finish successfully.

The designated tenant administrator account is currently unable to sign in to the environment. At the same time, when attempting to create the tenant again using the same details, the system returns a message indicating that the tenant is already registered.

Microsoft Security | Microsoft Entra | Other
0 comments

1 answer

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-03-12T08:56:20.4533333+00:00

    The behavior matches a tenant that exists in Microsoft Entra ID but is currently blocked/inaccessible, not a truly “half-created” tenant. The key is to recover or reactivate the existing tenant rather than trying to create a new one with the same details.

    Use these steps:

    1. Confirm the tenant exists and is the one being hit
      • Try signing in directly to the tenant in the Azure portal using the tenant ID or tenant name in the URL, for example:
        https://portal.azure.com/<TenantId> or https://portal.azure.com/<yourTenantName>.onmicrosoft.com
      • If the tenant is blocked due to inactivity, the sign-in will fail with an error like AADSTS5000225: This tenant has been blocked due to inactivity.
    2. Check if the tenant is blocked due to inactivity
      • When a tenant is blocked for inactivity, sign-in attempts show an error similar to:
        AADSTS5000225: This tenant has been blocked due to inactivity. To learn more about ...
      • Administrators can request reactivation within 20 days of the tenant entering the inactive state. After 20 days in this blocked state, the tenant is permanently deleted and cannot be recovered.
    3. If within 20 days: request tenant reactivation
      • The tenant administrator must contact Microsoft support using the global customer service phone numbers: see the link in the “Tenant inaccessible due to inactivity” article.
      • Provide the tenant ID, primary domain, and explain that the tenant is inaccessible and the admin cannot sign in.
      • Do not open multiple cases for the same issue; wait for the decision on the first case.
    4. If more than 20 days since the tenant was blocked
      • The tenant is deleted and cannot be recovered.
      • In that case, the only path is to use a different tenant (for example, create a new tenant and reconfigure services there). The original tenant name or domain may not be immediately reusable depending on deletion timelines and backend cleanup.
    5. If the admin cannot sign in at all to open a ticket
      • If there is no access to any admin account in that tenant, use the global support phone numbers route as described in the “Tenant inaccessible due to inactivity” guidance.
      • Alternatively, as shown in the Q&A example, a separate temporary tenant can be created (for example via a trial subscription) solely to access the Microsoft 365/Azure admin center and open a support ticket, clearly stating that the problem is with a different, existing tenant that is blocked/inaccessible.

    In summary, the tenant is already registered and likely blocked/inaccessible rather than partially created. The resolution is to have the tenant administrator work with Microsoft support to reactivate or confirm deletion status; tenant recreation with the same details is not possible while the existing tenant object still exists.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.