Expert knowledge for Azure Operator Service Manager development including troubleshooting, best practices, security, configuration, and integrations & coding patterns. Use when onboarding CNFs/VNFs with Helm, managing ACR artifacts, configuring cluster registry, Private Link, or RBAC, and other Azure Operator Service Manager related development tasks. Not for Azure Operator Insights (use azure-operator-insights), Azure Operator Nexus (use azure-operator-nexus), Azure Resource Manager (use azure-resource-manager), Azure Networking (use azure-networking).
This skill provides expert guidance for Azure Operator Service Manager. Covers troubleshooting, best practices, security, configuration, and integrations & coding patterns. 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
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
Troubleshooting
L33-L38
Diagnosing and fixing AOSM onboarding issues with the Azure CLI extension and troubleshooting Helm chart installation failures in AOSM CNF deployments.
Best Practices
L39-L47
Best practices for onboarding/deploying AOSM, designing configuration groups, packaging CNFs with Helm, cleaning up publisher resources, and controlling CNF upgrade failure behavior.
Security
L48-L55
Securing AOSM with Private Link, custom RBAC/roles, and User Assigned Managed Identities for controlled, least-privilege access and secure SNS/service operator deployments.
Configuration
L56-L65
Configuring AOSM deployment behavior: cluster registry for edge resiliency, pausing/resuming site services, Helm cleanup/tests, NFO extension settings, and artifact store geo-replication.
Integrations & Coding Patterns
L66-L75
Using CLI/ARM/Helm with AOSM to onboard CNFs/VNFs, manage images and artifacts (ACR/storage-backed stores), and add ARM resources to network service designs