Problem statement
Azure MCP is consumed through multiple packages, operating systems, deployment channels, agent hosts, and language ecosystems. Independent distribution and integration work can produce inconsistent installation, configuration, identity, update, and compatibility experiences.
Outcome
Users can discover, install, configure, launch, update, and troubleshoot Azure MCP through supported channels and hosts with clear compatibility and ownership.
In scope
- Supported packages, registries, bundles, installers, and publication workflows
- Agent-host discovery, configuration, launch, identity, and compatibility contracts
- Operating-system and language ecosystem integration
- Versioning, signing, provenance, updates, rollback, and channel lifecycle
- Installation, policy, compatibility, and troubleshooting guidance
Out of scope
- Adding Azure service or command coverage
- Contributor and service-team onboarding workflow
- Core protocol or server architecture except where required by a supported host contract
- Adoption measurement beyond signals needed to operate a distribution channel
Routing rules
- Each distribution channel, package family, or host integration should use a focused child workstream.
- Shared packaging and compatibility requirements belong here when they affect more than one channel.
- Host-specific product implementation remains in the relevant child Epic.
Success criteria
Parent initiative
#3108
Problem statement
Azure MCP is consumed through multiple packages, operating systems, deployment channels, agent hosts, and language ecosystems. Independent distribution and integration work can produce inconsistent installation, configuration, identity, update, and compatibility experiences.
Outcome
Users can discover, install, configure, launch, update, and troubleshoot Azure MCP through supported channels and hosts with clear compatibility and ownership.
In scope
Out of scope
Routing rules
Success criteria
Parent initiative
#3108