You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/enterprise-users/licensing-group-advanced.md
+47-37Lines changed: 47 additions & 37 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ Some Microsoft services aren't available in all locations. For group license ass
36
36
37
37
## Use group-based licensing with dynamic groups
38
38
39
-
You can use group-based licensing with any security group, including dynamic groups. Dynamic groups run rules against user resource attributes, such as department, to automatically add and remove members. Each group is assigned the licenses that you want members to receive. If an attribute changes, the member leaves the group, and the licenses are removed.
39
+
You can use group-based licensing with any security group, including dynamic groups. Dynamic groups run rules against user resource attributesto automatically add and remove members. Attributes can be department, job title, work location, or other custom attribute. Each group is assigned the licenses that you want members to receive. If an attribute changes, the member leaves the group, and the licenses are removed.
40
40
41
41
You can assign the attribute on-premises and sync it with Azure AD, or you can manage the attribute directly in the cloud.
42
42
@@ -115,51 +115,61 @@ You can use [Azure AD audit logs](../reports-monitoring/concept-audit-logs.md) t
115
115
- when the system started processing a group license change, and when it finished
116
116
- what license changes were made to a user as a result of a group license assignment.
117
117
118
-
>[!NOTE]
119
-
> Audit logs are available on most blades in the Azure Active Directory section of the portal. Depending on where you access them, filters may be pre-applied to only show activity relevant to the context of the blade. If you are not seeing the results you expect, examine [the filtering options](../reports-monitoring/concept-audit-logs.md#filtering-audit-logs) or access the unfiltered audit logs under [**Azure Active Directory > Activity > Audit logs**](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Audit).
118
+
Audit logs related to group-based licensing can be accessed from the Audit logs in the Groups or Licensing areas of Azure AD or use the following filter combinations from the main Audit logs:
120
119
121
-
### Find out who modified a group license
120
+
-**Service**: Core Directory
121
+
-**Category**: GroupManagement or UserManagement
122
122
123
-
1. Set the **Activity** filter to *Set group license* and select **Apply**.
124
-
2. The results include all cases of licenses being set or modified on groups.
125
-
>[!TIP]
126
-
> You can also type the name of the group in the *Target* filter to scope the results.
123
+

127
124
128
-
3. Select an item in the list to see the details of what has changed. Under *Modified Properties,* both old and new values for the license assignment are listed.
125
+
### Find out who modified a license
129
126
130
-
Here's an example of recent group license changes, with details:
127
+
1. To see the logs for group license changes, use the following Audit log filter options:
128
+
-**Service**: Core Directory
129
+
-**Category**: GroupManagement
130
+
-**Activity**: Set group license
131
+
1. Select a row in the resulting table to view the details.
132
+
1. Select the **Modified Properties** tab see the old and new values for the license agreement.
131
133
132
-

134
+
The following example shows the filter settings listed above, plus the *Target* filter set to all groups that start with "EMS."
133
135
134
-
### Find out when group changes started and finished processing
135
-
136
-
When a license changes on a group, Azure AD will start applying the changes to all users.
137
-
138
-
1. To see when groups started processing, set the **Activity** filter to *Start applying group based license to users*. The actor for the operation is *Microsoft Azure AD Group-Based Licensing* - a system account that is used to execute all group license changes.
139
-
>[!TIP]
140
-
> Click an item in the list to see the *Modified Properties* field - it shows the license changes that were picked up for processing. This is useful if you made multiple changes to a group and you are not sure which one was processed.
136
+

141
137
142
-
2. Similarly, to see when groups finished processing, use the filter value *Finish applying group based license to users*.
143
-
> [!TIP]
144
-
> In this case, the *Modified Properties* field contains a summary of the results - this is useful to quickly check if processing resulted in any errors. Sample output:
145
-
> ```
146
-
> Modified Properties
147
-
> ...
148
-
> Name : Result
149
-
> Old Value : []
150
-
> New Value : [Users successfully assigned licenses: 6, Users for whom license assignment failed: 0.];
151
-
> ```
138
+
To see license changes for a specific user, use the following filters:
139
+
-**Service**: Core Directory
140
+
-**Category**: UserManagement
141
+
-**Activity**: Change user license
152
142
153
-
3. To see the complete log for how a group was processed, including all user changes, set the following filters:
154
-
- **Initiated By (Actor)**: "Microsoft Azure AD Group-Based Licensing"
155
-
- **Date Range** (optional): custom range for when you know a specific group started and finished processing
156
-
157
-
This sample output shows the start of processing, all resulting user changes, and the finish of processing.
158
-
159
-

143
+
### Find out when group changes started and finished processing
160
144
161
-
>[!TIP]
162
-
> Clicking items related to *Change user license* will show details for license changes applied to each individual user.
145
+
When a license changes on a group, Azure AD will start applying the changes to all users, but the changes could take time to process.
146
+
147
+
1. To see when groups started processing, use the following filters:
148
+
-**Service**: Core Directory
149
+
-**Category**: GroupManagement
150
+
-**Activity**: Start applying group based license to users
151
+
1. Select a row in the resulting table to view the details.
152
+
1. Select the **Modified Properties** tab see the license changes that were picked up for processing.
153
+
- Use these details if you're making multiple changes to a group and aren't sure which license processed.
154
+
- The actor for the operation is *Microsoft Azure AD Group-Based Licensing*, which is a system account that is used to execute all group license changes.
155
+
156
+
To see when groups finished processing, change the **Activity** filter to *Finish applying group based license to users*. In this case, the **Modified Properties** field contains a summary of the results, which is useful to quickly check if processing resulted in any errors. Sample output:
157
+
> ```
158
+
> Modified Properties
159
+
> ...
160
+
> Name : Result
161
+
> Old Value : []
162
+
> New Value : [Users successfully assigned licenses: 6, Users for whom license assignment failed: 0.];
163
+
> ```
164
+
165
+
To see the complete log for how a group was processed, including all user changes, add the following filters:
166
+
- **Target**: Group name
167
+
- **Initiated By (Actor)**: Microsoft Azure AD Group-Based Licensing (case-sensitive)
168
+
- **Date Range** (optional): Custom range for when you know a specific group started and finished processing
169
+
170
+
This sample output shows the start and finish of processing the license change.
171
+
172
+

0 commit comments