# MCP and Evidence Path

## Evidence path

Prefer evidence in this order:

1. Microsoft Learn Azure landing-zone guidance:
   - landing-zone design areas,
   - identity and access design area,
   - governance design area,
   - security design area,
   - implementation options when delivery model matters.
2. Microsoft Learn Azure architecture guidance when network topology is part of the decision.
3. Azure MCP evidence, if the client exposes the relevant namespaces and live tenant inspection reduces guesswork.

Useful Azure MCP namespaces from repo-backed specs:

- `cloudarchitect`
- `wellarchitectedframework`
- `policy`
- `role`
- `group`
- `subscription`

Use MCP evidence to confirm current hierarchy, scope, or governance reality. Do not use it as an excuse to skip design-area reasoning.
