Press CTRL+K to open search

Azure DevOps

  • 5 minute(s) read
Prev Next

Overview

Azure DevOps Boards is a work-tracking service within Azure DevOps. It provides a set of work item types (WITs) — such as features, tasks, bugs, change requests, and feedback items — that teams use to plan, track, and manage work across the development lifecycle.

Turbo360 integrates with Azure DevOps as a notification channel. When an alert fires, Turbo360 can automatically create a work item in your Azure DevOps project, letting your team track and respond to platform issues directly within their existing workflow.

Business value

Connecting Turbo360 alerts to Azure DevOps Boards keeps operational incidents visible in the same system your development team already uses to manage work. This reduces context-switching, speeds up response times, and creates an auditable record of platform issues alongside your code and sprint activity.

Prerequisites

  • An active Azure DevOps organization with at least one project
  • A Personal Access Token (PAT) with sufficient permissions to create work items in the target project
  • A Turbo360 account with notification channel configuration access

Required permissions

You must have permission to manage notification channels in Turbo360. In Azure DevOps, the PAT must have Work Items (Read & Write) scope at minimum.

Dependencies

  • Azure DevOps organization must be accessible from Turbo360
  • The target project must use one of the supported process templates: Agile, Basic, CMMI, or Scrum

How it works

When you configure an Azure DevOps notification channel in Turbo360, you authenticate using a Personal Access Token. Turbo360 uses this token to connect to your Azure DevOps organization and retrieve the available projects and their supported work item types.

When a Turbo360 alert triggers, it creates a work item of the selected type in the configured project. You can optionally pre-fill fields such as assignee, tags, priority, iteration path, and probability to route and categorize work items automatically.

Steps

Use the following steps to configure an Azure DevOps notification channel. Navigate to Settings > Notification channels and select Azure DevOps to get started.

  1. Enter a Friendly name for the Azure DevOps notification channel.
  2. Enter your Personal Access Token and Organization name.
  3. Click Validate. Turbo360 verifies the credentials and displays a list of projects available in your organization, grouped by process template (Agile, Basic, CMMI, or Scrum).
  4. Select the Project name you want to use. Turbo360 loads the work item types supported by that project.
  5. Select a work item type to use for Turbo360 alerts.
  6. Optionally, fill in any of the following fields to pre-populate the work item: Assign to, Tags, Priority, Iteration path, Probability.
  7. Click Validate again. Turbo360 sends a sample notification to your Azure DevOps organization to confirm the configuration is working.
  8. Click Save to complete the setup.

Configuration

Option Type Required Description
Friendly name Text Yes Display name for this notification channel in Turbo360
Personal Access Token Text Yes PAT used to authenticate with your Azure DevOps organization
Organization name Text Yes The name of your Azure DevOps organization
Project name Dropdown Yes The Azure DevOps project where work items will be created
Work item type Dropdown Yes The type of work item to create for each alert (e.g. Bug, Task)
Assign to Text No Assigns the created work item to a specific team member
Tags Text No Comma-separated tags applied to the work item
Priority Dropdown No Sets the priority field on the work item
Iteration path Text No Places the work item in a specific sprint or iteration
Probability Text No Sets the probability field on the work item where supported

Permission behavior

With access: You can create and save Azure DevOps notification channels, validate credentials, and assign channels to alert rules.

Without access: The notification channel configuration section is not available. Contact your Turbo360 administrator to request the necessary permissions.

Example scenario

Your team monitors an Azure integration using Turbo360. You configure an Azure DevOps notification channel pointing to your Operations project using the Bug work item type, with Priority set to 1 and Assign to set to your on-call engineer. When a Turbo360 alert fires, a Bug work item is automatically created in the Operations project and assigned to the on-call engineer, ready to be picked up in the active sprint.

Limitations

  • Turbo360 creates work items but does not update or close them when an alert resolves. Work item lifecycle management must be handled in Azure DevOps.
  • Only process templates supported by Azure DevOps (Agile, Basic, CMMI, Scrum) are available for project selection.
  • The Personal Access Token must be manually rotated in Turbo360 when it expires. There is no automatic token refresh.

Troubleshooting

  1. Validation fails after entering credentials
    Cause: The Personal Access Token may be expired, have insufficient scope, or the organization name may be incorrect.
    Fix: Verify the organization name matches the URL of your Azure DevOps organization (e.g. dev.azure.com/{organization}). Regenerate the PAT with Work Items (Read & Write) scope and re-enter it.

  2. No projects appear after validation
    Cause: The PAT may not have access to any projects, or the organization has no active projects.
    Fix: Confirm the PAT has project-level access. Check that at least one project exists in the Azure DevOps organization.

  3. Work items are not being created when an alert fires
    Cause: The notification channel may not be assigned to the alert rule, or the channel configuration may have been saved with an expired token.
    Fix: Verify the Azure DevOps channel is selected in the alert rule's notification settings. Re-validate and re-save the channel if the token has expired.

  4. Work item type list is empty after selecting a project
    Cause: The selected project may use a custom process template not recognized by Turbo360.
    Fix: Switch to a project using a standard process template (Agile, Basic, CMMI, or Scrum).

  5. Sample notification sent but no work item appears in Azure DevOps
    Cause: The work item may have been created in a different project or under a different iteration path than expected.
    Fix: Search your Azure DevOps organization for recently created work items. Check the iteration path and project settings in the Turbo360 channel configuration.

FAQs

  1. Where can I find my Azure DevOps organization name?
    Your organization name appears in your Azure DevOps URL: https://dev.azure.com/{organization}. It is also visible on the Azure DevOps home page under your account.

  2. What PAT scopes does Turbo360 require?
    Turbo360 requires Work Items (Read & Write) scope at minimum. If your PAT has a narrower scope, validation will fail.

  3. Can I configure multiple Azure DevOps channels pointing to different projects?
    Yes you can configure multiple Azure DevOps channels pointing to different projects.

  4. What happens to existing work items when I update the channel configuration?
    Updating the channel configuration affects only future alerts. Work items already created in Azure DevOps are not modified.

Related articles