Azure DevOps Setup
Connect an Azure DevOps organization, configure its shared PAT and enable repositories for pull-request reviews.
Prerequisites
Use a Microsoft account accepted by your deployment's Azure sign-in and belonging to the intended Azure DevOps organization. You must be allowed to create an organization-scoped PAT with the required access. The PAT owner's provider permissions still limit what it can do.
Setup Steps
Step 1: Sign In with Azure DevOps OAuth
Choose Azure DevOps on the Codity Platform sign-in page and complete Microsoft authorization. Follow the welcome flow and organization selection. Azure repositories belong to the selected organization; there is no personal-repository scope.
Step 2: Create a Personal Access Token
In that Azure DevOps organization, open User settings → Personal access tokens → New Token. Select the organization and the scopes displayed by Codity's Required token scopes panel:
- Code (Read & Write)
- Build (Read & Execute)
- Work Items (Read & Write)
- Member Entitlement Management (Read)
Choose an expiration permitted by your organization. Copy the created PAT and keep it private. For provider token creation and policy restrictions, see Microsoft's PAT guide.
Step 3: Configure Token in Codity
Complete the Organization-wide access token screen at /azure/pat. Paste the PAT into Token under Organization PAT and choose Save token. Codity validates the token before saving.
The PAT is shared for the selected organization. After one is configured, only the account that configured it or an authorized account admin can replace it. Other members can see a read-only status. Ask that administrator to rotate it if you cannot edit it. The token needs the Member Entitlement Management scope for seat-related user lookup.
Step 4: Enable Repositories
Open Repositories → Manage Repositories. On Azure DevOps Repositories, check the selected organization, find the desired project/repository and choose Enable. Codity configures the provider notification integration. Resolve any returned permissions error before treating setup as complete.
Step 5: Verify Setup
Confirm the repository is enabled and appears in the correct account. Open a test PR targeting an eligible branch and check for Codity review activity. If no review appears, check account access, PAT validity, provider service-hook deliveries and review triggers. Review duration varies.
Azure DevOps Server (On-Premises) Setup
This guide describes the platform's Azure DevOps organization flow. The current setup screen does not provide the server-URL configuration described by older guides. Do not assume an on-premises Server installation can be connected through an undocumented Settings field; confirm deployment support with your administrator.
Troubleshooting
Cannot create a PAT: your organization may restrict issuance, scopes or lifetime. Ask the organization's Azure DevOps administrator.
Missing Member Entitlement Management: regenerate the PAT with that displayed scope and have its owner or account admin save it.
Cannot replace an organization PAT: ask the original configuring account or an account admin. Signing in as another member does not authorize replacement.
Microsoft Sign-In Fails Before the Dashboard Opens
Check the account selected in Microsoft's sign-in flow and the returned error. Your deployment's Microsoft application and tenant configuration determine which identities it accepts. If the error says the account type or tenant is unsupported, ask the deployment administrator to verify that configuration and use an identity it accepts.
Do not infer support solely from an email address or assume all deployments accept only work accounts. A PAT entered later cannot fix an OAuth sign-in failure.
PAT Saves but Repository Enabling Fails
- Verify the active organization and the organization selected when the PAT was issued.
- Confirm the PAT owner's access to the affected project/repository, not just membership in the organization.
- Check the token scopes against the current Required token scopes panel.
- Inspect the error from Enable, including any provider service-hook permission denial.
- Have the appropriate provider/account administrator resolve the missing access, then retry and confirm the repository is enabled.
A token's validity does not establish that its owner can configure notifications for every project. Replacing the shared organization PAT may affect other users, so coordinate planned changes with its configuring user or account administrator.
Enabled Repository Receives No Review
Check automatic-review trigger, target-branch scope and opt-out markers. Inspect available Azure service-hook delivery results and the Codity run status. Distinguish a notification failure from an event that arrived but was skipped or blocked by usage/authorization checks.
For example, a PR into develop will not pass a target-branch filter configured only for main, even if the organization PAT is valid. Correct the branch configuration or request an authorized manual review with @codity review.
Best Practices
Keep ownership and expiration of the shared PAT clear. Validate the replacement before relying on it for reviews or seat management.
Use a descriptive token name that identifies its purpose and organization. Track expiration according to your organization's policy, and verify an eligible PR review after a planned rotation. See API Keys and Tokens for replacement and revocation procedures.

