Azure Aigateway
microsoft/GitHub-Copilot-for-Azure
Configure Azure API Management as an AI Gateway for AI models, MCP tools, and agents.
Expert knowledge for Azure Connector Namespace development including configuration.
Install Azure Connector Namespace
$ npx skills add MicrosoftDocs/Agent-Skills --skill azure-connector-namespace -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MicrosoftDocs/Agent-Skills azure-connector-namespace --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/azure-connector-namespace .claude/skills/azure-connector-namespace && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "azure-connector-namespace" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/azure-connector-namespace into .claude/skills/azure-connector-namespace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-connector-namespace", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/azure-connector-namespaceType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add MicrosoftDocs/Agent-Skills --skill azure-connector-namespace -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MicrosoftDocs/Agent-Skills azure-connector-namespace --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/azure-connector-namespace .agents/skills/azure-connector-namespace && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "azure-connector-namespace" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/azure-connector-namespace into .agents/skills/azure-connector-namespace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-connector-namespace", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MicrosoftDocs/Agent-Skills --skill azure-connector-namespace -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MicrosoftDocs/Agent-Skills azure-connector-namespace --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/azure-connector-namespace .cursor/skills/azure-connector-namespace && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "azure-connector-namespace" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/azure-connector-namespace into .cursor/skills/azure-connector-namespace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-connector-namespace", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/MicrosoftDocs/Agent-Skills.git --path skills/azure-connector-namespace--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add MicrosoftDocs/Agent-Skills --skill azure-connector-namespace -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MicrosoftDocs/Agent-Skills azure-connector-namespace --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/azure-connector-namespace .gemini/skills/azure-connector-namespace && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "azure-connector-namespace" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/azure-connector-namespace into .gemini/skills/azure-connector-namespace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-connector-namespace", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install MicrosoftDocs/Agent-Skills azure-connector-namespaceInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add MicrosoftDocs/Agent-Skills --skill azure-connector-namespace -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/azure-connector-namespace .github/skills/azure-connector-namespace && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "azure-connector-namespace" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/azure-connector-namespace into .github/skills/azure-connector-namespace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-connector-namespace", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MicrosoftDocs/Agent-Skills --skill azure-connector-namespace -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install MicrosoftDocs/Agent-Skills azure-connector-namespace --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/azure-connector-namespace .opencode/skills/azure-connector-namespace && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "azure-connector-namespace" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/azure-connector-namespace into .opencode/skills/azure-connector-namespace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-connector-namespace", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
azure-connector-namespace- GitHub stars
- 777
- Token cost
- ~581 tokens
- SKILL.md length
- 168 words
- Files
- 1
- Skills in repo
- 149
- Repo updated
- First seen
- Licence
- CC-BY-4.0
At a glance
Expert knowledge for Azure Connector Namespace development including configuration.
- Setting up hosted MCP servers
- SKILL.md covers How to Use This Skill and Category Index
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Defining Connector Namespace endpoints
What it does
Azure Connector Namespace is an agent skill from MicrosoftDocs/Agent-Skills, published by the product's own GitHub organization. Expert knowledge for Azure Connector Namespace development including configuration. Use when setting up hosted MCP servers, defining Connector Namespace endpoints, auth settings, or runtime options, and other Azure Connector Namespace related development tasks. Not for Azure Service Connector (use azure-service-connector), Azure API Management (use azure-api-management), Azure Logic Apps (use azure-logic-apps), Azure Functions (use azure-functions).
Its SKILL.md is about 580 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires network access. Uses mcpmicrosoftdocs:microsoftdocsfetch or fetchwebpage to retrieve documentation.
It sits in Agent Workflows, covering MCP servers. It works with Microsoft Azure, Model Context Protocol, Azure API Management and Azure Functions. The repository describes itself as: Curated Agent Skills for Microsoft & Azure – giving AI coding assistants structured, real-time expertise from Microsoft Learn docs. The licence is CC-BY-4.0.
When your agent uses it
- Setting up hosted MCP servers
- Defining Connector Namespace endpoints
- Runtime options
- Other Azure Connector Namespace related development tasks
Example prompts
- “/azure-connector-namespace”
Requirements
- Compatibility (from SKILL.md): Requires network access. Uses mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage to retrieve documentation.
What it can do on your machine
Read from SKILL.md and the folder at commit ba74e8f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.comlearn.microsoft.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires network access. Uses mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage to retrieve documentation.
From compatibility in the SKILL.md frontmatter.
Context cost
Azure Connector Namespace loads about 581 tokens when it runs. Until then it costs about 120 tokens; SKILL.md has 168 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from MicrosoftDocs/Agent-Skills at commit ba74e8f, republished under its CC-BY-4.0 licence (© MicrosoftDocs). 168 words, ~581 tokens.
Download SKILL.mdSave it as
.claude/skills/azure-connector-namespace/SKILL.md (or your agent's skills folder).- name
- azure-connector-namespace
- description
- Expert knowledge for Azure Connector Namespace development including configuration. Use when setting up hosted MCP servers, defining Connector Namespace endpoints, auth settings, or runtime options, and other Azure Connector Namespace related development tasks. Not for Azure Service Connector (use azure-service-connector), Azure API Management (use azure-api-management), Azure Logic Apps (use azure-logic-apps), Azure Functions (use azure-functions).
- compatibility
- Requires network access. Uses mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage to retrieve documentation.
- metadata.generated_at
- 2026-09-27
- metadata.generator
- docs2skills/1.0.0
Azure Connector Namespace Skill
This skill provides expert guidance for Azure Connector Namespace. Covers configuration. It combines local quick-reference content with remote documentation fetching capabilities.
How to Use This Skill
IMPORTANT for Agent: Use the Category Index below to locate relevant sections. For categories with line ranges (e.g.,
L35-L120), useread_filewith the specified lines. For categories with file links (e.g.,[security.md](security.md)), useread_fileon the linked reference file
IMPORTANT for Agent: If
metadata.generated_atis more than 3 months old, suggest the user pull the latest version from the repository. Ifmcp_microsoftdocstools are not available, suggest the user install it: Installation Guide
This skill requires network access to fetch documentation content:
- Preferred: Use
mcp_microsoftdocs:microsoft_docs_fetchwith query stringfrom=learn-agent-skill. Returns Markdown. - Fallback: Use
fetch_webpagewith query stringfrom=learn-agent-skill&accept=text/markdown. Returns Markdown.
Category Index
| Category | Lines | Description |
|---|---|---|
| Configuration | L29-L32 | Configuring hosted MCP servers in Connector Namespace, including setup steps, connection settings, and runtime options for managing MCP server hosting. |
Configuration
| Topic | URL |
|---|---|
| Configure hosted MCP servers in Connector Namespace | https://learn.microsoft.com/en-us/azure/connector-namespace/hosted-mcp-dev-guide |
© MicrosoftDocs, CC-BY-4.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/azure-connector-namespace of MicrosoftDocs/Agent-Skills.
Open the folder on GitHubat commit ba74e8f
Compare with similar skills
Azure Connector Namespace next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Azure Connector Namespace this skillMicrosoftDocs/Agent-Skills | 777 | — | ~581 | Automated safety check: Pass | CC-BY-4.0 | |
| Azure Aigatewaymicrosoft/GitHub-Copilot-for-Azure | 255 | 2 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Add Manifest SampleAzure/azure-functions-templates | 362 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Azsdk Common Pipeline TroubleshootingAzure/azure-sdk-for-android | 121 | — | ~496 | Automated safety check: Pass | MIT | |
| Azure Resource Lookupmicrosoft/GitHub-Copilot-for-Azure | 255 | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Azure Typespec AuthorAzure/azure-sdk-tools | 134 | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
- Official
- Official
Add Manifest Sample
Azure/azure-functions-templates
Add a new Azure Functions sample/quickstart to the Template Manifest.
- Official
Azsdk Common Pipeline Troubleshooting
Azure/azure-sdk-for-android
Diagnose and resolve failures in Azure SDK CI and generation pipelines.
- Official
Azure Resource Lookup
microsoft/GitHub-Copilot-for-Azure
List, find, and show Azure resources across subscriptions or resource groups.
- Official
Azure Typespec Author
Azure/azure-sdk-tools
Authors and modifies Azure TypeSpec (.tsp) API specifications.
- Official
Azure Typespec Author
Azure/azure-sdk-tools
Authors and modifies Azure TypeSpec (.tsp) API specifications.
More from MicrosoftDocs/Agent-Skills
All 149 skills in this repo- Official
Azure Personalizer
MicrosoftDocs/Agent-Skills
Expert knowledge for Azure AI Personalizer development including troubleshooting, decision making, security, configuration, and integrations & coding patterns.
- Official
Azure Architecture Advisor
MicrosoftDocs/Agent-Skills
Guides Azure solution design by category, from reference architectures and design patterns to technology choices and migrations, fetching current Microsoft Learn pages over the network.
- Official
Azure Advisor Guidance
MicrosoftDocs/Agent-Skills
Reference guidance for Azure Advisor work: recommendations, alerts and digests, workbooks, RBAC access and sovereign-cloud limits, fetched from Microsoft Learn.
- Official
Azure AI Vision Reference
MicrosoftDocs/Agent-Skills
Looks up Microsoft Learn guidance for Azure AI Vision: Image Analysis, Read OCR containers, smart-crop thumbnails, background removal and video frame analysis, plus limits and deployment.
- Official
Azure Analysis Services
MicrosoftDocs/Agent-Skills
Expert knowledge for Azure Analysis Services development including troubleshooting.
- Official
Azure Anomaly Detector
MicrosoftDocs/Agent-Skills
Expert knowledge for Azure AI Anomaly Detector development including troubleshooting, best practices, limits & quotas, configuration, and deployment.
Related
Categories
Questions about Azure Connector Namespace
What does Azure Connector Namespace do?
Expert knowledge for Azure Connector Namespace development including configuration. Azure Connector Namespace is an agent skill from MicrosoftDocs/Agent-Skills, published by the product's own GitHub organization. Expert knowledge for Azure Connector Namespace development including configuration.
When should I use Azure Connector Namespace?
Azure Connector Namespace fits situations like: setting up hosted MCP servers; defining Connector Namespace endpoints; runtime options; other Azure Connector Namespace related development tasks.
How do I install Azure Connector Namespace in Claude Code?
Run `npx skills add MicrosoftDocs/Agent-Skills --skill azure-connector-namespace -a claude-code`. Or copy the skill folder (skills/azure-connector-namespace in MicrosoftDocs/Agent-Skills) into .claude/skills/azure-connector-namespace in your project. Claude Code loads it when a task matches its description.
How do I install Azure Connector Namespace in Codex?
Run `npx skills add MicrosoftDocs/Agent-Skills --skill azure-connector-namespace -a codex`. Or copy the skill folder (skills/azure-connector-namespace in MicrosoftDocs/Agent-Skills) into .agents/skills/azure-connector-namespace in your project. Codex loads it when a task matches its description.
Can I use Azure Connector Namespace in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MicrosoftDocs/Agent-Skills --skill azure-connector-namespace -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/azure-connector-namespace, .gemini/skills/azure-connector-namespace, .github/skills/azure-connector-namespace and .opencode/skills/azure-connector-namespace in your project.
What does Azure Connector Namespace need to run?
SKILL.md names no scripts, command-line tools or credentials: Azure Connector Namespace is instructions for the agent only. Compatibility (from SKILL.md): Requires network access. Uses mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage to retrieve documentation..
Does Azure Connector Namespace access the network?
SKILL.md names 2 domains. As links in the text: github.com and learn.microsoft.com. This is read from the text; nothing was executed.
Is Azure Connector Namespace safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Azure Connector Namespace use?
Azure Connector Namespace is published under the CC-BY-4.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Azure Connector Namespace use?
About 581 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Azure Connector Namespace?
Skills that share tags, products or a category with Azure Connector Namespace: Azure Aigateway (microsoft/GitHub-Copilot-for-Azure, 255 stars), Add Manifest Sample (Azure/azure-functions-templates, 362 stars), Azsdk Common Pipeline Troubleshooting (Azure/azure-sdk-for-android, 121 stars) and Azure Resource Lookup (microsoft/GitHub-Copilot-for-Azure, 255 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Azure Connector Namespace?
MicrosoftDocs (a GitHub organization, an official publisher) maintains it in MicrosoftDocs/Agent-Skills, which has 777 GitHub stars. The repository holds 149 skills in this directory. The repository was last updated on October 5, 2026.
Source: MicrosoftDocs/Agent-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.