Skip to content

Build Independently confirmed2 publishers 3 min read Published Updated

Foundry offers Provisioned Throughput for two of the three GPT-6 models

Microsoft says evaluations should decide which GPT-6 model runs each agent. The serving matrix leaves Luna without reserved capacity. GitHub turns both new models on for admins who left the default alone.

The Engineer · Build desk

Send a correction

Illustration accompanying Foundry offers Provisioned Throughput for two of the three GPT-6 models
Generated illustration

What happened

  • Microsoft made GPT-6 Sol and GPT-6 Luna generally available in Microsoft Foundry alongside GPT-6 Astra, which it recommends as the starting point for demanding reasoning and computer-use work.
  • GitHub added both models to the Copilot picker in VS Code, Visual Studio, the Copilot CLI, JetBrains, Xcode, Eclipse and its mobile apps, billed under usage-based billing on a gradual rollout.
  • Copilot Business and Enterprise admins govern access through model policy, where new models switch on automatically unless the global default is off or that model is explicitly disabled.

Why it matters

  • Who has to decide decision A team without comparison runs ends up on whatever tier GitHub's model policy turns on for its coding agents, and the cheapest place to find that out is an eval run.
  • What it limits constraint Any high-volume step that also needs guaranteed throughput has to be promoted from Luna to Sol, so predictability comes at a higher unit cost.
  • Who's exposed exposure A latency-sensitive agent pinned to the EU Data Zone falls outside the region list for Priority Processing, so an EU tenant and a Global tenant running the same agent are not on the same serving tier.
  • What it costs cost Cost per task is the measure Microsoft proposes, and producing it is customer-side work: traces, token counts per tier and a completion label per task, before any migration is priced.

Next story · Invest · Sep 27

Sending work to GPT-6 Luna saves more than OpenAI's halving of Sol's price

Confirmed2 publishers

The setting that decides this for most teams is in Copilot's model policy. GitHub's changelog says that under default model enablement, new models are enabled automatically unless an administrator has turned off the global default or explicitly disables the model [14]. Rollout is gradual [13]. On a Business or Enterprise tenant where nobody has opened that page, Sol and Luna arrive in the picker in VS Code, Visual Studio, the Copilot CLI, JetBrains, Xcode and Eclipse on GitHub's schedule [12].

Microsoft's own guidance treats the choice as an evidence problem. "The right model for a job should be determined through evaluations: an agent handling a complex business decision and one routing routine requests have different needs," the Azure post says [7]. It recommends starting with Astra for demanding work and carrying higher-volume workloads to Sol and Luna [5], with Luna aimed at extraction, summarization, request routing and routine customer interactions [6].

Then read the deployment list, because it does not line up with the tiers. Standard covers all three models across all 28 Global regions plus the US and EU Data Zones [2]. Provisioned Throughput covers Astra and Sol, in Global regions and the US and EU Data Zones [3]. Priority Processing is listed for Sol only, in Global regions and US Data Zones [4]. Count the options per model: Sol appears in three, Astra in two, Luna in one [17]. Luna is the model Microsoft recommends for the highest call volumes [18].

The plan matrix runs the other way. Sol needs Copilot Pro+, Max, Business or Enterprise, and Luna is the one of the two that also reaches Copilot Pro [11][20]. Both bill under usage-based billing, with GitHub pointing to its pricing page for rates [15].

On money, Microsoft writes that customers should look beyond pricing per token and seek to understand cost per task, which it calls a better measure of ROI [8]. The post refers to an accompanying chart it says illustrates why enterprise customers on Foundry are switching to GPT-5.6 Sol and the latest GPT-6 offerings; the post text does not include the chart's figures [9].

The named customer in the post talks about integration and support. "Through Azure, we reliably integrate advanced models into our agentic workflows, enabling Manus to understand user intent, plan tasks, and execute complex work," said Tao Zhang, Co-Founder and Product Partner at Manus [16].

So the harness has real work to do. For each agent step you need a completion measure, token counts per tier, and a note of which serving option that step actually has available in the region it runs in. Sol is the only model in the lineup for which all three serving options are listed [17].

What to watch

  • Whether Provisioned Throughput is extended to Luna, which would make the cheapest tier viable for reserved-capacity batch work.
  • Whether Priority Processing reaches the EU Data Zone, or Astra and Luna, beyond the current Sol-only listing.
  • Whether Microsoft publishes the cost-per-task figures behind the switching chart, or per-token prices for the three models.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence56
Adoption34
Hype gap+30
Incentives92
Confidence68
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    Microsoft announced that GPT-6 Sol and GPT-6 Luna join its generally available lineup in Microsoft Foundry, expanding the GPT-6 series alongside GPT-6 Astra.

    Reported SupportedView cited source
  2. [2]

    Standard deployment is available for Astra, Sol and Luna across all 28 Global regions, and US and EU Data Zones.

    Reported SupportedView cited source
  3. [3]

    Provisioned Throughput is available for Astra and Sol across Global regions and US and EU Data Zones.

    Reported SupportedView cited source
  4. [4]

    Priority Processing is available for Sol across Global regions and US Data Zones.

    Reported SupportedView cited source
  5. [5]

    Microsoft recommends customers start with GPT-6 Astra for demanding work, and says that for higher-volume workloads GPT-6 Sol and Luna carry that progress forward.

    Reported SupportedView cited source
  6. [6]

    Microsoft says GPT-6 Sol is excellent for general-purpose use, and that Luna should be used for extraction, summarization, request routing and routine customer interactions.

    Reported SupportedView cited source
  7. [7]

    "The right model for a job should be determined through evaluations: an agent handling a complex business decision and one routing routine requests have different needs."

    Reported Supported Source: Microsoft Azure blog post announcing GPT-6 Sol and Luna in Microsoft FoundryView cited source
  8. [8]

    Microsoft writes that customers should look beyond pricing per token and seek to understand cost per task, which it calls a better measure for understanding the ROI of AI.

    Reported SupportedView cited source
  9. [9]

    The Azure post refers to an accompanying chart it says illustrates why enterprise customers on Microsoft Foundry are switching to GPT-5.6 Sol and the latest GPT-6 offerings; the post text does not include the chart's figures.

    Reported SupportedView cited source
  10. [10]

    GitHub describes GPT-6 Sol as a balanced model for interactive and agentic coding, and GPT-6 Luna as a lightweight, cost-efficient model and the lowest-cost option in the GPT-6 family.

    Reported SupportedView cited source
  11. [11]

    GPT-6 Sol is available to Copilot Pro+, Max, Business and Enterprise plans; GPT-6 Luna is available to Copilot Pro, Pro+, Max, Business and Enterprise plans.

    Reported SupportedView cited source
  12. [12]

    The models can be selected in the model picker in Visual Studio Code, Visual Studio, Copilot CLI, the GitHub Copilot cloud agent, the GitHub Copilot app, github.com, GitHub Mobile iOS and Android, JetBrains, Xcode and Eclipse.

    Reported SupportedView cited source
  13. [13]

    GitHub says rollout of the two models will be gradual.

    Reported SupportedView cited source
  14. [14]

    Copilot Enterprise and Copilot Business plan administrators can manage access to GPT-6 models through the model policy in Copilot settings; under default model enablement, new models are enabled automatically unless an administrator has turned off the global default or explicitly disables this model.

    Reported SupportedView cited source
  15. [15]

    GitHub says the models are billed under usage-based billing and points to its pricing page for Copilot models and requests.

    Reported SupportedView cited source
  16. [16]

    "Through Azure, we reliably integrate advanced models into our agentic workflows, enabling Manus to understand user intent, plan tasks, and execute complex work."

    Reported Supported Source: Tao Zhang, Co-Founder & Product Partner, ManusView cited source
  17. [17]

    Counting the three serving options Microsoft lists, Sol appears in all three (Standard, Provisioned Throughput, Priority Processing), Astra in two, and Luna in one.

    Derived Supported
  18. [18]

    Luna is the model in the announced lineup with no reserved-capacity option, because Provisioned Throughput is listed for Astra and Sol only.

    Derived Supported
  19. [19]

    In the EU Data Zone the available options are Standard for all three models and Provisioned Throughput for Astra and Sol, since Priority Processing is listed only for Global regions and US Data Zones.

    Derived Supported
  20. [20]

    Of the two newly added Copilot models, Luna has the wider plan coverage because it includes Copilot Pro, while Sol starts at Pro+.

    Derived Supported

Sources

2 independent publishers whose own reporting we read for this story.

  1. azure.microsoft.com

    2 articles · September 22, 2026

    GPT-6 Astra, Sol, and Luna: For production agents in Microsoft Foundry
  2. github.blog

    1 article · September 22, 2026

    OpenAI's GPT-6 Sol and GPT-6 Luna now available - GitHub Changelog

Topics and entities

Topics