Assign licenses to users by group membership in Azure Active Directory
This article walks you through assigning product licenses to a group of users and verifying that they're licensed correctly in Azure Active Directory (Azure AD).
In this example, the Azure AD organization contains a security group called HR Department. This group includes all members of the human resources department (around 1,000 users). You want to assign Office 365 Enterprise E3 licenses to the entire department. The Yammer Enterprise service that's included in the product must be temporarily disabled until the department is ready to start using it. You also want to deploy Enterprise Mobility + Security licenses to the same group of users.
Some Microsoft services are not available in all locations. Before a license can be assigned to a user, the administrator has to specify the Usage location property on the user.
For group license assignment, any users without a usage location specified inherit the location of the directory. If you have users in multiple locations, we recommend that you always set usage location as part of your user creation flow in Azure AD (e.g. via AAD Connect configuration) - that ensures the result of license assignment is always correct and users do not receive services in locations that are not allowed.
Step 1: Assign the required licenses
Sign in to the Azure AD admin center with a license administrator account. To manage licenses, the account must be a license administrator, user administrator, or global administrator.
Select Licenses to open a page where you can see and manage all licensable products in the organization.
Under All products, select both Office 365 Enterprise E5 and Enterprise Mobility + Security E3 by selecting the product names. To start the assignment, select Assign at the top of the page.
On the Assign license page, select Users and groups to open a list of users and groups.
Select a user or group, and then use the Select button at the bottom of the page to confirm your selection.
On the Assign license page, click Assignment options, which displays all service plans included in the two products that we selected previously. Find Yammer Enterprise and turn it Off to disable that service from the product license. Confirm by clicking OK at the bottom of License options.
To complete the assignment, on the Assign license page, click Assign at the bottom of the page.
A notification is displayed in the upper-right corner that shows the status and outcome of the process. If the assignment to the group couldn't be completed (for example, because of pre-existing licenses in the group), click the notification to view details of the failure.
When assign licenses to a group, Azure AD processes all existing members of that group. This process might take some time, varying with the size of the group. The next step describes how to verify that the process has finished and determine if further attention is required to resolve problems.
Step 2: Verify that the initial assignment has finished
Go to Azure Active Directory > Groups. Select the group that licenses were assigned to.
On the group page, select Licenses. This lets you quickly confirm if licenses have been fully assigned to users and if there are any errors that you need to look into. The following information is available:
Service licenses that are currently assigned to the group. Select an entry to show the specific services that have been enabled and to make changes.
Status updates of the latest license changes, which are available if the changes are being processed or if processing has finished for all user members.
Information about user license assignments that are in an error state.
See more detailed information about license processing under Azure Active Directory > Users and groups > group name > Audit logs. Check the following activities:
Start applying group based license to users. This is logged when the system picks up the license assignment change on the group and starts applying it to all user members. It contains information about the change that was made.
Finish applying group based license to users. This is logged when the system finishes processing all users in the group. It contains a summary of how many users were successfully processed and how many users couldn't be assigned group licenses.
Read this section to learn more about how audit logs can be used to analyze changes made by group-based licensing.
Step 3: Check for license problems and resolve them
Go to Azure Active Directory > Groups, and find the group that licenses were assigned to.
On the group page, select Licenses. The notification on top of the page shows that there are 10 users that licenses couldn't be assigned to. Open it to see a list of all users in a licensing error state for this group.
The Failed assignments column tells us that both product licenses couldn't be assigned to the users. The Top reason for failure column contains the cause of the failure. In this case, it's Conflicting service plans.
Select a user to open the user's Licenses page. This page shows all licenses that are currently assigned to the user. In this example, the user has the Office 365 Enterprise E1 license that was inherited from the Kiosk users group. This conflicts with the E3 license that the system tried to apply from the HR Department group. As a result, none of the licenses from that group has been assigned to the user.
To solve this conflict, remove the user from the Kiosk users group. After Azure AD processes the change, the HR Department licenses are correctly assigned.
To learn more about the feature set for license assignment using groups, see the following articles:
- What is group-based licensing in Azure Active Directory?
- Identifying and resolving license problems for a group in Azure Active Directory
- How to migrate individual licensed users to group-based licensing in Azure Active Directory
- How to migrate users between product licenses using group-based licensing in Azure Active Directory
- Azure Active Directory group-based licensing additional scenarios
- PowerShell examples for group-based licensing in Azure Active Directory