[Knowledge] deployment-guide: ## Advisory Notes — Stage 1: Managed Identity - **[Stabilit...

Start by reviewing the Build advisory review context and create knowledge/services/deployment-guide.md. Cover the eight required sections, including Terraform and Bicep patterns, application examples in Python, C#, and Node.js, and the managed identity stability and security notes; the work is done when every listed section is present and addresses the requested Stage 1 guidance.

Knowledge Contribution

Type: New service
File: knowledge/services/deployment-guide.md
Status: NEW FILE — this knowledge file does not exist yet and must be created

Context

Advisory Notes — Stage 1: Managed Identity

• [Stability] The identity module uses API version 2023-07-31-preview; preview APIs may introduce breaking changes or be retired — consider pinning to the GA version 2023-01-31 for production deployments.

• [Security] Deployment outputs (client ID, principal ID) are written to a local JSON file with no access controls; in CI/CD pipelines, prefer storing these in a Key Vault or using deployment output references directly to avoid credent

Rationale

Advisory Notes — Stage 1: Managed Identity

• [Stability] The identity module uses API version 2023-07-31-preview; preview APIs may introduce breaking changes or be retired — consider pinning to the GA version 2023-01-31 for production deployments.

• [Security] Deployment outputs (client ID, principal ID) are written to a local JSON file with no access controls; in CI/CD pipelines, prefer storing these in a Key Vault or using deployment output references directly to avoid credent

Content to Add

## Advisory Notes — Stage 1: Managed Identity

- **[Stability]** The identity module uses API version `2023-07-31-preview`; preview APIs may introduce breaking changes or be retired — consider pinning

Source

Build advisory review

Required Knowledge File Sections

The new knowledge file MUST include ALL of these sections:

1. Description (one-line summary)
2. When to Use (scenarios and selection criteria)
3. POC Defaults (default SKU, tier, configuration)
4. Terraform Patterns (azapi_resource with RBAC)
5. Bicep Patterns (ARM template resources)
6. Application Code (Python, C#, Node.js — where applicable)
7. Common Pitfalls (deployment failures, misconfigurations)
8. Production Backlog Items (what changes for production)