Repository navigation
[docs-vnext] docs: sync vnext with GPT Realtime 2.1 updates - #1028
Closed
github-actions[bot] wants to merge 1 commit into
Closed
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
Merge the latest GPT Realtime 2.1 and Codex model updates into both docs-vnext route families while preserving their existing navigation and link structure. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
Author
|
This pull request was automatically closed because it expired on 2026-09-30T19:37:03.447Z.
|
auto-merge was automatically disabled
September 30, 2026 22:33
Pull request was closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Updates
docs-vnext/for sync commit0312cc4. Microsoft Learn confirms the GPT Realtime 2.1 model IDs, GA/openai/v1protocol, supported transports, and expanded voice list. The vnext variants retain their existing route structure and concise wording while incorporating the newer facts.File comparisons
docs-vnext/docs.jsondocs-vnext/foundry-models/codex.mdxdocs-vnext/foundry-models/model-retirement-schedule.mdxdocs-vnext/foundry-models/models-sold-directly-by-azure-region-availability.mdxdocs-vnext/foundry-models/models-sold-directly-by-azure.mdxdocs-vnext/foundry-models/realtime-2.mdxdocs-vnext/foundry-models/realtime-audio-sip.mdxdocs-vnext/foundry-models/realtime-audio-webrtc.mdxdocs-vnext/foundry-models/realtime-audio-websockets.mdxdocs-vnext/foundry-models/realtime-audio.mdxdocs-vnext/models/capabilities/codex.mdxdocs-vnext/models/catalog/models-sold-directly-by-azure.mdxdocs-vnext/models/catalog/realtime-2.mdxdocs-vnext/models/catalog/realtime-audio-sip.mdxdocs-vnext/models/catalog/realtime-audio-webrtc.mdxdocs-vnext/models/catalog/realtime-audio-websockets.mdxdocs-vnext/models/catalog/realtime-audio.mdxValidation
git diff --checkpasses, the new page includes required frontmatter, and changed MDX uses Mintlify-compatible syntax.