Microsoft 365 is now central to how most organizations communicate, collaborate, and manage identity, making it a high-value target for attackers. A single altered conditional access policy or an over-privileged administrator account can open the door to compromise, and an unnoticed configuration change can widen its impact.
Protecting the data inside Microsoft 365 is only part of the job. Organizations also need to secure the tenant itself, which means managing how it is configured, who holds privileged access, how changes are detected, and how a known-good state is restored after an incident. Many teams still treat these as separate concerns, leaving them with limited visibility into when configurations move away from what was originally agreed and few options for fast recovery.
The rollout of Microsoft 365 Copilot and Copilot Studio agents raises the stakes. AI assistants and agents work with whatever access they inherit from existing tenant permissions and configurations. If those permissions are broader than intended, AI can make overshared or sensitive content easier to find for people who shouldn’t have access to it.
In this webinar, KuppingerCole Analyst Matthew Gardiner examines the tenant-level security and resilience challenge inside Microsoft 365 and Entra ID environments, and what it means for SaaS security strategy. Lukas Haas of CoreView then shares practical experience from working with organizations on governance, cloud visibility, and secure Microsoft 365 operations, including how CoreView approaches configuration, privilege, and recovery at the tenant level. The session closes with a live Q&A.
Matthew Gardiner will present an independent view of tenant-level risk in Microsoft 365 and Entra ID, covering configuration drift, privilege exposure, and why resilience belongs in a modern SaaS security strategy.
Lukas Haas will share practical guidance on assessing and hardening Microsoft 365 tenants, detecting configuration tampering, limiting blast radius, and recovering a trusted security posture after an incident.
Who Should Attend
CISOs, security architects, identity and access management (IAM) and Microsoft 365 administrators, and IT and cloud leaders responsible for securing and operating Microsoft 365 and Entra ID environments.
See All Locations
See All Locations