Copilot Chat Basic: A Law Firm Admin Guide

The free tier is already at your associates’ desks. Here are the admin controls to set now.

Diverse legal administrators in a high-tech Houston office viewing a "Copilot Chat Basic" guide on a large display and laptop, featuring the Cocha Technology logo.

Copilot Chat Basic is the no-added-cost Copilot tier included with qualifying Microsoft 365 commercial subscriptions, so most of your associates already have it. It’s grounded in the web and doesn’t search your SharePoint unless someone pastes or uploads content. This guide covers the controls a law firm should set: access, web search, DLP, and logging.

The most important thing to understand upfront is this: Copilot Chat Basic is not a future consideration. Every user with a qualifying Microsoft 365 or Office 365 commercial subscription, meaning any account backed by a Microsoft Entra ID tenant, already has access to it. Whether or not your firm has officially launched an AI program, the tool is almost certainly already in use. The question is whether you are shaping that use or discovering it after the fact.

Before choosing an upgrade path, review which Microsoft 365 license includes what.

What Copilot Chat Basic is, and what it isn’t

The single most persistent misconception among practice group leaders is that the free tier of Copilot is reading every file in the firm. It is not. Copilot Chat Basic is primarily web-grounded: it uses Bing to find publicly available information and a large language model to reason over it. It does not connect to your organization’s SharePoint, Exchange corpus, or any internal data repository unless a user explicitly provides content in the chat window. That connection to internal data is the exclusive territory of the paid M365 Copilot (Premium) tier via the Microsoft Graph.

When you’re ready, here’s when to move from Basic to Premium and what to lock down first.

The free tier has gone through several names as Microsoft has iterated on its product structure: it was originally called Copilot with Enterprise Data Protection (EDP), then simply Copilot Chat, and as of the April 15, 2026 rollout it is labeled Copilot Chat (Basic) in product interfaces. Understanding that naming history is useful when reading older vendor documentation.

The three ways Copilot Chat Basic can consume firm data

While it does not index private data automatically, it can consume what a user actively provides. Firm data enters the chat in three ways:

  • Manual file uploads. Users can drag and drop a PDF, brief, or contract directly into the chat window. Microsoft Purview DLP can’t scan the contents of files uploaded directly into a prompt, so policy, training, and access gates are the controls here. See the DLP section below.
  • Copy-paste. Any text a user pastes into the prompt becomes part of the AI context. There is no technical guardrail against pasting privileged content; the control here is policy and training, not platform enforcement.
  • Outlook integration. Copilot Chat Basic has access to email summarization and calendar grounding in Outlook. This integration continues for unlicensed users, one of the few in-app experiences Microsoft kept for them.

Copilot data protection: what the EDP boundary means

Because these are commercial accounts with Entra ID, all Copilot Chat Basic interactions benefit from Enterprise Data Protection (EDP). Microsoft acts as a data processor under your organization’s Microsoft 365 commercial agreement. Prompts and uploaded data are not used to train the underlying public models. The data stays within the Microsoft 365 compliance boundary, subject to the same data residency, retention, and eDiscovery controls as the rest of your tenant. This is the same protection framework that governs your email and SharePoint data. See Microsoft Purview’s AI hub for the full compliance documentation.

Copilot access control: gating who gets the tool

Most firms do not want a firm-wide rollout before governance is in place. Copilot access control in Microsoft 365 operates at two levels: the tenant and the individual app. Here is how each works.

Tenant-level: Integrated Apps and the Copilot Control System

The primary lever for Copilot access control is the Copilot Control System inside the Microsoft 365 Admin Center. Go to:

Microsoft 365 Admin Center → Settings → Search & intelligence → Copilot

From here, the “Copilot app” entry controls the web experience and the standalone desktop app. To restrict access to a specific group, such as a Technology Committee pilot, a particular practice group, or a subset of IT staff, go to:

Microsoft 365 Admin Center → Settings → Integrated Apps → Copilot
 

Change the deployment status from “Everyone” to specific Azure AD security groups. Users outside those groups will not see the Copilot icon in the Microsoft 365 web portal or in the sidebars of their apps. This is the cleanest firm-wide access gate available without deploying endpoint policy. Deciding who gets Copilot is one control; deciding who can build and share agents inside it is another, covered in our Copilot Agent Builder controls guide.

App-level: suppressing Copilot inside specific Office apps

Some firms want the standalone Copilot app available for general research but want to keep it out of Word or Excel, where a user might feed it a sensitive draft or a client document by mistake. Two mechanisms handle this:

  • Microsoft Intune policy (via the Intune Admin Center): the preferred mechanism for organizations that already manage endpoints with Intune. Deploy a configuration profile that disables Connected Experiences for specific Office apps.
  • Microsoft 365 Apps Cloud Policy service (config.office.com): a cloud-based Group Policy equivalent. Create a policy that targets an Azure AD group and disables the “Allow Office to connect to online services” Connected Experiences setting for the apps you want to suppress.

 

Since Copilot relies on Connected Experiences to function within Office apps, disabling this setting for a specific app removes the Copilot sidebar from that app while leaving everything else intact. The user can still open the standalone Copilot app in a browser.

Post-April 15 note

After April 15, 2026, Copilot Chat Basic users will no longer have in-app sidebar access in Word, Excel, PowerPoint, or OneNote regardless of your Connected Experiences settings. The app-level suppression controls described above become primarily relevant for licensed M365 Copilot (Premium) users whose in-app integration you want to restrict on specific machines or for specific groups.

Teams: controlling the Copilot app pin

In Microsoft Teams, the presence of the Copilot app is governed by Teams App Setup Policies. The standard approach for a controlled rollout is:

  • Create a global policy that unpins the Copilot app for all users
  • Create a second policy that pins it for your pilot security group
  • Assign the pilot policy to the group via the Teams Admin Center

 

This gives you a clean on/off switch per group without touching Intune or Cloud Policy.

Copilot web search policy: the most consequential dial in the admin center

Because Copilot Chat Basic is grounded in the web, the Copilot web search policy is the single most impactful setting available to most firms. It controls whether the tool can query Bing at all, and what identifiers accompany those queries.

The setting lives in the Copilot Control System under the “Allow web search in Copilot“ policy. Here are the three configurations and their practical implications for a law firm:

A comparison chart showing three configuration options for Copilot web search: Web search on (default), Recommended Middle Ground with identifier stripping, and Web search off as an isolated summarizer.

Practical recommendation

For most law firms, the right Copilot web search policy is Option 2: web search enabled with identifier stripping. It preserves the research value of the tool while ensuring that Bing cannot correlate search behavior back to your firm or a specific attorney. If you have practice groups that require stricter isolation, such as international arbitration, M&A, or regulatory investigations, consider creating a separate Azure AD group for those users and applying Option 3 to that group specifically via a scoped policy.

Copilot DLP policy: what it covers, and what it doesn't

File uploads are one of the riskiest features in Copilot Chat Basic. Any user can drag a PDF, a brief, or a contract into the chat. Plan around one limit: Microsoft Purview DLP can’t scan the contents of files uploaded directly into a prompt. It checks only the text typed into the prompt itself (Microsoft Learn).

Here’s what a DLP policy on the Microsoft 365 Copilot and Copilot Chat location can do, per the same Microsoft Learn page:

  • Block sensitive prompts. Stop Copilot from responding when a prompt contains chosen sensitive information types, such as Social Security numbers or your own client matter number types. Microsoft lists this as a preview rolling out to tenants.
  • Keep sensitive prompts off the web. Stop prompts that contain those types from going to external web search, while Copilot still answers from permitted internal sources.
  • Exclude labeled files and emails. Stop Copilot from processing files and emails that carry chosen sensitivity labels. The item can still appear in citations, but Copilot doesn’t use its content.
  • Exclude external email (preview). Keep email from outside your accepted domains out of grounding and summaries.

What to check in your DLP configuration

  • Client matter numbers. If your firm has custom sensitive information types for matter identifiers, add them to a rule on the Copilot location, not only to your SharePoint and OneDrive policies.
  • Separate rules for labels and sensitive information types. Microsoft doesn’t allow both conditions in one rule. Put them in the same policy as two rules.
  • Custom template only. The Copilot location appears only in the Custom policy template, and turning it on disables the other locations in that policy.
  • Allow time. Policy changes can take up to four hours to reach Copilot.
  • Uploads. Because DLP can’t read uploaded files, the controls for uploads are your AI policy, training, and who can reach the tool at all.

Microsoft’s licensing notes for these controls are linked from the same Learn page.

Copilot Interaction logs: your visibility layer

The audit infrastructure for Copilot is available today and most firms are not using it. Copilot Interaction logs are available through the standard Audit log search in the Microsoft Purview Compliance portal. Go to:

 
Microsoft Purview Compliance portal → Audit → Search → Activity: Copilot activities

 

The logs show who is using the tool, which apps they are using it in, and whether they are uploading files. This data is the foundation for a fact-based conversation with practice group leaders about how AI is being used in their groups, rather than on assumptions in either direction.

Where Copilot Chat Basic shows up after April 15: surface-by-surface

The table below is designed to be shared with practice group leaders and your help desk team. It covers the post-April 15 state of Copilot Chat Basic across every Microsoft 365 surface a law firm attorney is likely to encounter.

App / SurfaceCopilot Chat Basic (no paid license)M365 Copilot Premium (paid license)Admin control
Word✗ Removed Apr 15
Sidebar access ends; users redirected to standalone app
✓ Full integration
Write, summarize, format in-document
Intune / Cloud Policy (Connected Experiences)
Excel✗ Removed Apr 15✓ Full integration
Formula help, data analysis
Intune / Cloud Policy
PowerPoint✗ Removed Apr 15✓ Full integrationIntune / Cloud Policy
OneNote✗ Removed Apr 15✓ Full integrationIntune / Cloud Policy
Outlook✓ Retained
Email summarization & calendar grounding confirmed
✓ Full integrationCopilot Control System
Teams○ Configurable
App available; pinning controlled by admin
✓ Full integrationTeams App Setup Policies
Standalone Copilot app
(m365copilot.com)
✓ Available
Web + file upload; primary surface post-Apr 15
✓ AvailableIntegrated Apps (Admin Center)
Microsoft Edge sidebar○ Available
Web-grounded; same EDP protections
✓ AvailableEdge management policies

Copilot Chat Basic FAQ

Does Copilot Chat Basic read our SharePoint files?

Not on its own. Copilot Chat Basic is grounded in the web and works with content a user pastes or uploads into the chat. It doesn’t search your SharePoint libraries the way licensed Microsoft 365 Copilot does. The risk is what people paste, so pair it with a policy and DLP.

Can we limit which attorneys see Copilot Chat?

Yes. In the Microsoft 365 admin center, Integrated Apps lets you change the Copilot deployment from everyone to specific security groups. In Teams, app setup policies control who has the Copilot app pinned. Start with a pilot group, then widen access once web search, DLP, and logging settings are in place.

Final technical considerations: shape the habit before it shapes itself

The free version of Copilot should not be ignored simply because your firm has not purchased paid licenses. The tool is already in use. The governance question isn’t whether attorneys are using AI. It’s whether they’re using it within a managed boundary or outside one.

By taking control of the Copilot access control settings in Integrated Apps and configuring the right Copilot web search policy for each practice group, a firm can shape the AI habit before it becomes a shadow IT problem. A group-based rollout, a Copilot DLP policy that covers prompts and labeled content, and clear communication about the difference between web-grounded and work-grounded data are the best first steps.

Don’t let unmanaged AI become your next shadow IT headache. Talk with us about these controls, or start with the free AI Readiness Snapshot.

Recent Posts

Have Any Question?

Call or email Cocha.  We can help with your cybersecurity needs!