How Corporate IT Admins Configure Microsoft Copilot with Enterprise Data Protection

Corporate IT administrators can secure Microsoft Copilot chat data against external leakage, unauthorized retention, and foundation model training by enforcing Enterprise Data Protection (EDP) through Microsoft Entra ID authentication and Microsoft 365 administrative policies.

Enterprise Data Protection (formerly known as Commercial Data Protection or CDP) applies automatically at no additional cost whenever eligible enterprise users authenticate with their corporate Microsoft Entra ID (work or school) account. Under EDP, chat prompts and generated responses remain within the organization’s Microsoft 365 tenant service boundary, are encrypted at rest and in transit, and are contractually prohibited from being used to train OpenAI or Microsoft foundation large language models (LLMs).

However, data protection is strictly identity-dependent. If employees use Copilot without signing in or log in with personal Microsoft accounts (MSA), their sessions fall back to consumer terms where conversations may be logged for service improvements and model tuning. To guarantee organizational protection, IT administrators must enforce corporate Entra ID authentication, restrict browser sign-in states, manage web-grounding policies, and set up Purview governance.

1. How Enterprise Data Protection (EDP) Protects Corporate Data

Microsoft Copilot operates under two distinct legal and architectural frameworks depending on the user's login identity:

Core Architectural Safeguards Under EDP

• Tenant Isolation and Encryption: All user prompts and AI responses are processed within the Microsoft 365 security boundary. Customer data is encrypted in transit using TLS 1.2+ and at rest using BitLocker and service encryption.
• No Model Training: Microsoft does not have access to customer prompts or responses to train foundation models from OpenAI or Microsoft. Data stays isolated to the active session and tenant storage.
• Exchange-Based Compliance Storage: Copilot chat interactions are stored in the user's Exchange Online mailbox architecture, enabling administrators to apply automated retention policies, legal holds, and Purview audit logging.
• Strict Processor Commitments: Microsoft operates as a data processor under the Data Protection Addendum (DPA), satisfying GDPR, ISO/IEC 27018, and EU Data Boundary requirements.

2. Prerequisites and License Eligibility

Enterprise Data Protection is included at no extra cost for organizations holding qualifying Microsoft 365 or Office 365 subscriptions:

• Enterprise: Microsoft 365 E3, E5, F1, F3; Office 365 E1, E3, E5, F3
• Business: Microsoft 365 Business Basic, Business Standard, Business Premium
• Education: Microsoft 365 A3, A5; Office 365 A1, A3, A5 (including faculty and eligible student licenses)
• Standalone Teams & Government: Teams Enterprise, Teams Essentials, and GCC / GCC High environments

Users assigned a dedicated Microsoft Copilot license (formerly Microsoft 365 Copilot add-on) receive the same EDP commitments while unlocking Microsoft Graph grounding across internal tenant files, emails, and SharePoint sites.

3. Step-by-Step IT Administrator Configuration Blueprint

Securing Copilot across an entire enterprise requires administrators to configure five key layers: identity enforcement, browser policy controls, web search grounding, network routing, and compliance governance.

+-----------------------------------------------------------------------------------+
|                           1. Identity & Network Layer                             |
|  - Assign M365 Licenses -> Route to copilot.cloud.microsoft -> Tenant Restrictions|
+-----------------------------------------------------------------------------------+
                                         |
                                         v
+-----------------------------------------------------------------------------------+
|                        2. Device & Edge Browser Policies                          |
|  - Force Entra Sign-in (BrowserSignin = 2) -> RestrictSigninToPattern             |
|  - Control Contextual Access via EdgeEntraCopilotPageContext                      |
+-----------------------------------------------------------------------------------+
                                         |
                                         v
+-----------------------------------------------------------------------------------+
|                       3. Copilot Control System & Policy                          |
|  - Microsoft 365 Admin Center Settings -> Manage Web Search Grounding             |
+-----------------------------------------------------------------------------------+
                                         |
                                         v
+-----------------------------------------------------------------------------------+
|                     4. Microsoft Purview Governance & Audit                       |
|  - Retention Policies -> eDiscovery & Audit Logs -> Data Loss Prevention (DLP)    |
+-----------------------------------------------------------------------------------+

Step 1: Enforce Entra ID Sign-In and Block Personal Accounts

Because data protection only activates when an Entra ID token is present, administrators must prevent employees from accessing Copilot with personal accounts on managed corporate devices.

A. Configure Microsoft Edge Management Policies (Intune / Group Policy)

Deploy administrative templates for Microsoft Edge to ensure users cannot sign in with non-corporate identities:

1. Force Browser Sign-In (BrowserSignin):
   • Set BrowserSignin to 2 (Force users to sign in to use the browser). This ensures that every Edge session is tied to an authenticated profile.
2. Restrict Allowed Accounts (RestrictSigninToPattern):
   • Set RestrictSigninToPattern to your corporate email domain regex pattern (for example: .*@yourcompany\.com).
   • This blocks employees from creating personal profiles or signing into Edge using @outlook.com, @gmail.com, or other external accounts.
3. Manage Edge Sidebar Page Context (EdgeEntraCopilotPageContext):
   • Set EdgeEntraCopilotPageContext to Enabled (1) if you allow Copilot to summarize active intranet pages and PDFs, or Disabled (0) to block the browser from passing active page text into the chat sidebar. Note that Microsoft Purview DLP policies automatically block Copilot summarization on protected pages regardless of this setting.

B. Configure Entra ID Tenant Restrictions v2

To prevent employees on the corporate network from signing into consumer Copilot or external vendor tenants:

1. Navigate to the Microsoft Entra admin center > External Identities > Cross-tenant access settings.
2. Configure Tenant Restrictions v2 to permit authentication only to your authorized Microsoft Entra directory ID, blocking unauthorized cloud sessions.

Step 2: Configure Network Endpoints and Ensure Access

Microsoft has unified Copilot services under the .cloud.microsoft domain architecture.

1. Permit Core Endpoints: Ensure corporate firewalls, secure web gateways (SWG), and proxy inspection tools allow wildcard traffic to:
   • *.cloud.microsoft
   • Primary entry point: https://copilot.cloud.microsoft
2. Avoid Network-Level URL Filtering on Copilot: Microsoft advises against attempting selective URL, IP, or network protocol blocks against Copilot subsystems. Because Copilot is deeply embedded into Teams, Outlook, and Microsoft 365 Web apps, partial packet blocking can break core collaboration workflows. Use Microsoft 365 in-service controls instead.

Step 3: Manage Web Search Grounding in Copilot

By default, Microsoft Copilot Chat utilizes Bing web search grounding to answer queries requiring real-time external knowledge (such as news or current industry data).

How Bing Search Queries are Handled

When web grounding is invoked:

• Copilot extracts a short, multi-word search query from the user's prompt.
• User identifiers (UPN), corporate domain names, and Tenant IDs are completely stripped from the query.
• Full documents, emails, and sensitive attachments are never sent to Bing.
• Queries are transmitted over HTTPS to Bing and are contractually isolated: they are not shared with advertisers, do not generate consumer search profiles, and do not train foundation models.

Controlling Web Grounding via Microsoft 365 Cloud Policy

If corporate regulatory standards forbid external search queries entirely:

1. Open the Microsoft 365 Apps admin center (config.office.com) and navigate to Cloud Policy.
2. Create or edit a policy configuration targeting your user groups.
3. Locate the setting Allow web search in Copilot:
   • Enabled in Microsoft Copilot and Microsoft Copilot Chat: Permits grounding with anonymized web queries.
   • Disabled in Microsoft Copilot Work mode; Enabled in Web mode: Restricts internal work queries from hitting Bing while allowing general web assistance.
   • Disabled in Microsoft Copilot and Microsoft Copilot Chat: Completely turns off Bing search queries. Copilot generates responses solely from its existing model weights or internal tenant data.

Administrators can also manage this control directly in the Microsoft 365 admin center under Copilot > Settings.

Step 4: Configure Data Retention and Purview Audit Controls

Under Enterprise Data Protection, Copilot chat interactions are stored in the compliance boundary of Exchange Online. IT administrators can govern this data using Microsoft Purview:

1. Retention Policies for Copilot:
   • Go to Microsoft Purview compliance portal > Data lifecycle management > Microsoft 365 > Retention Policies.
   • Create a dedicated retention policy scoping Microsoft Copilot user interactions.
   • Choose whether to automatically purge chat interactions after a specific time period (e.g., 30, 60, or 90 days) to minimize data exposure, or retain records to satisfy regulatory compliance.
2. Audit Logging & Activity Explorer:
   • In Microsoft Purview > Audit, search for Copilot interaction events under the CopilotInteraction schema.
   • Admins can inspect the timestamp, user ID, client application, and whether web search grounding was triggered.
3. Data Loss Prevention (DLP):
   • Configure Endpoint DLP and Edge DLP policies in Purview. When a user opens a document tagged as "Confidential" or "Restricted", Edge native DLP prevents the user from copying text into Copilot or asking Copilot to summarize the file.

4. Verification: How to Confirm Commercial Protection is Active

Once configuration is complete, administrators and end users should verify that Enterprise Data Protection is active:

1. Visual UI Check:
   • Visit https://copilot.cloud.microsoft or open Copilot in the Microsoft Edge sidebar.
   • Look for the green shield icon labeled Protected displayed prominently near the top navigation and next to the "New Chat" button.
   • Verify that the profile icon indicates a Work account rather than a personal profile.
   • Below the prompt input box, Copilot displays the security notice: "Your personal and company data are protected in this chat."
2. Personal Account Prevention Test:
   • Attempt to sign into Edge or Copilot using an unauthorized personal account (@outlook.com). Edge should display an administrative restriction banner blocking profile creation.
3. Purview Audit Test:
   • Submit a test prompt within an authenticated session.
   • Verify within 15–30 minutes that the interaction event is recorded in the Microsoft Purview Audit log under your tenant.

5. Summary and Best-Practice Recommendations

Securing Microsoft Copilot does not require third-party proxy wrappers or complex network blockers. Microsoft provides built-in enterprise isolation whenever Entra ID credentials are used.

To eliminate enterprise data leak risks:

• Never permit unauthenticated or personal MSA sessions on corporate endpoints. Use Intune and Edge policies (BrowserSignin = 2 and RestrictSigninToPattern) to enforce corporate Entra accounts.
• Educate staff on the green shield: Train employees to look for the green "Protected" shield badge before pasting sensitive internal text or technical code.
• Align Web Grounding with Compliance: If your business handles regulated information (e.g., defense, healthcare, strict financial services), evaluate whether to restrict Bing web queries via the "Allow web search in Copilot" cloud policy.
• Automate Lifecycles in Purview: Implement automated retention schedules so that chat prompts and responses are routinely purged according to your company's data governance policy.

References

• Enterprise data protection in Microsoft Copilot and Microsoft Copilot Chat | Microsoft Learn
• Microsoft Copilot Chat Privacy and Protections | Microsoft Learn
• Data, privacy, and security for web search in Microsoft Copilot and Microsoft Copilot Chat | Microsoft Learn
• Manage Microsoft Copilot Chat | Microsoft Learn