Azure DevOps

Connect Azure DevOps to Canary so you can sign in with Microsoft and authorize access to the Azure DevOps organizations and projects your team uses. Use this integration to prepare Canary for Azure DevOps-based ticketing and workflow management as support expands across your day-to-day processes.

01Prerequisites

Before you connect Azure DevOps, make sure you have:

• An active Microsoft account that can sign in to your Azure DevOps tenant
• Access to at least one Azure DevOps organization
• Permission to view the projects you want Canary to use
• Permission to create and edit work items in the Azure DevOps project you plan to use for Canary flows
• A Canary workspace or property where integrations are managed

If your team manages access centrally, confirm which Microsoft account, Azure DevOps organization, and project you should connect before you start. If you plan to create or update work items from Canary, ask your Azure DevOps admin to confirm that your account can create work items, edit existing items, and use the target project area and iteration paths.

02Connect Azure DevOps

Open the integrations area in Canary and choose Azure DevOps to start the connection flow. Canary redirects you to Microsoft so you can sign in and grant access without entering Azure DevOps credentials directly in Canary.

Sign in with Microsoft

1. Go to Integrations in Canary.
2. Click Azure DevOps.
3. Click Sign in with Microsoft.
4. Complete the Microsoft sign-in flow with the account that has access to your Azure DevOps organization.
5. Approve the requested access if Microsoft prompts you to consent.

If you see more than one Microsoft account during sign-in, choose the account that matches the Azure DevOps organization and projects you plan to use with Canary.

Choose organization and project access

After sign-in, review the Azure DevOps organizations and available project access shown in Canary. Select the organization your team uses, then confirm the projects or scope Canary should use if prompted.

Choose the narrowest access that supports your workflow. This helps keep the integration focused on the work your team manages in Canary. For work item flows, make sure you select the specific project where Canary should create or update work items.

03Configure how Canary uses Azure DevOps

After the connection succeeds, review the integration settings so the right teams and workflows use Azure DevOps in the expected way. Keep your configuration aligned with the project structure your team already uses.

Ticketing and workflow use cases

Use Azure DevOps when you want Canary work to align with the projects your team tracks in Azure DevOps. Depending on the features available in your property, this can support ticket-driven workflows, day-to-day task coordination, and related workflow management scenarios.

Use this setup when you want to:

• Connect Canary work to an Azure DevOps project your team already manages
• Create new Azure DevOps work items from Canary for follow-up or execution
• Update existing Azure DevOps work items as Canary workflows move forward
• Prepare a property for Azure DevOps-based workflow or ticketing support
• Keep planning and execution work aligned with the same project space your team uses outside Canary

The table below shows common ways to think about configuration choices.

If you also use Canary workflow tooling, keep your project access consistent with the teams running those workflows. For related workflow capabilities, see /docs/guides/release-qa.

Project configuration for work item flows

Before you use Azure DevOps work item actions in Canary, confirm that the target Azure DevOps project is ready for Canary to write into it.

1. Open the Azure DevOps project you want Canary to use.
2. Confirm that the project exists in the organization you connected in Canary.
3. Verify that your account can create work items and edit existing work items in that project.
4. Check that your team knows which work item types Canary should use, such as bugs, tasks, or user stories.
5. Confirm that any required fields, area paths, or iteration paths in the project are valid for the work items Canary will manage.

If your Azure DevOps project uses required fields or strict process rules, test with a simple work item first. This helps you catch project-specific validation issues before you depend on the flow in a release or workflow run.

Managing or reconnecting the integration

Return to Integrations any time to review the current Azure DevOps connection. Reconnect the integration if your Microsoft session expires, your project access changes, or you need to switch to a different account.

Use these actions as needed:

1. Open Integrations.
2. Select Azure DevOps.
3. Review the connected organization, project access, and account.
4. Click Reconnect, Manage, or the equivalent action shown in your workspace.
5. Sign in again with Microsoft and reselect the correct organization or project access if prompted.

Reconnect after permission changes so Canary can continue using the latest approved access.

04Troubleshooting

If the Azure DevOps connection does not work as expected, check the following:

• Make sure you signed in with the correct Microsoft account
• Confirm that your account can access the Azure DevOps organization you selected
• Verify that you can view the projects you expect to use
• Confirm that the target project is the same project Canary is configured to use for work item flows
• Reconnect the integration if the sign-in session has expired or consent needs to be granted again
• Ask your Azure DevOps admin to confirm that your organization and project permissions are active

You may also run into Azure DevOps work item failures after the connection succeeds. These are usually caused by project configuration or permission issues.

Common failure cases include:

• The selected project no longer exists or is not available to the connected account
• Your account can view the project but cannot create or edit work items
• The work item type your team expects to use is not available in that project process
• The project requires fields, area paths, or iteration paths that are missing or invalid for the item Canary is trying to create or update
• Your organization or project access changed after you first connected the integration

If the organization or project you need does not appear, sign out and reconnect with the correct Microsoft account. If access still does not appear, verify that the account has been added to the Azure DevOps organization first. If work item actions fail in a project you can see, verify project permissions and required field rules with your Azure DevOps admin, then reconnect the integration and try again.

05Related

• /docs/guides/release-qa
• /docs/integrations/jira
• /docs/integrations/github