Skip to main content

Azure DevOps Integration Setup

Complete guide for connecting your Azure DevOps repositories to ProdE's knowledge layer.

Overview​

Azure DevOps integration allows ProdE to access your Azure DevOps repositories and create intelligent knowledge layers for your selected codebases. Connection is done using a Personal Access Token (PAT).

Prerequisites​

  • Azure DevOps Account: Active Azure DevOps account with repository access
  • Organization Access: You must have access to the Azure DevOps organization you want to connect
  • Personal Access Token: A PAT with appropriate read permissions

Setup Process​

Step 1: Generate a Personal Access Token​

  1. Navigate to Azure DevOps and go to User Settings > Personal Access Tokens
  2. Create a New Token with the following scope:
    • Code (Read) — read access to repositories
  3. Copy the Token: Save the token securely — it will only be shown once

Step 2: Connect to ProdE​

  1. Log into your ProdE account
  2. Navigate to Knowledge Layer section in the sidebar
  3. Click on Azure DevOps provider option
  4. Enter Organization Name: Provide your Azure DevOps organization name
  5. Enter PAT: Paste your Personal Access Token
  6. Connect: ProdE will validate your credentials and discover your projects and repositories

Step 3: Repository Management​

After successful connection:

  • Automatic Discovery: All projects and repositories from your organization will be discovered automatically
  • Next Steps: Navigate to the Repository Management page to learn more about managing your connected repositories and creating knowledge layers

Adding More Organizations​

You can connect multiple Azure DevOps organizations to ProdE:

  1. Navigate to your integration settings
  2. Add a new organization using the same PAT (if the PAT has access) or a new PAT
  3. The new organization's repositories will be discovered and made available

Security Features​

Read-Only Access​

  • No Write Permissions: ProdE only requests read-only access to your repositories
  • Secure Authentication: PAT-based authentication with encrypted storage
  • Permission Scoping: Limited to repository content reading only

Data Privacy​

  • Azure DevOps Permissions: Access is limited by your Azure DevOps permissions
  • Encrypted Storage: Your PAT is encrypted before storage
  • Secure Processing: Repository data is processed securely
  • Deletion Option: Data can be deleted upon disconnection

Disconnection and Data Management​

Disconnecting Azure DevOps​

Important

Disconnecting Azure DevOps will permanently delete all associated repository data and knowledge layers.

When you disconnect Azure DevOps:

  1. All Azure DevOps repository data is permanently deleted
  2. Knowledge layers are removed
  3. Reconnection requires providing new credentials

Disconnecting Organizations​

Data Loss Warning

Disconnecting an organization permanently deletes all repository data and knowledge layers from that organization.

When you disconnect an organization:

  1. All repository data from the organization is permanently deleted
  2. Knowledge layers for that organization are completely removed
  3. No access to organization repository content or insights
  4. Other connected organizations remain unaffected
Last updated on