azure-peering-service ยท diff
git:20260520.b45a2ef to git:20260907.90ec55f
6 added, 6 removed. Audit A to A.
---
name: azure-peering-service
- description: Expert knowledge for Azure Peering Service development including best practices. Use when designing Peering Service prefixes, routing policies, prefix validation rules, or connectivity constraints, and other Azure Peering Service related development tasks. Not for Azure Internet Peering (use azure-internet-peering), Azure Virtual Network (use azure-virtual-network), Azure Virtual WAN (use azure-virtual-wan), Azure ExpressRoute (use azure-expressroute).
+ 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-05-17"
+ generated_at: "2026-09-06"
generator: "docs2skills/1.0.0"
---
# Azure Peering Service Skill
- This skill provides expert guidance for Azure Peering Service. Covers best practices. It combines local quick-reference content with remote documentation fetching capabilities.
+ 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 |
|----------|-------|-------------|
- | Best Practices | L29-L32 | Technical requirements and best practices for configuring Azure Peering Service prefixes, including routing, prefix validation, and connectivity constraints. |
+ | 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. |
- ### Best Practices
+ ### Limits & Quotas
| Topic | URL |
|-------|-----|
- | Meet Azure Peering Service prefix technical requirements | https://learn.microsoft.com/en-us/azure/peering-service/peering-service-prefix-requirements |
+ | Meet Azure Peering Service prefix requirements | https://learn.microsoft.com/en-us/azure/peering-service/peering-service-prefix-requirements |