Learn to use Visual Studio, Visual Studio Online, Application Insights and Team
Foundation Server to decrease rework, increase transparency into your application and increase the rate at which
you can ship high quality software throughout the application lifecycle
As you adopt Visual Studio Online (VSO) and assign licenses to your users you may want to assign the “Eligible MSDN Subscriber” license type to team members. MSDN subscriptions are purchased outside of VSO and assigned to individual users. Before an MSDN subscriber can log in to VSO as an eligible MSDN subscriber, the subscription process must first be completed. The general flow looks like this:
Sometimes though the team member may run into problems after this process. Specifically, they may log in only to see this message below and find that they have limited access to the account ("Stakeholder" license-level access):
Figure 1: (Message when MSDN subscription not found for signed in user)
The team member could be seeing this error for a number of reasons:
1. The specific MSDN subscription may not be eligible for Visual Studio Online accessNot all MSDN subscription types include VSO as a benefit. Please refer to the list of eligible MSDN subscriptions to verify.
2. The MSDN subscription was assigned to the user within the last 48 hoursThere is a delay between MSDN subscription assignments and when VSO will see it \ allow the user to log in. If the subscription was assigned less than 24 hours ago please wait 24-48 hours and have the user try again.
3. The "Software Downloads" benefit has not been provided with the MSDN subscriptionVSO usage is tied to the "Software Downloads" benefit of an MSDN subscription. In order to access VSO when assigned the “Eligible MSDN Subscriber” license type, the user’s MSDN subscription must include this "Software Downloads" benefit. Here’s an example of enabling that benefit via the Volume Licensing Service Center:
4. The wrong email address has been added to the VSO Users HubThis one is important. When an MSDN subscription is assigned to a user they receive an email (usually to their work email address) asking them to associate their new MSDN subscription with a Microsoft account\email address (MSA). This could be the same address where they received the mail or the user could pick a completely different MSA. The MSA they pick to associate with their new MSDN subscription is the one that needs to be added to the VSO Users Hub (https://Contoso.visualstudio.com/_user) and assigned the “Eligible MSDN Subscriber” license. It’s the one they use to manage their MSDN subscription via https://msdn.microsoft.com/subscriptions/manage.
Check with your user to see what MSA they’ve associated with & use to manage their MSDN subscription, and ensure that's the one on the Users Hub. If OrgIDs are being used with VSO the user should associate their OrgID with the MSDN subscription and you can add that to the Users Hub inside VSO.
If all this checks out, have the team member try this:
This will not change your subscription in any way but will essentially reactivate it and with any luck this will allow you to log in to VSO.
I hope you are not having any issues with the "Eligible MSDN Subscriber” license type in VSO, but if you are please run through this checklist. If you are still blocked after checking everything above, please open support case:
Something else to try... None of the above worked for me, so we contacted support and got a solution that worked:
Please have the owner or an admin go to <VSO ACCOUNT>.visualstudio.com/_USER. There they should set your license to STAKEHOLDER and SAVE, then set it back to MSDN and SAVE. Then you try logging in again.