![]() Instead, they're recorded on the user object and then reported via the administrative portal. For this reason, the errors can't be communicated to you immediately. When you're using group-based licensing, the same errors can occur, but they happen in the background while the Azure AD service is assigning licenses. The problem is immediately reported back to you. For example, there might be an insufficient number of licenses or a conflict between two service plans that can't be assigned at the same time. For example, when you execute the PowerShell cmdlet Set-MsolUserLicense on a user system, the cmdlet can fail for many reasons that are related to business logic. When you assign licenses directly to individual users, without using group-based licensing, the assignment operation might fail. In this article, we explain the reasons why users might end up in this state. Group-based licensing in Azure Active Directory (Azure AD) introduces the concept of users in a licensing error state.
0 Comments
Leave a Reply. |