Skip to content

Commit 90a4d04

Browse files
committed
metadata fixes for subscriptions folder
1 parent 30df4af commit 90a4d04

File tree

4 files changed

+16
-19
lines changed

4 files changed

+16
-19
lines changed

subscriptions/docfx.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@
3535
"feedback_github_repo": "MicrosoftDocs/visualstudio-docs",
3636
"feedback_product_url": "https://developercommunity.visualstudio.com/",
3737
"breadcrumb_path": "~/_breadcrumb/toc.yml",
38-
"ms.prod": "visual-studio-windows",
38+
"ms.prod": "visual-studio-family",
3939
"ms.technology": "vs-subscriptions"
4040
},
4141
"fileMetadata": {},

subscriptions/post-migration-onboarding.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,9 +18,9 @@ However, subscriptions are now managed via a new portal called the Visual Studio
1818

1919
You might encounter one of several scenarios:
2020

21-
1. [The primary contact didn’t complete the onboarding process.](#Onboarding-not-completed-by-Primary-Contact)<sup>1</sup>
22-
2. [The primary contact completed onboarding, but didn’t add you as an administrator. Your credentials were listed in VLSC.](#Primary-Contact-did-not-provide-you-administrator-access)
23-
3. [The primary contact completed onboarding, but didn’t add you as an administrator. Your credentials were not listed in the VLSC.](#Your-credentials-were-not-listed-in-VLSC-prior-to-migration)
21+
1. [The primary contact didn’t complete the onboarding process.](#onboarding-not-completed-by-primary-contact)
22+
2. [The primary contact completed onboarding, but didn’t add you as an administrator. Your credentials were listed in VLSC.](#primary-contact-did-not-provide-you-administrator-access)
23+
3. [The primary contact completed onboarding, but didn’t add you as an administrator. Your credentials were not listed in the VLSC.](#Your-credentials-were-not-listed-in-VLSC-prior-to-migration)
2424

2525
<sup>1</sup> If you are the primary or notices contact and didn’t complete the onboarding process, you will need to follow the steps in scenario one in order to set up your organization.
2626

subscriptions/vlsc-admin-faq.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,6 @@ ms.topic: conceptual
88
description: Volume License Service Center Admin Migration FAQs
99
searchscope: VS Subscription
1010
---
11-
1211
# Visual Studio subscriptions administration migration
1312

1413
Over the next few months, changes are coming to the management of Visual Studio subscriptions (formerly MSDN Subscriptions). Today, you can purchase Visual Studio subscriptions through Volume Licensing and the subscriptions are managed within the Volume License Service Center portal (VLSC). A new management portal is being created and Visual Studio subscriptions will be managed in this new portal in the future. In addition to the existing operations provided by the VLSC, the new portal will allow bulk assignment with no limits, tracking and filtering of subscriptions, and the ability to utilize Azure Active Directory (Azure AD) to manage access. The new Visual Studio Administration Portal will be located at: [https://manage.visualstudio.com](https://manage.visualstudio.com).
@@ -31,7 +30,7 @@ This is a massive transition and will be completed in phases until all customers
3130
Your organization does not need to sign up for Azure AD, but you can do so at any time. If you choose to onboard to Azure AD, you can do so at no cost by using the free tier for Azure AD. With Azure Active Directory, you will be protecting your organization with increased security, control, and long-term reliability. However, if you are not ready for Azure AD, you will be able to continue using your Microsoft Accounts (MSAs) as you do today.
3231

3332
### How do I know when my organization will be migrated?
34-
Primary/Notices Contacts will receive an email from us inviting them to complete the onboarding process one week before your organization is migrated. Subscription Managers will also receive an email letting them know that we’ve contacted the Primary/Notices Contacts and provided details on how to help ensure successful onboarding. Learn how to [locate your organization’s Primary/Notices Contacts](#How-do-I-find-out-who-my-Primary-or-Notices-Contact-is?).
33+
Primary/Notices Contacts will receive an email from us inviting them to complete the onboarding process one week before your organization is migrated. Subscription Managers will also receive an email letting them know that we’ve contacted the Primary/Notices Contacts and provided details on how to help ensure successful onboarding. Learn how to [locate your organization’s Primary/Notices Contacts](#how-do-i-find-out-who-my-primary-or-notices-contact-is?).
3534

3635
### Is onboarding different from migration?
3736
Yes. There are two phases in this process. Setting up (or onboarding) your organization in advance of migration ensures that there is no interruption in your work as an administrator. Once we migrate your organization’s information, you will then be able to manage Visual Studio subscriptions in the new portal. If the Primary/Notices Contacts don’t onboard before being migrated, the Subscription Managers will be blocked and will not be able to manage subscriptions until you complete the onboarding process.

subscriptions/vs-tech-support.md

Lines changed: 11 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,13 @@ author: evanwindom
44
ms.author: jaunger
55
manager: lank
66
ms.date: 2/13/2019
7-
ms.topic: Get-Started-Article
7+
ms.topic: conceptual
88
description: Learn how to activate the technical support benefit included with your Visual Studio subscription.
99
searchscope: VS Subscription
1010
---
1111
# Activate and use the Technical Support benefit in Visual Studio subscriptions
1212

13-
The Technical Support benefit in Visual Studio subscriptions is for resolving break-fix issues in **non-production environments** for products that are still in the mainstream support phase of the [support lifecycle](https://support.microsoft.com/lifecycle/search). Visual Studio Enterprise standard and annual cloud subscriptions receive four incidents, while Visual Studio Professional standard and annual cloud subscriptions receive two incidents, for up to 1 year from benefit activation. Benefit activation must occur while the subscription is current.
13+
The Technical Support benefit in Visual Studio subscriptions is for resolving break-fix issues in **non-production environments** for products that are still in the mainstream support phase of the [support lifecycle](https://support.microsoft.com/lifecycle/search). Visual Studio Enterprise standard and annual cloud subscriptions receive four incidents, while Visual Studio Professional standard and annual cloud subscriptions receive two incidents, for up to 1 year from benefit activation. Benefit activation must occur while the subscription is current.
1414

1515
> [!NOTE]
1616
> Microsoft no longer offers Visual Studio Professional Annual subscriptions and Visual Studio Enterprise Annual subscriptions in Cloud Subscriptions. There will be no change to existing customers experience and ability to renew, increase, decrease, or cancel their subscriptions. New customers are encouraged to go to https://visualstudio.microsoft.com/vs/pricing/ to explore different options to purchase Visual Studio subscriptions.
@@ -21,14 +21,15 @@ The Technical Support benefit in Visual Studio subscriptions is for resolving br
2121
**To submit a support request using the benefit, you must first activate it. Follow the steps in the next section to complete the activation.**
2222

2323
## How to activate the benefit
24-
1. Go to https://my.visualstudio.com/Benefits, scroll down to the Support section and on the Technical Support tile click **Chat to activate**.
24+
25+
1. Go to https://my.visualstudio.com/Benefits, scroll down to the Support section and on the Technical Support tile click **Chat to activate**.
2526
> [!div class="mx-imgBorder"]
2627
> ![Technical Support Benefit Tile](_img/vs-tech-support/vs-tech-support-tile.png)
27-
2. This will initiate a chat session with a representative who can create your **Contract ID** and **Access ID** and provide those to you via email so you will have them for your records.
28+
2. This will initiate a chat session with a representative who can create your **Contract ID** and **Access ID** and provide those to you via email so you will have them for your records.
2829

2930
3. To complete the process, you will need to provide the representative with:
3031
- Your country
31-
- Company name
32+
- Company name
3233
- Your full name
3334
- The email address you use to sign in to your subscription
3435
- Your phone number
@@ -37,19 +38,18 @@ The Technical Support benefit in Visual Studio subscriptions is for resolving br
3738
> [!div class="mx-imgBorder"]
3839
> ![Technical Support Benefit Find Subscription ID](_img/vs-tech-support/vs-tech-support-subID-cropped.png)
3940
40-
4. After the process is completed, you will receive an email containing your **Contract ID** and **Access ID** you will use when creating a support incident.
41+
4. After the process is completed, you will receive an email containing your **Contract ID** and **Access ID** you will use when creating a support incident.
4142

4243
> [!NOTE]
4344
> To activate your support account in a language other than English, choose your country from [this list](https://support.microsoft.com/help/14084/activate-support-contract).
4445
45-
4646
## How to submit an incident using your benefit
4747

4848
Once you have your **Contract ID** and **Access ID** set up, you can use it to submit a Tech Support incident [online](http://support.microsoft.com/oas/) (sign-in required), or via the [Azure portal](https://ms.portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview) , or by calling the technical support number for your country. If you submit your incident online, you have the option to have a Microsoft Support Professional call you back.
4949

50-
### Already have your Contract ID and Access ID associated with the account used to sign in to submit a Tech Support incident online?
50+
### Already have your Contract ID and Access ID associated with the account used to sign in to submit a Tech Support incident online?
5151

52-
When submitting an incident online, you will first be prompted to sign in. Sign in with the account you know is associated with your Contract ID and Access ID. Your existing Support Plan benefit associated to your account will appear on Step 3 in the support workflow. Simply select that plan and continue to submit your case. You can submit incidents up to the limit indicated on the plan or until the expiration date of the plan, whichever comes first. Once remaining incidents show “0” or if your plan expires, it is no longer active.
52+
When submitting an incident online, you will first be prompted to sign in. Sign in with the account you know is associated with your Contract ID and Access ID. Your existing Support Plan benefit associated to your account will appear on Step 3 in the support workflow. Simply select that plan and continue to submit your case. You can submit incidents up to the limit indicated on the plan or until the expiration date of the plan, whichever comes first. Once remaining incidents show “0” or if your plan expires, it is no longer active.
5353

5454
> [!div class="mx-imgBorder"]
5555
> ![Technical Support Benefit Incident Submission Step 3](_img/vs-tech-support/vs-tech-support-step3.png)
@@ -81,18 +81,17 @@ When submitting an incident online, you will first be prompted to sign in. Using
8181
> [!div class="mx-imgBorder"]
8282
> ![Technical Support Benefit Incident Submission - Add Contract ID](_img/vs-tech-support/vs-tech-support-add-contract-id.png)
8383
84-
5. After your contract has been added, it will appear under **Select a support plan** at the top. Your plan will contain the term “MSDN” in the title. Choose it, scroll down, and click **Next**.
84+
5. After your contract has been added, it will appear under **Select a support plan** at the top. Your plan will contain the term “MSDN” in the title. Choose it, scroll down, and click **Next**.
8585

8686
> [!div class="mx-imgBorder"]
8787
> ![Technical Support Benefit Incident Submission - Choose Plan](_img/vs-tech-support/vs-tech-support-choose-plan.png)
8888
89-
6. Complete the remaining steps (severity, contact information, review). After you submit your incident, you’ll see a confirmation that your incident has been successfully submitted and you can upload files to the case. A Support Professional will be assigned to your incident and will reach out to you to resolve your issue using the contact method you selected.
89+
6. Complete the remaining steps (severity, contact information, review). After you submit your incident, you’ll see a confirmation that your incident has been successfully submitted and you can upload files to the case. A Support Professional will be assigned to your incident and will reach out to you to resolve your issue using the contact method you selected.
9090

9191
#### Submit an incident by phone
9292

9393
If you would like to create a support incident over the phone, please locate the [Customer Service](https://support.microsoft.com/help/13948/global-customer-service-phone-numbers) phone number for your country. Please ensure you have your Contract ID and Access ID available when you call.
9494

95-
9695
#### Submit an incident within the Azure portal
9796

9897
To use your Visual Studio subscription technical support benefit for issues relating to Azure, you will need to link your Contract ID and Access ID to your Azure subscription.
@@ -117,4 +116,3 @@ To use your Visual Studio subscription technical support benefit for issues rela
117116
<sup>2</sup> *Includes: Imagine Standard.*
118117

119118
Not sure which subscription you're using? Connect to [https://my.visualstudio.com/subscriptions](https://my.visualstudio.com/subscriptions?wt.mc_id=o~msft~docs) to see all the subscriptions assigned to your email address. If you don't see all your subscriptions, you may have one or more assigned to a different email address. You'll need to sign in with that email address to see those subscriptions.
120-

0 commit comments

Comments
 (0)