Azure DevOps
For teams building in Rocket from Azure DevOps: connect for work-item context, then set env vars so your app can call Azure DevOps APIs.
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.
In the preview toolbar, click the ... button.
Select Connectors from the menu.
Click the Azure DevOps card.
On the Azure DevOps connector page, click Connect.
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.
Under Select Organization, choose which Azure DevOps organization to connect, then confirm. When the connection is active, Disconnect is available on the connector page.
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
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.
| Variable | Purpose |
|---|---|
AZURE_DEVOPS_ORG | Azure DevOps organization name |
AZURE_DEVOPS_PROJECT | Project within that organization |
AZURE_DEVOPS_PAT | Personal Access Token for app API auth |
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 access in Azure DevOps and create a new one.
Open the Code tab and add:
AZURE_DEVOPS_ORG=your-org
AZURE_DEVOPS_PROJECT=your-project
AZURE_DEVOPS_PAT=your-pat-hereOpen Settings → Environment and fill in Staging and Production for all three variables.
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.
| Goal | Say this in chat |
|---|---|
| Build from a story | Build the feature described in [ADO_URL]. Read the requirements, acceptance criteria, and linked items first. |
| Fix a bug | Fix the bug at [ADO_URL]. Read the steps to reproduce and expected vs actual behavior, then generate a targeted fix. |
| See my work | Show my assigned Azure DevOps work items in this project and suggest which one to build first. |
| Search the board | Search Azure DevOps for work items about checkout and summarize the open ones. |
| Create follow-ups | Create Azure DevOps tasks for QA and edge cases from this build, and link them under the parent story. |
| Update and comment | Move work item [ADO_URL] to Done and leave a comment describing what was built. |
Revoke access
To fully remove Rocket's access to Azure DevOps, disconnect in Rocket and revoke credentials on Microsoft's side.
- Disconnect in Rocket. Use Disconnect on the Azure DevOps connector, or go to Settings > Connectors.
- Revoke the OAuth authorization. In Azure DevOps, open User settings → Profile → Authorizations, find Rocket, and click Revoke. You can also revoke Microsoft account consent at My Apps (⋯ → Manage your application → Revoke Permissions).
- Revoke any Personal Access Token. If you set
AZURE_DEVOPS_PATin Environment settings for a generated app, in Azure DevOps open User settings → Personal access tokens, select that PAT, and click Revoke.
Revoke a Personal access token (Microsoft Learn)
Follow Microsoft Learn to revoke a PAT in Azure DevOps.
Manage OAuth authorizations in Azure DevOps
Revoke Rocket from Azure DevOps user authorizations.
Disconnecting in Rocket alone does not revoke the OAuth grant or delete a PAT. Complete the provider steps above for a full revoke.