Latest in AI
GPT-6.2 Astra Missing in Microsoft Copilot? Check the App and Frontier Access
Copilot Studio and Cowork can get Astra without the same preview rules as Word, Excel, PowerPoint and Chat. Here’s how to narrow down a missing model.
Microsoft announced its GPT-6.2 Sol and Astra rollout on November 20. Where you open Copilot matters. Astra is rolling out to eligible users in Cowork and Studio, while in Chat, Word, Excel and PowerPoint, Microsoft lists it for Frontier users. If Astra is missing in Word but present in Studio, that can be expected.
OpenAI's model announcement does not tell you which Microsoft product surface has finished rolling out. Start from the place you actually need to use the model.
Check the rollout by app
| Copilot surface | GPT-6.2 Sol | GPT-6.2 Astra |
|---|---|---|
| Cowork and Studio | Worldwide rollout for eligible users | Worldwide rollout for eligible users |
| Chat, Excel, PowerPoint and Word | Worldwide rollout for eligible users | Frontier users |
The table describes Microsoft's rollout, not a guarantee that every account is enabled. An employee who can use Copilot in Word may still be outside the preview group for Astra. A Studio environment exposing Astra is not evidence that Word should also expose it for the same employee.
The announcement is about Microsoft Copilot. ChatGPT, GitHub Copilot and direct OpenAI API access have separate controls and model availability. Changing settings in one does not resolve a missing model in another.
Check the account, then the preview group
Confirm the person signed in with the expected work account, and record the exact Copilot surface and whether Sol is visible. Ask a Microsoft 365 admin to check the account's product eligibility and release state. A screenshot from another tenant usually does not answer either question.
For Word, Excel, PowerPoint or Chat, have the admin verify whether the affected account is included in an approved Frontier group. Microsoft's admin guide describes a Frontier control that can target selected users or groups. For a pilot, compare one approved preview account with a similarly licensed account outside that group. Use the same app and client type. If the preview account sees Astra and the other does not, that is more useful evidence than switching between apps.
An admin can also check the Frontier program requirements. Enrolling someone in Frontier does not automatically enable optional AI providers or make every feature available. Follow your organization's approval process rather than loosening provider settings to make a model appear.
Treat rollout and billing as separate checks
If Astra is missing in Cowork or Studio, start with eligibility and rollout there. Microsoft's announcement does not list the same Frontier requirement for those two products. The Microsoft 365 Message Center notice, archived publicly, describes usage-based billing for Astra in Cowork and Studio. Check the notice in your tenant and confirm who owns any applicable spend before expanding a pilot. API token prices from OpenAI do not tell you what Microsoft will bill.
When filing an internal support ticket, send the app name, client type, time of the check, whether Sol is available and whether the account is in the relevant Frontier group. Do not attach actual customer prompts or documents. That is enough to separate access troubleshooting from a question about model quality.
Test one task where Astra is visible
For a Word rollout, take a synthetic policy draft and ask both models to list contradictions and cite the relevant section numbers. Keep the source text and instructions identical. For an Excel rollout, use a small fabricated budget and ask for anomalies with cell references, without changing the workbook. Judge whether the references are right and how much review each answer needs.
If Sol handles the job with little correction, I would leave it in place while Astra rolls out. A controlled comparison on the app people actually use is more valuable than a screenshot proving the model exists somewhere else.
I'm Paras. I help AI teams explain model releases and enterprise rollout decisions in clear technical writing.