From 22ac88c9525ad7f0593c0d97a027be8411f6461c Mon Sep 17 00:00:00 2001 From: Nick Meisenheimer Date: Tue, 9 Jun 2026 15:11:31 +0000 Subject: [PATCH] docs(azure-devops): correct auth mechanism from PAT to OAuth Co-Authored-By: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com> --- docs/integrations/source-code-mgmt/azure-devops/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/source-code-mgmt/azure-devops/index.mdx b/docs/integrations/source-code-mgmt/azure-devops/index.mdx index 0b20400c2a296..9abc19edf7231 100644 --- a/docs/integrations/source-code-mgmt/azure-devops/index.mdx +++ b/docs/integrations/source-code-mgmt/azure-devops/index.mdx @@ -16,7 +16,7 @@ Azure DevOps was formerly known as Visual Studio Team Services (VSTS). We recommend creating a dedicated service account on Azure DevOps when installing this integration rather than using a personal user account.

- Since the integration uses personal access tokens for authentication, activities such as comments and work item creation will be attributed to the Azure DevOps user who created the tokens. + Since the integration authenticates via OAuth, activities such as comments and work item creation will be attributed to the Azure DevOps user who authorized the integration.

Using a service account helps maintain proper access control, prevents disruption when team members leave, and ensures consistent attribution for all features across your organization.