Does Azure OpenAI (gateway) support the latest GPT-5 models in Atlas?

Azure OpenAI (gateway) provides access to the full GPT-5 family, including coding-specialized models like gpt-5.3-codex. However, new OpenAI models, such as the GPT-5.6 tier, typically become available on Azure weeks after their initial release via the direct OpenAI API.

What is the maximum context window available with Azure OpenAI (gateway) in Atlas?

The context window for Azure OpenAI (gateway) varies by the specific model you deploy. On the advanced GPT-5.4+ line, you can access models with a context window of up to 1.05M tokens, allowing Atlas to process very large codebases.

How does pricing work for Azure OpenAI (gateway) when used with Atlas?

Pricing for Azure OpenAI (gateway) is passthrough at your standard Azure rates. These rates broadly match OpenAI's direct pricing, integrating direct into your existing Azure billing and enterprise agreement. You pay for usage directly through your Azure account.

Can I keep my code data within my Azure region using Atlas with Azure OpenAI (gateway)?

Yes, a key benefit of Azure OpenAI (gateway) is that your data remains within your chosen Azure region. This ensures compliance with your existing enterprise agreement and data residency requirements, which is often the primary reason for selecting this provider.

Are coding-specific GPT-5 models available through Azure OpenAI (gateway)?

Yes, Azure OpenAI (gateway) provides access to the coding-specialized models within the GPT-5 family, including gpt-5.3-codex, gpt-5.1-codex-max, and gpt-5.1-codex-mini. These models are not enterprise-gated when accessed via Azure.

What setup is required to use Azure OpenAI (gateway) with Atlas?

You must set `AZURE_RESOURCE_NAME` and `AZURE_API_KEY` environment variables. Additionally, you need to create a named deployment for each model in the Azure portal. Atlas then resolves these deployments, falling back to chat completions if necessary.

Atlas with Azure OpenAI (gateway) in 2026

Azure OpenAI (gateway) provides Atlas users in 2026 with the full GPT-5 model family, including coding-specialized Codex models, all within your existing Azure enterprise agreement and chosen data region. Pricing is passthrough at Azure rates, broadly matching OpenAI's direct pricing, making it a robust choice for secure, large-scale development.

Why choose Azure OpenAI (gateway) for Atlas in 2026?

For enterprise developers in 2026, Azure OpenAI (gateway) is the premier choice for Atlas when data residency and existing Azure agreements are paramount. It provides the full GPT-5 model lineup, including specialized Codex models like gpt-5.3-codex, ensuring your coding agent operates within your secure cloud environment.

Atlas with Azure OpenAI (gateway) integrates directly with your Microsoft Azure infrastructure, allowing you to leverage your existing enterprise agreement and maintain data within your chosen Azure region. This capability is often the primary driver for selecting Azure OpenAI, providing crucial data residency and compliance benefits. The full GPT-5 family, including the powerful coding-specialized models such as gpt-5.3-codex, gpt-5.1-codex-max, and gpt-5.1-codex-mini, are readily available without the enterprise gating sometimes seen with other providers. Atlas is designed to resolve Azure deployments efficiently, first attempting `sdk.responses(modelID)` and then falling back to `sdk.chat(modelID)`, which ensures robust compatibility with both newer and older deployments you might have configured within your Azure environment.

What are the context window and pricing for Azure OpenAI (gateway)?

Azure OpenAI (gateway) offers a flexible context window that varies by the specific model deployed, reaching up to an impressive 1.05M tokens on the advanced GPT-5.4+ line. Pricing for Azure OpenAI (gateway) is passthrough at standard Azure rates, which broadly align with OpenAI's direct pricing structure.

The context window for Azure OpenAI (gateway) models is not fixed but depends on the specific GPT-5 model you choose to deploy within your Azure environment. Developers can access models with context windows reaching up to an impressive 1.05M tokens, particularly on the GPT-5.4+ line. This extensive context window enables Atlas to handle very large codebases, complex multi-file tasks, and maintain a deep understanding of project state over extended interactions. Regarding cost, Atlas passes through the pricing directly at Azure's prevailing rates. These rates are generally comparable to what you would pay for direct access to OpenAI's API, ensuring cost predictability and integration within your existing Azure billing framework. This passthrough model means you pay for what you use, integrated into your enterprise's Azure consumption, without additional markups from Atlas.

What are the tradeoffs of using Azure OpenAI (gateway) with Atlas?

While Azure OpenAI (gateway) offers significant enterprise benefits, developers should be aware of two key tradeoffs in 2026. First, each model requires a named deployment in the Azure portal before Atlas can utilize it. Second, new OpenAI models typically arrive on Azure weeks after their direct API release, meaning the newest GPT-5.6 tier might not be immediately available.

A primary consideration for Azure OpenAI (gateway) is the administrative overhead of creating named deployments. Simply having access to a model in Azure is insufficient; you must explicitly create a named deployment for each specific model in the Azure portal before Atlas can successfully call it. This step is crucial for Atlas to properly resolve and interact with the models you intend to use. Another important tradeoff is the latency in model availability. New OpenAI models, such as the current GPT-5.6 tier, typically become available on Azure weeks after they are released directly through OpenAI's API. This delay means that if your development workflow demands immediate access to the absolute latest model iterations for new capabilities or performance improvements, you might experience a waiting period when using Azure OpenAI (gateway).

When should I consider an alternative to Azure OpenAI (gateway) for Atlas?

You should consider an alternative to Azure OpenAI (gateway) for Atlas if your priority in 2026 is immediate access to the absolute newest OpenAI models, such as the GPT-5.6 tier, as soon as they are released. The Azure platform typically introduces these models weeks after their direct API availability.

While Azure OpenAI (gateway) is an excellent choice for enterprise environments prioritizing data residency, compliance, and leveraging existing Azure agreements, it may not be the optimal choice if your primary need is to leverage the very latest OpenAI model advancements the moment they are announced. Due to the typical release cadence, new OpenAI models, including the most recent GPT-5.6 tier, often become available on Azure weeks after their initial release via the direct OpenAI API. If your development strategy relies on integrating with bleeding-edge model capabilities without any delay, or if you prefer a setup with minimal pre-configuration steps for each model, exploring direct OpenAI API access or other providers might be more suitable for your Atlas workflow to ensure immediate access to new features.

Setup

01Set your Azure resource name and API key: `export AZURE_RESOURCE_NAME=my-resource` and `export AZURE_API_KEY=...`.
02Atlas will automatically construct the base URL as `https://<resource>.cognitiveservices.azure.com/openai`.
03Alternatively, explicitly set a `baseURL` within the `azure` provider block in your `atlas.json` file to override the derived one.
04Create a named deployment for your desired model (e.g., `gpt-5.3-codex`) in the Azure portal.
05Run `atlas models azure` in your terminal to confirm Atlas successfully detects your Azure deployments.
06Select your deployed Azure OpenAI model from the `/models` interface within Atlas to activate it.

Frequently asked questions

Does Azure OpenAI (gateway) support the latest GPT-5 models in Atlas?: Azure OpenAI (gateway) provides access to the full GPT-5 family, including coding-specialized models like gpt-5.3-codex. However, new OpenAI models, such as the GPT-5.6 tier, typically become available on Azure weeks after their initial release via the direct OpenAI API.
What is the maximum context window available with Azure OpenAI (gateway) in Atlas?: The context window for Azure OpenAI (gateway) varies by the specific model you deploy. On the advanced GPT-5.4+ line, you can access models with a context window of up to 1.05M tokens, allowing Atlas to process very large codebases.
How does pricing work for Azure OpenAI (gateway) when used with Atlas?: Pricing for Azure OpenAI (gateway) is passthrough at your standard Azure rates. These rates broadly match OpenAI's direct pricing, integrating direct into your existing Azure billing and enterprise agreement. You pay for usage directly through your Azure account.
Can I keep my code data within my Azure region using Atlas with Azure OpenAI (gateway)?: Yes, a key benefit of Azure OpenAI (gateway) is that your data remains within your chosen Azure region. This ensures compliance with your existing enterprise agreement and data residency requirements, which is often the primary reason for selecting this provider.
Are coding-specific GPT-5 models available through Azure OpenAI (gateway)?: Yes, Azure OpenAI (gateway) provides access to the coding-specialized models within the GPT-5 family, including gpt-5.3-codex, gpt-5.1-codex-max, and gpt-5.1-codex-mini. These models are not enterprise-gated when accessed via Azure.
What setup is required to use Azure OpenAI (gateway) with Atlas?: You must set `AZURE_RESOURCE_NAME` and `AZURE_API_KEY` environment variables. Additionally, you need to create a named deployment for each model in the Azure portal. Atlas then resolves these deployments, falling back to chat completions if necessary.

Try SeaShell in your terminal

The terminal-native AI coding agent. Free core, single binary.

Install SeaShell

Related guides

Atlas vs PearAI: A Developer's Guide to AI Coding Agents in 2026

Comparing Atlas, the terminal-native AI coding agent, with PearAI, a VS Code fork aggregating open agents, for developers in 2026. Evaluate features, pricing, and ecosystem.

Rename a Symbol Across the Repo with Atlas in 2026

How to rename a symbol across a repo with Atlas in 2026: findReferences gets the true reference set, grep catches strings and docs, and edit refuses ambiguous matches.

Atlas vs Cosine: Choosing Your AI Coding Agent in 2026

Compare Atlas and Cosine AI coding agents for 2026. Atlas offers terminal-native TUI, explicit change review, and BYO model keys. Cosine features its Lumen models and a 30.08% SWE-bench record.

Atlas for Astro: Islands, Content Collections, and Zero JS by Default in 2026

Atlas is a terminal-native AI coding agent for Astro in 2026. It reads astro.config.mjs, src/pages, and content collection schemas, drops needless client:load directives, and runs astro check.

Atlas vs Sourcery: Terminal AI Coding Agents in 2026

Comparing Atlas, the terminal-native AI coding agent, with Sourcery, the Python-first AI reviewer, in 2026. Evaluate features, pricing, and workflow for developers.

Atlas vs. Graphite: Choosing Your AI Coding Agent in 2026

Atlas and Graphite comparison for 2026. Atlas offers terminal-native AI with permission-gated tools and local embeddings. Graphite provides stacked PRs and AI review for GitHub teams.

Atlas for C++ in 2026

In 2026, C++ developers adopt Atlas, the terminal-native AI coding agent, to enhance productivity. Atlas offers secure, context-aware assistance for modern C++ projects, integrating with CMake and ensuring code quality

Atlas for dbt: Terminal-Native AI Coding in 2026

Atlas is a terminal-native AI coding agent for dbt. Read the ref() DAG, convert a table model to incremental, run dbt build against dev, and add tests in 2026.

Browse this resource hub