You add Microsoft 365 Copilot in Word by assigning a qualifying Copilot license to your account, signing into Word with that same account, and updating Word to a current channel build so the Copilot icon appears in the ribbon and the left margin of your document. If you are a home user, that license is Copilot Pro, a $20 per user per month add-on to a Microsoft 365 Personal or Family subscription. If you are on a business, enterprise, frontline, education, or government plan, you add Copilot through the Microsoft 365 admin center by purchasing Microsoft 365 Copilot licenses at $30 per user per month with an annual commitment, then assigning those licenses to users who already hold a qualifying base plan.
The specific problem this article solves is the quiet gap between owning Microsoft 365 and having Copilot inside Word. The Microsoft Services Agreement and the Microsoft Product Terms treat Copilot as a separate paid service, which means a standard Microsoft 365 subscription does not include generative AI features in Word, and users who expect Copilot to appear automatically will see nothing in the ribbon. The immediate consequence is wasted spend and staff frustration, because teams pay for a base plan, expect AI drafting, and then find that no license, no tenant switch, and no current build means no Copilot at all.
According to Microsoft’s Work Trend Index 2024, 75% of global knowledge workers already use generative AI at work, and Copilot users reported saving an average of 14 minutes per day on writing tasks inside Word, Outlook, and Teams. That adds up to more than 60 hours per user per year, which is why the right setup matters more than the fast setup.
Here is what you will learn in this guide:
- ๐งพ How to choose the correct Copilot license for your Microsoft 365 plan and avoid overpaying.
- ๐ ๏ธ Step-by-step instructions to add, assign, and activate Copilot in Word on Windows, Mac, web, iOS, and Android.
- โ๏ธ Real Copilot-in-Word examples for drafting, rewriting, summarizing, and transforming a document into a PowerPoint deck.
- ๐ก๏ธ Admin controls for data residency, Purview, DLP, sensitivity labels, and the semantic index that grounds Copilot in your files.
- ๐ซ The seven most common mistakes that break Copilot in Word, and how to fix each one before your users file a ticket.
What Microsoft 365 Copilot in Word Actually Is
Microsoft 365 Copilot in Word is a generative AI layer that sits inside Word and connects your prompts to a large language model, your document content, and, for business users, your organization’s data through the Microsoft Graph. It uses OpenAI models hosted inside Microsoft’s Azure tenant, which means your prompts and file content are processed under Microsoft’s commercial data protection terms and are not used to train the foundation models, a point confirmed in Microsoft’s Copilot data protection documentation.
Copilot in Word shows up in three places inside the app. The first is the Copilot icon in the ribbon on the Home tab, which opens the side pane for chat, document Q&A, and long-form drafting. The second is the Copilot icon in the left margin next to each paragraph, which lets you draft, rewrite, visualize as a table, or summarize a selection. The third is the “Draft with Copilot” box that appears on a blank document, which lets you start a document from a prompt, a file reference, or a meeting transcript.
The service is governed by the Microsoft Product Terms for Copilot, which bind Microsoft to contractual promises around tenant isolation, data residency, and eDiscovery. The consequence of ignoring those terms is real: if you share Copilot output externally without review, you inherit liability for accuracy, bias, and copyright under your own acceptable use policies, not Microsoft’s. A common misconception is that Copilot is ChatGPT; it is not. It uses related models, but the grounding, logging, and compliance surface are entirely different, and you should treat them as different products.
Copilot Pro vs Microsoft 365 Copilot: Know the Difference
Copilot Pro and Microsoft 365 Copilot sound similar but solve different problems. Copilot Pro is a consumer add-on for individuals who already pay for Microsoft 365 Personal or Family, and it costs $20 per user per month. It unlocks Copilot in Word, Excel, PowerPoint, Outlook, and OneNote on the desktop apps, plus priority access to the newest OpenAI models inside Copilot chat.
Microsoft 365 Copilot is the commercial SKU for work tenants, priced at $30 per user per month on an annual commitment through an Enterprise Agreement, CSP partner, or Microsoft 365 admin center. It includes everything Copilot Pro offers, plus grounding in your Microsoft Graph data, Copilot in Teams, Copilot Studio lite, enterprise-grade data protection, and admin controls inside Purview. The consequence of picking the wrong tier is severe: Copilot Pro cannot read your SharePoint or OneDrive for Business files across a tenant the way the commercial SKU can, so a marketing director who buys Copilot Pro will still be stuck copy-pasting from intranet docs.
A real scenario makes it clear: Maria, a freelance copywriter using Microsoft 365 Personal, needs Copilot Pro to draft client proposals in Word. David, an in-house counsel at a 400-person law firm on Microsoft 365 E3, needs Microsoft 365 Copilot so Word can summarize a matter folder stored in SharePoint. A common misconception is that a Business Standard tenant can just “upgrade” to Copilot Pro for cheaper access; it cannot, because Copilot Pro is not sold for work or school accounts.
| Feature | Copilot Pro ($20/user/mo) |
|---|---|
| Eligible accounts | Microsoft 365 Personal or Family |
| Word, Excel, PowerPoint, Outlook, OneNote Copilot | Yes, on desktop and web |
| Grounding in work data via Microsoft Graph | No |
| Copilot in Teams | No |
| Admin controls in Purview | No |
| Commercial data protection | No, consumer terms apply |
| Feature | Microsoft 365 Copilot ($30/user/mo) |
|---|---|
| Eligible accounts | Business Basic, Standard, Premium, E3, E5, A3, A5, F3, and GCC |
| Word, Excel, PowerPoint, Outlook, OneNote Copilot | Yes, across web, desktop, and mobile |
| Grounding in work data via Microsoft Graph | Yes |
| Copilot in Teams | Yes |
| Admin controls in Purview | Yes |
| Commercial data protection | Yes, under Product Terms |
Prerequisites Before You Add Copilot to Word
Before any license shows up in Word, you need the right base plan, the right account type, the right build channel, and the right network policy. Microsoft’s Copilot requirements page lists the qualifying SKUs, and the list changed in early 2024 when Microsoft dropped the former 300-seat minimum, which means even a single-person Business Basic tenant can now buy one Copilot seat. The consequence of skipping this check is a billing error: some partners still quote the old minimums, and you may sign a larger deal than you need.
Your base plan must be one of the following: Microsoft 365 Business Basic, Business Standard, Business Premium, Apps for Business, Enterprise E3, E5, A3, A5, F3, or the Apps for Enterprise standalone. If you are on a legacy Office 365 E1 or a plan that only includes web Office, you must upgrade first because Copilot in Word needs the connected desktop or web clients, not the free reader. A common misconception is that Microsoft 365 Apps for Business and Microsoft 365 Business Standard are the same; Apps for Business skips Exchange and SharePoint, which means Copilot grounding inside Word will not see your email or intranet content.
Your account must be a work or school identity inside Microsoft Entra ID, not a personal Microsoft account, for the commercial SKU. Your Word build must be at least version 2402 on Windows, version 16.82 on Mac, or the current web client, which you can verify under File > Account > About Word. The immediate consequence of running an outdated Semi-Annual Channel build is that the Copilot icon simply will not render, and users will believe the license is broken when it is actually a deployment gap.
Network, Identity, and Compliance Checks
Your tenant must allow outbound traffic to the Microsoft 365 Copilot service endpoints on ports 80 and 443, and to the telemetry domains *.officeapps.live.com and *.cloud.microsoft. If you block those, Copilot calls fail silently and users see a generic “Something went wrong” error inside Word. The consequence is a wave of helpdesk tickets that look like license problems but are actually firewall rules.
Your identity setup needs modern authentication turned on, which has been the Microsoft 365 default since 2022, and multifactor authentication enforced under Entra Conditional Access. Without MFA, Copilot still technically works, but you fail most NIST SP 800-63B and HIPAA Security Rule guidance, and that is a real regulatory risk if Word is used to draft protected health information. A common misconception is that Copilot is “just an app” and needs no compliance review; in fact, Microsoft’s own Service Trust Portal lists Copilot under the same audit scope as Exchange Online.
For compliance, confirm your tenant’s data residency in the Microsoft 365 admin center under Settings > Org settings > Data location. Copilot for enterprise honors your advanced data residency commitment for prompts, responses, and the semantic index, but only when you are on an Advanced Data Residency add-on. The consequence of missing that add-on is that your prompt data may transit regions, which can break EU data boundary commitments under the GDPR.
How to Add Copilot Pro for Personal Users
If you pay for Microsoft 365 Personal or Family, adding Copilot Pro takes about three minutes and a credit card. Go to the Copilot Pro purchase page, sign in with the same Microsoft account that holds your Microsoft 365 subscription, and click Get Copilot Pro. The billing page will show a monthly charge of $20, and the subscription starts immediately after payment.
After you buy, close Word completely, reopen it, and sign in with that Microsoft account under File > Account. The Copilot icon appears on the Home tab of the ribbon within a few minutes, and a “Draft with Copilot” box appears on any new blank document. The consequence of signing in with the wrong account, for example a work account when your Copilot Pro sits on a personal account, is that Word sees no entitlement and hides the icon. A common misconception is that Copilot Pro must be installed; there is no installer, because the feature ships inside the existing Office build.
A named example: Priya is a part-time novelist on Microsoft 365 Family. She buys one Copilot Pro seat for herself, leaves the five other family seats as regular Microsoft 365 Family, and only she sees Copilot in Word. Her husband, who shares the Family plan but does not have Copilot Pro, opens Word and sees no icon. That is working as designed, because Copilot Pro is per user, not per household.
Turning On Copilot Pro Inside Word for the First Time
Open Word, start a blank document, and you will see a light gray prompt box near the top of the page that says Draft with Copilot. Click it, type a prompt like “Write a 500-word birthday toast for my grandfather’s 90th, warm but not cheesy,” and press the send arrow. Copilot generates the draft in the document body, with Keep it, Regenerate, and Discard buttons underneath.
To use Copilot on existing text, select a paragraph, and click the small Copilot icon that appears in the left margin. A menu gives you Rewrite, Visualize as a table, Summarize, and Auto rewrite, each of which calls the model with your selection and your instruction. The consequence of not selecting text first is that the margin icon defaults to Draft new content, which inserts rather than edits, and users often undo repeatedly before realizing the mistake.
A common misconception is that Copilot Pro works offline; it does not. It needs a live internet connection because the model runs in Azure, so a user writing on a plane without Wi-Fi sees the icon but gets a “Copilot needs a connection” error. Turn off any VPN split-tunnel rules that block *.cloud.microsoft if you want reliable performance.
How to Add Microsoft 365 Copilot for Business and Enterprise
For a commercial tenant, adding Copilot is a four-step process that lives inside the Microsoft 365 admin center. You must be a Global Administrator or Billing Administrator to buy, and a License Administrator to assign. The least-privilege guidance from Microsoft recommends you split those roles, and the consequence of skipping that split is that a single compromised admin account can both buy and assign Copilot, which can quietly spin up expensive licenses an attacker could use to exfiltrate data through prompts.
Step one is to confirm eligibility. Go to Billing > Purchase services and search for Copilot. If your tenant qualifies, the Microsoft 365 Copilot tile appears with the $30 per user per month price and the annual commitment term. If it does not appear, your base plan is not eligible, and you need to upgrade from, for example, Office 365 E1 to Microsoft 365 E3 first. A common misconception is that you can buy monthly; you cannot, because Microsoft only sells Copilot on an annual or three-year term.
Step two is to purchase the seats you need. Enter a quantity, choose annual billing, and complete checkout. Step three is to assign licenses under Users > Active users, select a user, click Licenses and apps, and check Microsoft 365 Copilot. Step four is to wait 10 to 30 minutes for the license to propagate to Entra ID, then ask the user to restart Word. The consequence of skipping the restart is that Word’s license cache still reports no entitlement, and the Copilot icon stays hidden.
Using PowerShell to Bulk-Assign Copilot Licenses
For larger rollouts, assign in bulk with the Microsoft Graph PowerShell SDK. Connect with Connect-MgGraph -Scopes "User.ReadWrite.All, Organization.Read.All", pull the Copilot SKU ID with Get-MgSubscribedSku | Where-Object SkuPartNumber -eq "Microsoft_365_Copilot", and loop through a CSV of usernames with Set-MgUserLicense. The consequence of assigning without a pilot group first is that 500 users all hit Copilot at once, telemetry spikes, and your change advisory board loses visibility.
A named example: Lena, an IT admin at a 2,000-seat engineering firm, assigns 50 Copilot licenses to the legal team first, monitors adoption in the Microsoft 365 Copilot Dashboard, and waits two weeks before expanding to marketing. Her phased rollout catches a data loss prevention rule that was blocking Copilot from reading a Confidential sensitivity label, and she fixes it before rollout continues.
A common misconception is that a license assignment is instant; it is eventually consistent. Entra ID, Exchange, and the Copilot service each have their own provisioning queue, and the full end-to-end activation can take up to an hour, which your communications plan should set as the expected timeline.
Hands-On Examples of Copilot in Word
The best way to learn Copilot in Word is to run it against a real document. The four scenarios below cover the most common tasks, and each one shows a prompt, the expected behavior, and the consequence of a bad prompt.
Example 1: Draft a Proposal From a Prompt
Jordan, an account manager at a SaaS startup, opens a blank Word document and clicks Draft with Copilot. He types: “Draft a three-page proposal for Acme Corp to renew our CRM contract for two years at a 7% increase, emphasize our 99.95% uptime, and include a signature block.” Copilot returns a structured draft with headings, body copy, and a signature block in about 20 seconds.
Jordan can reference up to three existing files in the prompt by typing / and selecting from OneDrive or SharePoint. The consequence of not referencing the prior year’s proposal is that Copilot hallucinates numbers, which is the single most common complaint in Microsoft’s Copilot feedback data. A common misconception is that longer prompts are better; in practice, prompts over 2,000 characters often return weaker output because the model loses focus.
Example 2: Rewrite a Paragraph for Tone
Select any paragraph, click the Copilot icon in the left margin, and choose Rewrite. Type “Make it more formal and remove passive voice,” and Copilot returns three variants you can cycle through with arrow buttons. Accept one and the original text is replaced with versioned history preserved in Word’s Review > Compare.
The consequence of rewriting without a backup is minimal here, because Ctrl + Z still restores the original, but if you rewrite and save, an autosave can overwrite the previous version. A named example: Ahmed, a paralegal, uses Rewrite to soften a demand letter. He forgets to run Review > Track Changes first, so his senior partner cannot see what changed. The fix is to turn on track changes before using Copilot on legal text every time.
Example 3: Summarize a Long Contract
Open a 40-page contract, click the Copilot icon in the ribbon, and type “Summarize this document in 10 bullets, focusing on termination, indemnity, and payment terms.” Copilot reads the entire document through the semantic index and returns a bulleted summary in the side pane, with citations that deep-link back to the source paragraphs.
The consequence of relying on the summary without spot-checking the citations is real: Copilot occasionally misattributes a clause to the wrong section, and in contract review that is a material error. A common misconception is that Copilot reviews contracts; it summarizes contracts. Legal review is still your lawyer’s job, and ABA Formal Opinion 512 makes it clear that lawyers remain responsible for the accuracy of AI-assisted work product.
Example 4: Turn a Word Doc Into a PowerPoint Deck
Open a finished Word document, click File > Export > Export to PowerPoint presentation (a feature that now uses Copilot under the hood), and choose a design theme. Copilot builds a deck with one slide per H1 heading, speaker notes from body text, and images pulled from Microsoft Designer. Samir, a product marketer, turns a 12-page launch brief into a 15-slide deck in under a minute.
The consequence of messy Word formatting is a messy deck. Copilot uses your heading styles to map slides, so if you used bold text instead of Heading 1, your deck ends up as one giant slide. A common misconception is that Copilot “designs” the deck; it generates structure and pulls themed stock assets, but branded templates still require a manual polish pass.
Three High-Impact Copilot-in-Word Scenarios
| Scenario | Copilot Outcome |
|---|---|
| Drafting a client proposal from a blank page using a /reference to last year’s file | A structured first draft in under 30 seconds with pricing pulled from the prior file |
| Summarizing a 50-page vendor MSA with citation links | A 10-bullet summary you can verify by clicking back into the source clauses |
| Converting a long Word brief into a pitch deck with speaker notes | A themed PowerPoint file mapped from your heading structure, ready for design polish |
| Scenario | Common Failure |
|---|---|
| Drafting a proposal with no file reference | Hallucinated pricing or fabricated case studies |
| Summarizing a contract on a personal Copilot Pro account | Copilot cannot read the SharePoint copy and refuses the prompt |
| Converting a Word doc without heading styles | The deck collapses into one or two slides of solid text |
| Scenario | Recommended Guardrail |
|---|---|
| Any external-facing Copilot draft | Run a human edit pass and a Microsoft Purview sensitivity label check |
| Any Copilot output quoting a policy | Click the inline citation and verify the source paragraph still exists |
| Any Copilot rewrite on a legal or medical doc | Turn on Review > Track Changes before the prompt, not after |
Admin Controls, Data Residency, and Compliance
Once Copilot is live, your admin work starts. The Microsoft 365 Copilot Dashboard in Viva shows per-app adoption, and Microsoft Purview gives you audit, DLP, eDiscovery, and sensitivity label enforcement over Copilot prompts and responses. The consequence of turning Copilot on without Purview is that you have no record of what prompts your users sent, and in a regulatory audit under SEC Rule 17a-4 for broker-dealers, that gap is itself a violation.
Data residency follows your tenant’s geo, plus any Advanced Data Residency add-on you purchased. Prompts and responses are encrypted in transit with TLS 1.2 or higher and at rest with Microsoft-managed keys, with Customer Key supported for bring-your-own-key scenarios. A common misconception is that Copilot trains on your data; Microsoft’s data, privacy, and security documentation states the models are not trained on your prompts or your tenant content, and that promise is contractual under the Online Services Terms.
Sensitivity labels flow into Copilot’s grounding behavior. If a file is labeled Confidential – Legal Only, Copilot honors the label and refuses to include that content in a response for users outside the policy scope. The consequence of mislabeling is either leakage, if you under-label, or false refusals, if you over-label, and both break user trust fast. A named example: Chen, a CISO at a biotech, labels the clinical trial SharePoint as Highly Confidential, and Copilot correctly blocks it from a marketing assistant’s prompt.
Restricted SharePoint Search and the Semantic Index
The semantic index for Copilot is the engine that grounds Copilot in your tenant’s content, and it must be provisioned before Copilot in Word can reference work files reliably. Microsoft provisions it automatically when you assign the first Copilot license, but full tenant indexing can take 24 to 72 hours depending on data volume. The consequence of a half-indexed tenant is that Copilot returns “I couldn’t find that” for files that do exist, which frustrates early adopters.
Pair the semantic index with Restricted SharePoint Search, which limits Copilot’s grounding to a curated allow-list of sites while you clean up oversharing. This is the single most important control to enable before a large Copilot rollout, because most tenants have legacy permissions that would let Copilot surface HR files to the wrong users. A common misconception is that Copilot introduces oversharing; it only surfaces oversharing that was already there, and Microsoft’s oversharing assessment guidance explains the remediation steps.
Mistakes to Avoid When Adding Copilot in Word
- Buying Copilot Pro for a work or school account, which Microsoft does not allow, and then having to refund and repurchase the commercial SKU at a higher price.
- Forgetting to update Word to a current channel build, which hides the ribbon icon even when the license is assigned correctly.
- Skipping the Restricted SharePoint Search rollout, which causes Copilot to surface overshared HR or finance files to random staff.
- Rolling out Copilot tenant-wide without a pilot group, which means you find data loss prevention conflicts after users complain rather than before.
- Blocking
*.cloud.microsoftor*.officeapps.live.comin the firewall, which causes silent Copilot failures that look like license bugs. - Treating Copilot output as final work product, which breaks lawyer-client duty under ABA Formal Opinion 512 and healthcare obligations under HIPAA.
- Ignoring sensitivity labels before rollout, which either leaks confidential data into prompts or triggers false refusals that erode user trust.
- Assigning Copilot without enabling Microsoft Purview audit, which leaves you blind to what prompts users submitted during a later investigation.
- Using long, vague prompts over 2,000 characters, which usually produce worse results than a focused 300-character prompt with a file reference.
- Assuming license assignment is instant, when Entra ID propagation can take up to an hour and users will report “it’s broken” during that window.
Do’s and Don’ts for a Clean Copilot Rollout
- Do pilot Copilot with 25 to 50 users for at least two weeks, because adoption telemetry and DLP conflicts surface in that window.
- Do turn on Restricted SharePoint Search before assigning a single license, because oversharing remediation is easier with Copilot contained.
- Do train users on prompt basics with Microsoft’s Copilot Lab, because prompt quality is the single biggest driver of user-reported satisfaction.
- Do enable Purview audit for Copilot, because regulators will ask for prompt logs during an investigation.
Do review sensitivity labels and data classification before rollout, because Copilot honors labels but only if the labels exist.
Don’t buy Copilot Pro for a work tenant, because the SKU is for consumer accounts and your admin cannot manage it.
- Don’t skip the Word client update, because older builds silently hide the Copilot icon even when the license is valid.
- Don’t rely on Copilot output without a human review, because the model still hallucinates names, numbers, and citations.
- Don’t turn on Copilot tenant-wide before the semantic index finishes provisioning, because early users will see “no results” errors.
- Don’t ignore the annual commitment term, because Microsoft does not offer month-to-month commercial Copilot and mid-term cancellations are not free.
Pros and Cons of Adding Copilot in Word
- Pro: Copilot reduces drafting time on routine Word tasks by an average of 14 minutes per user per day, according to Microsoft’s Work Trend Index 2024.
- Pro: Grounding in Microsoft Graph means Word can summarize your OneDrive and SharePoint content without copy-paste.
- Pro: Enterprise data protection under the Product Terms is stronger than most third-party AI writing tools.
- Pro: The same license covers Copilot in Excel, PowerPoint, Outlook, Teams, and OneNote, so the per-feature cost is lower than it looks.
Pro: Admin controls in Purview give compliance teams visibility no consumer AI tool offers.
Con: $30 per user per month with an annual commitment is a meaningful budget line for smaller firms.
- Con: Quality depends heavily on prompt skill, and most users need training before they see real productivity gains.
- Con: Copilot can amplify permission mistakes, so tenants with messy SharePoint sharing must remediate first.
- Con: Hallucinations still happen on unusual topics, so every output needs a human review before it goes out.
- Con: Offline use is not supported, which is a real limitation for traveling users and field staff.
Key Entities in the Copilot-in-Word Ecosystem
Microsoft is the service owner and sets the commercial terms. OpenAI supplies the foundation models that Microsoft hosts inside its own Azure tenant under a commercial agreement. Microsoft Entra ID is the identity provider that authenticates every Copilot call and enforces conditional access. Microsoft Purview is the compliance plane that gives you audit, DLP, eDiscovery, and sensitivity label enforcement over Copilot content.
Microsoft Graph is the API layer that lets Copilot read your files, emails, calendar, and chats with the user’s own permissions. The semantic index is a new retrieval index that grounds prompts in your tenant content. Microsoft 365 Apps is the client delivery mechanism that ships Word, Excel, and PowerPoint to endpoints and receives the Copilot UI through monthly updates.
The Federal Trade Commission has issued AI guidance on deceptive use, which matters because Copilot output in Word is still your organization’s speech under Section 5 of the FTC Act. The American Bar Association has issued Formal Opinion 512 on generative AI and lawyer duties, which binds lawyers using Copilot in Word to competence, confidentiality, and supervision standards. The European Union AI Act, while a non-US law, affects US firms with EU users and classifies general-purpose AI writing aids under a transparency regime that interacts with Copilot output.
Frequently Asked Questions
Do I need Microsoft 365 to use Copilot in Word?
Yes. You need either a Microsoft 365 Personal or Family plan with a Copilot Pro add-on, or a qualifying Microsoft 365 business, enterprise, education, or frontline plan with the Microsoft 365 Copilot SKU assigned.
Is Copilot in Word included in my Microsoft 365 Business Standard plan?
No. Microsoft 365 Business Standard qualifies you to buy Copilot, but Copilot is a separate $30 per user per month add-on that must be purchased and assigned through the Microsoft 365 admin center.
Does Copilot Pro work with my company email?
No. Copilot Pro is a consumer SKU tied to a personal Microsoft account and cannot be assigned to a work or school account, so you must use the commercial Microsoft 365 Copilot SKU instead.
Can one user have both Copilot Pro and Microsoft 365 Copilot?
Yes. A user can hold Copilot Pro on a personal account and Microsoft 365 Copilot on a separate work account, but the two licenses live on different identities and do not merge features.
Is Copilot available on Word for Mac?
Yes. Copilot in Word for Mac requires version 16.82 or later of the client, a current-channel build, and a valid Copilot Pro or Microsoft 365 Copilot license signed into the app.
Does Copilot train on my Word documents?
No. Microsoft’s product terms and Copilot privacy documentation confirm that prompts, responses, and tenant content are not used to train the foundation models or improve the service for other customers.
Can I buy Microsoft 365 Copilot monthly?
No. Microsoft 365 Copilot is sold only on an annual or three-year commitment through the admin center, an Enterprise Agreement, or a CSP partner, and month-to-month pricing is not offered.
Will Copilot see files I do not have permission to open?
No. Copilot honors the exact same permissions you already have in SharePoint, OneDrive, Teams, and Exchange, so if you cannot open a file directly, Copilot cannot ground on it either.
Does Copilot in Word work offline?
No. Copilot sends prompts to Microsoft-hosted OpenAI models in Azure, so an active internet connection is required, and offline use returns a connection error inside Word.
Can I disable Copilot for specific users in my tenant?
Yes. You control Copilot access by simply not assigning the license, or by applying a Microsoft Purview policy that restricts Copilot for particular users, groups, or sensitivity label scopes.
Is Copilot HIPAA compliant?
Yes. Microsoft 365 Copilot is covered under Microsoft’s Business Associate Agreement for HIPAA-regulated customers, but your organization must configure Purview, DLP, and auditing to meet the full HIPAA Security Rule.
Does Copilot replace my proofreader or editor?
No. Copilot drafts and rewrites but still produces factual errors, tone mismatches, and citation mistakes, so a human editor remains necessary for any external or regulated document.