Microsoft Adoption an Error Occurred Try Again Later

Skip to main content

Identify and resolve license assignment problems for a group in Azure Active Directory

• Article
• 03/17/2022
• 10 minutes to read

Is this folio helpful?

Feedback will be sent to Microsoft: By pressing the submit push, your feedback volition be used to ameliorate Microsoft products and services. Privacy policy.

In this commodity

Group-based licensing in Azure Agile Directory (Azure AD) introduces the concept of users in a licensing error state. In this article, we explain the reasons why users might end up in this state.

When you assign licenses directly to private users, without using group-based licensing, the assignment operation might fail for reasons that are related to business organisation logic. For case, in that location might be an insufficient number of licenses or a conflict between 2 service plans that can't be assigned at the same time. The trouble is immediately reported back to you.

When you lot're using grouping-based licensing, the same errors can occur, but they happen in the background while the Azure Advertizement service is assigning licenses. For this reason, the errors can't be communicated to you lot immediately. Instead, they're recorded on the user object and so reported via the administrative portal. The original intent to license the user is never lost, but it's recorded in an mistake state for future investigation and resolution.

Notice license assignment errors

To find users in an fault state in a group

1. Open the group to its overview page and select Licenses. A notification appears if there are any users in an error country.

   

2. Select the notification to open a listing of all affected users. You tin select each user individually to see more than details.

   

3. To notice all groups that contain at least i error, on the Azure Active Directory blade select Licenses, and so select Overview. An information box is displayed when groups require your attention.

   

4. Select the box to encounter a listing of all groups with errors. You lot tin select each group for more details.

   

The following sections give a description of each potential problem and the way to resolve it.

Non plenty licenses

Trouble: At that place aren't enough available licenses for one of the products that'southward specified in the group. You demand to either purchase more licenses for the production or costless up unused licenses from other users or groups.

To see how many licenses are available, go to Azure Active Directory > Licenses > All products.

To come across which users and groups are consuming licenses, select a product. Under Licensed users, you run across a listing of all users who accept had licenses assigned directly or via one or more groups. Nether Licensed groups, y'all see all groups that have that products assigned.

PowerShell: PowerShell cmdlets report this mistake as CountViolation.

Conflicting service plans

Problem: 1 of the products that's specified in the group contains a service program that conflicts with some other service plan that'due south already assigned to the user via a dissimilar production. Some service plans are configured in a way that they tin can't be assigned to the same user every bit another, related service plan.

Consider the post-obit case. A user has a license for Office 365 Enterprise E1 assigned direct, with all the plans enabled. The user has been added to a grouping that has the Office 365 Enterprise E3 product assigned to it. The E3 product contains service plans that can't overlap with the plans that are included in E1, so the grouping license consignment fails with the "Alien service plans" fault. In this case, the conflicting service plans are:

• Substitution Online (Program 2) conflicts with Exchange Online (Plan ane).

To solve this conflict, you lot need to disable one of the plans. You lot tin disable the E1 license that's directly assigned to the user. Or, you need to modify the entire group license assignment and disable the plans in the E3 license. Alternatively, yous might decide to remove the E1 license from the user if it's redundant in the context of the E3 license.

The determination almost how to resolve conflicting product licenses e'er belongs to the ambassador. Azure AD doesn't automatically resolve license conflicts.

PowerShell: PowerShell cmdlets report this error every bit MutuallyExclusiveViolation.

Other products depend on this license

Trouble: Ane of the products that'due south specified in the group contains a service programme that must be enabled for some other service programme, in another product, to function. This error occurs when Azure Advertizement attempts to remove the underlying service plan. For example, this can happen when you remove the user from the grouping.

To solve this trouble, y'all need to brand sure that the required plan is nonetheless assigned to users through some other method or that the dependent services are disabled for those users. Later on doing that, you tin properly remove the group license from those users.

PowerShell: PowerShell cmdlets report this error equally DependencyViolation.

Usage location isn't allowed

Problem: Some Microsoft services aren't available in all locations because of local laws and regulations. Before you can assign a license to a user, you must specify the Usage location property for the user. You can specify the location nether the User > Profile > Edit department in the Azure portal.

When Azure AD attempts to assign a group license to a user whose usage location isn't supported, information technology fails and records an mistake on the user.

To solve this problem, remove users from unsupported locations from the licensed group. Alternatively, if the current usage location values don't represent the bodily user location, you tin can change them so that the licenses are correctly assigned next time (if the new location is supported).

PowerShell: PowerShell cmdlets report this error every bit ProhibitedInUsageLocationViolation.

Note

When Azure AD assigns group licenses, any users without a specified usage location inherit the location of the directory. We recommend that administrators set the correct usage location values on users before using group-based licensing to comply with local laws and regulations.

Indistinguishable proxy addresses

If you use Exchange Online, some users in your organization might be incorrectly configured with the aforementioned proxy accost value. When group-based licensing tries to assign a license to such a user, information technology fails and shows "Proxy address is already being used".

After you resolve any proxy address problems for the affected users, brand sure to force license processing on the grouping to make sure that the licenses can at present be applied.

Problem: While updating license assignment on a user or a group, you might see that the Azure Ad Mail and ProxyAddresses attribute of some users are changed.

Updating license consignment on a user causes the proxy address calculation to be triggered, which can change user attributes. To empathise the exact reason of the change and solve the trouble, run across this article on how the proxyAddresses attribute is populated in Azure AD.

LicenseAssignmentAttributeConcurrencyException in audit logs

Problem: User has LicenseAssignmentAttributeConcurrencyException for license consignment in audit logs. When group-based licensing tries to procedure concurrent license assignment of aforementioned license to a user, this exception is recorded on the user. This usually happens when a user is a member of more ane grouping with same assigned license. Azure Advertizing will retry processing the user license and will resolve the issue. There is no action required from the client to gear up this outcome.

More than 1 product license assigned to a group

You can assign more than than one product license to a group. For instance, you can assign Office 365 Enterprise E3 and Enterprise Mobility + Security to a group to easily enable all included services for users.

Azure AD attempts to assign all licenses that are specified in the group to each user. If Azure Advertising tin't assign one of the products because of business organisation logic issues, it won't assign the other licenses in the group either. An example is if in that location aren't plenty licenses for all, or if there are conflicts with other services that are enabled on the user.

Yous can see the users who failed to go assigned and check which products are afflicted by this problem.

When a licensed group is deleted

You must remove all licenses assigned to a group earlier yous can delete the group. Notwithstanding, removing licenses from all the users in the group may accept fourth dimension. While removing license assignments from a group, there can be failures if user has a dependent license assigned or if there is a proxy address conflict event which prohibits the license removal. If a user has a license that is dependent on a license which is being removed due to group deletion, the license assignment to the user is converted from inherited to direct.

For example, consider a group that has Office 365 E3/E5 assigned with a Skype for Business service plan enabled. Also imagine that a few members of the group have Audio Conferencing licenses assigned directly. When the grouping is deleted, group-based licensing will try to remove Function 365 E3/E5 from all users. Because Sound Conferencing is dependent on Skype for Business, for whatever users with Audio Conferencing assigned, group-based licensing converts the Function 365 E3/E5 licenses to directly license assignment.

Manage licenses for products with prerequisites

Some Microsoft Online products you might own are add together-ons. Add-ons crave a prerequisite service plan to be enabled for a user or a grouping before they tin can be assigned a license. With group-based licensing, the organisation requires that both the prerequisite and add-on service plans be present in the aforementioned group. This is done to ensure that any users who are added to the group can receive the fully working production. Allow's consider the following example:

Microsoft Workplace Analytics is an add-on product. It contains a unmarried service plan with the same name. Nosotros can merely assign this service programme to a user, or grouping, when one of the following prerequisites is as well assigned:

• Exchange Online (Program ane)
• Exchange Online (Plan 2)

If we try to assign this product on its own to a group, the portal returns a notification message. If we select the detail details, it shows the post-obit error bulletin:

"License operation failed. Make sure that the group has necessary services earlier adding or removing a dependent service. The service Microsoft Workplace Analytics requires Exchange Online (Programme 2) to be enabled besides."

To assign this addition license to a group, nosotros must ensure that the group besides contains the prerequisite service plan. For example, we might update an existing group that already contains the full Office 365 E3 product, and so add the add-on product to it.

Information technology is also possible to create a standalone group that contains only the minimum required products to make the addition work. Information technology tin can the be used to license only selected users for the add-on production. Based on the previous example, you would assign the post-obit products to the same grouping:

• Function 365 Enterprise E3 with only the Exchange Online (Plan 2) service plan enabled
• Microsoft Workplace Analytics

From now on, any users added to this group eat one license of the E3 product and one license of the Workplace Analytics product. At the same fourth dimension, those users can be members of some other group that gives them the full E3 product, and they nevertheless consume only i license for that product.

Tip

You lot can create multiple groups for each prerequisite service plan. For example, if you apply both Role 365 Enterprise E1 and Part 365 Enterprise E3 for your users, y'all can create two groups to license Microsoft Workplace Analytics: 1 that uses E1 as a prerequisite and the other that uses E3. This lets you lot distribute the add-on to E1 and E3 users without consuming additional licenses.

Force group license processing to resolve errors

Depending on what steps you've taken to resolve the errors, information technology might be necessary to manually trigger the processing of a group to update the user state.

For case, if yous free up some licenses past removing direct license assignments from users, you lot need to trigger the processing of groups that previously failed to fully license all user members. To reprocess a grouping, go to the grouping pane, open up Licenses, and then select the Reprocess push button on the toolbar.

Force user license processing to resolve errors

Depending on what steps y'all've taken to resolve the errors, it might be necessary to manually trigger the processing of a user to update the users land.

For instance, afterwards yous resolve duplicate proxy address problem for an afflicted user, you need to trigger the processing of the user. To reprocess a user, become to the user pane, open Licenses, and then select the Reprocess button on the toolbar.

Side by side steps

To learn more than about other scenarios for license management through groups, run into the post-obit:

• What is grouping-based licensing in Azure Active Directory?
• Assigning licenses to a group in Azure Agile 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 boosted scenarios
• PowerShell examples for grouping-based licensing in Azure Active Directory

Feedback

Submit and view feedback for

whitakerbeyea1975.blogspot.com

Source: https://docs.microsoft.com/en-us/azure/active-directory/enterprise-users/licensing-groups-resolve-problems