Update availability of models in Australia East region

[leongj]

• Added availability tick for gpt-5-mini 2025-08-07 in australiaeast which was added recently
  • source: https://foundry-models.azurewebsites.net/
  • source: https://aoaisolutionsizingtool.azurewebsites.net/

[learn-build-service-prod]

Learn Build status updates of commit ef6b0ae:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/ai-foundry/openai/includes/model-matrix/provisioned-models.md	✅Succeeded

For more details, please refer to the build report.

[Copilot]

Pull request overview

This PR updates the model availability matrix to reflect that the gpt-5-mini model (version 2025-08-07) is now available in the Australia East region for provisioned throughput deployments.

Changes:

• Added availability checkmark (✅) for gpt-5-mini 2025-08-07 in the australiaeast region in the provisioned models availability table

Comments suppressed due to low confidence (1)

articles/ai-foundry/openai/includes/model-matrix/provisioned-models.md:10

• The metadata date 05/07/2025 (May 7, 2025) is in the future relative to the current date (January 14, 2026 based on the instructions). This date should be updated to reflect when this change was actually made, or at minimum should be a date that has already passed.

ms.date: 05/07/2025

[Copilot]

The provisioned-global.md file (line 14) already shows gpt-5-mini 2025-08-07 as available (✅) in australiaeast for global provisioned deployments. This creates an inconsistency: the model appears to have been available in the global provisioned file but not in the regional provisioned-models.md file until now. Please verify whether this change represents a new availability or if this was previously available and the table was outdated. If the model was already available, consider whether the metadata date should reflect the original availability date rather than today's update date.

[Court72]

@mrbullwinkle

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[github-actions]

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict