Copilot readiness for companies whose rollout is waiting on governance and legal.

Staff who use Microsoft Copilot need a paid Copilot license: Microsoft 365 Copilot, or Copilot Business for organizations with up to 300 users. Microsoft Copilot Chat is included with Microsoft 365 business and enterprise plans, so many companies start there. For the governance controls, Business Premium covers most of the data foundation, and a few controls need E5 or a Purview add-on, as the licensing table on this page shows.

Yes. Business Premium includes manual sensitivity labels with default and mandatory labeling set in label policies, DLP for email, SharePoint and OneDrive, and 180 days of audit. One paid Copilot license in the tenant turns on Restricted Content Discovery and the other SharePoint Advanced Management tools for oversharing, which we confirm in your admin center for Copilot Business. The policy, the registers and the training need no extra license. Automatic labeling and the DLP rule that keeps labeled content out of Copilot need E5 or the Purview Suite for Business Premium. Label encryption, which Business Premium includes, can also stop Copilot using a file, and we tell you which route fits before you buy anything.

No. Copilot uses only what the signed-in person can already open, although an agent built in Copilot Studio can connect to other systems with its author's credentials, so we check each agent's connections too. The bigger risk is content shared far wider than intended, such as sites opened to the whole company through broad groups. Before Copilot goes wider, we run the oversharing reports in SharePoint Advanced Management and, where your licenses include it, Purview Data Security Posture Management (DSPM), and fix the worst exposure first.

Yes. Restricted Content Discovery hides a named site from company-wide search and Copilot without changing who can open it, and people with access can still open the site and its files. It controls what people find, so the lasting fix is still the site's permissions, and Restricted Access Control can limit a site to one group. Restricted SharePoint Search, the older control, is retiring and can no longer be newly turned on.

Microsoft states that prompts, responses and the work data Copilot reads are not used to train its foundation models. Client terms usually ask for more, so discovery lists each AI clause and we map it to controls we then test: a client label whose encryption withholds the rights Copilot needs to use the content, a DLP policy that keeps that label out of Copilot where your licenses allow it, and the client's sites kept out of Copilot search. Where no setting can enforce a term, that client's data stays out of the AI workflow and the policy records the rule.

Partly. Microsoft documents no switch that stops people creating agents in Agent Builder. Admins can decide who may use agents and who may share them with the whole company, and can block or delete any agent; setting company-wide sharing to no users still lets people share with named colleagues. In Copilot Studio, makers can be routed to managed environments with sharing limits and connector rules. We pair those settings with a written rule, maker training and an agent register.

Your own staff, trained to build agents, under the rules we set up together. They build in approved workspaces with sharing rules, new agents go into the register with an owner and a review date, and your IT team approves any agent before it is shared company-wide and runs the reviews from the runbook. Run support can keep the registers current after handover, and we can build agents on the foundation as separately scoped work.

For office use, mainly AI literacy. The AI Act requires measures that support AI literacy, sized to the role and the risk, and that duty has applied since February 2025. The European Commission says no certificate is needed and suggests keeping internal records. Office use of Copilot is not a high-risk use under the Act, although AI that screens job candidates or assesses staff would be.

Copilot and the controls around it can monitor staff, so a German company with a works council needs its agreement before go-live, and German data protection authorities say a DPIA under GDPR will often be needed for AI. In the regulated track we prepare the DPIA with your data protection officer, the works council information pack and German versions of the documents, and your counsel gives the legal sign-off. Our teams in Texas and Munich cover the US and German sides of the rollout.

Most readiness assessments end with a report and a roadmap, and your team does the work afterwards. We do the hands-on work in your tenant: we fix the sharing, set up labels and DLP, write the policy and registers with your compliance lead, train each team and run the pilot. Then we hand every control to your IT team with a runbook and the acceptance tests they signed.

It can be, once a few settings are chosen on purpose. When staff sign in with their work account, Copilot Chat runs under Microsoft's enterprise data protection, and prompts are not used to train the foundation models. What needs deciding is web search, what staff may paste in and which agents they may use. Early in discovery we set those, add a DLP rule that blocks web search when a prompt matches the sensitive information types we configure, and give staff an interim AI rule.