Merge pull request #13233 from rigel512/VSS_signinupdates

VSS subscriber email change

Author: Stacyrch140

subscriptions/personal-email-sign-ins.md

@@ -3,22 +3,22 @@ title: Personal emails for Visual Studio subscriptions in VLSC
 author: joseb-rdc
 ms.author: amast
 manager: shve
-ms.date: 09/16/2024
+ms.date: 10/11/2024
 ms.topic: conceptual
-description:  Visual Studio Subscriptions – Why Am I Seeing Hotmail or Gmail Addresses for My Subscribers?
+description:  Visual Studio Subscriptions – Why do I see personal accounts for my subscribers?
 ---
 
-# Visual Studio subscriptions – Why do I see personal accounts for my subscribers?
+# Why do I see personal accounts for my subscribers?
 
-After companies migrated from the Volume Licensing Service Center (VLSC) to the new Visual Studio [Subscriptions Admin Portal](https://manage.visualstudio.com), admins were surprised to find that the “Sign-in Email Address” for some subscribers shows a personal email address like Hotmail or Outlook. 
+After companies migrated from the Volume Licensing Service Center (VLSC) to the new Visual Studio [Subscriptions Admin Portal](https://manage.visualstudio.com), admins were surprised to find that the "Sign-in Email Address" for some subscribers shows a personal email address like Hotmail or Outlook. 
 
 ## Cause
 
-This scenario occurs due to sign-in processes that were associated with the legacy MSDN subscriber experience. Users were migrated from the Volume License Service Center (VLSC) to the Visual Studio Subscriptions Admin Portal without modifications. Admins might not know that users are using personal accounts to access their subscription benefits. Before the Visual Studio subscriber migrations, which were completed in 2016, there were two actions required to successfully use a Visual Studio Subscription:
-1. The admin “assigned” the subscription to an individual subscriber, using their work or school email address.
-2. The subscriber “activated” the subscription.
+This scenario occurs due to sign-in processes that were associated with the legacy Microsoft Developer Network (MSDN) subscriber experience. Users were migrated from the Volume License Service Center (VLSC) to the Visual Studio Subscriptions Admin Portal without modifications. Admins might not know that users are using personal accounts to access their subscription benefits. Before the Visual Studio subscriber migrations, which were completed in 2016, there were two actions required to successfully use a Visual Studio Subscription:
+1. The admin "assigned" the subscription to an individual subscriber, using their work or school email address.
+2. The subscriber "activated" the subscription.
 
-During the subscriber activation process, a Microsoft Account (MSA) was required to sign-in. If the subscriber didn’t attempt to make their work or school account (example: `[email protected]`) an MSA, they could create a new MSA or use an existing one. Use of a personal email resulted in their “Sign-in Email Address” being different than their “Assigned to Email Address."
+During the subscriber activation process, a Microsoft Account (MSA) was required to sign-in. If the subscriber didn’t attempt to make their work or school account (example: '[email protected]') an MSA, they could create a new MSA or use an existing one. Use of a personal email resulted in their "Sign-in Email Address" being different than their "Assigned to Email Address."
 
 > [!NOTE]
 > The modern subscriber experience on [https://my.visualstudio.com](https://my.visualstudio.com?wt.mc_id=o~msft~docs) supports both Work/School and Microsoft Account (MSA) identity types.
@@ -41,12 +41,29 @@ You can also use the **Search Directory** to correct the errors or fill in missi
 
 Next select on **Continue** which takes you to a list of the changes to take place. If you agree, select **Save** and the changes are made. Your subscriber will also get a message informing them of the change the next time they sign in to their subscription. Notice that only the two subscribers that were matched in the Microsoft Entra ID appear in this list. In our example, since Frederick didn't have a corresponding address in the Microsoft Entra ID, the Microsoft account (MSA) wasn't matched to a work account. 
 
+**What happens when I update a Visual Studio subscriber's sign-in address?**
+
 > [!NOTE]
-> When you edit the sign in email address this only updates the email used by the subscriber to sign in to their subscription on https://my.visualstudio.com. If the subscriber has already activated benefits such as Azure or Pluralsight using the other email address, they will need to continue to use those email addresses to access them. For any new benefits that they access, they should use the new email address. 
+> When you edit the sign in email address this updates the email used by the subscriber to sign in to their subscription on https://my.visualstudio.com. Subscribers can use the newly updated email address going forward when activating benefits. For previously activated benefits, continue reading below for more information about which email address a subscriber should use.
+
+## Impact on Benefits
+
+If you, the admin, changed the sign-in email address on a subscription, subscribers should use this new email address for any new benefit activations. Refer to the chart below for insights on any currently active benefits that might be impacted.
+
+| Benefit Name | Use updated email address? | If subscriber hasn't activated the benefit yet | If subscriber activated with the previous sign-in email address | If the subscriber is using an alternate email address |
+|--------------|----------------------------|-------------------------------------------------|-----------------------------------------------------------------|------------------------------------------------------|
+| **Power BI Pro**<br>**Microsoft 365 apps for Enterprise**<br>**PARASOFT Virtualize/SOAtest Professional Desktop**<br>**WhiteSource Bolt**<br>**DataCamp - 3-month subscription**<br>**CODE Magazine** | No  | Use new sign-in email address to activate. | Continue using the old email address for access. | N/A |
+| **Pluralsight**<br>**LinkedIn Learning**<br>**Dometrain**<br>**DevForge** | No | Access can be created using any email address. Once it's created, it will not change even if an admin updates the subscriber's sign in email. | Access can be created using any email address. Once it's created, it will not change even if an admin updates the subscriber's sign in email. | Access can be created using any email address. Once it's created, it will not change even if an admin updates the subscriber's sign in email. |
+| **Visual Studio LIVE! Events discount** | No | No email address is needed. | No email address is needed. | No email address is needed. |
+| **GitHub Enterprise** | No\* | This benefit is set up by the GitHub admin in your org. Subscribers should use the email address where their invitation was sent. | This benefit is set up by the GitHub admin in your org. Subscribers should use the email address where their invitation was sent. | This benefit is set up by the GitHub admin in your org. Subscribers should use the email address where their invitation was sent. |
+| **Visual Studio IDE**<br>**Azure DevOps**<br>**Azure dev/test monthly credit**<br>**Azure Dev/Test PAYG subscription (Unlimited)** | Yes | Use new sign-in email address to activate. | Use the new sign-in email address to continue accessing. | Continue using alternate email address. |
+| **TFS License**<br>**TFS CAL**<br>**Visual Studio App Center**<br>**Windows Developer Account**<br>**Microsoft 365 Developer**<br>**Microsoft R Server**<br>**Most Microsoft Server trials**<br>**Microsoft Office Pro Plus 2021, Project, Visio**<br>**Windows, Windows Server, Windows Embedded, SQL Server**<br>**SharePoint, Exchange, Dynamics & other MS**<br>**Technical Support**<br>**Developer Community Forums**<br>**Azure Community Forum**<br>**Online Concierge Chat**<br>**Code Search (included as Basic license)**<br>**Exploratory Testing (included in Basic license)**<br>**Azure Artifacts**<br>**C# Dev Kit for VS Code**<br>**Azure Test Plans** | Yes  | Use new sign-in email address to activate. | Use the new sign-in email address to continue accessing. | N/A |
+
+\* *Note: This benefit is set up by the GitHub Admin. To determine the email address to use, get in touch with the GitHub Admin.* 
 
 ## Support resources
 
-For assistance with administration of Visual Studio Subscriptions, contact [Visual Studio subscriptions support](https://aka.ms/vsadminhelp).
+For assistance with the administration of Visual Studio Subscriptions, contact [Visual Studio subscriptions support](https://aka.ms/vsadminhelp).
 
 ## See also