Share via

Azure DevOps not recognizing Visual Studio Enterprise license after renewal for some users

Michele Ietri 0 Reputation points
2026-03-19T09:51:45.5866667+00:00

We recently renewed our Visual Studio Enterprise (MAICPP) subscription through PartnerCenter and reassigned licenses to our users via the Visual Studio Subscriptions admin portal.

After the renewal, Azure DevOps is not recognizing the Visual Studio license for some of the reassigned users — they are being treated as Stakeholder users instead of getting the Visual Studio subscriber access level. Other users with the exact same setup are working fine.

Azure DevOps

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Rakesh Mishra 9,680 Reputation points Microsoft External Staff Moderator
    2026-03-19T10:34:41.06+00:00

    Hi Michele,

    Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

    We connected via Private messages and created a request with backend team. As of now as confirmed that issue is resolved. Below is the summary of discussion.

    Below, please find an overview of this support request, for your records:

    Problem statement: 

    You had renewed your Visual Studio Enterprise (MAICPP) subscription through PartnerCenter and reassigned licenses to our users via the Visual Studio Subscriptions admin portal. After the renewal, Azure DevOps is not recognizing the Visual Studio license for some of the reassigned users, and they are being treated as Stakeholder users instead of getting the Visual Studio subscriber access level. Other users with the exact same setup are working fine.

    Assessments and guidance shared:

    Based on my investigations, we did not notice anything that stands out so as to cause such an issue. To be sure if this is not related to a FULL sign-in, we recommended the user(s) to perform a sign-in from an InPrivate browser window and complete the sign in and check if the issue goes away.

    • Close all browsers, including browsers that aren't running Azure DevOps.
    • Open an InPrivate or Incognito browsing session.
    • Sign out from https://aka.ms/vssignout .
    • Sign in to Azure DevOps again with your user account.

    Issue was mitigated as confirmed. Please accept the answer if answer was helpful and let us know in comments if facing any issues still in comments.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.