Copilot Control System (CCS)¶

Learning Status

📖 Comprehensive overview complete — session prep for Tuesday April 21. Last updated: 2026-04-16.

Internal Insight

⚠️ This page contains internal positioning guidance sourced from Microsoft field FAQs and enablement materials. Do not share publicly.

☕ Café Analogy¶

Your café just installed a brilliant AI espresso machine (Copilot) that can make any drink a customer asks for. But the café owner needs answers:

"Who's allowed to use the machine?" → Management Controls
"Is it accidentally giving away free drinks or using the secret recipe?" → Security & Governance
"How many coffees did it make today? Are customers happier?" → Measurement & Reporting

The Copilot Control System is the café's operations manual — it doesn't make the coffee, but it makes sure the coffee-making is safe, managed, and measurable.

Without CCS: You have an amazing AI machine with no guardrails. With CCS: You have an enterprise-grade AI platform that IT can confidently deploy.

What Is Copilot Control System?¶

The Copilot Control System is a framework of integrated controls and capabilities designed to help IT administrators and security professionals effectively secure, manage, and analyse the use of AI across Microsoft 365.

Key Facts¶

	Detail
What it is	A governance framework — NOT a product, NOT a SKU
What it covers	M365 Copilot, Copilot Chat, Copilot Studio agents, pre-built agents
Where controls live	M365 Admin Center, Power Platform Admin Center, Purview, Defender, SharePoint Admin
Cost	No separate cost — capabilities are distributed across existing M365 licences (E3/E5/Copilot)

The One-Liner¶

👉 CCS = The enterprise IT control layer for AI in Microsoft 365

It answers the customer question:

"How do we control AI safely at enterprise scale?"

The 3 Pillars of CCS¶

┌─────────────────────────────────────────────────────────────────┐
│                   COPILOT CONTROL SYSTEM                        │
│                                                                 │
│  ┌──────────────────┐  ┌──────────────────┐  ┌──────────────┐  │
│  │  🔐 SECURITY &   │  │  ⚙️ MANAGEMENT   │  │  📊 MEASURE  │  │
│  │   GOVERNANCE     │  │   CONTROLS       │  │  & REPORT    │  │
│  │                  │  │                  │  │              │  │
│  │ • Data security  │  │ • Licensing      │  │ • Readiness  │  │
│  │ • AI security    │  │ • Agent lifecycle│  │ • Adoption   │  │
│  │ • Compliance     │  │ • Customisation  │  │ • ROI        │  │
│  │ • Privacy        │  │ • Access control │  │ • Impact     │  │
│  └──────────────────┘  └──────────────────┘  └──────────────┘  │
│                                                                 │
│  Covers: M365 Copilot │ Copilot Chat │ Agents │ Copilot Studio │
└─────────────────────────────────────────────────────────────────┘

🔐 Pillar 1: Security & Governance¶

☕ Analogy: Making sure the espresso machine doesn't accidentally serve someone's secret recipe to a rival café.

When organisations deploy Copilot and agents, they face new and amplified risks related to data security, compliance, and governance. This pillar helps mitigate them.

Capability	What It Does	Tools Involved
Data security	Prevent sensitive data from being exposed via Copilot responses	Purview DLP, Sensitivity Labels, SharePoint Advanced Management
AI security	Detect risky prompts, unsafe tool use, anomalous behaviour	Defender XDR, Purview Insider Risk
Compliance & privacy	Retain/log Copilot interactions, eDiscovery, audit trails	Purview Compliance Manager, Audit Logs
Oversharing detection	Identify broadly shared content that Copilot could surface	SharePoint Advanced Management
Prompt-level DLP	Block Copilot from returning responses grounded in sensitive data	Purview DLP for Copilot (rolling out now)

Key message for customers:

"Copilot respects your existing permissions. Sensitivity labels add additional protection on top. CCS ensures this is enforced, auditable, and measurable."

⚙️ Pillar 2: Management Controls¶

☕ Analogy: Deciding which staff members get a key to the espresso machine, what menu items they can make, and setting the opening hours.

Capability	What It Does
Licensing governance	Deploy Copilot licences to the right users, track utilisation
Agent lifecycle management	Manage agent creation, approval, versioning, retirement
Access control	Who can use what AI capability (role-based, group-based)
AI sprawl prevention	Ensure only approved agents are deployed — no shadow AI
Policy enforcement	Connection approvals, agent publishing controls, data flow rules
Controlled rollout	Phase deployment by department/geography/user group

Where you manage this:

M365 Admin Center → Copilot settings
Power Platform Admin Center → Agent policies
SharePoint Admin Center → Oversharing controls
Copilot Studio → Agent publication settings

📊 Pillar 3: Measurement & Reporting¶

☕ Analogy: Checking the café dashboard every morning — how many coffees were served, which barista is fastest, and whether customers are coming back.

Capability	What It Does
Readiness tracking	Are permissions clean? Is data labelled? Ready for rollout?
Adoption metrics	Who's using Copilot? How often? Which features?
Productivity impact	Time saved, meetings summarised, emails drafted
Business value / ROI	Demonstrate tangible returns to leadership
Licence optimisation	Identify underutilised licences, reassign to active users

Tools: Copilot Analytics (in M365 Admin Center), Viva Insights, Admin Centre usage reports.

This pillar answers leadership questions like:

"Are people actually using Copilot?"
"Where is it creating the most value?"
"Which departments should we scale to next?"
"Are we getting our money's worth?"

CCS vs Agent 365 — Complement, Not Conflict¶

This is where customers (and sellers!) get confused. Let me make it crystal clear.

The Simple Mental Model¶

┌─────────────────────────────────────────────────────────┐
│                    M365 E7 ($99/user/mo)                │
│         "Securely run a human-led, agent-operated       │
│                     enterprise"                         │
│                                                         │
│  ┌─────────────────────────┐ ┌───────────────────────┐  │
│  │   COPILOT CONTROL       │ │     AGENT 365         │  │
│  │   SYSTEM (CCS)          │ │                       │  │
│  │                         │ │                       │  │
│  │ Governs AI FOR people   │ │ Governs AI that WORKS │  │
│  │ (Copilot experience)    │ │ FOR people (Agents)   │  │
│  │                         │ │                       │  │
│  │ • How users interact    │ │ • Central registry    │  │
│  │   with Copilot          │ │ • Identity & access   │  │
│  │ • Data protection       │ │ • Lifecycle mgmt      │  │
│  │ • Compliance/audit      │ │ • Threat detection    │  │
│  │ • Usage analytics       │ │ • Agent observability │  │
│  └─────────────────────────┘ └───────────────────────┘  │
│                                                         │
│               + M365 E5 + Entra Suite                   │
└─────────────────────────────────────────────────────────┘

One-Line Differentiation (Memorise This!)¶

Layer	What It Governs	Simple English
CCS	M365 Copilot & Copilot Chat	Governance for people using AI
Agent 365	All enterprise agents	Governance for AI that works for people
M365 E7	Both together	Governance for both at enterprise scale

They Are Designed to Work Together¶

	Copilot Control System	Agent 365
Focus	User AI experience	Agent execution
Manages	Copilot interactions	Agent lifecycle
Security	Prompt-level DLP, audit	Agent identity, threat detection
Analytics	Copilot usage & adoption	Agent performance & observability
Is a SKU?	❌ No — distributed across existing licences	✅ Yes — $15/user/mo add-on or in E7
Required?	Comes with M365 Copilot licence	Needed for enterprise agent governance

The Evolution (Important Context)¶

⚠️ Internal insight — do not share publicly.

Originally, CCS included governance for Copilot-connected agents too. With Agent 365's introduction:

Agent controls are moving to Agent 365 — this is a positioning shift, not a licensing change
Copilot Analytics is becoming Copilot & Agent Analytics — Copilot analytics stays in CCS, agent analytics moves to A365
CCS remains the Copilot experience governance layer
Agent 365 becomes the agent execution governance layer

How to Position CCS With Customers¶

The 5-Step Story (Use This in Presentations)¶

Step	Message	What You're Selling
1. Copilot alone	"Copilot helps your people work smarter"	Productivity
2. + CCS	"CCS helps IT safely manage how people use AI"	Governance & trust
3. + Agents	"Now AI isn't just helping — it's doing work for you"	Automation
4. + Agent 365	"Agent 365 helps IT safely manage AI that acts on behalf of people"	Agent governance
5. = M365 E7	"E7 brings it all together for enterprise-scale AI"	The complete platform

Customer-Friendly Architecture Stack¶

┌──────────────────────────────────────┐
│  👤 USERS                            │   People use Copilot
├──────────────────────────────────────┤
│  🤖 COPILOT                          │   AI assistant experience
├──────────────────────────────────────┤
│  🔧 AGENTS                           │   AI doing work autonomously
├──────────────────────────────────────┤
│  📊 MICROSOFT GRAPH                  │   Enterprise data grounding
├──────────────────────────────────────┤
│  🛡️ CCS + AGENT 365                  │   Governance & control plane
├──────────────────────────────────────┤
│  🔐 SECURITY (E5/Entra/Defender)     │   Identity + compliance + threat
└──────────────────────────────────────┘

What's Coming to CCS (Roadmap)¶

⚠️ Internal insight — sourced from NDA roadmap decks and ANZ field materials. Do not share publicly.

Rolling Out Now (FY26)¶

Feature	What It Does	Impact
Purview DLP for Copilot prompts	Detect sensitive data in prompts, block grounded responses using sensitive data	Real-time data leakage prevention at prompt level
Enhanced agent governance	Govern SharePoint content sharing inside agents, prevent unintentional oversharing	Addresses regulated customer concerns
Unified admin extensibility tab	Manage Copilot extensibility in one place in M365 Admin Center	Replaces fragmented admin across 4+ portals

Coming Soon (FY26–FY27)¶

Feature	What It Does	Impact
Lifecycle automation for agents	Bulk reassignment on ownership change, deletion rules, stakeholder notifications	From manual management → automated governance
Agent risk monitoring	Purview + Entra + Defender surface agent risks, detect unsafe tool use	CCS becomes "endpoint security for agents"
Expanded Copilot Analytics	Business leader + IT admin reporting, consumption/adoption/licensing telemetry	Beyond usage → business impact tracking
One unified governance plane	Single admin experience for Copilot + Agents + Extensibility	One place to govern all AI in M365

The Direction¶

CCS is evolving from "admin settings for Copilot" to:

👉 The enterprise security, governance, and intelligence plane for ALL AI in Microsoft 365

Customer Objection Handling¶

🟡 Objection 1: "We don't need CCS — we already have security tools"¶

Response:

"You're absolutely right that you already have great security tools like Purview and Defender. The good news is — CCS is built on top of those exact tools. It's not a new product. It's a framework that extends your existing security investment to cover AI-specific risks like Copilot prompt leakage, agent oversharing, and AI sprawl. If you already have E5, you already have most of the CCS capabilities. CCS just helps you use them for AI governance."

Key point: CCS is not a new thing to buy — it's a new way to USE what you already have.

🟡 Objection 2: "Isn't this just another Microsoft buzzword / marketing wrapper?"¶

Response:

"Fair question! CCS is a logical grouping of controls that already exist across M365, Purview, Defender, and SharePoint. Microsoft grouped them under one name so IT teams have a clear framework to answer 'how do we govern AI?' — instead of hunting across 6 different admin portals. Think of it like 'Zero Trust' — it's not a product, it's a framework. CCS is the same idea for AI governance."

Analogy: Zero Trust = security framework. CCS = AI governance framework. Same concept.

🟡 Objection 3: "Does CCS conflict with Agent 365? Do we need both?"¶

Response:

"They complement each other perfectly. Think of it this way: CCS governs how people use AI (Copilot experience). Agent 365 governs how AI works for people (agent execution). If you only deploy Copilot, CCS covers you. The moment you start deploying agents that act autonomously, you need Agent 365 too. Together, they give you governance across the entire AI spectrum — from assisted to autonomous."

Scenario	What You Need
Deploying M365 Copilot only	CCS (included with Copilot licence)
Copilot + a few agents	CCS + consider Agent 365
Enterprise-scale agents + Copilot	CCS + Agent 365 (or E7 which bundles both)

🟡 Objection 4: "We're worried about data leakage through Copilot"¶

Response:

"That's the #1 concern we hear, and it's exactly what CCS addresses. Let me walk you through the layers:

Permissions first — Copilot only accesses data the user already has permission to see. It doesn't bypass any existing access controls.

Sensitivity labels — If content is labelled 'Confidential', Copilot respects those labels.

DLP policies — Purview DLP can now detect sensitive data IN Copilot prompts and block responses grounded in that data.

SharePoint Advanced Management — Identifies broadly shared content that Copilot could surface, so you can clean it up proactively.

Audit trails — Every Copilot interaction is logged and available for eDiscovery.

The data leakage problem Copilot creates is actually a data hygiene problem that already existed — Copilot just makes it visible. CCS helps you fix the root cause."

🟡 Objection 5: "We can't justify the cost of E7 just for governance"¶

Response:

"You don't need E7 for CCS. CCS capabilities are distributed across your existing licences:

E3 gives you basic admin controls and SharePoint management

E5 adds Purview, Defender, advanced compliance

M365 Copilot licence includes SharePoint Advanced Management and Copilot Analytics

E7 makes sense when you need Copilot + Agent 365 + Entra Suite together. For customers who only need Copilot with strong governance, E5 + Copilot licence gives you a very solid CCS foundation."

Licence	CCS Capabilities
E3 + Copilot	Basic admin controls, SharePoint management, usage reports
E5 + Copilot	Full Purview DLP, Defender, eDiscovery, advanced compliance, Copilot Analytics
E7	All of the above + Agent 365 + Entra Suite

🟡 Objection 6: "How do we audit what Copilot is doing?"¶

Response:

"CCS gives you full visibility:

Copilot Analytics — Usage dashboards showing who's using Copilot, how often, which features

Purview Audit — Every Copilot interaction is logged (subject to your Purview configuration and licensing)

eDiscovery — Search and review Copilot interactions as part of legal or compliance investigations

Insider Risk Management — Flag unusual AI usage patterns

Admin Activity Logs — Track admin changes to Copilot policies

You get the same level of visibility into AI interactions as you have for email and Teams today."

🟡 Objection 7: "What if we want to restrict Copilot to specific users or departments?"¶

Response:

"Absolutely possible. CCS management controls let you:

Assign licences to specific security groups (not tenant-wide)

Use Conditional Access to restrict Copilot access by user/group/device/location

Cloud Policy to disable specific Copilot features per group (e.g., web grounding off for legal team)

Phased rollout — start with IT, then expand to early adopters, then department-by-department

We always recommend a scoped rollout. No customer should go tenant-wide on day one."

🟡 Objection 8: "What about regulated industries / government?"¶

Response:

"CCS respects your compliance boundaries:

All Copilot processing stays within the Microsoft 365 trust boundary (enterprise data protection commitments)

EU Data Boundary is supported for EU/EFTA customers

Sensitivity labels + DLP ensure classified content stays protected

eDiscovery and audit satisfy regulatory evidence requirements

GCC/GCC-High/DoD support is rolling out (check specific feature availability)

⚠️ Caveat for Anthropic/Claude: If your tenant uses Claude models in Copilot, data processed by Anthropic currently falls outside the EU Data Boundary. This is important for regulated workloads. CCS gives admins controls to restrict model routing if needed."

Quick Reference Card — CCS at a Glance¶

Question	Answer
What is CCS?	A governance framework for AI in M365 — security, management, analytics
Is it a product?	No — it's a logical grouping of controls across M365, Purview, Defender, SharePoint
Do I buy it separately?	No — capabilities come with E3/E5/Copilot licences
How is it different from Agent 365?	CCS = governs Copilot (user AI). Agent 365 = governs agents (autonomous AI)
Do they conflict?	No — they complement each other and layer together
What admin portals?	M365 Admin Center, Power Platform Admin, SharePoint Admin, Purview
What's the future?	Evolving into a unified governance plane for ALL AI in M365

Mermaid: CCS in the M365 AI Stack¶

flowchart LR
    subgraph Users["👤 End Users"]
        A[Use Copilot in Apps]
    end

    subgraph AI["🤖 AI Layer"]
        B[M365 Copilot]
        C[Agents]
    end

    subgraph Data["📊 Data Layer"]
        D[Microsoft Graph]
        E[SharePoint / OneDrive / Exchange]
    end

    subgraph Governance["🛡️ Governance Layer"]
        F["CCS<br/>Security · Management · Measurement"]
        G["Agent 365<br/>Registry · Identity · Lifecycle"]
    end

    subgraph Security["🔐 Security Foundation"]
        H[Purview DLP]
        I[Defender XDR]
        J[Entra ID]
        K[Conditional Access]
    end

    A --> B
    A --> C
    B --> D
    C --> D
    D --> E
    F --> B
    G --> C
    H --> F
    I --> F
    J --> G
    K --> F

    style F fill:#3B82F6,stroke:#1E40AF,color:#ffffff
    style G fill:#8B5CF6,stroke:#6D28D9,color:#ffffff

Session Prep Notes — Tuesday April 21¶

Suggested Talking Points¶

Open with the problem — "You've deployed Copilot. Now your CISO asks: how do we govern this? That's CCS."
3 pillars — Security, Management, Measurement. One slide each.
CCS vs Agent 365 — use the complement diagram. This clears 90% of confusion.
Not a new SKU — this lands well. "You already own most of this."
Data leakage story — walk through the 5-layer protection. Most impactful objection handler.
Roadmap teaser — prompt-level DLP, unified admin, lifecycle automation. Shows Microsoft's investment.
Close with E7 positioning — CCS + Agent 365 + Entra = the AI-ready enterprise.

Demo Ideas¶

M365 Admin Center → Copilot settings, licence assignment
Purview → Show DLP policies that apply to Copilot
SharePoint Admin → Oversharing detection reports
Copilot Analytics → Usage dashboard

Key Numbers to Have Ready¶

Stat	Source
353% ROI (SMB)	Forrester TEI
116% ROI (Enterprise)	Forrester TEI
29% faster task completion	Microsoft Research
26 min/day saved	UK Government trial

Copilot Control System (CCS)¶

☕ Café Analogy¶

What Is Copilot Control System?¶

Key Facts¶

The One-Liner¶

The 3 Pillars of CCS¶

🔐 Pillar 1: Security & Governance¶

⚙️ Pillar 2: Management Controls¶

📊 Pillar 3: Measurement & Reporting¶

CCS vs Agent 365 — Complement, Not Conflict¶

The Simple Mental Model¶

One-Line Differentiation (Memorise This!)¶

They Are Designed to Work Together¶

The Evolution (Important Context)¶

How to Position CCS With Customers¶

The 5-Step Story (Use This in Presentations)¶

Customer-Friendly Architecture Stack¶

What's Coming to CCS (Roadmap)¶

Rolling Out Now (FY26)¶

Coming Soon (FY26–FY27)¶

The Direction¶

Customer Objection Handling¶

🟡 Objection 1: "We don't need CCS — we already have security tools"¶

🟡 Objection 2: "Isn't this just another Microsoft buzzword / marketing wrapper?"¶

🟡 Objection 3: "Does CCS conflict with Agent 365? Do we need both?"¶

🟡 Objection 4: "We're worried about data leakage through Copilot"¶

🟡 Objection 5: "We can't justify the cost of E7 just for governance"¶

🟡 Objection 6: "How do we audit what Copilot is doing?"¶

🟡 Objection 7: "What if we want to restrict Copilot to specific users or departments?"¶

🟡 Objection 8: "What about regulated industries / government?"¶

Quick Reference Card — CCS at a Glance¶

Mermaid: CCS in the M365 AI Stack¶

Session Prep Notes — Tuesday April 21¶

Suggested Talking Points¶

Demo Ideas¶

Key Numbers to Have Ready¶

Official References¶