Why? Because you can't customize the settings in preset security policies (in particular, actions that are taken on messages). Ideally, we would tell you to define your pilot users in the Standard and Strict preset security policies, but we can't do that. The terms Standard and Strict come from our recommended security settings, which are also used in preset security policies. As you create policies for the various protection features in Defender for Office 365, use these groups as conditions that define who the policy applies to. When you're ready to begin testing, add these groups as exceptions to the SCL=-1 mail flow rule.
#Office 365 migration plan free#
A pilot group for Strict anti-spam and anti-phishing policy settings: For example, MDOPilot_SpamPhish_Strictįor clarity, we use these specific group names throughout this article, but you're free to use your own naming convention.A pilot group for Standard anti-spam and anti-phishing policy settings: For example, MDOPilot_SpamPhish_Standard.A Safe Links pilot group: For example, MDOPilot_SafeLinks.A Safe Attachments pilot group: For example, MDOPilot_SafeAttachments.With this approach in mind, we recommend the following distribution groups: Using a staged approach for the protection features that are in effect for your pilot users makes troubleshooting and adjusting easier. Testing of specific Defender for Office 365 protection features: Even for the pilot users, you don't want to turn on everything at once. Eliminating the possibility of filtering by your existing protection service and relying exclusively on Defender for Office 365 is the best and closest representation of what's going to happen after your migration is complete. You get this result by defining your pilot users in the appropriate distribution groups in Microsoft 365, and configuring these groups as exceptions to the SCL=-1 mail flow rule.Īs we described in Onboard Step 2: (Optional) Exempt pilot users from filtering by your existing protection service, you should consider exempting these same pilot users from scanning by your existing protection service.
#Office 365 migration plan full#
Step 1: Create distribution groups for pilot usersĭistribution groups are required in Microsoft 365 for the following aspects of your migration:Įxceptions for the SCL=-1 mail flow rule: You want pilot users to get the full effect of Defender for Office 365 protection, so you need Defender for Office 365 to scan their incoming messages.
Create distribution groups for pilot users.Welcome to Phase 2: Setup of your migration to Microsoft Defender for Office 365! This migration phase includes the following steps:
0 kommentar(er)
