Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The azure-functions-connector-validate skill checks a deployed connector integration before an Azure Functions hosted skill uses it automatically.
Skill: azure-functions-connector-validate | Source code
Important
Azure Functions skills and the @azure/functions-skills package are in preview. Features and supported workflows can change before general availability. For current release information, see the @azure/functions-skills package.
What it provides
This skill checks the connected account, managed-identity access, MCP configuration, runtime settings, and protocol initialization. It compares the deployed tool names and schemas with the approved contract. It then tests connector operations and the hosted skill's use of those tools.
The skill verifies the result in the downstream service, not just an HTTP success code or successful function execution. Write tests require your approval, a controlled target, and a cleanup plan. Missing proof is reported as not verified.
The skill stops dependent tests after a failure. It does not expand permissions or silently change infrastructure to make a test pass.
Prerequisites
- Azure Functions skills installed in a supported coding agent.
- A connection prepared with
azure-functions-connector-create. - An MCP configuration and expected contract from
azure-functions-connector-mcp. - A deployed hosted skill, the intended identity, and safe read-only test inputs.
- Your approval of any write test, its target, verification method, and cleanup.
When to use this skill
Use this skill when you need to:
- Confirm that the intended account and managed identity can use a connection.
- Check MCP initialization, tool discovery, and input schemas.
- Verify that no unintended operation is exposed.
- Confirm an email, Teams post, or other approved external result.
- Test the hosted skill before enabling a schedule or event trigger.
For connection or identity failures, use azure-functions-connector-create. For tool or schema failures, use azure-functions-connector-mcp.
Example prompts
Try these prompts to activate this skill:
- "Validate this connector integration before I enable the timer."
- "Check that the deployed tools match the approved MCP contract."
- "Verify access for this function app's managed identity."
- "Confirm that this approved Teams test produced the expected post."
- "Report which connector validation checks passed or remain unverified."