How to Check Copilot License Conflicts Across Tenants

When your organization uses multiple Microsoft 365 tenants, assigning Copilot licenses can lead to conflicts. A user might hold a Copilot license in one tenant but sign in to another tenant that also has Copilot enabled. This causes authentication failures, missing features, or unexpected billing. This article explains how to detect these conflicts using the Microsoft 365 admin center, PowerShell, and the Entra admin center. You will learn the exact steps to audit license assignments and resolve overlaps.

Why Copilot License Conflicts Occur Across Tenants

Copilot for Microsoft 365 is licensed per user per tenant. A single user can have a user principal name in one tenant but also be invited as a guest user in another tenant. If both tenants assign a Copilot license to that user, the licensing system may reject one assignment. This happens because Microsoft 365 checks the user’s home tenant for the active license. When a guest user tries to use Copilot in the resource tenant, the service looks for the license in the home tenant. If the home tenant does not have Copilot enabled, the user gets an error. The conflict appears as a failed license activation in the resource tenant.

Another common cause is tenant migration or merger. When two organizations merge, users may keep licenses in both tenants for a transition period. The Microsoft 365 licensing service does not automatically deduplicate these assignments. You must manually identify and remove the extra license. Failing to do so can result in double billing and inconsistent Copilot availability.

How the Licensing System Resolves Conflicts

Microsoft 365 uses the home tenant license as the primary source. If a user has a Copilot license in Tenant A and is a guest in Tenant B, Copilot in Tenant B will attempt to use the Tenant A license. If Tenant A does not have Copilot, the user sees a license error. The resource tenant cannot override this behavior. To fix it, you must either assign Copilot to the user in the home tenant or remove the guest user from the resource tenant’s Copilot license assignment.

Steps to Detect and Resolve Copilot License Conflicts

1. Open the Microsoft 365 admin center in each tenant
   Go to admin.microsoft.com and sign in with Global Admin credentials. Navigate to Billing > Licenses. Select the Copilot product SKU. Review the list of assigned users. Write down the user principal names for users who might also exist in another tenant.
2. Check the Entra ID guest user list in each tenant
   Open the Microsoft Entra admin center. Go to Identity > Users > All users. Filter by User type and select Guest. Compare this list with the Copilot license assignments from step 1. Any guest user who has a Copilot license in this tenant is a potential conflict.
3. Run a cross-tenant license audit with PowerShell
   Install the Microsoft Graph PowerShell module if not already present. Run the following command to connect to each tenant: Connect-MgGraph -Scopes User.Read.All, LicenseAssignment.Read.All. For each tenant, run Get-MgUser -All | Where-Object {$_.AssignedLicenses.SkuId -eq 'YOUR_COPILOT_SKU_ID'}. Replace YOUR_COPILOT_SKU_ID with the Copilot SKU ID for your region. Compare the output across tenants to find duplicate user principal names.
4. Review sign-in logs for license errors
   In the Entra admin center, go to Identity > Monitoring & health > Sign-in logs. Add a filter for Status and select Failure. Look for error code 53003 or 9002313, which indicate license assignment failures. Click each entry to see the user and tenant details. This helps identify which tenant is blocking Copilot for a specific user.
5. Remove the conflicting license from the resource tenant
   If a guest user should use Copilot from their home tenant, remove the Copilot license from the resource tenant. In the Microsoft 365 admin center, go to Billing > Licenses, select the Copilot product, choose the user, and click Remove license. Confirm the change. The user will now use their home tenant license when accessing Copilot in this tenant.
6. Verify the fix
   Ask the affected user to sign out and sign back into Microsoft 365. Test Copilot in Word or Teams. If the feature works, the conflict is resolved. If not, repeat steps 1 through 5 to check for additional duplicate assignments.

If Copilot Still Has Issues After the Main Fix

Copilot License Shows as Inactive in the User’s Profile

After removing the conflicting license, the user might see a message that Copilot is not available. This usually means the license propagation took longer than expected. Wait 30 minutes, then ask the user to restart their device. If the issue persists, go to Microsoft 365 admin center > Users > Active users, select the user, and click Licenses and apps. Verify that Copilot appears as assigned. If not, reassign the license from the home tenant.

Copilot Returns Generic Output Instead of Tenant-Specific Data

When a guest user accesses Copilot in a resource tenant, the AI may not have access to the resource tenant’s Microsoft Graph data. This happens because Copilot uses the home tenant’s data context. To give the user access to resource tenant data, you must assign a Copilot license in the resource tenant and configure data permissions. This is a separate license assignment, not a conflict. Ensure you are not confusing a licensing conflict with a data access limitation.

PowerShell Script Fails with Authentication Error

If the Graph PowerShell script returns an error like Insufficient privileges to complete the operation, the admin account lacks the required permissions. Use Global Admin or Privileged Role Admin credentials. Run Connect-MgGraph -Scopes User.Read.All, LicenseAssignment.Read.All, Organization.Read.All to grant the needed scopes. If the error persists, check whether multi-factor authentication is blocking the connection. Use an app password or a conditional access exception for the script.

Copilot License Conflict Detection Methods Across Tenants

Item	Microsoft 365 Admin Center	Microsoft Graph PowerShell	Entra Sign-in Logs
Description	GUI-based license assignment review per tenant	Automated cross-tenant comparison of assigned licenses	Failure log analysis for license-related error codes
Setup time	5 minutes per tenant	15 minutes for script creation and execution	10 minutes for log filtering and review
Best for	Small organizations with 2-3 tenants	Large enterprises with 10+ tenants	Diagnosing active license errors
Requires Global Admin	Yes	Yes	Yes
Can detect duplicates automatically	No	Yes with custom script logic	No

Use the admin center for quick checks. Use PowerShell for systematic audits across many tenants. Use sign-in logs to troubleshoot active errors.

You can now identify Copilot license conflicts across tenants using the Microsoft 365 admin center, PowerShell, and Entra sign-in logs. Start by reviewing license assignments in each tenant. Then run the PowerShell script to find duplicate user principal names. Finally, remove conflicting licenses from resource tenants to ensure Copilot works consistently. For ongoing monitoring, set up a scheduled PowerShell script that runs weekly and emails a report of any duplicate assignments. This prevents billing surprises and keeps Copilot accessible to all authorized users.