azure-celisted

# Azure Customer Edge Run CE work as an immutable cross-plane transaction. Never substitute generic `az_exec`, legacy Azure VNet Site, Fleet, or shared registration-token workflows. Read [contracts.md](references/contracts.md) before planning or mutating a CE site. ## Orchestration 1. Research the current vendor procedure before making any recommendation. Use `web_search` to retrieve the official F5 **Deploy Secure Mesh Site v2 in Azure** guide from `docs.cloud.f5.com` and Microsoft image/SKU guidance from `learn.microsoft.com`. Read the relevant results and cite their titles and URLs. Do not substitute memory, cached identifiers, third-party pages, or generic CLI help. If current official sources cannot be retrieved, stop before recommending a catalog tuple, region, VM size, or plan. 2. Check Azure authentication with `az_account_show`. Check Platform authentication without displaying credentials. 3. Call `azure_compute_discover` without publisher, offer, plan, version, or VM-size hints unless the user explicitly pins one. The tool must enumerate live Azure publishers, offers, image SKUs, exact versions, and subscription-aware VM SKUs; validate terms, quota, policy, zones, NIC limits, Route Server support, and brownfield proximity; and persist a discovery artifact. Require `research.method=azure-cli-live`, the enumerated command receipt, and official source URLs in its result. Never guess or copy catalog identifiers from a prior s