3.1. Enable and Manage Copilot
💡 First Principle: Enabling Copilot is a sequence of gates, each owned by a different part of the platform: technical readiness (licenses and app channels), data readiness (permissions and labels), then tenant settings that decide what Copilot may reach — the web, third-party models, external data through connectors — and what users see. Most Copilot admin questions are really asking which gate a requirement belongs to.
Why care? Every Copilot setting is a decision about what data leaves the organization's protections, what users can do, and what it costs. Web search sends queries outside the Data Protection Addendum. Third-party model providers process data under different terms. Connectors bring external content into Copilot's reach. An admin who flips these on without knowing the consequences can create compliance exposure in a single click; one who leaves everything off delivers a Copilot nobody uses.
The mental model is a settings map organized by who owns the control:
| Requirement | Where it's controlled |
|---|---|
| Who is eligible and licensed | Microsoft 365 admin center > Reports (readiness) and license assignment |
| Which content Copilot can surface | SharePoint permissions, SharePoint Advanced Management, Purview |
| Web grounding | Cloud Policy service — the Allow web search in Copilot policy |
| Tenant behavior — self-service purchase, admin-center Copilot, release cadence, AI disclaimer, image generation, AI providers | Microsoft 365 admin center > Copilot > Settings (AI Administrator) |
| Copilot Cowork access | Microsoft 365 admin center > Copilot > Cost Management (a spending policy) |
| External data sources | Microsoft 365 admin center > Copilot > Connectors |
⚠️ Common Misconception: Admins often look for a web search toggle under Copilot > Settings and assume it controls web grounding. That entry only links to the Cloud Policy service, where the Allow web search in Copilot policy is the actual control.