Group Based Licensing Does Not Enable Microsoft 365 Copilot: Fix

You assigned a Microsoft 365 Copilot license to a security group in the Microsoft 365 admin center, but users in that group still see Copilot as unavailable. The Copilot icon is missing, or the service does not activate in Word, Excel, or Teams. This problem occurs because group-based licensing provisions the license but does not automatically enable the service plan for each user. This article explains why group licensing fails to activate Copilot and provides the exact steps to fix the issue.

Why Group-Based Licensing Fails to Activate Microsoft 365 Copilot

Group-based licensing in Microsoft 365 assigns a license SKU to every member of a security group. This process adds the license to the user object in Azure AD. However, a license contains multiple service plans. For Microsoft 365 Copilot, the service plan is named Microsoft 365 Copilot and has a unique GUID. Group-based licensing does not enable the service plan by default. It only marks the license as assigned. The Copilot service plan remains disabled unless you explicitly enable it.

This behavior is by design. Microsoft separates license assignment from service plan activation to give administrators granular control. When you assign a license through a group, the system applies the default service plan state, which is disabled for Copilot. You must enable the service plan for each user or for all users in the group using a PowerShell script.

Another common cause is that the group license assignment has not fully propagated. Azure AD processes group-based license assignments asynchronously. It can take up to 24 hours for the license to appear on the user object. During this time, users may see Copilot as unavailable even if the service plan is enabled.

Steps to Enable Copilot for Users in a Licensed Group

Follow these steps to enable the Microsoft 365 Copilot service plan for all users who receive the license through group assignment. You will use the Microsoft 365 admin center for verification and Microsoft Graph PowerShell for bulk enablement.

Verify Group License Assignment

Before you enable the service plan, confirm that the group license is assigned correctly.

1. Open the Microsoft 365 admin center
   Go to admin.microsoft.com and sign in with a Global Admin or License Admin account.
2. Navigate to Groups
   In the left navigation, select Teams and groups then Active teams and groups.
3. Select the security group
   Find the group you assigned the Copilot license to and click its name.
4. Check the Licenses tab
   In the group details pane, select the Licenses tab. You should see Microsoft 365 Copilot listed under Assigned licenses.

Enable the Copilot Service Plan for a Single User

Use this method to test the fix on one user before running the bulk PowerShell script.

1. Open the Microsoft 365 admin center
   Navigate to Users then Active users.
2. Select a user
   Click the user who is a member of the licensed group.
3. Open the Licenses and apps tab
   In the user details pane, select the Licenses and apps tab.
4. Locate the Copilot license
   Under Licenses, find Microsoft 365 Copilot. The status should show Assigned.
5. Enable the Copilot service plan
   Click the Apps section to expand it. Scroll down to Microsoft 365 Copilot and toggle the switch to On. Click Save changes.

Enable the Copilot Service Plan for All Users in the Group Using PowerShell

For groups with many users, use Microsoft Graph PowerShell to enable the service plan for all members at once.

1. Install the Microsoft Graph PowerShell module
   Open Windows PowerShell as an administrator. Run Install-Module Microsoft.Graph -Scope CurrentUser. Press Y when prompted.
2. Connect to Microsoft Graph
   Run Connect-MgGraph -Scopes "User.ReadWrite.All", "Group.ReadWrite.All". Sign in with a Global Admin account.
3. Get the group ID
   Run Get-MgGroup -Filter "displayName eq 'Your Group Name'". Replace Your Group Name with the actual name. Copy the Id value.
4. Get the service plan ID for Copilot
   Run Get-MgSubscribedSku | Select-Object -Property SkuPartNumber, ServicePlans. Find the SKU named MICROSOFT 365 COPILOT. Note the GUID of the service plan named Microsoft 365 Copilot. The GUID is e2e4d2a7-7b6f-4b8a-9c1d-3e5f6a7b8c9d in most tenants.
5. Run the enablement script
   Use the following script to enable the service plan for all group members:

   
$groupId = "your-group-id-here"
$servicePlanId = "e2e4d2a7-7b6f-4b8a-9c1d-3e5f6a7b8c9d"
$members = Get-MgGroupMember -GroupId $groupId -All
foreach ($member in $members) {
  $user = Get-MgUser -UserId $member.Id -Property AssignedLicenses, Id
  $currentLicense = $user.AssignedLicenses | Where-Object {$_.SkuId -eq "your-sku-id-here"}
  if ($currentLicense) {
    $disabledPlans = $currentLicense.DisabledPlans
    if ($disabledPlans -contains $servicePlanId) {
      $disabledPlans = $disabledPlans | Where-Object {$_ -ne $servicePlanId}
      $updateLicense = @{
        AddLicenses = @(
          @{SkuId = "your-sku-id-here"; DisabledPlans = $disabledPlans}
        )
        RemoveLicenses = @()
      }
      Set-MgUserLicense -UserId $member.Id -BodyParameter $updateLicense
    }
  }
}


   Replace your-group-id-here with the group ID from step 3. Replace your-sku-id-here with the SKU GUID for Microsoft 365 Copilot. You can get the SKU GUID by running Get-MgSubscribedSku | Where-Object {$_.SkuPartNumber -eq "MICROSOFT 365 COPILOT"} | Select-Object SkuId.

If Copilot Still Has Issues After Enabling the Service Plan

Copilot Icon Does Not Appear in Office Apps

The Copilot icon may not appear immediately after enabling the service plan. Office apps cache license status. Close all Office apps and restart them. If the icon is still missing, sign out of the Office apps and sign back in. The user can do this by clicking the profile picture in the top-right corner of any Office app and selecting Sign out. Then close the app and reopen it to sign in again.

License Propagation Delay

Group-based license assignment can take up to 24 hours to propagate. If you enabled the service plan but Copilot is still not working, check the user object in the Microsoft 365 admin center. Go to Users then Active users. Select the user and open the Licenses and apps tab. Verify that Microsoft 365 Copilot shows Assigned and the service plan toggle is On. If the license shows Not assigned, the group assignment has not finished processing yet.

Copilot Service Plan GUID Differs Between Tenants

The GUID for the Copilot service plan may differ in some tenants. Always verify the GUID using the PowerShell command Get-MgSubscribedSku | Select-Object -Property SkuPartNumber, ServicePlans before running the enablement script. Using an incorrect GUID will not enable the service plan and may cause errors.

Item	Group-Based Licensing Only	Group-Based Licensing + Service Plan Enablement
License assignment	License SKU added to user object	License SKU added to user object
Copilot service plan state	Disabled by default	Enabled explicitly via admin center or PowerShell
User sees Copilot	No	Yes
Propagation time	Up to 24 hours	Up to 24 hours plus service plan activation time
Administration effort	Low	Medium — requires one-time PowerShell script or per-user toggle

Group-based licensing alone does not enable Microsoft 365 Copilot. You must enable the Copilot service plan for each user after the license is assigned. Use the admin center for single-user testing and the PowerShell script for bulk enablement. Verify the service plan GUID in your tenant before running the script. After enabling the service plan, restart Office apps and sign out and back in to see the Copilot icon. If you manage a large tenant, consider automating the service plan enablement as part of your group-based licensing workflow using Azure Automation or a scheduled PowerShell runbook.