add-data-source
Guide the user to add a data source, connection, or API connector to a Canvas App via Power Apps Studio, then verify and continue. USE WHEN the user asks to add a data source, add a connection, add an API, add a connector, connect to SharePoint / Dataverse / SQL / Excel / OneDrive / Teams / Office 365, or any similar request to make new data available to the app. DO NOT USE WHEN the user is asking to list or describe existing data sources — call listdatasources or listapis directly instead.
- Installs
- 236
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/microsoft/power-platform-skills --skill add-data-source- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads add-data-source automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Data sources, connections, and API connectors cannot be added by the coding agent — they must be added through the Power Apps Studio interface. This skill informs the user, guides them to add the connection in their Studio session, verifies it is available via the MCP server, and then continues with any pending work.
Phase 0 — Identify the Connection Type
From the user's request, determine what they want to add and how to verify it:
| Request type | Verify with |
|---|---|
| Data source (SharePoint list, Dataverse table, SQL table, Excel file, OneDrive, etc.) | list_data_sources |
| API / connector (Office 365 Users, Teams, custom connector, etc.) | list_apis |
| Unclear | Both list_data_sources and list_apis |
Note what the user is trying to add so you can look for it by name in Phase 3.
Phase 1 — Inform the User
Explain that this step requires action in their Studio session. Tell the user:
- The coding agent cannot add data sources or connections programmatically — this must be done directly in Power Apps Studio.
- To add the connection, follow these steps in their open Studio session:
- Open the Data panel in the left sidebar
- Click Add data
- Search for the data source or connector they want (e.g., "SharePoint", "Dataverse", "SQL Server", "Office 365 Users")
- Follow the authentication prompts and select the specific table, list, file, or dataset
- Once added, the connection will be available to the MCP server and you can continue.
Phase 2 — Wait for Confirmation
Use AskUserQuestion to pause until the user has completed the steps in Studio:
"Please add the data source or connection in your Power Apps Studio session. Reply here when it's ready and I'll verify the connection before continuing."
Do not proceed until the user confirms they have added it.
Phase 3 — Verify the Connection
Once the user confirms, call the appropriate MCP tools to check that the connection is now available:
- If the request was for a data source: call
list_data_sources - If the request was for an API / connector: call
list_apis - If the type was unclear: call both in parallel
Scan the results for the connection the user added:
Found — Confirm to the user that the data source or connection is now visible to the agent. Include the exact name as returned by the MCP tool (this is how it must be referenced in Power Fx formulas). If it is a data source, call get_data_source_schema to retrieve its column names and types, and include the schema summary in your response so it is ready for use in edits. Similarly, for APIs/connectors, call describe_api to retrieve the available endpoints and their parameters, and include the schema summary in your response.
Not found — Inform the user that the connection is not yet visible. Ask them to:
- Confirm they completed the Studio steps and the connection appears in the Data panel there.
- Check that their Studio session is still active (the MCP server must be connected to a live coauthoring session).
- Let you know when ready to try again.
Use AskUserQuestion to wait for their follow-up, then re-run Phase 3.
Phase 4 — Continue
After the connection is confirmed:
- If the user had a pending task (e.g., "add SharePoint as a data source, then build a gallery"), continue with that work now using the verified connection name and schema.
- If adding the connection was the only request, summarize what was confirmed (connection name, type, and schema if applicable) and suggest a natural next step (e.g., building a screen or gallery that uses the new data).
FAQ
What does the add-data-source skill do?
Guide the user to add a data source, connection, or API connector to a Canvas App via Power Apps Studio, then verify and continue. USE WHEN the user asks to add a data source, add a connection, add an API, add a connector, connect to SharePoint / Dataverse / SQL / Excel / OneDrive / Teams / Office 365, or any similar request to make new data available to the app. DO NOT USE WHEN the user is asking to list or describe existing data sources — call listdatasources or listapis directly instead.
How do I install add-data-source?
Run npx skills add https://github.com/microsoft/power-platform-skills --skill add-data-source in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/add-data-source/ (personal) or .claude/skills/add-data-source/ (project).
Which AI agents can use add-data-source?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is add-data-source safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains add-data-source?
It is published by microsoft in microsoft/power-platform-skills, and it is an official skill from the maker of the technology it covers. It has 236 recorded installs.
More from microsoft/power-platform-skills
add-sharepoint
microsoft/power-platform-skills
Open the skill to read its SKILL.md instructions.
create-code-app
microsoft/power-platform-skills
Creates Power Apps code apps using React and Vite. Use when building code apps, scaffolding projects, or deploying to Power Platform.
add-dataverse
microsoft/power-platform-skills
Open the skill to read its SKILL.md instructions.
configure-canvas-mcp
microsoft/power-platform-skills
Open the skill to read its SKILL.md instructions.
add-office365
microsoft/power-platform-skills
Open the skill to read its SKILL.md instructions.
canvas-app
microsoft/power-platform-skills
Open the skill to read its SKILL.md instructions.
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.