What problem does it solve? Operating Microsoft's Azure SRE Agent (Preview) safely in production requires knowing its extension model, MCP connector constraints, and approval doctrine — without this guidance, teams risk unbounded blast radius, blown tool budgets, and un-audited autonomous remediation. ## Core Features & Use Cases - Extension Model Guidance: Covers the six extension primitives — Skills/runbooks, built-in Subagents, Python tools, MCP servers, agent hooks, and the Permission gate — with rules for choosing the lightest fitting primitive. - MCP Connector Model: Documents Streamable-HTTP vs stdio transports, Bearer/custom-headers/managed-identity auth, namespaced connection-id_tool registration, and the hard 80-tool-per-agent budget. - Approval Doctrine: Encodes the propose-then-approve safety model where the Permission gate evaluates every tool call (approve/policy/block) and composes with Managed-Identity RBAC, with audit telemetry routed to your own Application Insights. - Use Case: When wiring a Dynatrace MCP connector into Azure SRE Agent for AKS incident triage, use this Skill to scope tools per subagent with mcp_tools:, define gate rules before granting mutating tools, and keep auto-remediation opt-in. ## Quick Start Ask the AI to help configure an Azure SRE Agent MCP connector with proper permission-gate rules and a scoped tool budget for incident triage on AKS.