Your company discovers that several employees use personal ChatGPT accounts to assist with work tasks.

The core business concern in the scenario is data leakage —employees using consumer tools where corporate data could be pasted, stored, or processed outside the organization’s governance boundary. The key differentiator of Microsoft 365 Copilot is that it’s designed to work inside your Microsoft 365 tenant and to respect the organization’s existing security, compliance, identity, and data access controls. Therefore, D is the best answer: Copilot accesses internal work data (Microsoft Graph-connected content such as mail, files, chats, meetings) in accordance with existing Microsoft 365 policies and permissions —meaning it can only surface content the user is already allowed to access, and it operates under enterprise-grade controls (authentication, auditing, compliance boundaries, and admin governance).

Options B and C describe general generative AI capabilities that personal ChatGPT can also provide (brainstorming, drafting, rewriting). A can be done in multiple tools as well, and it is not the primary “enterprise value” difference tied to the stated risk. The scenario’s driver is governance: reducing the likelihood of proprietary data leaving controlled systems while still enabling productivity. Rolling out Copilot addresses that by providing “work-safe” AI anchored to organizational content and managed through the same tenant controls your company already uses.