Labsco
microsoft logo

add-azuredevops

✓ Official408

by microsoft · part of microsoft/power-platform-skills

Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.

🔥🔥🔥✓ VerifiedFreeQuick setup
🧩 One of 7 skills in the microsoft/power-platform-skills package — works on its own, and pairs well with its siblings.

Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.

Inspect the full instructions your agent will receiveExpand

This is the exact playbook injected into your agent when the skill activates — shown here so you can audit it before installing. You don't need to read it to use the skill.

by microsoft

Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls. npx skills add https://github.com/microsoft/power-platform-skills --skill add-azuredevops Download ZIPGitHub408 📋 Shared Instructions: shared-instructions.md - Cross-cutting concerns.

Add Azure DevOps

Workflow

  • 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.

Step 2: Add Connector

First, find the connection ID (see 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.

Copy & paste — that's it
npx power-apps add-data-source -a azuredevops -c 

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:

Copy & paste — that's it
// 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 visualstudioteamservicesHttpRequestparameters section. Rename the property key:

Copy & paste — that's it
// BEFORE (generated):
HttpRequest: {
 parameters: {
 parameters: { ... }

// AFTER (fixed):
HttpRequest: {
 parameters: {
 body: { ... }

3. .power/schemas/visualstudioteamservices/visualstudioteamservices.Schema.json: Find the /{connectionId}/httprequestpostparameters array. Change the name field:

Copy & paste — that's it
// 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:

Copy & paste — that's it
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

Use Grep to find specific methods in src/generated/services/AzureDevOpsService.ts (generated files can be very large -- see connector-reference.md).

Step 5: Build

Copy & paste — that's it
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.