Skip to main content
For teams who plan work in Azure DevOps and build in Rocket. Connect so you can build or fix from a work item or wiki URL and update Azure DevOps from chat. After you set env vars, your app can call Azure DevOps APIs.
You need two pieces: the connector (Azure DevOps as generation context for Rocket) and environment variables plus a PAT (so your generated app can call Azure DevOps APIs). Connect at workspace level (Settings, shared across tasks) or task level (Connectors tab or chat).
Before you start: a Microsoft account with access to the target Azure DevOps organization and project; permission to approve OAuth (or an admin if you see Need admin approval); a Personal Access Token you can create (or an admin policy that allows it); and the organization name from https://dev.azure.com/{organization} plus the project name for env vars. Use the same organization in Select Organization and AZURE_DEVOPS_ORG.

What you can do

Build from a work item

Paste a user story or task URL. Rocket reads requirements and acceptance criteria, then generates the feature.

Fix a bug from a report

Paste a bug URL. Rocket reads reproduce steps and expected vs actual behavior, then produces a targeted fix.

Build from the current sprint

Ask Rocket to read the active sprint and build the highest-priority work first.

Use repo and pull request context

Point Rocket at a repository or pull request so new code matches your existing patterns.

Fix a failing pipeline

Paste a failing build URL. Rocket checks the logs and fixes the issue in the app.

Build from a wiki page

Paste a wiki URL. Rocket follows the specs on that page when generating the feature.

Connect Azure DevOps

Authorize with Microsoft, then select the organization Rocket should use. You can also connect from workspace Settings.
1

Open the overflow menu

In the preview toolbar, click the ... button.
Rocket preview toolbar with the three-dot overflow menu highlighted.Rocket preview toolbar with the three-dot overflow menu highlighted.

Open the overflow menu in the preview toolbar

2

Choose Connectors

Select Connectors from the menu.
Overflow menu with Connectors highlighted.Overflow menu with Connectors highlighted.

Choose Connectors from the menu

3

Open Azure DevOps

Click the Azure DevOps card.
Connectors list with the Azure DevOps card highlighted.Connectors list with the Azure DevOps card highlighted.

Open the Azure DevOps connector

4

Click Connect

On the Azure DevOps connector page, click Connect.
Azure DevOps connector detail page with the Connect button highlighted.Azure DevOps connector detail page with the Connect button highlighted.

Click Connect on the Azure DevOps connector

5

Authorize with Microsoft

A Microsoft sign-in screen opens. Sign in with an account that has access to your Azure DevOps organization, review the permissions Rocket requests, and approve access. You return to Rocket when authorization completes.
If Microsoft shows Need admin approval, ask your Microsoft Entra admin (your organization’s Microsoft login) to grant admin consent or review consent requests. For OAuth scopes and consent, see Microsoft Entra OAuth for Azure DevOps and the OAuth scope reference.
6

Select organization

Under Select Organization, choose which Azure DevOps organization to connect, then confirm. When the connection is active, Disconnect is available on the connector page.
Azure DevOps connector with Select Organization dropdown highlighted.Azure DevOps connector with Select Organization dropdown highlighted.

Select your Azure DevOps organization

Your account needs access to the organization and project you intend to use. Admins can add organization users and grant project access. OAuth approval alone does not grant admin rights; see the Azure DevOps permissions reference.

Disconnect a service

Disconnect or switch accounts from workspace Settings.

Set environment variables

These three values are for the generated app, not for signing into the connector. Use the same organization you chose under Select Organization.
Create a Personal Access Token in Azure DevOps with Microsoft’s Personal Access Token guide. If PAT creation or scopes are restricted, see PAT policies for administrators. The organization name appears in https://dev.azure.com/{organization}; the project name is in the project selector and URL. See Microsoft’s guides for finding organizations and viewing projects.
Reference them in server-side code as process.env.AZURE_DEVOPS_ORG, process.env.AZURE_DEVOPS_PROJECT, and process.env.AZURE_DEVOPS_PAT.
Never paste your Personal Access Token into chat, and never share passwords, OAuth tokens, refresh tokens, client secrets, or PATs with support. Add placeholders in .env, then set real values in Environment settings. If a token is exposed, revoke it in Azure DevOps and create a new one.
1

Add placeholders in `.env`

Open the Code tab and add:
2

Set real values in Environment

Open Settings → Environment and fill in Staging and Production for all three variables.
3

Ask Rocket to use these variables in your app

Ask Rocket to use these variables when building Azure DevOps-backed features in your app.

Environment variables

How to add and manage Staging and Production values in Rocket.

Example prompts

Pick the tab that matches what you are doing. Paste an Azure DevOps URL when you have one. Review changes in Azure DevOps before sharing; they appear in your org immediately.

What’s next?

Jira

Prefer Jira for tickets and sprints? Connect it for issue-driven builds.

Linear

Already using Linear? Connect it for bi-directional ticket integration.

GitHub

Push your code to a repository and keep version history.

All connectors

Browse every available integration.