Verify that no license assignments failed by checking each group for users in error state. Hence no additional licenses are required to perform migration. When the same product license is assigned to the user both directly and through a group, only one license is consumed by the user. You can run a PowerShell script to verify how licenses are assigned to users. You will see that they have the same licenses assigned “directly” and “inherited” from groups. You can spot check individual users by looking at their license details. This application can be done by checking the processing state on each group and by checking Audit Logs.
Verify that licenses have been applied to all users in those groups. Leave it running as is.Ĭreate a new licensing group (or decide which existing groups to use) and make sure that all required users are added as members.Īssign the required licenses to those groups your goal should be to reflect the same licensing state your existing automation (for example, PowerShell) is applying to those users. You have existing automation (for example, PowerShell) managing license assignment and removal for users. Any process that may result in removal of licenses should be avoided to remove the risk of users losing access to services and their data. The most important thing to keep in mind is that you should avoid a situation where migrating to group-based licensing will result in users temporarily losing their currently assigned licenses. Before you begin using group-based licensing to manage licenses in your organization, you can use this migration plan to seamlessly replace existing solutions with group-based licensing.
In Azure Active DIrectory (Azure AD), part of Microsoft Entra, you can have licenses deployed to users in your tenant organizations by direct assignment, using PowerShell scripts or other tools to assign individual user licenses.
0 kommentar(er)
