Zero Trust deployment plan with Microsoft 365

This article provides a deployment plan for building Zero Trust security with Microsoft 365. Zero Trust is a new security model that assumes breach and verifies each request as though it originated from an uncontrolled network. Regardless of where the request originates or what resource it accesses, the Zero Trust model teaches us to "never trust, always verify."

Use this article together with this poster.

Item Description
Illustration of the Microsoft 365 Zero Trust deployment plan.
PDF | Visio
Updated March 2022
Related solution guides

Zero Trust security architecture

A Zero Trust approach extends throughout the entire digital estate and serves as an integrated security philosophy and end-to-end strategy.

This illustration provides a representation of the primary elements that contribute to Zero Trust.

The Zero Trust security architecture

In the illustration:

  • Security policy enforcement is at the center of a Zero Trust architecture. This includes Multi Factor authentication with conditional access that takes into account user account risk, device status, and other criteria and policies that you set.
  • Identities, devices, data, apps, network, and other infrastructure components are all configured with appropriate security. Policies that are configured for each of these components are coordinated with your overall Zero Trust strategy. For example, device policies determine the criteria for healthy devices and conditional access policies require healthy devices for access to specific apps and data.
  • Threat protection and intelligence monitors the environment, surfaces current risks, and takes automated action to remediate attacks.

For more information about Zero Trust, see Microsoft's Zero Trust Guidance Center.

Deploying Zero Trust for Microsoft 365

Microsoft 365 is built intentionally with many security and information protection capabilities to help you build Zero Trust into your environment. Many of the capabilities can be extended to protect access to other SaaS apps your organization uses and the data within these apps.

This illustration represents the work of deploying Zero Trust capabilities. This work is broken into units of work that can be configured together, starting from the bottom and working to the top to ensure that prerequisite work is complete.

The Microsoft 365 Zero Trust deployment stack

In this illustration:

  • Zero Trust begins with a foundation of identity and device protection.
  • Threat protection capabilities are built on top of this foundation to provide real-time monitoring and remediation of security threats.
  • Information protection and governance provide sophisticated controls targeted at specific types of data to protect your most valuable information and to help you comply with compliance standards, including protecting personal information.

This article assumes you have already configured cloud identity. If you need guidance for this objective, see Deploy your identity infrastructure for Microsoft 365.

Step 1. Configure Zero Trust identity and device access protection — starting-point policies

The first step is to build your Zero Trust foundation by configuring identity and device access protection.

The process to configure Zero Trust identity and device access protection

Go to Zero Trust identity and device access protection for prescriptive guidance to accomplish this. This series of articles describes a set of identity and device access prerequisite configurations and a set of Azure Active Directory (Azure AD) Conditional Access, Microsoft Intune, and other policies to secure access to Microsoft 365 for enterprise cloud apps and services, other SaaS services, and on-premises applications published with Azure AD Application Proxy.

Includes Prerequisites Doesn't include
Recommended identity and device access policies for three tiers of protection:
  • Starting point
  • Enterprise (recommended)
  • Specialized

Additional recommendations for:
  • External users (guests)
  • Microsoft Teams
  • SharePoint Online
  • Microsoft Defender for Cloud Apps
Microsoft E3 or E5

Azure Active Directory in either of these modes:
  • Cloud-only
  • Hybrid with password hash sync (PHS) authentication
  • Hybrid with pass-through authentication (PTA)
  • Federated
Device enrollment for policies that require managed devices. See Step 2. Manage endpoints with Intune to enroll devices

Start by implementing the starting-point tier. These policies do not require enrolling devices into management.

The Zero Trust identity and device access policies — starting-point tier

Step 2. Manage endpoints with Intune

Next, enroll your devices into management and begin protecting these with more sophisticated controls.

The Manage endpoints with Intune element

Go to Manage devices with Intune for prescriptive guidance to accomplish this.

Includes Prerequisites Doesn't include
Enroll devices with Intune:
  • Corporate-owned devices
  • Autopilot/automated
  • enrollment

Configure policies:
  • App Protection policies
  • Compliance policies
  • Device profile policies
Register endpoints with Azure AD Configuring information protection capabilities, including:
  • Sensitive information types
  • Labels
  • DLP policies

For these capabilities, see Step 5. Protect and govern sensitive data (later in this article).

Step 3. Add Zero Trust identity and device access protection — Enterprise policies

With devices enrolled into management, you can now implement the full set of recommended Zero Trust identity and device access policies, requiring compliant devices.

The Zero Trust identity and access policies with device management

Return to Common identity and device access policies and add the policies in the Enterprise tier.

The Zero Trust identity and access policies — Enterprise (recommended) tier

Step 4. Evaluate, pilot, and deploy Microsoft 365 Defender

Microsoft 365 Defender is an extended detection and response (XDR) solution that automatically collects, correlates, and analyzes signal, threat, and alert data from across your Microsoft 365 environment, including endpoint, email, applications, and identities.

The process of adding Microsoft 365 Defender to the Zero Trust architecture

Go to Evaluate and pilot Microsoft 365 Defender for a methodical guide to piloting and deploying Microsoft 365 Defender components.

Includes Prerequisites Doesn't include
Set up the evaluation and pilot environment for all components:
  • Defender for Identity
  • Defender for Office 365
  • Defender for Endpoint
  • Microsoft Defender for Cloud Apps

Protect against threats

Investigate and respond to threats
See the guidance to read about the architecture requirements for each component of Microsoft 365 Defender. Azure AD Identity Protection is not included in this solution guide. It is included in Step 1. Configure Zero Trust identity and device access protection.

Step 5. Protect and govern sensitive data

Implement Microsoft Purview Information Protection to help you discover, classify, and protect sensitive information wherever it lives or travels.

Microsoft Purview Information Protection capabilities are included with Microsoft Purview and give you the tools to know your data, protect your data, and prevent data loss.

The Information protection capabilities protecting data through policy enforcement

While this work is represented at the top of the deployment stack illustrated earlier in this article, you can begin this work anytime.

Microsoft Purview Information Protection provides a framework, process, and capabilities you can use to accomplish your specific business objectives.

Microsoft Purview Information Protection

For more information on how to plan and deploy information protection, see Deploy a Microsoft Purview Information Protection solution.

If you're deploying information protection for data privacy regulations, this solution guide provides a recommended framework for the entire process: Deploy information protection for data privacy regulations with Microsoft 365.