Skip to content

Commit a341e1e

Browse files
committed
group-scenario-fixing
1 parent 6e8dccc commit a341e1e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/active-directory/enterprise-users/licensing-group-advanced.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,9 +48,9 @@ Licenses are assigned to the user shortly after they're added to the group. When
4848

4949
Consider the example of an on-premises identity management solution that decides which users should have access to Microsoft web services. It uses `extensionAttribute1` to store a string value representing the licenses the user should have. Azure AD Connect syncs it with Azure AD.
5050

51-
Users might need one license but not another, or might need both. Here's an example, in which you're distributing Microsoft 365 E5 and Enterprise Mobility + Security (EMS) licenses to users in groups:
51+
Users might need one license but not another, or might need both. In this example, you're distributing Microsoft 365 E5 and Enterprise Mobility + Security (EMS) licenses to users in groups.
5252

53-
#### Microsoft 365 E5
53+
Users that need the Microsoft 365 E5 license will be added to the *Microsoft365_E5* group. User that need the Enterprise Mobility + Security license will be added to the *EMS* group. A third group is created for users that need both licenses.
5454

5555
![Screenshot of Microsoft 365 E5 attribute in dynamic membership rules.](./media/licensing-group-advanced/dynamic-groups-rules-E5.png)
5656

0 commit comments

Comments
 (0)