← Back to directory

Azure / Model configuration

Foundry · Standard · Australia East

AU processing documented

The current regional availability matrix lists this model in Australia East for Standard/Regional usage billing.

The important distinction:Availability changes over time and is subscription-specific. Check live deployment access, quota and version lifecycle.

Source review: 09 Nov 2026 · Exact model configuration not yet verified

Model coverage

gpt-4.1-mini · 2025-04-14

API access

Azure subscription and model deployment; check quota and live availability

Billing

Pay per token; Australia East input/output price by SKU not yet captured

Capacity commitment

No reserved capacity required for this service category.

Storage

Model processing is region-scoped in Australia East. Stored resource data and stateful features need their own location and retention review.

Retention and training

Inputs and outputs are not used to train base models without permission. Abuse monitoring may retain flagged samples for human review unless eligible Modified Abuse Monitoring terms apply. Stateful features can store content.

Ownership and control

Microsoft operates this Azure service. Australian processing does not establish Australian ownership.

What to check before using it

  1. Create a Standard deployment in Australia East with version 2025-04-14.
  2. Avoid Global Standard and Data Zone deployments if the workload requires Australia-only inference.
  3. Check current price, quota, retirement status and stateful feature storage.

Still to verify

Sources and supported claims

Documentation

Azure model and region availability ↗

Microsoft lists gpt-4.1-mini · 2025-04-14 for Standard/Regional deployment in Australia East. Standard/Regional prompts and responses are processed in the deployment region.

Checked 2026-11-09 · Scope: this service profile
Documentation

Azure deployment types ↗

Standard deployment is pay-per-token and region-scoped where available.

Checked 2026-11-09 · Scope: this service profile
Documentation

Azure OpenAI data privacy ↗

Training, stateful feature storage, content filters and abuse monitoring are distinct controls.

Checked 2026-11-09 · Scope: this service profile

Add to comparison →Suggest a correction

made. directory guide

Ask the directory

Ask about listed providers, Australian processing, model routes, sources, API access, billing or commitments.

The directory does not store chat history. Provider processing and retention terms still apply; avoid sharing confidential or personal information.

Start with a question

Compare what providers publish, including where the evidence leaves gaps.

0 / 1,600

Directory snapshot reviewed 9 November 2026. Follow the linked sources and check your account configuration before relying on a provider claim.