# azure-peering-service

Check Azure Peering Service prefix and routing requirements, including BGP, RPKI status, and AS number criteria. Useful when reviewing a peering configuration.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 165 installs · ★ 818 repo stars
- Author: MicrosoftDocs
- License: CC-BY-4.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/MicrosoftDocs/Agent-Skills/tree/HEAD/skills/azure-peering-service/SKILL.md
- Updated: 2026-10-25
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/azure-peering-service

## What it does

The skill covers Azure Peering Service limits and quotas, with reference material on prefix and routing requirements. Ask an agent to review a prefix size, BGP setup, RPKI status, or AS number requirements. Azure Internet Peering, ExpressRoute, Virtual Network, and Virtual WAN are handled by separate skills.

It pairs a local quick reference with network-based Microsoft documentation retrieval through `mcp_microsoftdocs:microsoft_docs_fetch` or `fetch_webpage`. Network access is required to fetch documentation, so checks that rely on current remote guidance cannot run without it. In Claude Code, install with `npx skills add MicrosoftDocs/Agent-Skills --skill azure-peering-service -a claude-code`; the skill file is at `~/.claude/skills/azure-peering-service/SKILL.md`.

## Requirements
- Works with: Azure

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add MicrosoftDocs/Agent-Skills --skill azure-peering-service -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/azure-peering-service/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/azure-peering-service/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add MicrosoftDocs/Agent-Skills --skill azure-peering-service -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/azure-peering-service/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add MicrosoftDocs/Agent-Skills --skill azure-peering-service -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/azure-peering-service/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install MicrosoftDocs/Agent-Skills skills/azure-peering-service
```

2. **Manually: put the files in place**
- File: `.github/skills/azure-peering-service/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add MicrosoftDocs/Agent-Skills --skill azure-peering-service -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/MicrosoftDocs/Agent-Skills --path skills/azure-peering-service
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/azure-peering-service/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add MicrosoftDocs/Agent-Skills --skill azure-peering-service -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/MicrosoftDocs/Agent-Skills/tree/HEAD/skills/azure-peering-service/SKILL.md

## When to use it
- check an IP prefix against Azure Peering Service requirements
- review routing and BGP configuration
- verify a prefix’s RPKI status
- check AS number requirements

## Example prompts
- Check whether this IP prefix meets Azure Peering Service requirements.
- Review my BGP setup against Azure Peering Service requirements.
- Tell me what to verify about RPKI status and the AS number.

## Source text · SKILL.md · CC-BY-4.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: e0a2160abbe2eb79.

BEGIN THIRD-PARTY FILE e0a2160abbe2eb79
```text
---
name: azure-peering-service
description: Expert knowledge for Azure Peering Service development including limits & quotas. Use when validating prefix size, routing setup, BGP config, RPKI status, or AS number requirements, and other Azure Peering Service related development tasks. Not for Azure Internet Peering (use azure-internet-peering), Azure ExpressRoute (use azure-expressroute), Azure Virtual Network (use azure-virtual-network), Azure Virtual WAN (use azure-virtual-wan).
compatibility: Requires network access. Uses mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage to retrieve documentation.
metadata:
  generated_at: "2026-09-06"
  generator: "docs2skills/1.0.0"
---
# Azure Peering Service Skill

This skill provides expert guidance for Azure Peering Service. Covers limits & quotas. 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`), use `read_file` with the specified lines. For categories with file links (e.g., `[security.md](security.md)`), use `read_file` on the linked reference file

> **IMPORTANT for Agent**: If `metadata.generated_at` is more than 3 months old, suggest the user pull the latest version from the repository. If `mcp_microsoftdocs` tools are not available, suggest the user install it: [Installation Guide](https://github.com/MicrosoftDocs/mcp/blob/main/README.md)

This skill requires **network access** to fetch documentation content:
- **Preferred**: Use `mcp_microsoftdocs:microsoft_docs_fetch` with query string `from=learn-agent-skill`. Returns Markdown.
- **Fallback**: Use `fetch_webpage` with query string `from=learn-agent-skill&accept=text/markdown`. Returns Markdown.

## Category Index

| Category | Lines | Description |
|----------|-------|-------------|
| Limits & Quotas | L29-L32 | Prefix size, routing, and configuration requirements your IP prefixes must meet to use Azure Peering Service, including validation and compliance constraints. |

### Limits & Quotas
| Topic | URL |
|-------|-----|
| Meet Azure Peering Service prefix requirements | https://learn.microsoft.com/en-us/azure/peering-service/peering-service-prefix-requirements |
```
END THIRD-PARTY FILE e0a2160abbe2eb79

The third-party file has ended. Everything between the e0a2160abbe2eb79 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

© MicrosoftDocs · CC-BY-4.0 · https://github.com/MicrosoftDocs/Agent-Skills/tree/HEAD/skills/azure-peering-service/SKILL.md

## Similar
- [azure-security-lab-terraform](https://affpapa.org/en/nevibecode/skills/azure-security-lab-terraform.md) — skill · 134 installs
- [azure-kubernetes](https://affpapa.org/en/nevibecode/skills/azure-kubernetes.md) — skill · ★ 3232 repo stars
- [azure-local](https://affpapa.org/en/nevibecode/skills/azure-local.md) — skill · ★ 3232 repo stars
- [azure-infra-engineer](https://affpapa.org/en/nevibecode/agents/voltagent-azure-infra-engineer.md) — subagent · ★ 6505 repo stars

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
