Merge pull request #6475 from MicrosoftDocs/master637511046219972539

For protected CLA branch, push strategy should use PR and merge to target branch method to work around git push error

Author: ghogen

subscriptions/admin-responsibilities.md

@@ -4,7 +4,7 @@ author: evanwindom
 ms.author: v-evwin
 manager: cabuschl
 ms.assetid: b26b31dc-1eeb-4871-9ce6-2c980e703f1e
-ms.date: 02/02/2021
+ms.date: 03/11/2021
 ms.topic: conceptual
 description:  Learn about responsibilities of subscriptions admins.
 ---
@@ -27,7 +27,7 @@ Visual Studio subscriptions allow developers to install and use software to desi
 | User-based licensing                     | MSDN Platforms and all levels of Visual Studio subscriptions are licensed on a per-user basis. Each development team member that will interact (install, configure, or access) with the software included with these products and services requires their own Visual Studio subscription.                                                                                                                                                                                                                                                                                                                                  |
 | Unlimited installations                  | Each licensed user may install and use the software on any number of devices to design, develop, test, evaluate, and demonstrate software. The exception is Microsoft Office, which is licensed for one desktop. Visual Studio-licensed software can be installed and used at work, home, school, and on devices at a customer’s office or on dedicated hardware hosted by a third party.                                                                                                                                                                                                                                  |
 | Not intended for production environments | Visual Studio subscriptions software is not licensed for production environments, including any environment accessed by end users for more than acceptance testing or feedback, an environment connecting to a production database, supporting disaster recovery or production backup, or used for production during peak periods of activity. Exceptions to this include specific benefits for certain subscription levels, outlined in the [Visual Studio Licensing White Paper](https://aka.ms/vslicensing).                                                                                            |
-| License reassignment                     | When a user leaves a team and no longer requires a license, you may reassign the license after 90 days have passed. When you reassign a license, any product keys that were already used will still be available but will not be replaced. For organizations that have Enterprise Agreements (EA), any benefits that were used by the original user, such as Pluralsight training, will be reset.                                                                                                                                                                                                                                                 |
+| License reassignment                     | When a user leaves a team and no longer requires a license, you may reassign the license to another user if at least 90 days have passed since it was assigned to the previous user. When you reassign a license, any product keys that were already used will still be available but will not be replaced. For organizations that have Enterprise Agreements (EA), any benefits that were used by the original user, such as Pluralsight training, will be reset.                                                                                                                                                                                                                                                 |
 | Exception for end users                  | At the end of a software development project, end users typically review an application and determine whether it meets the necessary criteria for release. This process is called user acceptance testing (UAT). Team members such as a business sponsor or a product manager can act as proxies for end users. End users who do not have a Visual Studio subscription may access the software for UAT if use of the software otherwise complies with all Visual Studio licensing terms. It is rare that someone whose primary role is designing, developing, or testing the software would also qualify as an “end user”. |
 
 ## See also

subscriptions/anonymization.md

@@ -4,7 +4,7 @@ author: evanwindom
 ms.author: v-evwin
 manager: cabuschl
 ms.assetid: ce5fc8a4-484c-4df6-97c3-cb60174fb66b
-ms.date: 02/20/2020
+ms.date: 03/11/2021
 ms.topic: conceptual
 description:  Learn how subscriber data is anonymized when access to subscriptions is lost.
 ---
@@ -30,7 +30,9 @@ Events that render a subscription unusable to a subscriber will trigger anonymiz
 A:  No.  The anonymization is in response to an event that causes the loss of access to the subscription, but does not cause the lack of access.
 
 ### Q:  I'm an admin for my organization's subscriptions.  If one of my subscriber's information is anonymized, can that subscription be reassigned to another user?
-A:  Yes -- As long as the subscription has not expired, it can be reassigned to another subscriber.
+A:  Yes.  A subscriptions can be reassigned if these criteria are met:
+- The subscription has not expired
+- A minimum of 90 days have passed since the subscription was last assigned to a subscriber.  For example, if a subscription was assigned to a subscriber on June 1, it cannot be reassigned until at least August 30.
 
 ### Q: How can I prevent anonymization caused by deleting a sign-in email address?
 A:  There are two ways to prevent the issue:

subscriptions/delete-license.md

@@ -10,7 +10,9 @@ description:  Learn how admins can delete subscription assignments in the Visual
 ---
 
 # Delete assignments in Visual Studio subscriptions
-When a subscriber no longer requires a Visual Studio subscription, such as when they leave the company, complete a project, or switch to a new job role, you can remove their subscription and  assign it to someone else. Please note that when you reassign a subscription, not all the subscriber benefits will be reset.  The new user will be able to claim any unclaimed keys and view previously claimed keys but claim limits are **not** reset.  For organizations that have Enterprise Agreements (EA), any benefits that were used by the original user, such as Pluralsight training, will be reset. 
+When a subscriber no longer requires a Visual Studio subscription, such as when they leave the company, complete a project, or switch to a new job role, you can remove their subscription and assign it to someone else. Please note that when you reassign a subscription, not all the subscriber benefits will be reset.  The new user will be able to claim any unclaimed keys and view previously claimed keys but claim limits are **not** reset.  For organizations that have Enterprise Agreements (EA), any benefits that were used by the original user, such as Pluralsight training, will be reset. 
+> [!Important]
+> Subscriptions can only be assigned to different users if a minimum of 90 days have passed since the subscription was last assigned.  For example, if a subscription was assigned to a subscriber on June 1, it cannot be assigned to a new subscriber until at least August 30. 
 
 Watch this video or read on to learn how to delete assignments.