Add and verify a data source or connector in Power Apps Studio.
This skill is essentially an open-source prompt-only workflow that guides the user to manually add a data source in Power Apps Studio and then verify it. The material does not show that it requires secrets, performs direct network egress, or executes local code by itself; overall risk is low, with minor caution around downstream MCP access to Studio-visible resources and unclear license/maintenance metadata.
The material explicitly states that no keys or environment variables are required. The skill only instructs the user to complete authentication in Studio and does not itself collect, store, or transmit credentials.
The system flags no remote host and the skill is prompt-only. The README says it cannot add connections programmatically and only verifies availability via platform tools after the user acts, with no sign of this skill itself sending data to unknown or unrelated external endpoints.
There is no indication of spawning local processes, running scripts, or invoking privileged system capabilities. Its behavior is limited to instructing the user, waiting for confirmation, and suggesting follow-up listing/description MCP calls, so the skill itself has no direct code-execution surface.
The skill itself does not directly read or write files or data, but it is designed to guide the user to add new data sources and then verify them through `list_data_sources`, `list_apis`, `get_data_source_schema`, and `describe_api`. This is a normal data-visibility capability consistent with its stated purpose; users should watch the scope available to downstream tools, but no overprivilege red flag is shown in the material.
The source is an open-source GitHub repository under Microsoft, which is a meaningful risk-reducing signal. However, the material also shows no declared license, 0 stars, and unknown maintenance status, so supply-chain assurance is limited; this supports a caution rating rather than high risk.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "add-data-source" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/power-platform-skills/main/plugins/canvas-apps/skills/add-data-source/SKILL.md 2. Save it as ~/.claude/skills/add-data-source/SKILL.md 3. Reload skills and tell me it's ready
Help me add a SharePoint data source to this Canvas App, connect to the 'Project Tasks' list in our team site, and continue after confirming the connection works.
Step-by-step guidance to add the SharePoint connection in Power Apps Studio, select the target list, and verify the data source is available.
I want to connect this app to a SQL Server database. Guide me to add the connector, enter the connection details, and continue after the connection succeeds.
Instructions to add the SQL Server connector, configure connection settings, and confirm the app can access the database tables.
Help me add the Office 365 Users connector to the Canvas App so it can read user information, then continue after verification.
Guidance to add the Office 365 Users connector, complete authorization, and verify that user data can be retrieved correctly.
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.
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.
Explain that this step requires action in their Studio session. Tell the user:
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.
Once the user confirms, call the appropriate MCP tools to check that the connection is now available:
list_data_sourceslist_apisScan 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:
Use AskUserQuestion to wait for their follow-up, then re-run Phase 3.
After the connection is confirmed:
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 Azure DevOps to Power Apps for work items, bugs, pipelines, and API calls.
Set up Power Platform Pipelines for automated Power Pages deployments.
Add any Power Platform connector to a Power Apps code app.
Add Dataverse tables to Power Apps code apps with generated TypeScript services.
Add the Excel Online connector to read and write workbook data.
Connect SharePoint to Power Apps for lists, documents, and site integration.
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.