Merge pull request #6409 from CaityBuschlen/cabuschl-aadgroup-spacing-fix

Update assign-license-bulk.md

Author: PRMerger14

subscriptions/assign-license-bulk.md

@@ -70,10 +70,10 @@ Using this feature makes it easy to stay on top of your subscription assignments
 >
 > The following limitations apply to the use of Azure AD groups for adding subscribers:
 > - Groups must contain at least one member.  Empty groups are not supported.
-> - Groups must have less than 1,000 users 
-> - All users must be in the top level of the group.  Nested groups are not supported
-> - Only trusted agreements are supported
-> - All members of the group must have an email address associated with their Azure AD account
+> - Groups must have less than 1,000 users. 
+> - All users must be in the top level of the group.  Nested groups are not supported.
+> - Only trusted agreements are supported.
+> - All members of the group must have an email address associated with their Azure AD account.
 > - Separate email addresses for notifications are not supported for subscriptions added using Azure AD groups.  
 
 1. Sign in to the Visual Studio Subscriptions Administration Portal at [https://manage.visualstudio.com](https://manage.visualstudio.com).
@@ -101,6 +101,7 @@ Using this feature makes it easy to stay on top of your subscription assignments
 > [!NOTE]
 > If you have already assigned subscriptions individually to users who are subsequently added as part of an Azure AD group, they will be added as part of the group and will no longer be listed individually. However, if the individual subscription is for a different subscription level, they will have two subscriptions.  Example:  If a user has an individual Visual Studio Professional subscription, and they are a member of a group to which you assign Visual Studio Enterprise subscriptions, they will have both.  
 
+<br>
 
 > [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4rvvW]