[Initiative] 🌐 Expand Azure scenario and service coverage

## Problem statement

Azure developers expect GitHub Copilot for Azure to help with complete tasks, not isolated service operations. Coverage is currently uneven across Azure services and developer journeys, and adding skills one request at a time does not ensure that the highest-value scenarios are complete, discoverable, or supported end to end.

## Vision

GitHub Copilot for Azure provides intentional coverage for the Azure scenarios developers use most. Each priority journey has a clear entry point, the required skills and tools, secure defaults, and an owner responsible for closing gaps.

## Who this helps

- **Azure developers** can complete common cloud tasks without discovering product boundaries themselves.
- **Azure service teams** get a consistent path to expose supported agent experiences.
- **Skill authors** can prioritize work against an explicit coverage model.
- **Maintainers** can invest in scenarios based on user value and measurable gaps.

## Goals (in scope)

- Define and maintain a prioritized map of Azure developer scenarios and service coverage
- Close the highest-value skill and tool gaps across build, deploy, operate, troubleshoot, and optimize journeys
- Ensure priority scenarios have complete workflows rather than disconnected operations
- Establish reusable onboarding patterns for Azure service teams and skill contributors
- Use product signals and user feedback to guide coverage investments

## Non-goals (out of scope)

- Providing shallow support for every Azure service
- Reimplementing capabilities already owned by Azure MCP or service teams
- Solving cross-client distribution and compatibility, which is tracked separately
- Treating raw skill count as the measure of success

## Success criteria

- [ ] Priority Azure scenarios and coverage gaps are documented, ranked, and owned
- [ ] Each top scenario has an end-to-end workflow with the required skills and tools
- [ ] New service coverage follows shared authoring, security, evaluation, and release standards
- [ ] User demand and completion signals inform the coverage roadmap
- [ ] Gaps discovered through support or evaluations produce scoped epics and measurable outcomes

## Dependencies

- **Azure MCP and service teams**: Scenario completion depends on stable, supported operations
- **Skill authoring and evaluation infrastructure**: New coverage must route and execute reliably
- **Product telemetry and feedback**: Prioritization requires trustworthy demand and completion signals
- **Release infrastructure**: New capabilities must reach supported clients consistently

Start by reviewing the success criteria and the stated dependencies on Azure MCP, service teams, skill authoring and evaluation infrastructure, telemetry, and release infrastructure. Identify a single priority scenario or coverage gap and check whether it can be scoped into a separate epic with measurable outcomes; this initiative is complete only when its ranked, owned coverage model and resulting end-to-end workflows are established.

Written by the indexing model from the issue text.