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

## Knowledge Contribution

**Type:** Pitfall
**File:** `knowledge/services/log-analytics.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/log-analytics.md` and review the existing section around the managed identity guidance. Add the advisory notes described in the issue, checking the full issue text for the intended content because the “Content to Add” excerpt is truncated. The work is done when the file contains the requested notes.

Written by the indexing model from the issue text.