Azure AI models
-
microsoft decision 1 model from Microsoft (version 1) microsoft microsoft decision 1 model, version 1
This optional research check is not the main feedback path. For maintainer observations, use page feedback instead. Founder or repeat-reader observations are qualitative, not unbiased first-time-reader results.
Read the briefing, then answer from memory: what changed most, where, and what does the evidence prove? This measures comprehension, not whether you liked the design.
Privacy: answers and timing stay in this page's memory. No analytics, cookies, background submissions, or browser storage. Ordinary page/evidence requests still reach the static host. Opening a GitHub draft sends its summary to GitHub, but does not submit an issue. You review it and choose the final Submit on GitHub.
Public feedback: submitted issues and attachments in this repository are public. Do not share secrets or private information. The dashboard needs no backend or authentication token.
Use one attempt. Switching away from this tab marks it interrupted; it does not silently pause the clock. You may stop or skip at any time. Do not enter names, email addresses, subscription IDs, or private workload details.
No screenshot capture is offered in this timed check. Use normal page feedback for optional screenshots.
Case: 2026-10-10. The timer limits reading, not answering. This is a self-selected check, not a controlled experiment.
Choose your perspective and prior familiarity to begin.
At a glance — since 2026-10-09Daily regional evidence
What this proves: read-only catalog/list or measurement evidence; not quota, capacity, successful deployment, outage, or confirmed retirement. Methodology
New regions: + Australia Central 2+ Korea Central Dropped: − East US− UAE North
Australia Central, Australia Central 2, Australia East, Australia South East, Austria East, Belgium Central, Brazil South, Brazil South East, Canada Central, Canada East, Central India, Central US, Central US EUAP, Chile Central, Denmark East, East Asia, East US, East US 2, East US 2 EUAP, East US STG, France Central, France South, Germany North, Germany West Central, India South Central, Indonesia Central, Israel Central, Italy North, Japan East, Japan West, Jio India Central, Jio India West, Korea Central, Korea South, Malaysia West, Mexico Central, New Zealand North, North Central US, North Europe, Norway East, Norway West, Poland Central, Qatar Central, South Africa North, South Africa West, South Central US, South Central US STG, South East Asia, South India, Spain Central, Sweden Central, Switzerland North, Switzerland West, UAE Central, UAE North, UK South, UK West, West Central US, West Europe, West India, West US, West US 2, West US 3
Absence tracking starts at 2026-09-05; older disappearances may not be included.
All regions and services. Groups below separate new changes from continuing observations.
2,585 feature-region records
320 feature-region records
Australia Central 2, Korea Central
Example: Standard D128ads V7 VM size. Listing coverage: 29 → 31 regions.
New regional listing of an already observed feature.
Documented family
Standard_D128ads_v7 - General purpose VM size
Standard_D128ads_v7 is a general purpose VM size decoded from Azure's naming convention.
Naming-convention decoding does not verify memory, CPU model, GPU model, disk throughput, network bandwidth, quota, capacity, price, successful deployment, or measured performance.
Read more: Azure VM sizes naming conventions · General purpose family overview
Catalog/list evidence only; verify exact requirements before changing regional plans.
38 feature-region records
East US, UAE North
Example: Standard Nv16as V4 VM size. Listing coverage: 11 → 10 regions.
Documented family
Standard_NV16as_v4 - GPU visualization optimized VM size
Standard_NV16as_v4 is a gpu visualization optimized VM size decoded from Azure's naming convention.
Naming-convention decoding does not verify memory, CPU model, GPU model, disk throughput, network bandwidth, quota, capacity, price, successful deployment, or measured performance.
Read more: Azure VM sizes naming conventions · GPU visualization optimized family overview
If this matches a planned regional target, verify it with the provider. This is not an outage or retirement notice.
2,227 feature-region records
Australia East, Brazil South, Canada Central, Central India, Central US, Central US EUAP, East US 2, East US 2 EUAP, France Central, Germany West Central, India South Central, Italy North, Japan East, Korea Central, North Central US, North Europe, Norway East, Norway West, Poland Central, South Africa North, South Central US, South East Asia, Spain Central, Switzerland North, UK South, West Europe, West US, West US 2, West US 3
Example: Standard Nv16as V4 VM size. Listing coverage: 11 → 10 regions.
Documented family
Standard_NV16as_v4 - GPU visualization optimized VM size
Standard_NV16as_v4 is a gpu visualization optimized VM size decoded from Azure's naming convention.
Naming-convention decoding does not verify memory, CPU model, GPU model, disk throughput, network bandwidth, quota, capacity, price, successful deployment, or measured performance.
Read more: Azure VM sizes naming conventions · GPU visualization optimized family overview
Previously tracked delistings remain absent. No new delistings does not mean recovery.
606 feature-region records
31 feature-region records
Australia East, Brazil South, Canada Central, Canada East, Central US, East US, East US 2, France Central, Germany West Central, Italy North, Japan East, Japan West, Korea Central, North Central US, Norway East, Poland Central, South Africa North, South Central US, South India, Spain Central, Sweden Central, Switzerland North, Switzerland West, UAE North, UK South, UK West, West Central US, West Europe, West US, West US 2, West US 3
Example: microsoft decision 1 model from Microsoft (version 1). Listing coverage: 0 → 31 regions.
First observed in retained monitoring history; not a confirmed product launch.
Category context
microsoft decision 1 (catalog version 1) - microsoft
A model identifier observed by this modality; exact capabilities are not verified.
No exact model capability or version is verified. The source provides category context only. Regional model-catalog evidence does not establish quota, account approval, deployment type, inference access, content filtering, performance, or data residency.
Read more: microsoft model catalog (category only) · Search Microsoft Learn for this exact identifier (not verified)
Catalog/list evidence only; verify exact requirements before changing regional plans.
543 feature-region records
Australia East, Brazil South, Canada Central, Canada East, Central India, Central US, East Asia, East US, East US 2, France Central, Germany West Central, Italy North, Japan East, Japan West, Korea Central, North Central US, North Europe, Norway East, Poland Central, South Africa North, South Central US, South East Asia, South India, Spain Central, Sweden Central, Switzerland North, Switzerland West, UAE North, UK South, UK West, West Central US, West Europe, West US, West US 2, West US 3
Example: llama 3 2 11b vision instruct model from Meta (version 1). Listing coverage: 0 → 0 regions.
Category context
llama 3 2 11b vision instruct (catalog version 1) - meta
A model identifier observed by this modality; exact capabilities are not verified.
No exact model capability or version is verified. The source provides category context only. Regional model-catalog evidence does not establish quota, account approval, deployment type, inference access, content filtering, performance, or data residency.
Read more: meta model catalog (category only) · Search Microsoft Learn for this exact identifier (not verified)
Previously tracked delistings remain absent. No new delistings does not mean recovery.
32 feature-region records
Australia Central, Australia Central 2, Australia South East, Austria East, Belgium Central, Brazil South East, Central India, Central US EUAP, Chile Central, Denmark East, East Asia, East US 2 EUAP, East US STG, France South, Germany North, India South Central, Indonesia Central, Israel Central, Jio India Central, Jio India West, Korea South, Malaysia West, Mexico Central, New Zealand North, North Europe, Norway West, Qatar Central, South Africa West, South Central US STG, South East Asia, UAE Central, West India
Example: microsoft decision 1 model from Microsoft (version 1). Listing coverage: 0 → 31 regions.
Category context
microsoft decision 1 (catalog version 1) - microsoft
A model identifier observed by this modality; exact capabilities are not verified.
No exact model capability or version is verified. The source provides category context only. Regional model-catalog evidence does not establish quota, account approval, deployment type, inference access, content filtering, performance, or data residency.
Read more: microsoft model catalog (category only) · Search Microsoft Learn for this exact identifier (not verified)
Catalog/list evidence only; verify exact requirements before changing regional plans.
No matching change or evidence-gap records. This is not a deployment-health assessment.
2,770 tracked listings remain absent. Zero new delistings does not mean previous absences recovered. Absence tracking starts at 2026-09-05; older disappearances may not be included.
Previous snapshot: 2026-10-09T03:50:53.585372+00:00
Current snapshot: 2026-10-10T03:54:25.455152+00:00
Snapshot timestamps do not establish freshness of every carried-forward modality. The monitor does not assess your running workloads.
Added check records: 63; removed check records: 0. Changes to the observation set do not establish provider intent.
Grouped by feature. Coverage counts are scan-wide; region and service filters limit the listed records.
Open to load the complete records, without rerunning probes.
This is not submitted. Open a GitHub draft to review a human-readable summary of your answers, case/view IDs, timing, and eligibility. No raw JSON packet goes in the URL. Only your final Submit on GitHub creates the public issue.
The full local record includes your answers, timing, role, case ID, and presentation version, with no expected answers or automatic grade. You may download JSON and manually attach it to the draft. Review it first: attachments upload immediately when pasted or attached on GitHub, even before you submit the issue.
GitHub may log the draft URL and requires its own sign-in to submit. The dashboard never asks for a token. If the summary exceeds the draft URL limit, the full local result and JSON download remain available; nothing is truncated or automatically sent.