# Azure Regional Feature Availability Monitor - LLM Reference

This project publishes public, read-only evidence about Azure regional feature rollout. It does not perform create/delete deployment probes, quota checks, inference tests, or private subscription capacity validation.

## Canonical URLs

- Site: https://azwatch.operator.lat/
- Repository: https://github.com/sergey-goncharenko/azure-region-monitor
- Latest JSON snapshot: https://azwatch.operator.lat/api/latest.json
- History index: https://azwatch.operator.lat/api/history/index.json
- Methodology: https://azwatch.operator.lat/methodology.html
- Sitemap: https://azwatch.operator.lat/sitemap.xml

## Snapshot Summary

- Timestamp: 2026-05-14T05:27:41.944718+00:00
- Regions: 62
- Checks: 157,108
- Available: 94,002
- Unavailable: 59,451
- Partial: 0
- Unknown: 3,655

## Modalities

- AKS Kubernetes versions: 4 features, 248 checks
- AKS extensions: 727 features, 45,074 checks
- Azure AI models: 261 features, 16,182 checks
- Azure Functions: 27 features, 1,674 checks
- Container Apps: 5 features, 310 checks
- VM SKUs: 1,510 features, 93,620 checks

## Snapshot Shape

`api/latest.json` has this shape:

```json
{
  "timestamp": "ISO-8601 UTC timestamp",
  "regions": {
    "<azure-region>": {
      "<service>": {
        "<feature-key>": {
          "status": "available | unavailable | partial | unknown",
          "message": "optional probe message",
          "error_code": "optional error code",
          "latency_ms": "optional latency"
        }
      }
    }
  }
}
```

## Interpretation Rules

- Treat unavailable as absence from a read-only catalog or listing, not as quota exhaustion or deployment failure.
- Treat unknown as no trustworthy evidence for that region/feature pair.
- Use methodology.html for modality-specific caveats before summarizing availability claims.
- Full daily history snapshots are published as gzip JSON files referenced by `api/history/index.json`.

## History

Recent change days in published summary: 5.