![pipesim could not check out a license pipesim could not check out a license](https://www.software.slb.com/-/media/software-v2/software/images/related-image-thumbnails_313x296/ofm/ofm.jpg)
Users might need one license but not another, or might need both. It uses extensionAttribute1 to store a string value representing the licenses the user should have. ExampleĬonsider the example of an on-premises identity management solution that decides which users should have access to Microsoft web services. When the attribute is changed, the user leaves the groups and the licenses are removed. Licenses are assigned to the user shortly after they are added to the group. You can assign the attribute on-premises and sync it with Azure AD, or you can manage the attribute directly in the cloud. Each group is populated by a rule adding users by their attributes, and each group is assigned the licenses that you want them to receive. Dynamic groups run rules against user resource attributes to automatically add and remove users from groups.įor example, you can create a dynamic group for some set of products you want to assign to users.
![pipesim could not check out a license pipesim could not check out a license](https://www.software.slb.com/-/media/software-media-items/software/images/image-viewer/pipe_netw_anal_net/pipe_netw_anal_net_1_xl.jpg)
![pipesim could not check out a license pipesim could not check out a license](https://i.ytimg.com/vi/GGAA1pnPTX0/sddefault.jpg)
You can use group-based licensing with any security group, which means it can be combined with Azure AD dynamic groups. Use group-based licensing with dynamic groups We recommend that you always set usage location as part of your user creation flow in Azure AD (for example, via AAD Connect configuration) - that will ensure the result of license assignment is always correct, and users do not receive services in locations that are not allowed. Group license assignment will never modify an existing usage location value on a user.