How to Enable Microsoft Copilot in Microsoft 365 (and What to Check First)
A surprising number of IT tickets about Microsoft Copilot have nothing to do with the AI itself. They're about Copilot simply not appearing, even after a license has been assigned and everyone's been told it's ready to go. The license is rarely the actual problem.
This guide walks through how to enable Copilot correctly in Word, Excel, Outlook, and Teams, the privacy setting that silently blocks it even with a valid license, and how to turn it off again if you need to. It also covers what's worth checking before you roll Copilot out to your whole team, since the setup matters more than most guides admit.
Before You Enable Copilot, Check These Two Things
A qualifying Microsoft 365 subscription and an assigned Copilot license come first. Without both, the Copilot button simply won't appear in any app, no matter how many times you restart it. This part trips up fewer people than you'd expect, but it's worth confirming before troubleshooting anything else.
The setting almost nobody checks is buried in privacy controls, and it's very likely the actual cause behind the kind of frustrated IT forum posts you'll find searching for this exact problem. Copilot won't show up at all unless two specific privacy toggles are turned on: "Experiences that analyze your content" and "All connected experiences." These settings exist independently of licensing, which means a fully licensed user can still see no Copilot button anywhere.
To check them, go to File, then Account, then Account Privacy, then Manage Settings. Both toggles need to be on. If either one is off, no amount of license reassignment or app restarting will make Copilot appear.
Confirming these two things first saves a genuine amount of back-and-forth. Once they're both in place, enabling Copilot in each app is straightforward.
How to Enable Copilot in Word, Excel, Outlook, and Teams
Start in the Microsoft 365 admin center. Go to Billing, then Licenses, select Microsoft 365 Copilot, and assign licenses to the specific users or groups who need access. This step alone won't make Copilot appear immediately for everyone.
Office apps need to be running a current build for Copilot to load correctly. Confirm Word and Excel are on at least version 2412, and that Mac users running Word are on at least version 16.93. Older builds simply won't show the Copilot interface even with a valid license attached.
If a user already has both a license and an updated app and still doesn't see Copilot, the license itself may need a manual refresh. On Windows, that's File, then Account, then Update License. On Mac, it's the app name, then About, then More Info, then Refresh License. This single step resolves more "I have a license but no Copilot" tickets than any other fix.
After refreshing, close and reopen every Microsoft 365 app. Copilot sometimes appears immediately. In other cases, it takes 24 to 48 hours to show up across all devices tied to that account, which is worth setting expectations for before anyone assumes the rollout failed.
Outlook and Teams follow the same general pattern, with the Copilot icon appearing directly in the toolbar once licensing, app version, and privacy settings all line up. Getting Copilot turned on is usually the easy part. Knowing how to turn it back off matters just as much.
How to Turn Copilot Off, and Why You Might Want To
Disabling Copilot in Word, Excel, PowerPoint, and OneNote takes one setting per app. Go to File, then Options, then Copilot, and uncheck Enable Copilot. The app needs a restart for the change to take effect, and this has to be repeated on every device the user works from, since it isn't tied to the account centrally.
Outlook works differently. Instead of the same Options menu, the toggle lives under Settings, then Copilot, with a switch labeled Turn on Copilot. This setting applies across every device signed into that account, which makes it more centralized than the per-app toggle used elsewhere. Turning it off in Outlook doesn't affect Copilot in other apps.
If the Enable Copilot checkbox isn't visible at all in a given app, the privacy settings fallback is the next option. Go to File, then Account, then Account Privacy, then Manage Settings, and uncheck "Turn on experiences that analyze your content." This disables Copilot, but it also removes other connected features like text predictions and suggested replies, so it's worth using deliberately rather than as a first resort.
Individual app-level control works for one person at a time. For an entire organization, the better path runs through the admin center instead.
Managing Copilot Across Your Whole Organization
Removing access for a single person is straightforward. In the admin center, go to Users, then Active Users, select the person, and remove their Copilot for Microsoft 365 license. That action blocks Copilot access across every app for that user immediately.
Doing this one account at a time doesn't scale past a handful of people. Azure AD group-based licensing solves that by tying Copilot access to group membership instead of individual accounts, so adding or removing someone from the right group automatically updates their access without a separate manual step each time.
A third option controls Copilot at the application level rather than the license level. In the admin center, go to Settings, then Integrated Apps, then Copilot, where you can block it tenant-wide or scope access to specific users or groups. This is the setting worth using if you want Copilot available to a pilot group while keeping it off for everyone else.
These controls answer who can turn Copilot on. They don't answer what Copilot can see once it's running, and that question matters more than most rollout plans account for.
What to Check Before You Roll It Out to Everyone
Copilot doesn't create new access. It surfaces whatever a user's existing permissions already allow, instantly and in plain language. A file-sharing setting that's been overly broad for three years stays invisible until Copilot makes it easy to find and summarize in seconds.
This is the real risk in a Copilot rollout, and it has nothing to do with the AI itself. Our IT audit checklist covers exactly this kind of review, specifically the access control section, which is worth running before turning Copilot on for a full team rather than after something surfaces that shouldn't have.
A pilot group is the practical way to catch this early. Enabling Copilot for three to five high-usage employees first, running it for about 60 days, and watching what comes up gives you a real read on both adoption and exposure before expanding company-wide. Most organizations that skip this step end up doing the access review retroactively, which is a harder conversation than doing it first.
Getting the access picture right costs nothing extra. What Copilot itself costs is worth knowing too, even if it's a smaller piece of the decision than people expect.
What It Costs (Briefly)
Copilot Chat comes included at no additional cost with most eligible Microsoft 365 subscriptions, and it's worth checking whether your organization already has it before assuming you need to buy anything. The free tier is web-grounded only. It doesn't connect to your organization's files, email, or Teams content.
The paid tier, Microsoft 365 Copilot Business, is what adds that deeper integration: Copilot working directly with your actual documents, inbox, and meeting data. Pricing has shifted through 2026 with promotional rates in place for part of the year.
The license is rarely the expensive part once you account for setup. Getting permissions, SharePoint structure, and app configuration right before rollout takes real time, and skipping that step is what produces the disappointing results and security gaps that give Copilot deployments a bad reputation.
Getting Copilot Running the Right Way
Enabling Copilot correctly takes minutes once licensing, app versions, and privacy settings are all in place. Doing it responsibly takes a bit more: knowing who has access, what that access actually exposes, and having a plan to scale beyond a pilot group deliberately.
AllSafe IT handles Microsoft 365 optimization for businesses across Los Angeles, Orange County, and Pasadena, including Copilot rollout and the access review that should come before it. If you want help getting this set up correctly the first time, contact our team.
Frequently Asked Questions
Why does Copilot not show up even after I get a license?
The most common cause is a privacy setting, not the license itself. Two toggles, "Experiences that analyze your content" and "All connected experiences," need to be turned on under File, then Account, then Account Privacy, then Manage Settings. If either is off, Copilot won't appear regardless of licensing. Outdated app versions and a license that hasn't been manually refreshed are the next two things worth checking.
How do I turn off Copilot in Outlook specifically?
Outlook handles this differently from Word, Excel, and PowerPoint. Go to Settings, then Copilot, and switch off the Turn on Copilot toggle. This applies across every device signed into that account, so you don't need to repeat it on each one separately. Turning off Copilot in Outlook doesn't affect whether it's enabled in other Microsoft 365 apps.
Do I need a paid plan to use any version of Copilot?
No. Copilot Chat is included at no additional cost with most eligible Microsoft 365 subscriptions, and it works without a separate paid add-on. It's web-grounded only and doesn't connect to your organization's internal files, email, or Teams content. Deeper integration with your actual business data requires the paid Microsoft 365 Copilot Business or Enterprise tier.
Can I control which employees have access to Copilot?
Yes, at both the individual and group level. For one person, removing their Copilot license in the admin center under Active Users blocks access immediately. For scale, Azure AD group-based licensing ties access to group membership, and Integrated Apps Governance lets you block Copilot tenant-wide or limit it to specific users or groups, which is useful for running a pilot before a full rollout.
Will disabling Copilot affect other Microsoft 365 features?
It depends on how you disable it. Turning off the Enable Copilot setting in each app's options menu only affects Copilot itself. Using the privacy settings fallback, unchecking "Turn on experiences that analyze your content," also disables other connected features like text predictions and suggested replies. If you only want Copilot off, use the app-level toggle rather than the privacy fallback.
What should I check before rolling out Copilot to my whole team?
Review existing file and folder permissions before anyone gets access, since Copilot can surface anything a user's current permissions already allow, including sharing settings that have gone unreviewed for years. Start with a small pilot group of three to five users for about 60 days to see what comes up before expanding further. Confirm app versions and privacy settings are correct ahead of time so the rollout doesn't stall on basic technical issues instead of the access questions that actually matter.
