Skip to main content

Connecting Azure DevOps to Axiamatic

Connect Azure DevOps to enable agents to analyze work items, access project data, and identify user membership gaps across platforms.

A
Written by Axiamatic
Updated today

By connecting to an Azure DevOps organization or project, Axiamatic can retrieve work items and related artifacts to assess project health, track progress, and identify issues or risks. Here is a step-by-step guide to connect Azure DevOps to Axiamatic, including the permissions you need to grant and their meanings.

Prerequisites

Required permissions: You must have either Enterprise Admin or Integrations Admin permissions in Axiamatic to access the Integrations page.

Step 1: Create Personal Access Token in Azure DevOps

Before connecting in Axiamatic, you need to create a Personal Access Token (PAT) in Azure DevOps.

  1. Navigate to Azure DevOps:

    • Go to dev.azure.com/{your-organization}

    • Click on your profile icon in the top right

    • Select Personal access tokens

  2. Create new token:

    • Click + New Token

    • Name: Enter a descriptive name (e.g., "axiamatic-integration")

    • Organization: Select your organization from the dropdown

    • Expiration: Set a custom expiration date (recommended: 1 year)

  3. Configure permissions:

    • Select Custom defined under Scopes

    • Required permissions (check "Read" for each):

      • Identity - For user identification and resolving user details

      • Member Entitlement Management - For project membership validation

      • Project and Team - For project access and dashboard display

      • Work Items - For work item data analysis and findings generation

    • Leave all other permissions unchecked

  4. Generate token:

    • Click Create

Important: Copy the generated token immediately and store it securely. You won't be able to view this token again

Step 2: Navigate to Integrations

  1. Log into your Axiamatic account

  2. From the main navigation menu, click Settings, click on Integrations

Step 3: Connect to Azure DevOps

  1. Locate the Project Management section on the Integrations page

  2. Find the Azure DevOps integration card

  3. Click the Connect button

You will now see a pop-up confirming the action. Fill in the required information.

PAT stands for Personal Access Token. The PAT must include scopes for Work Items and Project read

Step 4: Enter the Credentials

  1. In the connection form, fill in the details and paste the Personal Access Token you created in Step 1.

  2. Click Connect to store the connection details

Integration complete! Your Azure DevOps account is now connected and ready to use with Axiamatic. These steps establish the connection and allow Axiamatic to start importing work items and related data from Azure DevOps.

To verify the connection:

  • Check that the Azure DevOps card shows Connected status on the Integrations page

  • Initial data sync may take a few minutes depending on your project size

Troubleshooting

Token expired or invalid:

  • Create a new Personal Access Token following Step 1

  • Update the token in your Axiamatic integration settings

Connection failed:

  • Verify that your organization URL is correct

  • Ensure the Personal Access Token has the required permissions

  • Check that the token hasn't expired

How Axiamatic Uses Your Azure DevOps Data

Collecting this data allows Axiamatic to generate findings such as backlog analytics, development velocity, and potential dependency or compliance issues based on code and work-item information.

Read-only access only - Axiamatic cannot modify, delete, or create any data in your Azure DevOps account.

What Axiamatic accesses:

Work Item Data (Critical)

  • Permission: vso.work

  • What it does: Reads work items, queries, and WIT-related features

  • Used for: Generating findings and insights from work item data

Project Access (Critical)

  • Permission: vso.project

  • What it does: Views the list of projects you have access to

  • Used for: Displaying available projects in the dashboard during connection setup

User Identity (Optional)

  • Permission: vso.identity

  • What it does: Identifies users by name or email

  • Used for: Resolving user details during data analysis

Project Membership (Optional)

  • Permission: vso.memberEntitlementManagement

  • What it does: Reads user membership information for projects

  • Used for: Validating user project access and membership status

Your data security: All permissions are delegated, meaning Axiamatic only accesses information you already have permission to view in Azure DevOps and never makes changes to your account.

For pricing information, demo requests, or assistance, contact us at [email protected]

Did this answer your question?