A finance analyst reports that Microsoft 365 Copilot returned salary figures from a spreadsheet stored in a SharePoint site owned by the HR team, and the analyst should not have access to that file. Which action resolves the underlying exposure?
- ADisable Microsoft 365 Copilot for the finance analyst until the HR team confirms the file is safe to expose.
- BEnable a Microsoft Purview sensitivity label on the spreadsheet so Copilot stops indexing it.
- CCorrect the SharePoint permissions on the HR site so the analyst no longer has access to the spreadsheet. Correct
- DTurn off the semantic index for the finance department in the Microsoft 365 admin center.
Why A is wrong: Tempting because it appears to stop the analyst seeing the data, but Copilot only surfaced a file the analyst could already open, so turning Copilot off leaves the underlying permission intact and hides rather than fixes the exposure.
Why B is wrong: Tempting because labels do govern content, but a sensitivity label classifies and can encrypt a file rather than remove a user's existing site access, so the analyst who already has permission would still be able to open it.
Why C is correct: Correct: Copilot honours existing permissions and can only return content the user could already reach, so removing the analyst's access to the file at the SharePoint layer is what actually closes the exposure.
Why D is wrong: Tempting because the semantic index is how Copilot reasons over content, but there is no per-department switch to disable it, and the index respects permissions anyway, so this neither exists as a control nor addresses the over-permission.