Why does this matter before Microsoft 365 Copilot?
Copilot can find and summarise anything a user already has permission to access. If a SharePoint site full of payroll files is shared with everyone, Copilot makes that much easier to discover.
A security review before rollout fixes oversharing, tightens permissions and checks sensitivity labels, so Copilot is far less likely to surface data a person shouldn’t see. Our Copilot readiness service builds on this review with licensing, governance and adoption.
Which framework controls does this cover?
Under the shared responsibility model, the settings these frameworks care about are yours to manage, not the provider’s.
Several of the controls ASD prioritises apply directly to Microsoft 365. In ASD Essentials, sign-in and admin controls fall under the identity services domain. In the maturity model organisations are assessed against today, the relevant controls include multi-factor authentication, restricting administrative privileges, restricting Microsoft Office macros, user application hardening and regular backups. ISO/IEC 27001:2022 includes a specific control for information security in the use of cloud services (A.5.23), which an ISMS needs to consider. Each finding in your report is mapped to these frameworks, so the work counts towards your compliance goals.
Who applies the fixes?
Either we do, or your own team or Microsoft 365 provider does with our support. Changes such as enforcing MFA are planned and piloted, as the FAQ explains, and each finding carries the business risk alongside the fix so you can decide the order.
For example, a review might find a Microsoft 365 tenant where an old global admin account has no MFA and mailbox auditing is switched off. Both would be fixed as a priority, and the admin role moved to a separate, protected account.