[EPIC] Azure Service and Scenario Coverage

## Problem statement

Azure MCP service and scenario coverage grows through individual requests, service onboarding work, and cross-service workflows. Without a shared portfolio, it is difficult to prioritize gaps by user value, identify duplicate capabilities, or measure whether supported Azure scenarios are complete.

## Outcome

Azure MCP provides deliberate, sustainable coverage for priority Azure services and end-to-end user scenarios. Coverage decisions are based on user value, ownership, and measurable completeness rather than raw tool count.

## In scope

- Prioritize gaps in Azure service, resource, operation, and workflow coverage
- Group related command work into coherent service or scenario workstreams
- Define minimum useful coverage and acceptance criteria for each supported scenario
- Track cross-service workflows that require coordinated capabilities
- Identify obsolete, duplicate, or low-value coverage

## Out of scope

- Contributor intake and onboarding process improvements
- Packaging, distribution channels, or host compatibility
- Adoption measurement, usage analysis, or customer-feedback operations
- Service-specific implementation tasks that already belong to a narrower child Epic

## Routing rules

- Service and scenario workstreams may be child Epics of this Epic.
- Individual coverage requests should be children of the relevant service or scenario workstream when one exists.
- New service requests remain here until ownership, scope, and the correct workstream are clear.

## Success criteria

- [ ] Priority service and scenario gaps have explicit owners and acceptance criteria
- [ ] Supported scenarios define a minimum useful operation set
- [ ] Cross-service workflows are tracked as coherent workstreams
- [ ] Coverage decisions use customer value, usage evidence, and sustainable ownership
- [ ] Completed coverage is reflected in command documentation and evaluation prompts

## Parent initiative

microsoft/mcp#3108