Add Azure DevOps to Power Apps for work items, bugs, pipelines, and API calls.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "add-azuredevops" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/power-platform-skills/main/plugins/code-apps/skills/add-azuredevops/SKILL.md 2. Save it as ~/.claude/skills/add-azuredevops/SKILL.md 3. Reload skills and tell me it's ready
Add the Azure DevOps connector to my current Power Apps code app and provide an example that queries incomplete work items by project and iteration.
Connector setup guidance plus sample code or call configuration for querying work items.
Connect Azure DevOps in Power Apps and generate an example for creating a Bug work item with title, priority, repro steps, and assignee fields.
A setup approach for bug creation plus an editable sample request or code snippet.
Add the Azure DevOps connector to Power Apps and show how to call the ADO API to get pipeline status, trigger a build, and read the run result.
Pipeline API examples covering status checks, build triggering, and reading execution results.
📋 Shared Instructions: shared-instructions.md - Cross-cutting concerns.
Check for memory-bank.md per shared-instructions.md.
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.
npx power-apps add-data-source -a azuredevops -c <connection-id>
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:
// 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:
// 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:
// BEFORE (generated):
{ "name": "parameters", "in": "body", ... }
// AFTER (fixed):
{ "name": "body", "in": "body", ... }
Ask the user what Azure DevOps operations they need (query work items, create items, trigger pipelines, etc.).
HttpRequest -- make arbitrary ADO REST API calls:
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).
npm run build
Fix TypeScript errors before proceeding. Do NOT deploy yet.
Update memory-bank.md with: connector added, HttpRequest fix applied, build status.
Review and fix Power Pages security headers, CSP, CORS, cookies, and embedding settings.
Run an end-to-end Power Pages security review with a consolidated HTML report.
Test deployed Power Pages sites with browsing, crawling, and API verification.
Add a data source or connector to a Power Apps code app.
Add the Excel Online connector to read and write workbook data.
Set up Power Platform Pipelines for automated Power Pages deployments.
Add any Power Platform connector to a Power Apps code app.
Add a Teams connector to Power Apps for messaging and channel integration.
Add a Copilot Studio connector to Power Apps code apps for agent integration.
Connect SharePoint to Power Apps for lists, documents, and site integration.
Add a OneDrive for Business connector for file operations in Power Apps.
Add the Office 365 Outlook connector for email and calendar features.