Thunder Bay AI
The Journal
PerspectiveJuly 15, 2026 6 min read

GPT-5.6 just became the default model in Microsoft 365 Copilot — the real Northwestern Ontario story is who hasn't turned it on

Word, Excel, PowerPoint, and Copilot Chat quietly got a smarter engine on July 9. No new invoice required. For a local organization already paying for Microsoft 365, the harder question is not whether to buy AI — it is why the tool sitting in the license is still switched off, or switched on with nobody checking what it can see.

On July 9, Microsoft made OpenAI's newest model, GPT-5.6, the preferred model behind Microsoft 365 Copilot across Word, Excel, PowerPoint, Copilot Chat, and Copilot Cowork. Nothing about that requires a Northwestern Ontario business, municipality, school board, or health authority to buy anything new — if a tenant already has Copilot licensing, the upgrade arrives on Microsoft's own rollout schedule, not on a purchase order. That is exactly why it matters more here than the GPT-5.6 model launch itself did two days earlier. This is not a new AI product to evaluate, pilot, and budget for. It is a capability jump inside software most local organizations already run — and it exposes a gap that has nothing to do with the technology: many of them do not actually know whether Copilot is switched on in their own tenant, or what it can read once it is.

What actually changed on July 9

Microsoft's own announcement, corroborated by OpenAI's release notes and TechCrunch's reporting, says GPT-5.6 became available the same day it reached general release in ChatGPT, Codex, and the OpenAI API — across Word, Excel, PowerPoint, Copilot Chat, and Copilot Cowork. Where a tenant has it, Copilot may automatically use GPT-5.6 when Microsoft judges it the better fit for a task, and where model selection is exposed, a user can pick it directly. Microsoft's own framing on the rollout is worth repeating exactly: availability varies by region and tenant configuration, so a Copilot that has not shown the new model yet is not broken — it is waiting its turn in the phased rollout.

A partnership that is not standing still

The announcement landed alongside reporting that Microsoft is also building and shifting some of its own apps toward in-house MAI models, partly to manage cost — meaning "GPT-5.6 is the preferred model today" and "Microsoft is reducing its OpenAI dependence" are both being reported as true at the same time. Neither company's efficiency or quality claims here have been independently benchmarked; they are vendor statements at launch. The practical read for a Northwestern Ontario organization is not to pick a side in that relationship. It is to notice that the engine running inside a licensed productivity suite is a decision made entirely by the vendor, on a timeline the tenant does not control — which is a reason not to build a critical process so tightly around any one model's specific behaviour that a routine engine swap breaks it.

Why this is a Northwestern Ontario story, not a Redmond one

Microsoft 365 is already the default productivity stack across the region — small businesses, the City of Thunder Bay, school boards, health authorities, and post-secondary institutions run on it, procured and IT-approved long before "AI adoption" was a line item anyone had to justify. That is what makes this different from every other model release in this space: the AI capability shows up inside software already sitting on local machines, with no new vendor evaluation, no new contract, and often no new conversation with whoever handles IT. That is also the risk. A capability that requires zero decision to appear is a capability that can appear without anyone deciding what it should be allowed to touch — which matters a great deal for an organization holding health records, student data, legal files, or resident information.

Two things to hold onto here. First, rollout is phased by region and tenant — Microsoft's own language — so do not assume every NWO organization with Copilot licensing has GPT-5.6 today; confirm your tenant's status directly rather than assuming from this post. Second, the underlying model is not fixed: Microsoft controls what powers Copilot, and reporting on its own MAI investment suggests that engine can change again without a tenant choosing it. Treat GPT-5.6-in-Copilot as the current state, not a permanent foundation to build an irreplaceable workflow on.

A practical first step

The realistic move is not to wait for a vendor pitch or a formal AI strategy document. Ask whoever manages your Microsoft 365 tenant — an internal IT lead, or a local implementation partner if you do not have one — two specific questions this week: is Copilot licensing already present in this tenant, and has GPT-5.6 reached it yet; and for any team handling sensitive records, what tenant-level admin controls currently govern what Copilot can read, retain, or send outside the organization. Answering those two questions costs nothing and takes a fraction of the time a new-tool pilot would. If the answer points to a genuine gap — licensing that is unused, or controls that were never configured — a tenant governance review is the kind of project that can fall under an AI-adoption grant. NOIC's BBAA and FedNor's RAII programs are both built for exactly this category of work; confirm current eligibility and intake status directly with each program before assuming a review project qualifies.

Frequently asked questions

  • Do we have to buy anything to get this? No — the GPT-5.6 upgrade applies automatically to tenants that already have Copilot licensing, on Microsoft's rollout schedule. If your organization does not have Copilot licensed yet, this specific change does not apply until it does; confirm licensing options directly with Microsoft or your IT provider.
  • Is GPT-5.6 live in our tenant right now? Possibly not yet. Microsoft says availability is phased by region and tenant configuration, so a Copilot that has not shown the new model is not malfunctioning — check with your admin or IT partner for your tenant's actual rollout status rather than assuming.
  • Could the AI engine inside Copilot change again without us choosing it? Yes. Microsoft, not the tenant, decides which model powers Copilot, and reporting alongside this announcement describes Microsoft also developing its own in-house models for parts of the suite. Design any Copilot-dependent process to tolerate that kind of change rather than assuming today's model behaviour is permanent.

Sources: GPT-5.6 is now the preferred model in Microsoft 365 Copilot — OpenAI, July 9, 2026 (openai.com/index/gpt-5-6-preferred-model-microsoft-365-copilot/) | Available today: OpenAI's GPT-5.6 in Microsoft 365 Copilot — Microsoft 365 Copilot Blog, July 9, 2026 (techcommunity.microsoft.com/blog/microsoft365copilotblog/available-today-openais-gpt-5-6-in-microsoft-365-copilot/4533152) | OpenAI says GPT 5.6 is the "preferred model" for Microsoft Copilot 365 amid breakup chatter — TechCrunch, July 9-10, 2026 (techcrunch.com/2026/07/09/openai-says-gpt-5-6-is-the-preferred-model-for-microsoft-copilot-amid-breakup-chatter/). Rollout, regional/tenant variability, and per-app details are Microsoft's and OpenAI's own announcements; efficiency and quality claims are vendor statements, not independently benchmarked at time of writing. This is commentary, not a recommendation of any specific vendor, tool, or funding program — confirm any program's current eligibility directly with the program.

Frequently asked

Do we have to buy anything to get this?

No, if your Microsoft 365 tenant already has Copilot licensing — the upgrade arrives on Microsoft's rollout schedule, not through a new purchase. If Copilot is not licensed yet, confirm options directly with Microsoft or your IT provider.

Is GPT-5.6 live in our tenant right now?

Maybe not yet. Microsoft says the rollout is phased by region and tenant configuration, so check with your admin rather than assuming — a Copilot that has not shown the new model is not broken, it may just not have reached your tenant.

Could the model powering Copilot change again without us choosing it?

Yes. Microsoft controls which model runs Copilot, and reporting alongside this announcement describes Microsoft also building its own in-house models for parts of the suite. Do not design a critical workflow that assumes today's model is permanent.

Share this brief

Get the weekly Signal

The AI, funding, government, and tech moves that matter for Northwestern Ontario — one email a week, source-linked, read by a human before it reaches you.

One email a week from Thunder Bay AI. Unsubscribe anytime.