fix(integration): vso permissions are wrong#18704
Open
michaelmairegger wants to merge 2 commits into
Open
Conversation
|
@michaelmairegger is attempting to deploy a commit to the Sentry Team on Vercel. A member of the Team first needs to authorize it. |
aldy505
approved these changes
Jul 14, 2026
aldy505
changed the title
aldy505
changed the title
aldy505
enabled auto-merge (squash)
July 14, 2026 00:59
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Azure DevOps integration developer docs to reflect the currently required Azure DevOps permission scopes when configuring the vsts_new app registration, aligning the documentation with the newer configuration introduced around vsts_new.
Changes:
- Replaces outdated Azure DevOps permission scopes with updated ones in the app setup instructions.
bitsandfoxes
approved these changes
Jul 16, 2026
bitsandfoxes
left a comment
bitsandfoxes
left a comment
Contributor
There was a problem hiding this comment.
Thanks for fixing these! Even just based on the Microsoft docs these old identifier indeed don't even exist.
Collaborator
|
@coolguyzone can you help approve the vercel stuff? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DESCRIBE YOUR PR
As when implementing the new
vsts_newconfig because of #4405 I found out that the Graph Permissions you wrote in the documentation are outdated. This PR fixes this.LEGAL BOILERPLATE
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
EXTRA RESOURCES