I have an extension which needs to access Azure Devops resources, right now we can use the old ADO scope 499b84ac-1321-427f-aa17-267ca6975798/.default which gets access to all ADO resources. For some time this was the only option available.
However it seems the current VSCode client app doesn't support these new scopes
It would be great if the VSCode team could add support for these new scopes as well, considering we already have the earlier full scope authorized it shouldn't be that much of a stretch to get permissions for the smaller scopes 😊
Yeah we're in the process of getting this ironed out. They will preauthorize things for us so this will "just work"... but it hasn't happened yet. Let's check up on this in a month. For now, use the big scope.
I have an extension which needs to access Azure Devops resources, right now we can use the old ADO scope
499b84ac-1321-427f-aa17-267ca6975798/.default
which gets access to all ADO resources. For some time this was the only option available.ADO recently added support for smaller scopes, described here https://learn.microsoft.com/en-us/azure/devops/integrate/get-started/authentication/oauth?view=azure-devops#scopes, and the release announcement https://devblogs.microsoft.com/devops/new-azure-devops-scopes-now-available-for-microsoft-identity-oauth-delegated-flow-apps/.
We want to switch over to using the smaller scopes as our extension doesn't usually need the full scope https://github.com/microsoft/ado-codespaces-auth/issues/11.
However it seems the current VSCode client app doesn't support these new scopes![image](https://github.com/microsoft/vscode/assets/2021979/2a83f5db-e18a-40ae-a4f6-76ef8a52ad9f)
It would be great if the VSCode team could add support for these new scopes as well, considering we already have the earlier full scope authorized it shouldn't be that much of a stretch to get permissions for the smaller scopes 😊