Share via


Preventing tenant lockouts

Tenant lockouts can occur when all Global Administrators lose access due to misconfigured policies, expired credentials, or MFA failures. Partners play a critical role in preventing these issues by ensuring tenants are set up with redundancy, recovery options, and lifecycle awareness.

Checklist for Tenant Setup and GDAP Management

  1. Partner should review the GDAP role guidance to find right roles to support the customers.

  2. Partner should proactively review GDAP management features to assure the GDAP relationship with end customer doesn't expire.

  3. Global Admin account redundancy

  4. Break-Glass Accounts

    • Create emergency accounts excluded from Conditional Access policies.
    • Use complex passwords and monitor sign-in activity for these accounts.
    • For more information, see Manage emergency access admin accounts
  5. Conditional Access Policy Design

  6. Emergency Recovery Planning & SSPR

    • Document recovery procedures and ensure all admins know how to access emergency accounts.
    • Encourage customers to configure Self-Service Password Reset (SSPR) and keep recovery methods up to date. For more information, see Self-service password reset deep dive.
  7. Lifecycle Awareness

Note

For any scenarios that involve the Customer tenant, Microsoft must work directly with a Global Administrator on the tenant where access issues are occurring. In most scenarios, if the Partner has the appropriate granular delegated admin permissions (GDAP), they should be able to help the customer without engaging with Microsoft. Customers and Partners should always try recovering access through the Self Service Password Reset tool before contacting Microsoft for support.

Tenant Lockout: Scenarios & Next Steps

Following are some scenarios which Partners & Customers can encounter and steps on how to resolve them.

To contact Microsoft Support: Find Microsoft 365 for business support phone numbers by country or region.

The scenarios are categorized in two broad categories:

  • No GDAP Access or No Partner Relationship - This covers all scenario’s where the customer has no Partner Relationship or No GDAP Relationship with any Partners.
  • GDAP Access – This covers all scenarios where the Partner has GDAP relationship with a customer, Since GDAP relies on Entra ID roles, it's important to understand what review the active roles to determine if a Partner can perform the request action.

Scenario 1.1: Password reset, MFA, or forgot username

GDAP Active with partner having Password reset roles. Customer has lost access to a tenant, needs a password, and the Partner has granular delegated admin privileges (GDAP) with the appropriate roles see Who can reset passwords for role guidance?

Scenario 1.2: Password reset, MFA, or forgot username

GDAP Active with partner having no Password reset roles. Customer lost access to a tenant, needs a password, and the Partner has granular delegated admin privileges (GDAP) but doesn't have the roles required to reset User Password.

Scenario 2.1: Promote user to Global Administrator

Customer user needs to become Global Administrator on a tenant and the Partner has granular delegated admin privileges (GDAP) with the appropriate roles either Global Administrator or Privileged Role Administrator.

  • The Partner should work directly with the customer to promote the user to global administrator. There's no need to engage Microsoft.

Scenario 2.2: Promote user to Global Administrator

Customer needs to become a Global Administrator on a tenant and the Partner doesn't have an Active GDAP Relationship or Doesn't have the right GDAP roles to elevate the user.

  • Customer needs to find another global Administrator on the tenant to elevate this role, if no other Global Administrator is available then the Tenant Owner needs to contact Microsoft for Support.
    • Find Microsoft 365 for business support phone numbers by country or region - Microsoft 365 admin | Microsoft Learn

Scenario 3: End customers GA lost access to their tenant and there's no other GA, but doesn't have a partner with GDAP access or need to establish a new GDAP relationship with a partner

Scenario 4: Conditional Access Policy or Unusual Activity preventing tenant access for all end customers and Partner

Scenario 5: Partner needs to create a Service Request on behalf of the Customer

Scenario 6: Customer is unavailable in the Partner Center Portal

The GDAP partner is unable to see the end customer’s tenant in their Partner Center Dashboard.

Scenario 7: Domain dispute

Customer needs to add their domain to a tenant, but the domain is held in a different Microsoft 365 tenant.

  • If the end customer or partner is unable to remove the domain from the current tenant, the customer or partner needs to submit a Support Request.
  • The end customer Global Administrator should create a Support Request with Microsoft from the tenant where they're trying to add the domain. Or the Partner can open a Service Request from the end customer’s tenant where they're trying to add the domain, on behalf of the customer.