Skip to content

Commit 8ba8b27

Browse files
Shawn Dyasampcode-com
andcommitted
Initial commit: Restructure Microsoft 365 security docs into separate docsets
- Organized content into 7 separate docsets with dedicated base URLs - Created docfx.json configurations for each docset - Added OpenPublishing configuration for all docsets - Cleaned up unreferenced media files Amp-Thread: https://ampcode.com/threads/T-1723d56b-b736-4840-88ff-b3462b61e264 Co-authored-by: Amp <[email protected]>
1 parent e214cce commit 8ba8b27

9 files changed

Lines changed: 889 additions & 0 deletions

AGENT.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
# Microsoft 365 Documentation Repository
2+
3+
## Build/Test Commands
4+
- Build: `powershell .\.openpublishing.build.ps1`
5+
- No automated tests - content validation via OpenPublishing platform
6+
- Validate links and content structure via DocFX locally (install DocFX and run `docfx serve` in subdirectories)
7+
8+
## Architecture & Structure
9+
- **microsoft-365/**: Main Microsoft 365 documentation (admin, business, enterprise, security, etc.)
10+
- **copilot/**: Microsoft 365 Copilot documentation
11+
- **defender/**: Microsoft Defender Threat Intelligence documentation
12+
- **security-insights/**: Security insights documentation
13+
- Uses Microsoft OpenPublishing platform with DocFX for documentation generation
14+
- Content organized by product area with separate docfx.json configs for each docset
15+
16+
## Content Guidelines
17+
- **Format**: Markdown (.md) files with YAML frontmatter containing metadata
18+
- **Metadata required**: title, author, ms.author, manager, ms.date, audience, ms.topic, ms.service
19+
- **Links**: Use relative paths for internal content, absolute for external
20+
- **Images**: Store in /media/ subdirectories, reference with relative paths
21+
- **Style**: Follow Microsoft Learn style guide for technical documentation
22+
- **File naming**: Use lowercase with hyphens (kebab-case)
23+
- **Redirects**: Managed via .openpublishing.redirection.*.json files for each service area

microsoft-365/security/defender/active-content-in-trusted-docs.md

Lines changed: 166 additions & 0 deletions
Large diffs are not rendered by default.
Lines changed: 153 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,153 @@
1+
---
2+
title: "Zero Trust deployment plan with Microsoft 365"
3+
f1.keywords:
4+
- deploy zero trust
5+
- zero trust strategy
6+
ms.author: bcarter
7+
author: brendacarter
8+
manager: dansimp
9+
audience: Admin
10+
description: Learn how to apply Zero Trust security principles with Microsoft 365 to defend against threats and protect sensitive data.
11+
ms.topic: tutorial
12+
ms.service: microsoft-365-zero-trust
13+
ms.localizationpriority: medium
14+
search.appverid:
15+
- MET150
16+
ms.collection:
17+
- m365solution-zerotrust
18+
- m365solution-overview
19+
- m365-security
20+
- zerotrust-solution
21+
- highpri
22+
- tier1
23+
ms.date: 1/31/2023
24+
---
25+
26+
# Zero Trust deployment plan with Microsoft 365
27+
28+
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."
29+
30+
Use this article together with this poster.
31+
32+
| Item | Description |
33+
|:-----|:-----|
34+
|[![Illustration of the Microsoft 365 Zero Trust deployment plan.](../media/solutions-architecture-center/m365-zero-trust-deployment-plan-thumb.png)](https://download.microsoft.com/download/f/d/b/fdb6ab0c-34bb-4cb8-84e6-5de8f13298da/m365-zero-trust-deployment-plan.pdf) <br/> [PDF](https://download.microsoft.com/download/f/d/b/fdb6ab0c-34bb-4cb8-84e6-5de8f13298da/m365-zero-trust-deployment-plan.pdf) \| [Visio](https://download.microsoft.com/download/f/d/b/fdb6ab0c-34bb-4cb8-84e6-5de8f13298da/m365-zero-trust-deployment-plan.vsdx) <br/> Updated February 2023 | **Related solution guides** <br/> <ul><li>[Deploy your identity infrastructure for Microsoft 365](/microsoft-365/enterprise/deploy-identity-solution-overview)</li><li>[Recommended identity and device access configurations](../security/office-365-security/zero-trust-identity-device-access-policies-overview.md)</li><li>[Manage devices with Intune](../solutions/manage-devices-with-intune-overview.md)</li><li>[Evaluate and pilot Microsoft Defender XDR](../security/defender/eval-overview.md)</li><li>[Deploy an information protection solution with Microsoft Purview](../compliance/information-protection-solution.md)</li><li>[Deploy information protection for data privacy regulations with Microsoft 365](../solutions/information-protection-deploy.md)</li></ul>
35+
36+
## Zero Trust security architecture
37+
38+
A Zero Trust approach extends throughout the entire digital estate and serves as an integrated security philosophy and end-to-end strategy.
39+
40+
This illustration provides a representation of the primary elements that contribute to Zero Trust.
41+
42+
:::image type="content" source="../media/zero-trust/zero-trust-architecture.png" alt-text="The Zero Trust security architecture" lightbox="../media/zero-trust/zero-trust-architecture.png":::
43+
44+
In the illustration:
45+
46+
- 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.
47+
- 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.
48+
- Threat protection and intelligence monitors the environment, surfaces current risks, and takes automated action to remediate attacks.
49+
50+
For more information about Zero Trust, see Microsoft's [_**Zero Trust Guidance Center**_](/security/zero-trust).
51+
52+
<!---
53+
For more information about this architecture, including deployment objectives for your entire digital estate, see [Zero Trust Rapid Modernization Plan (RaMP)](/security/zero-trust/zero-trust-ramp-overview).
54+
-->
55+
56+
## Deploying Zero Trust for Microsoft 365
57+
58+
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.
59+
60+
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.
61+
62+
:::image type="content" source="../media/zero-trust/m365-zero-trust-deployment-stack.png" alt-text="The Microsoft 365 Zero Trust deployment stack" lightbox="../media/zero-trust/m365-zero-trust-deployment-stack.png":::
63+
64+
In this illustration:
65+
66+
- Zero Trust begins with a foundation of identity and device protection.
67+
- Threat protection capabilities are built on top of this foundation to provide real-time monitoring and remediation of security threats.
68+
- 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.
69+
70+
This article assumes you have already configured cloud identity. If you need guidance for this objective, see [**Deploy your identity infrastructure for Microsoft 365**](/microsoft-365/enterprise/deploy-identity-solution-overview).
71+
72+
73+
> [!TIP]
74+
> When you understand the steps and the end-to-end deployment process, you can use the [Set up your Microsoft Zero Trust security model](https://go.microsoft.com/fwlink/?linkid=2224820) advanced deployment guide when signed in to the Microsoft 365 admin center. This guide steps you through applying Zero Trust principles for standard and advanced technology pillars. To step through the guide without signing in, go to the [Microsoft 365 Setup portal](https://go.microsoft.com/fwlink/?linkid=2222968).
75+
76+
## Step 1: Configure Zero Trust identity and device access protection — starting-point policies
77+
78+
The first step is to build your Zero Trust foundation by configuring identity and device access protection.
79+
80+
:::image type="content" source="../media/zero-trust/m365-zero-trust-architecture-identities.png" alt-text="Diagram that shows the process to configure Zero Trust identity and device access protection." lightbox="../media/zero-trust/m365-zero-trust-architecture-identities.png":::
81+
82+
Go to [**_Zero Trust identity and device access protection_**](office-365-security/zero-trust-identity-device-access-policies-overview.md) for prescriptive guidance to accomplish this. This series of articles describes a set of identity and device access prerequisite configurations and a set of Microsoft Entra 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 Microsoft Entra application proxy.
83+
84+
|Includes|Prerequisites|Doesn't include|
85+
|---------|---------|---------|
86+
|Recommended identity and device access policies for three levels of protection: <ul><li>Starting point</li><li>Enterprise (recommended)</li><li>Specialized</li></ul> <br> Additional recommendations for: <ul><li>External users (guests)</li><li>Microsoft Teams</li><li>SharePoint Online</li><li>Microsoft Defender for Cloud Apps</lu></ul>|Microsoft E3 or E5 <br><br> Microsoft Entra ID in either of these modes: <ul><li>Cloud-only</li><li>Hybrid with password hash sync (PHS) authentication</li><li>Hybrid with pass-through authentication (PTA)</li><li>Federated</li></ul>|Device enrollment for policies that require managed devices. See [Step 2. Manage endpoints with Intune](#step-2-manage-endpoints-with-intune) to enroll devices|
87+
88+
Start by implementing the starting-point tier. These policies do not require enrolling devices into management.
89+
90+
:::image type="content" source="../media/zero-trust/identity-access-starting-point-tier.png" alt-text="The Zero Trust identity and device access policies — starting-point tier" lightbox="../media/zero-trust/identity-access-starting-point-tier.png":::
91+
92+
## Step 2: Manage endpoints with Intune
93+
94+
Next, enroll your devices into management and begin protecting these with more sophisticated controls.
95+
96+
:::image type="content" source="../media/zero-trust/m365-zero-trust-architecture-endpoints.png" alt-text="Diagram that shows the Manage endpoints with Intune element." lightbox="../media/zero-trust/m365-zero-trust-architecture-endpoints.png":::
97+
98+
Go to [**_Manage devices with Intune_**](../solutions/manage-devices-with-intune-overview.md) for prescriptive guidance to accomplish this.
99+
100+
|Includes|Prerequisites|Doesn't include|
101+
|---------|---------|---------|
102+
|Enroll devices with Intune: <ul><li>Corporate-owned devices</li><li>Autopilot/automated</li><li>enrollment</li></ul> <br> Configure policies: <ul><li>App Protection policies</li><li>Compliance policies</li><li>Device profile policies</li></ul>|Register endpoints with Microsoft Entra ID|Configuring information protection capabilities, including: <ul><li>Sensitive information types</li><li>Labels</li><li>DLP policies</li></ul> <br> For these capabilities, see [Step 5. Protect and govern sensitive data](#step-5-protect-and-govern-sensitive-data) (later in this article).|
103+
104+
For more information, see [Zero Trust for Microsoft Intune](/mem/intune/fundamentals/zero-trust-with-microsoft-intune).
105+
106+
## Step 3: Add Zero Trust identity and device access protection — Enterprise policies
107+
108+
With devices enrolled into management, you can now implement the full set of recommended Zero Trust identity and device access policies, requiring compliant devices.
109+
110+
:::image type="content" source="../media/zero-trust/m365-zero-trust-architecture-enterprise-policies.png" alt-text="The Zero Trust identity and access policies with device management" lightbox="../media/zero-trust/m365-zero-trust-architecture-enterprise-policies.png":::
111+
112+
Return to [**_Common identity and device access policies_**](office-365-security/zero-trust-identity-device-access-policies-common.md) and add the policies in the Enterprise tier.
113+
114+
:::image type="content" source="../media/zero-trust/identity-access-enterprise-tier.png" alt-text="The Zero Trust identity and access policies — Enterprise (recommended) tier" lightbox="../media/zero-trust/identity-access-enterprise-tier.png":::
115+
116+
<a name='step-4-evaluate-pilot-and-deploy-microsoft-365-defender'></a>
117+
118+
## Step 4: Evaluate, pilot, and deploy Microsoft Defender XDR
119+
120+
Microsoft Defender XDR 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.
121+
122+
:::image type="content" source="../media/zero-trust/m365-zero-trust-architecture-defender.png" alt-text="The process of adding Microsoft Defender XDR to the Zero Trust architecture" lightbox="../media/zero-trust/m365-zero-trust-architecture-defender.png":::
123+
124+
Go to [**_Evaluate and pilot Microsoft Defender XDR_**](defender/eval-overview.md) for a methodical guide to piloting and deploying Microsoft Defender XDR components.
125+
126+
|Includes|Prerequisites|Doesn't include|
127+
|---------|---------|---------|
128+
|Set up the evaluation and pilot environment for all components: <ul><li>Defender for Identity</li><li>Defender for Office 365</li><li>Defender for Endpoint</li><li>Microsoft Defender for Cloud Apps</li></ul> <br> Protect against threats <br><br> Investigate and respond to threats|See the guidance to read about the architecture requirements for each component of Microsoft Defender XDR.| Microsoft Entra ID Protection is not included in this solution guide. It is included in [Step 1. Configure Zero Trust identity and device access protection](#step-1-configure-zero-trust-identity-and-device-access-protection--starting-point-policies).|
129+
130+
For more information, see these additional Zero Trust articles:
131+
132+
- [Defender for Endpoint](./defender-endpoint/zero-trust-with-microsoft-defender-endpoint.md)
133+
- [Defender for Office 365](./office-365-security/zero-trust-with-microsoft-365-defender-office-365.md)
134+
- [Defender for Cloud Apps](/defender-cloud-apps/zero-trust)
135+
- [Defender for Identity](/defender-for-identity/zero-trust)
136+
137+
## Step 5: Protect and govern sensitive data
138+
139+
Implement Microsoft Purview Information Protection to help you discover, classify, and protect sensitive information wherever it lives or travels.
140+
141+
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.
142+
143+
:::image type="content" source="../media/zero-trust/m365-zero-trust-architecture-info-protect.png" alt-text="The Information protection capabilities protecting data through policy enforcement" lightbox="../media/zero-trust/m365-zero-trust-architecture-info-protect.png":::
144+
145+
While this work is represented at the top of the deployment stack illustrated earlier in this article, you can begin this work anytime.
146+
147+
Microsoft Purview Information Protection provides a framework, process, and capabilities you can use to accomplish your specific business objectives.
148+
149+
![Microsoft Purview Information Protection](../media/zero-trust/mip-solution-overview.png)
150+
151+
For more information on how to plan and deploy information protection, see [**_Deploy a Microsoft Purview Information Protection solution_**](../compliance/information-protection-solution.md).
152+
153+
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_**](../solutions/information-protection-deploy.md).

0 commit comments

Comments
 (0)