Currently when you add a user to a licensing policy the end result is that the licenses defined in that policy, plus any licenses defined in Policies to groups they are Currently a A Member Of will be the end state licenses DRA sets on the object. After this process runs these will then be the Only licenses applied. Any licenses not defined in a policy associated with one of the user's membership, will be removed. The downside to this is that if anyone manipulates the group using native tools, or other methods it could result in a current user being unlicensed for email and having their mailbox disconnected. And if not properly implemented could cause the same issue with bulk of users upon first defining these policies.

Example. You have a policy for Mail license and another policy for Skype license. You inadvertently add the users to the Skype license group policy first, or some other process has natively removed the user from the email license group. The email license for those users will be removed.

DRA needs to make the removal of current licenses an option and default to disabled in order to prevent unexpected negative impact.

by: Scott H. | over a year ago | Integrations