[Epic] Use Azure services with lifecycle-complete executable guidance

## Problem statement

Service guidance often stops at description or isolated code. Developers need current, secure, executable instructions spanning setup, development, deployment, operation, and diagnosis.

## Outcome

Priority Azure services have lifecycle-complete guidance that developers can execute safely from their working environment.

## Goals

- Cover prerequisites, authentication, SDK usage, deployment, operation, and troubleshooting
- Use supported terminology, APIs, and secure authentication patterns
- Produce executable commands and code with explicit assumptions
- Close material gaps across compute, data, messaging, storage, networking, and hybrid services

## Non-goals

- Shallow coverage for every Azure service
- Duplicating authoritative service documentation

## Success criteria

- [ ] Priority service journeys cover the complete lifecycle
- [ ] Examples execute against supported interfaces
- [ ] Guidance is validated for correctness, security, and currency

## Dependencies

Azure MCP, Microsoft Learn, SDK owners, service teams, and evaluation infrastructure.

No files, tests, or entry points are named. Start by clarifying the priority Azure service journeys and coordinating with Azure MCP, Microsoft Learn, SDK owners, service teams, and evaluation infrastructure. Done means lifecycle-complete guidance exists, examples execute against supported interfaces, and the guidance is validated for correctness, security, and currency.

Written by the indexing model from the issue text.