add-azuredevops — Claude Code skill: what it does, how to install
add-azuredevops attaches the Azure DevOps connector to a Power Apps code app to query work items, create bugs, and trigger build pipelines.
MIT ★ 1,167 updated 2026-10-29
/plugin marketplace add microsoft/power-platform-skills
/plugin install code-apps-preview@power-platform-skillsWhat add-azuredevops does
This skill configures the Azure DevOps connector for Power Apps code apps. It discovers the target connection ID with /list-connections or guides the user to set up credentials in the Power Apps maker portal, then invokes pa app add data-source --connector azuredevops -c <connection-id>.
Code generation for this connector introduces a bug: the HttpRequest method labels the payload parameter parameters, whereas the REST API expects body. Raw ADO calls will fail unless modified. The skill fixes this by renaming the field across AzureDevOpsService.ts, dataSourceInfo.ts, and the schema JSON.
Once configured, it runs npm run build to catch TypeScript compilation errors and records changes in memory-bank.md.
What it helps with
- bind the Azure DevOps data source to a Power Apps code project
- patch the HttpRequest parameter bug in generated service schemas
- dispatch arbitrary queries to the Azure DevOps REST API
- query work items and submit bug records from application code
Example prompts for the agent
- Add the Azure DevOps connector to this Power Apps code app
- Configure Azure DevOps REST API calls to fetch work items
- Set up Azure DevOps and apply the HttpRequest body fix
How to install add-azuredevops
1Plugin marketplace
/plugin marketplace add microsoft/power-platform-skills/plugin install code-apps-preview@power-platform-skillsThis installs the whole code-apps-preview plugin with all its skills
2Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill add-azuredevops -a claude-code3Manually: put the files in place
~/.claude/skills/add-azuredevops/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/add-azuredevops/
1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill add-azuredevops -a codex2Manually: put the files in place
.agents/skills/add-azuredevops/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill add-azuredevops -a cursor2Manually: put the files in place
.cursor/skills/add-azuredevops/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install microsoft/power-platform-skills plugins/code-apps/skills/add-azuredevops2Manually: put the files in place
.github/skills/add-azuredevops/SKILL.md1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill add-azuredevops -a gemini-cli2Platform CLI
gemini skills install https://github.com/microsoft/power-platform-skills --path plugins/code-apps/skills/add-azuredevopsManually: put the files in place
.devin/skills/add-azuredevops/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about add-azuredevops
How to install add-azuredevops in Claude Code?
Run npx skills add microsoft/power-platform-skills --skill add-azuredevops -a claude-code in your terminal.
What does add-azuredevops do?
It attaches Azure DevOps to a Power Apps code app via pa app add data-source, patches a known HttpRequest naming issue in three generated files, and builds the TypeScript project.
Why does the skill modify HttpRequest files?
Generated client code calls the payload property parameters, but the Azure DevOps endpoint requires body. The skill renames this property across TypeScript code and schemas so API calls succeed.
Source text
SKILL.md · MIT
---
name: add-azuredevops
description: Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.
user-invocable: true
allowed-tools: Read, Edit, Write, Grep, Glob, Bash, LSP, TaskCreate, TaskUpdate, TaskList, TaskGet, AskUserQuestion, Skill
model: sonnet
---
**📋 Shared Instructions: [shared-instructions.md](${PLUGIN_ROOT}/shared/shared-instructions.md)** - Cross-cutting concerns.
# Add Azure DevOps
## Workflow
1. Check Memory Bank → 2. Add Connector → 3. Apply HttpRequest Fix → 4. Configure → 5. Build → 6. Update Memory Bank
---
### Step 1: Check Memory Bank
Check for `memory-bank.md` per [shared-instructions.md](${PLUGIN_ROOT}/shared/shared-instructions.md).
### Step 2: Add Connector
**First, find the connection ID** (see [connector-reference.md](${PLUGIN_ROOT}/shared/connector-reference.md)):
Run the `/list-connections` skill. Find the Azure DevOps connection in the output. If none exists, direct the user to create one using the environment-specific Connections URL — construct it from the active environment ID in context (from `power.config.json` or a prior step): `https://make.powerapps.com/environments/<environment-id>/connections` → **+ New connection** → search for the connector → Create.
```bash
pa app add data-source --connector azuredevops -c <connection-id>
```
### Step 3: Apply HttpRequest Fix (Required)
The generated code has a known issue: the `HttpRequest` method uses `parameters` as the parameter name, but the API expects `body`. Rename `parameters` to `body` in these 3 files:
Use the `Edit` tool to rename `parameters` to `body` in each file:
**1. `src/generated/services/AzureDevOpsService.ts`:**
Find the `HttpRequest` method. Rename the parameter and its usage:
```typescript
// BEFORE (generated):
async HttpRequest(parameters: any) {
const params = { parameters: parameters, ... };
// AFTER (fixed):
async HttpRequest(body: any) {
const params = { body: body, ... };
```
**2. `.power/appschemas/dataSourceInfo.ts`:**
Find the `visualstudioteamservices` → `HttpRequest` → `parameters` section. Rename the property key:
```typescript
// BEFORE (generated):
HttpRequest: {
parameters: {
parameters: { ... }
// AFTER (fixed):
HttpRequest: {
parameters: {
body: { ... }
```
**3. `.power/schemas/visualstudioteamservices/visualstudioteamservices.Schema.json`:**
Find the `/{connectionId}/httprequest` → `post` → `parameters` array. Change the `name` field:
```json
// BEFORE (generated):
{ "name": "parameters", "in": "body", ... }
// AFTER (fixed):
{ "name": "body", "in": "body", ... }
```
### Step 4: Configure
Ask the user what Azure DevOps operations they need (query work items, create items, trigger pipelines, etc.).
**HttpRequest** -- make arbitrary ADO REST API calls:
```typescript
await AzureDevOpsService.HttpRequest({
Uri: "https://dev.azure.com/{org}/{project}/_apis/wit/wiql?api-version=7.2",
Method: "POST",
Body: JSON.stringify({
query:
"SELECT [System.Id], [System.Title] FROM WorkItems WHERE [System.TeamProject] = @project"
})
});
```
Docs: [Azure DevOps REST API](https://learn.microsoft.com/en-us/rest/api/azure/devops/?view=azure-devops-rest-7.2)
Use `Grep` to find specific methods in `src/generated/services/AzureDevOpsService.ts` (generated files can be very large -- see [connector-reference.md](${PLUGIN_ROOT}/shared/connector-reference.md#inspecting-large-generated-files)).
### Step 5: Build
```bash
npm run build
```
Fix TypeScript errors before proceeding. Do NOT deploy yet.
### Step 6: Update Memory Bank
Update `memory-bank.md` with: connector added, HttpRequest fix applied, build status.
© Microsoft · MIT · microsoft/power-platform-skills