The problem
Staff could paste company data into the free, personal version of Copilot. Paid seats were going unused, and “Copilot” covers several products with different licensing, which made it easy to tell users something that wasn’t true.
What I did
- Blocked personal-account Copilot on work PCs with Tenant Restrictions v2 and browser policies. I piloted on IT machines first, then rolled out to office PCs after the AI use policy was approved and users were notified.
- Steered staff to work-account Copilot Chat, which comes with the existing Microsoft 365 licenses.
- Connected the internal knowledge base to Copilot with a Microsoft Graph connector, then confirmed that Copilot answers questions from it and cites the source documents.
- Found that changing the connector’s permissions after the first crawl left documents unreadable, and rebuilt it with the right permissions from the start. I also made the knowledge base’s Markdown files searchable by generating text copies automatically.
- Reviewed paid Copilot use, removed unused seats, and scheduled the subscription to shrink at renewal.
- Made it a rule to check every Copilot licensing claim against the tenant’s subscriptions and Microsoft’s current documentation before telling users.
Outcome
Work PCs steer AI use to the company’s own Microsoft 365 tenant, and Copilot can answer from our own documentation. Licenses match real use, and users get accurate answers about what they have.