Microsoft 365 Copilot guides — brief
Full Copilot guides · Editorial notes on the sources
Condensed 2 November 2026 from the two Markdown conversions in the full Copilot guides. This is a reworded digest for orientation and planning. The full guides remain authoritative; follow the page links in each section before you rely on a detail.
What this brief covers
The architecture guide explains how Copilot reaches organisational data and the order in which to roll out protections and licences. The blueprint sets out what to configure in SharePoint Advanced Management (SAM) and Microsoft Purview to remediate oversharing, enforce guardrails and meet regulatory obligations.
| # | Chapter | Use it for | Source |
|---|---|---|---|
| 1 | Architecture and deployment | Data boundary, Semantic Index scope, E3/E5 environment preparation, Teams protection tiers, rollout rings | Architecture & deployment guide (7 pages) |
| 2 | Secure and govern | Three workstreams, E5 and E3 checklists compared, entitlement markers, decisions and owners | Secure and Govern blueprint (22 pages) |
Read chapter 1 first if Copilot is not yet licensed: it puts identity and device protection before licence assignment.
Version boundaries
| Source | Printed version | Naming used |
|---|---|---|
| Architecture & deployment | November 2023 (PDF metadata 14 March 2024) | Microsoft Copilot for Microsoft 365 |
| Secure and Govern blueprint | “Last updated March 6, 2026” (filename ends vMar24) |
Microsoft 365 Copilot |
The guides are more than two years apart; “current” in the architecture guide means November 2023. Neither has been refreshed for licensing, product names, indexing behaviour or regulatory claims (version boundaries). This brief inherits that limitation and adds no outside facts.
Each section links to the source pages it paraphrases. Examples are distinguished from requirements, entitlement markers are reproduced rather than interpreted, and source differences are recorded at the end of each chapter rather than silently reconciled.
Terminology
| Term | Meaning in the sources |
|---|---|
| DLP | Data Loss Prevention |
| DLM | Data Lifecycle Management |
| DSPM | Data Security Posture Management |
| EEEU | Used in the blueprint alongside company-wide sharing; not expanded there |
| Grounding | Supplying additional content or context to a prompt or response |
| IRM | Insider Risk Management |
| RAC | Restricted Access Control (SAM) |
| RCD | Restricted Content Discovery (SAM) |
| SAM | SharePoint Advanced Management, described as included in Microsoft 365 Copilot |
| SIT | Sensitive information type |
1. Architecture and deployment
Condensed 2 November 2026 from the seven-page architecture and deployment guide, printed November 2023. Product names, indexing scope and licensing statements are retained as that version states them and have not been refreshed.
How Copilot reaches your data
Sources: page 1, page 2, page 4
How Copilot answers a prompt
Scroll sideways to read the full diagram →
| Component | Where the guide places it | Role |
|---|---|---|
| Microsoft 365 apps | On user devices, outside the service boundary | Where the user issues a prompt and receives the response |
| Copilot | Microsoft 365 service, outside the tenant box | Orchestrates grounding and the call to the LLM |
| Microsoft Graph | Inside your tenant | Calendar, email, chats, documents, meetings and their relationships |
| Semantic Index for Copilot | Inside your tenant | Vectorised map of user and company data; created automatically |
| Large Language Model | Azure Open AI service subscription for Microsoft 365, inside the service boundary | Produces the response |
The query flow has two grounding stages: Copilot grounds the prompt using Microsoft Graph and the Semantic Index, calls the LLM, grounds the response again, and returns it to the app using only data the user has access to.
The guide states that customer data stays within the Microsoft 365 service boundary, that prompts, responses and Graph data are not used to train the foundation LLMs, and that tenant-to-Copilot communication is encrypted. Data is secured by the security, compliance and privacy policies the organisation has already deployed. The blueprint draws the consequence: because Copilot builds on data already in Microsoft 365, oversharing, data-loss and insider-risk practices need strengthening (see chapter 2).
What the Semantic Index covers
Source: page 3 (November 2023 scope)
| Location | Indexed, as stated in the source |
|---|---|
| SharePoint | Text-based files shared with two or more people |
| Mailbox | All email, at user level |
| OneDrive | Text-based files that have been shared, interacted with (even only by the user) or commented on |
| File types | Word (doc/docx), PowerPoint (pptx), PDF, web pages (html/aspx), OneNote (one) |
Decision: whether to exclude a SharePoint Online site from both Microsoft Search and the Semantic Index. Site administrators set this in Site Settings. Payroll and financial information are the source’s examples.
Prepare the environment: E3 then E5
Source: page 5
| Area | Getting started with E3 | Next steps with E5 |
|---|---|---|
| Identity and access | Conditional Access with MFA for administrators and all users; block legacy authentication; include Microsoft 365 and other SaaS apps in scope; for hybrid identities, on-premises Entra Password Protection | MFA when sign-in risk is medium or high; block legacy authentication; high-risk users must change password; Privileged Identity Management |
| Microsoft 365 Apps | Intune App Protection policies to stop corporate data being pasted into other apps, even on unmanaged devices | Blank in the source |
| Devices | Enrol devices, set compliance policies, require healthy and compliant devices, deploy device profiles | Integrate Intune with Defender for Endpoint; use device risk as an access condition; monitor Windows security-baseline compliance |
| Threat protection | Exchange Online Protection preset policies; Defender for Endpoint P1 | Pilot and deploy Microsoft 365 Defender (Identity, Office 365, Endpoint, Cloud Apps) |
| Organisation data | Map the existing classification taxonomy to sensitivity labels; create DLP and retention policies; review with Content Explorer | Extend labelling to more content and methods, such as container labels for sites and Teams and automatic labelling |
Both identity columns name Microsoft Entra ID P1, including the E5 column with risk-based policies. That is preserved as printed and is not a verified licensing conclusion (editorial note).
Teams and external sharing
Source: page 6
The guide calls Copilot’s introduction a good time to review Teams protection and external sharing, working from the most protected tier down:
| Order | Tier | Expected share of Teams |
|---|---|---|
| 1 | Highly sensitive (“highest protection” in the diagram) | Very few; many organisations have no data needing it |
| 2 | Sensitive | Some |
| 3 | Baseline, as a minimum for everything | Most |
The diagram gives no percentages; tier guidance covers sensitivity labels and site sharing settings. The statement that guest accounts are not licensed for Copilot dates from November 2023.
Deployment sequence
Source: page 7
For both E3 and E5 customers: (1) apply identity and access protection, (2) apply device protection, (3) assign Copilot licences to users who have both. Plan, test the plan, then roll out incrementally so lessons improve the plan.
Protect first, then license, ring by ring
Scroll sideways to read the full diagram →
| Stage | Identity and access | Devices |
|---|---|---|
| Evaluate | 50 test users (source figure); can be IT or a partner team | Test device protections with the same users |
| Pilot | Next 50–100 users in production | Apply device protections to the same users |
| Full deployment | Remaining users in larger increments | Remaining endpoints in larger increments |
At every stage, assign Copilot licences only after a user’s account and devices are protected. Information protection runs in parallel through six overlapping stages: discover sensitive data; develop a classification and protection schema; pilot it; deploy it across Microsoft 365; extend it to other SaaS apps; continue discovery elsewhere. The source sets no dates, durations or gate requiring this to finish before licensing.
Source differences
- Page 1 labels a box “Teams Chat” but captions it “Viva Engage groups”.
- The E5 Microsoft 365 Apps cell on page 5 is blank; nothing has been inferred.
- Page 6 uses “highest protection” (diagram) and “highly sensitive” (text) for the top tier.
- Page 3’s indexing criteria are “current” as of November 2023, not a statement of present behaviour.
2. Secure and govern
Condensed 2 November 2026 from the 22-page Secure and Govern Microsoft 365 Copilot blueprint, printed “Last updated March 6, 2026”. The E5 and E3 checklists are merged into comparison tables; entitlement markers are reproduced as printed, not refreshed.
Why it matters
Sources: page 4, page 5, page 6
Copilot honours existing permissions and builds on data already in Microsoft 365. Unsecured grounding data and interactions risk access beyond a role’s needs, unauthorised disclosure, and out-of-date or irrelevant responses. Two tools carry the work: Microsoft Purview and SharePoint Advanced Management, which the blueprint describes as included in Microsoft 365 Copilot.
Prerequisites and entitlements
The guidance assumes Copilot technical prerequisites are in place: core services (Teams, SharePoint, Exchange) technically enabled, and Office applications deployed on the current or monthly update channel, with modern Outlook recommended. Select deployment services are included in the FastTrack benefit; others are available through Microsoft Unified or partners.
| Marker | Source entitlement label |
|---|---|
| 1 | Copilot and SAM |
| 2 | OE3/ME3 |
| 3 | ME5/Purview suite |
| consumption | Printed against Microsoft 365 Archive actions |
The E5 checklist is titled “Optimized” and the E3 checklist “Foundational”. These markers indicate the source’s view of entitlement; confirm licensing separately (editorial note).
Three workstreams
Source: page 7
Three workstreams for secure, governed Copilot
Scroll sideways to read the full diagram →
| Workstream | Activities, in order | Outcome |
|---|---|---|
| Remediate oversharing | Identify high-risk sites and content; apply interim Copilot protections; fix access and permissions | High-risk sites contained; Copilot exposure reduced immediately, before full clean-up |
| Set up guardrails | Establish secure defaults; establish secure guardrails; continuously enforce and optimise | Protection by default; new content and sites protected at creation; Copilot scales without reintroducing oversharing |
| Meet regulations | Identify gaps against AI regulations; define regulatory requirements; improve data hygiene | Usage auditable, enforceable and defensible; better responses from a smaller overshared surface |
Remediate oversharing
Sources: page 9, page 10, page 11, checklists on pages 20–21
| Step | Both checklists | E5 adds | E3 instead |
|---|---|---|---|
| Identify | SAM Content Management Assessment for oversized audiences, EEEU usage, broken inheritance, inappropriate sharing, inactive or ownerless sites (1); prioritise high-risk sites | DSPM Data Risk Assessments for sensitive data and risky sharing links accessible to Copilot (3) | Content Explorer to find sites and files containing SITs (2) |
| Interim protection | Restricted Content Discovery to exclude sensitive sites from Copilot discovery (1); validate via audit and reports that restricted content no longer surfaces | DLP for Copilot to exclude sensitive content from grounding (3) | DLP for Copilot prompts policy (1) |
| Fix access | SAM site access reviews so site owners remediate down to file level (1); remove interim restrictions once remediated | Act on DSPM Data Risk Assessment recommendations (3) | — |
Page 11 expands the fixes: remove excess users, groups and company-wide links (including EEEU); correct broken inheritance; confirm ownership via SAM site lifecycle management; apply site sensitivity labels; tighten permissive links. Interim protections are temporary and should be removed once permissions are fixed.
Set up guardrails
Sources: page 13, page 14, page 15
| Step | Both checklists | E5 adds | E3 instead |
|---|---|---|---|
| Secure defaults | Restricted Access Control by default for business-critical sites at provisioning (1); disable or restrict company-wide sharing groups and Anyone links tenant-wide (2); require site sensitivity labels at provisioning (2) | — | — |
| Guardrails | DLP for Copilot prompts policy (1) | Default sensitivity labels for new content (3); DLP for Copilot to restrict processing of labelled content (3); IRM policies for inappropriate or non-compliant AI use (3) | Site labels marking sites Private, members only (2) |
| Optimise | Review DLP alerts; DSPM Activity Explorer | Activity Explorer includes prompts, responses and web search keywords (3); Data Risk Assessments for ongoing validation (3); IRM alerts (3) | Activity Explorer for interactions and sensitive data activity (2); DLP alerts (2) |
Meet regulations
Sources: page 17, page 18, page 19
| Step | Actions | Markers (E5 / E3) |
|---|---|---|
| Gaps | Compliance Manager assessment; review improvement actions; assign and track remediation (Compliance Score on page 17). E5 also validates with DSPM reports | 3 / 2 |
| Requirements | Set audit log retention; decide Copilot interaction retention or deletion with DLM; use eDiscovery to search, preserve and produce Copilot content | 2,3 / 2 |
| Site hygiene | Address inactive or obsolete sites with SAM policies and reports; move inactive high-value content to Microsoft 365 Archive, which stops Copilot processing it | 1; consumption |
| File hygiene | Retention and deletion policies for obsolete files; retention labels plus Microsoft 365 Archive to exclude files from Copilot while preserving records | 2,3 / 2; 2, consumption |
Page 17 cites checklists for 300+ continuously updated regulations. The E5 checklist targets AI-related requirements; the E3 checklist says regulatory requirements generally.
Decisions to make
| Decision | Source |
|---|---|
| Which sites are business-critical and get RAC at provisioning | page 13 |
| Which labelled files or emails Copilot should not use for grounding | page 14 |
| Which keywords or sensitive data types Copilot should not respond to; optionally, allowing them for Work IQ grounding but blocking web grounding | page 14 |
| When access is remediated enough to remove interim protections | page 11 |
| How long to keep audit log activities | page 18 |
| How long to keep, or when to delete, Copilot interactions | page 18 |
Who does what
The guides name few owners. Site owners act on SAM access reviews down to file level; site administrators can exclude sites from the Semantic Index (architecture page 3); Compliance Manager splits improvement actions between Microsoft as SaaS provider and the organisation as data owner. Deployment services come from FastTrack, Microsoft Unified or partners. No other roles are assigned.
Source differences
- E3 interim protection uses the DLP for Copilot prompts policy (marker 1), whereas page 10 and the E5 checklist use DLP for Copilot to exclude sensitive content (marker 3). The prompts policy carries marker 1 in both checklists.
- E3 heading order: the Remediate Oversharing column prints 1, 3, 2 (Identify, Apply interim protections, Fix access). This brief follows the 1–2–3 order used elsewhere.
- E3 access-review bullet ends “file level:” with no sub-bullets; page 11’s detail has not been imported into the E3 column.
- IRM: page 14 says IRM can automatically add risky users to more restrictive policies; the E5 checklist says only that IRM detects inappropriate or non-compliant use.
- Page 11 site labels list several outcomes; this is not a claim that one setting achieves them all.
- Work IQ versus web grounding is an optional refinement of the prompts policy, not a substitute for restricting labelled content.
- Interaction retention: page 18 says “how long to keep”; both checklists print “how to keep”.
- Retention purpose: page 19 frames deletion as improving response quality; the checklists frame it as reducing exposure while meeting record-keeping obligations.