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

## Knowledge Contribution

**Type:** Pitfall
**File:** `knowledge/services/key-vault.md`

### 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

Open knowledge/services/key-vault.md and review its existing structure for advisory notes. Add the supplied Stage 1: Managed Identity notes in the requested format, then confirm the section is complete, readable, and consistent with the surrounding knowledge content.

Written by the indexing model from the issue text.