Azure Connector Namespace — manage namespaces, connections, triggers, and MCP server configs. Connect external SaaS services (Office 365, Teams, SharePoint, OneDrive, Forms, GitHub, Azure Blob) to any user-provided webhook URL via event-driven triggers, expose selected connector operations as an MCP server endpoint, or call connector operations on demand via dynamicInvoke. Use when: - Managing connector namespaces and connections - Creating trigger configs that POST to a callback URL - Subscribing to connector events (email, file, list-item, form response) - Wiring event sources to a webhook, Function App, Logic App, or API - Recurrence / sliding-window triggers that fire on a schedule - Exposing connector operations as MCP tools at a namespace endpoint - Calling connector APIs (send email, post Teams message, upload files) Triggers: "connector namespace", "connector", "trigger config", "webhook trigger", "recurrence trigger", "on new email", "callback url", "mcp", "send email", "post teams message"
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryEngineeringStars0
About this skill
Azure Connector Namespace — manage namespaces, connections, triggers, and MCP server configs. Connect external SaaS services (Office 365, Teams, SharePoint, OneDrive, Forms, GitHub, Azure Blob) to any user-provided webhook URL via event-driven triggers, expose selected connector operations as an MCP server endpoint, or call connector operations on demand via dynamicInvoke. Use when: - Managing connector namespaces and connections - Creating trigger configs that POST to a callback URL - Subscribing to connector events (email, file, list-item, form response) - Wiring event sources to a webhook, Function App, Logic App, or API - Recurrence / sliding-window triggers that fire on a schedule - Exposing connector operations as MCP tools at a namespace endpoint - Calling connector APIs (send email, post Teams message, upload files) Triggers: "connector namespace", "connector", "trigger config", "webhook trigger", "recurrence trigger", "on new email", "callback url", "mcp", "send email", "post teams message"
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
Azure Connector Namespace — manage namespaces, connections, triggers, and MCP server configs. Connect external SaaS services (Office 365, Teams, SharePoint, OneDrive, Forms, GitHub, Azure Blob) to any user-provided webhook URL via event-driven triggers, expose selected connector operations as an MCP server endpoint, or call connector operations on demand via dynamicInvoke. Use when: - Managing connector namespaces and connections - Creating trigger configs that POST to a callback URL - Subscribing to connector events (email, file, list-item, form response) - Wiring event sources to a webhook, Function App, Logic App, or API - Recurrence / sliding-window triggers that fire on a schedule - Exposing connector operations as MCP tools at a namespace endpoint - Calling connector APIs (send email, post Teams message, upload files) Triggers: "connector namespace", "connector", "trigger config", "webhook trigger", "recurrence trigger", "on new email", "callback url", "mcp", "send email", "post teams message"
About this listing
Category
Engineering
Reported license
MIT
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLI