You can choose a model or response mode in Copilot experiences that expose a selector, but there is no single documented GPT-4/GPT-4 Turbo switch that sets every Microsoft 365 app. First distinguish a user’s response-mode choice from an administrator’s provider-access controls. This guide covers organizational Microsoft Copilot, still labeled Microsoft 365 Copilot in some apps and licenses.
Official documentation checked: October 14, 2026. Available controls depend on the experience, tenant and rollout.
How Copilot Chooses a Model
Microsoft documents a real-time router in the default Auto mode. Where offered, Quick response prioritizes routine questions and Think deeper is intended for more complex work. These are product options, not a promise of one permanently fixed underlying model. See the Microsoft Copilot overview.
Do not infer a model’s context window from a provider’s API specification. Copilot also has its own retrieval, file handling and app-specific behavior. A longer model context does not prove that an entire document or workbook was read.
What Administrators Can Actually Control
For provider access, an AI Administrator or Global Administrator can open Copilot → Settings → View all → AI providers operating as Microsoft subprocessors in the Microsoft 365 admin center. Microsoft documents selecting the provider and assigning eligible users or groups. This controls access; it is not the old article’s claimed universal model-version policy. Review the subprocessor settings documentation before saving changes.
Microsoft also documents an Anthropic setting for supported Word, Excel and PowerPoint experiences in EU/EFTA and UK tenants. Its behavior depends on the global provider scope; it can be unavailable when the provider is enabled for all or specified users. It is not a general-purpose selector for all Copilot services. The app-specific documentation explains the dependency and warns that this processing is outside the EU Data Boundary.
Record the current provider assignment and obtain your organization’s approval before changing it. Do not enable a provider simply to make a missing button appear.
How to Choose an Available Mode as a User
- Open the Copilot experience you intend to use, signed in with the correct work or school account.
- Look for the visible model or response-mode selector in that experience. Use the options actually offered there; do not search for an assumed Settings → Model menu in every Office app.
- Select the appropriate option, then submit a small, non-sensitive test task.
- Check the answer against the source document. For an editing task, inspect the proposed changes before accepting them.
- When starting another chat or switching apps, check the selector again if the choice matters. Do not assume that a choice is a permanent, cross-app default.
When the Selector or a Provider Is Missing
Note the app, account type, build, selected feature and license before contacting IT. A model selector in Copilot Chat does not establish that the same selector exists in a Word editing workflow.
Ask the administrator whether the provider is enabled for your user or group, whether the feature is supported in your cloud and whether a rollout notice applies. Updating a supported app can resolve a client mismatch, but installing Office version 2402 specifically does not unlock a universal model picker.
Do not add undocumented registry keys or deploy a policy named “Microsoft 365 Copilot Model.” This article has no verified Microsoft policy reference for that instruction.
Compare the Controls Before Changing Anything
- Response mode: a choice for the current user experience; test speed and answer quality with the same input.
- Provider access: an administrator’s decision about which users may use an available AI provider.
- App-specific default behavior: a documented setting with limited scope and dependencies, not a tenant-wide version lock.
- Data governance: requires checking the applicable terms, processing location and any separate retention controls. A model name alone is insufficient.
Verify the Result
After an authorized change, test with an affected ordinary user, not only the administrator. Record the visible option, date, app and outcome. If the goal was document accuracy, verify citations and edits; if the goal was provider restriction, confirm the relevant experience cannot use the blocked provider. Keep those two tests separate.
The practical answer is to use the supported selector where it exists and the documented provider controls where governance is required. Do not treat a missing generic default-model menu as an installation fault.