Add Azure DocumentDB control-plane MCP proposal

[udsmicrosoft]

Summary

• Proposes Azure MCP as the primary user entry point for the complete Azure DocumentDB control-plane capability.
• Uses native Azure MCP commands by default for stateless ARM reads and mutations, with a DocumentDB-owned orchestration component only when durable state or independently constrained execution is required.
• Defines identity, risk tiers, mutation safety, secret handling, long-running operations, durable workflows, delivery phases, and acceptance criteria.
• Records what the read-only list/get POC demonstrated and which mutation and production questions remain unresolved.

[German Eichberger (xgerman)]

Summary

The architecture direction is understandable, but the proposal often states it in implementation shorthand rather than decision-oriented language. These non-blocking edits clarify committed versus conditional scope, potentially misleading undo/redo terminology, undefined acronyms, and the full-feature exit criteria. Together with the concrete replacement text in the existing threads, they should make the proposal easier for product, security, and engineering approvers to evaluate consistently.

[German Eichberger (xgerman)]

Summary

The update addresses the earlier clarity feedback well: it now separates target from validated scope, explains the native versus orchestrated paths with examples, makes the Azure CLI POC-only, adds a glossary, and turns acceptance into a checklist. I found four remaining non-blocking consistency issues where wording or examples conflict with definitions elsewhere in the proposal.

[Lei Jiang (lionelc)]

There may be one step missing from the proposal. The question is: can we put all work in microsoft/mcp alone and deploy it from there? We need an end-to-end proposal before diving into feature details