What’s an Early Adapter Access Level in Online Visual Studio

VSTS automatically assigns them Basic features, if your account has seats available,

or Stakeholder features, if not. -Microsoft Docs

https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/add-organization-users?view=azure-devops&viewFallbackFrom=vsts&tabs=browser

What this effectively means is that VSTS will upgrade your user to the highest available license when the user logs in.

1)Any unassigned Basic License registered to your account automatically get assigned to stakeholders as they log in. (based on Microsoft Docs)

https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/add-organization-users?view=azure-devops&viewFallbackFrom=vsts&tabs=browser

2)The same auto upgrade happens when the user have some sort of MSDN license. (based on personal experience)

So due to the auto upgrade process, trying to keep a user in the Stakeholder License as a means to restrict access might be a losing battle. You might want to modify permissions around this user instead or create a custom security group between Readers and Contributors.

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Harsh Gupta7y ago
I got one more answer.
https://devblogs.microsoft.com/visualstudio/visual-studio-online-early-adoption-period-extended/
0
Rajanikant Hawaldar7y ago
VSTS automatically assigns them Basic features, if your account has seats available,
or Stakeholder features, if not. -Microsoft Docs

https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/add-organization-users?view=azure-devops&viewFallbackFrom=vsts&tabs=browser

What this effectively means is that VSTS will upgrade your user to the highest available license when the user logs in.
1)Any unassigned Basic License registered to your account automatically get assigned to stakeholders as they log in. (based on Microsoft Docs)
https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/add-organization-users?view=azure-devops&viewFallbackFrom=vsts&tabs=browser

2)The same auto upgrade happens when the user have some sort of MSDN license. (based on personal experience)
So due to the auto upgrade process, trying to keep a user in the Stakeholder License as a means to restrict access might be a losing battle. You might want to modify permissions around this user instead or create a custom security group between Readers and Contributors.
0