[EPIC] Azure MCP Distribution and Host Integration

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

• Every supported channel and host has an owner and compatibility contract
• Publication and update workflows are repeatable, versioned, and auditable
• Installation, configuration, identity, and troubleshooting paths are documented and validated
• Unsupported combinations fail clearly rather than appearing partially functional
• Channel health and compatibility failures produce actionable signals

Parent initiative

microsoft/mcp#3108

The issue names no files, tests, or entry points; start by decomposing the routing rules into focused child workstreams and identifying supported channels and hosts. Done means each supported channel and host has an owner and compatibility contract, repeatable auditable publication and update workflows, validated installation and troubleshooting guidance, and actionable failure signals.