Merge pull request #199517 from Justinha/licence-2

Update licensing-groups-assign.md

Author: PRMerger18

articles/active-directory/enterprise-users/licensing-groups-assign.md

@@ -11,7 +11,7 @@ ms.service: active-directory
 ms.subservice: enterprise-users
 ms.topic: how-to
 ms.workload: identity
-ms.date: 12/02/2020
+ms.date: 05/26/2022
 ms.author: curtand
 ms.reviewer: sumitp
 ms.custom: it-pro
@@ -27,7 +27,7 @@ In this example, the Azure AD organization contains a security group called **HR
 > [!NOTE]
 > Some Microsoft services are not available in all locations. Before a license can be assigned to a user, the administrator has to specify the Usage location property on the user.
 >
-> For group license assignment, any users without a usage location specified inherit the location of the directory. If you have users in multiple locations, we recommend that you always set usage location as part of your user creation flow in Azure AD (e.g. via AAD Connect configuration) - that ensures the result of license assignment is always correct and users do not receive services in locations that are not allowed.
+> For group license assignment, any users without a usage location specified inherit the location of the directory. If you have users in multiple locations, we recommend that you always set usage location as part of your user creation flow in Azure AD. For example, configure Azure AD Connect configuration to set usage location. This recommendation makes sure the result of license assignment is always correct and users do not receive services in locations that are not allowed.
 
 ## Step 1: Assign the required licenses
 
@@ -43,6 +43,9 @@ In this example, the Azure AD organization contains a security group called **HR
 
 1. Select a user or group, and then use the **Select** button at the bottom of the page to confirm your selection.
 
+   >[!NOTE]
+   >When assigning licenses to a group with service plans that have dependencies on other service plans, they must both be assigned together in the same group, otherwise the service plan with the dependency will be disabled.
+
 1. On the **Assign license** page, click **Assignment options**, which displays all service plans included in the two products that we selected previously. Find **Yammer Enterprise** and turn it **Off** to disable that service from the product license. Confirm by clicking **OK** at the bottom of **License options**.
 
    ![select service plans for licenses](./media/licensing-groups-assign/assignment-options.png)