| Category | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| backup | Backup View Edit Policies | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/backup/backup-view-edit-policies.md | Follow these steps to set up a backup policy for Exchange mailboxes sites using  -6. On the **Choose selection method** page, you can set up Exchange mailboxes using any or all three ways. A protection scope is the scope of mailboxes within Exchange that you want to protect with Microsoft 365 Backup. +6. On the **Choose selection method** page, you can set up shared or user Exchange mailboxes using any or all three ways. A protection scope is the scope of mailboxes within Exchange that you want to protect with Microsoft 365 Backup.  Follow these steps to view and edit backup policies for Exchange. 3. You can either add new user mailboxes to or remove user mailboxes from the existing Exchange backup policy. - a. To add new user mailboxes, select **+ Add user mailboxes**. + a. To add new shared or user mailboxes, select **+ Add user mailboxes**.  |
| commerce | Manage Billing Notifications | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/commerce/billing-and-payments/manage-billing-notifications.md | You can change who receives billing notifications for your organization in the M ### If you have an MCA billing account type -If you have an MCA billing account type, billing notification emails are sent to the primary and alternate email addresses for users who are assigned one of the following roles: +If you have an MCA billing account type, billing notification emails are sent to the primary email addresses for users who are assigned one of the following roles: - Billing profile owner - Billing profile contributor To change the billing profile roles assigned to users, see [Assign billing profi To learn more about billing profile roles and how to manage them, see [Understand Microsoft Customer Agreement administrative roles in Azure](/azure/cost-management-billing/manage/understand-mca-roles). +#### Add additional recipients ++In case your primary email address isn't configured to receive emails, or if you want to receive the notifications at different email addresses, you can add them by using the following steps. ++1. In the admin center, go to the **Billing** > <a href="https://go.microsoft.com/fwlink/p/?linkid=2102895" target="_blank">Billing accounts</a> page. +2. Select the Billing account that includes the Billing profile that you want to add email recipients to. +3. Select the **Billing profiles** tab. +4. Select the Billing profile that you want to update. +5. In the **Invoice and billing notifications** - **Additional recipients** section, select **Edit recipients**. +6. In the **Additional recipients (optional)** text box, enter an email address that you want to add. +7. A box with the email address that you just entered appears. Select the box. +8. Repeat steps 6 and 7 for all the email addresses that you want to add. +9. Select **Save Changes**. + ### If you have an MOSA billing account type If you have an MOSA billing account type, billing notifications are sent to the primary and alternate email address of every Global and Billing admin in your organization. To change which users have the Global or Billing admin role, use the following steps. |
| enterprise | Contoso Case Study | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/contoso-case-study.md | f1.keywords: - NOCSH Previously updated : 04/12/2024 Last updated : 09/06/2024 audience: ITPro description: How a fictional but representative global organization adopted Micr # Microsoft 365 for enterprise for the Contoso Corporation -Microsoft 365 for enterprise is the Microsoft premier cloud offering that combines local and cloud-based productivity apps and services with Windows 10 Enterprise and advanced security features. It's a complete, intelligent solution that enables everyone to work together creatively and securely. +Microsoft 365 for enterprise is the Microsoft premier cloud offering that combines local and cloud-based productivity apps and services with Windows 11 Enterprise and advanced security features. It's a complete, intelligent solution that enables everyone to work together creatively and securely. -Contoso Corporation is a fictional but representative global manufacturing conglomerate with its headquarters in Paris. The company deployed Microsoft 365 for enterprise and addressed major design decisions and implementation details for networking, identity, Windows 10 Enterprise, Microsoft 365 Apps for enterprise, mobile device management, information protection, and security. +Contoso Corporation is a fictional but representative global manufacturing conglomerate with its headquarters in Paris. The company deployed Microsoft 365 for enterprise and addressed major design decisions and implementation details for networking, identity, Windows 11 Enterprise, Microsoft 365 Apps for enterprise, mobile device management, information protection, and security. The company's overall goal for Microsoft 365 for enterprise is to accelerate its digital transformation by using cloud services to bring together its employees, partners, data, and processes to create customer value and maintain its competitive advantage in a digital-first world. See these articles for the details: The Contoso identity-in-the-cloud solution leverages the company's on-premises Active Directory Domain Services (AD DS) forest. It includes federated authentication with their existing trusted, third-party identity providers. -- [Windows 10 Enterprise](contoso-win10.md)+- [Windows 11 Enterprise](contoso-win10.md) - The Contoso infrastructure for Windows 10 Enterprise deploys and automatically installs updates for devices that are running the company's primary PC and device operating system. + The Contoso infrastructure for Windows 11 Enterprise deploys and automatically installs updates for devices that are running the company's primary PC and device operating system. - [Microsoft 365 Apps for enterprise](contoso-o365pp.md) Learn [about the Contoso Corporation](contoso-overview.md) and the design consid ## See also [Microsoft 365 for enterprise overview](microsoft-365-overview.md)--[Test lab guides](m365-enterprise-test-lab-guides.md) |
| enterprise | Contoso Identity | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/contoso-identity.md | f1.keywords: - NOCSH Previously updated : 07/01/2024 Last updated : 09/06/2024 audience: ITPro Here's the resulting set of Contoso identity and device Conditional Access polic ## Next step -Learn how Contoso uses its Microsoft Endpoint Configuration Manager infrastructure to [deploy and keep current Windows 10 Enterprise](contoso-win10.md) across its organization. +Learn how Contoso uses its Microsoft Endpoint Configuration Manager infrastructure to [deploy and keep current Windows 11 Enterprise](contoso-win10.md) across its organization. ## See also |
| enterprise | Contoso Info Protect | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/contoso-info-protect.md | f1.keywords: - NOCSH Previously updated : 10/02/2019 Last updated : 09/06/2024 audience: ITPro +- must-keep description: Understand how Contoso uses the information protection features in Microsoft 365 for enterprise to secure their digital assets in the cloud. These policies ensure that: The following table maps Contoso data levels to information protection features in Microsoft 365 for enterprise. -| Level | Microsoft 365 cloud services | Windows 10 and Microsoft 365 Apps for enterprise | Security and compliance | +| Level | Microsoft 365 cloud services | Windows 11 and Microsoft 365 Apps for enterprise | Security and compliance | |:-|:--|:--|:--| | Level 1: Baseline | SharePoint and Exchange Online Conditional Access policies <BR> Permissions on SharePoint sites | Sensitivity labels <BR> BitLocker <BR> Windows Information Protection | Device Conditional Access policies and Mobile Application Management policies | | Level 2: Sensitive | Level 1 plus: <BR> <BR> Sensitivity labels <BR> Microsoft 365 retention labels on SharePoint sites <BR> Data Loss Prevention for SharePoint and Exchange Online <BR> Isolated SharePoint sites | Level 1 plus: <BR> <BR> Sensitivity labels on digital assets | Level 1 | Learn how Contoso uses the [security features across Microsoft 365 for enterpris [Microsoft Defender for Office 365](/microsoft-365/security/office-365-security/defender-for-office-365) [Microsoft 365 for enterprise overview](microsoft-365-overview.md)--[Test lab guides](m365-enterprise-test-lab-guides.md) |
| enterprise | Contoso Infra Needs | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/contoso-infra-needs.md | f1.keywords: - NOCSH Previously updated : 05/17/2024 Last updated : 09/06/2024 audience: ITPro The Contoso IT department determined the following mapping of business needs to | Compliance | | | | | Adhere to regional regulatory requirements | GDPR features in Microsoft 365 | | Management | | |-| | Lower IT overhead for installing client updates | Windows 10 Enterprise updates <br> Microsoft 365 Apps for enterprise updates | +| | Lower IT overhead for installing client updates | Windows 11 Enterprise updates <br> Microsoft 365 Apps for enterprise updates | |||| ## Next step Learn about the Contoso Corporation [on-premises network](contoso-networking.md) ## See also [Microsoft 365 for enterprise overview](microsoft-365-overview.md)--[Test lab guides](m365-enterprise-test-lab-guides.md) |
| enterprise | Contoso Mdm | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/contoso-mdm.md | f1.keywords: - NOCSH Previously updated : 08/01/2024 Last updated : 09/06/2024 audience: ITPro This is how Contoso set up their mobile device management infrastructure: - Device encryption to help prevent unauthorized access. - A six-digit PIN or password. - An inactivity-timeout period.- - Antivirus and malware protection, and signature updates with Windows Defender on Windows 10 devices. - - Automatic updates on Windows 10 devices that include the latest security updates. + - Antivirus and malware protection, and signature updates with Windows Defender on Windows 11 devices. + - Automatic updates on Windows 11 devices that include the latest security updates. - Pushing certificates to managed devices. - A clear separation of business and personal data. Users or admins can selectively wipe corporate data from the device, while leaving personal data such as pictures, personal email accounts, and personal files untouched. Learn how Contoso uses the [information protection capabilities](contoso-info-pr [Device management for Microsoft 365](device-management-roadmap-microsoft-365.md) [Microsoft 365 for enterprise overview](microsoft-365-overview.md)--[Test lab guides](m365-enterprise-test-lab-guides.md) |
| enterprise | Contoso Networking | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/contoso-networking.md | f1.keywords: - NOCSH Previously updated : 07/29/2024 Last updated : 09/06/2024 audience: ITPro Learn how Contoso is [leveraging its on-premises Active Directory Domain Service [Networking roadmap for Microsoft 365](networking-roadmap-microsoft-365.md) -[Microsoft 365 for enterprise overview](microsoft-365-overview.md) +[Microsoft 365 network connectivity principles](microsoft-365-network-connectivity-principles.md) -[Test lab guides](m365-enterprise-test-lab-guides.md) +[Microsoft 365 for enterprise overview](microsoft-365-overview.md) |
| enterprise | Contoso O365pp | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/contoso-o365pp.md | f1.keywords: - NOCSH Previously updated : 09/13/2018 Last updated : 09/06/2024 audience: ITPro +- must-keep description: Understand how Contoso uses Microsoft Endpoint Configuration Manager to deploy Microsoft 365 Apps for enterprise. description: Understand how Contoso uses Microsoft Endpoint Configuration Manage # Microsoft 365 Apps for enterprise deployment for Contoso -Contoso upgraded their PCs to Windows 10 Enterprise and Microsoft 365 Apps for enterprise to enable more effective collaboration, better security, and a more modern desktop experience. After they assessed their infrastructure and business needs, Contoso identified these key requirements for the deployment: +Contoso upgraded their PCs to Windows 11 Enterprise and Microsoft 365 Apps for enterprise to enable more effective collaboration, better security, and a more modern desktop experience. After they assessed their infrastructure and business needs, Contoso identified these key requirements for the deployment: - All PCs should run Microsoft 365 Apps for enterprise. - Deployment should use existing management tools and infrastructure when possible. Contoso upgraded their PCs to Windows 10 Enterprise and Microsoft 365 Apps for e ## Deployment tools -Based on their requirements, Contoso chose to deploy Windows 10 Enterprise and Microsoft 365 Apps for enterprise through Configuration Manager (Current Branch). Configuration Manager scales for large environments and provides extensive control over installation, updates, and settings. It also has built-in features to make it easier and more efficient to deploy and manage Office, including: +Based on their requirements, Contoso chose to deploy Windows 11 Enterprise and Microsoft 365 Apps for enterprise through Configuration Manager (Current Branch). Configuration Manager scales for large environments and provides extensive control over installation, updates, and settings. It also has built-in features to make it easier and more efficient to deploy and manage Office, including: - Peer cache, which can help with limited network capacity when deploying to devices in remote locations. - The Office Client Management dashboard, which makes it easy to deploy Office and monitor updates and gives administrators access to the latest deployment and management features. Because the Semi-Annual Enterprise Channel (Preview) releases a version of Micro To complete the deployment of Office, Contoso implemented the following process, which includes best practice recommendations from Microsoft: 1. Before deployment, Contoso used the Readiness Toolkit for Office Add-in and VBA to test their apps and Office Add-ins to assess their compatibility with Microsoft 365 Apps for enterprise.-1. In Configuration Manager, they enabled peer cache on their client devices, which helps with limited network capacity when deploying to client devices in remote locations. -1. Contoso defined two deployment groups as device collections in Configuration +1. In Configuration Manager, they enabled peer cache on their client devices, which helps with limited network capacity when deploying to client devices in remote locations. +1. Contoso defined two deployment groups as device collections in Configuration 1. They created deployment packages for Office by using the Office Client Management dashboard and the Office 365 Installer wizard, which are both part of the Configuration Manager console. They built two Microsoft 365 Apps for enterprise packages, one for the pilot group on the Semi-Annual Enterprise Channel (Preview) and one for the broad group on the Semi-Annual Enterprise Channel.-2. Each Office package included English, French, and German Language packs. If a device required a language that wasn't included in the Office package, that language pack was automatically downloaded from the Office Content Delivery Network (CDN). -3. They used the built-in feature in the Office package to automatically remove all existing MSI versions of Office before installing Microsoft 365 Apps for enterprise. -4. In Configuration Manager, they deployed the Windows and Office packages to distribution points across their network. Then they ran the Configuration Manager deployment task sequences to deploy the pilot Microsoft 365 Apps for enterprise package to the pilot group. -5. After they addressed compatibility issues with the pilot group, Contoso ran the task sequences to deploy the Microsoft 365 Apps for enterprise package to the broad group. +1. Each Office package included English, French, and German Language packs. If a device required a language that wasn't included in the Office package, that language pack was automatically downloaded from the Office Content Delivery Network (CDN). +1. They used the built-in feature in the Office package to automatically remove all existing MSI versions of Office before installing Microsoft 365 Apps for enterprise. +1. In Configuration Manager, they deployed the Windows and Office packages to distribution points across their network. Then they ran the Configuration Manager deployment task sequences to deploy the pilot Microsoft 365 Apps for enterprise package to the pilot group. +1. After they addressed compatibility issues with the pilot group, Contoso ran the task sequences to deploy the Microsoft 365 Apps for enterprise package to the broad group. Because Contoso chose to automatically update devices from the cloud, there was no need to manage the process in Configuration Manager. Their devices are automatically updated directly from the cloud-based on the update channel that was defined in the initial deployment. Here is the Contoso Microsoft 365 Apps for enterprise installation and ongoing updates deployment architecture. - + ## Next step Learn how Contoso is [using Microsoft Intune](contoso-mdm.md) in Microsoft 365 for enterprise to manage its devices and the apps that they run across the organization. Learn how Contoso is [using Microsoft Intune](contoso-mdm.md) in Microsoft 365 f [Microsoft 365 Apps for enterprise](/deployoffice/deployment-guide-microsoft-365-apps) [Microsoft 365 for enterprise overview](microsoft-365-overview.md)--[Test lab guides](m365-enterprise-test-lab-guides.md) |
| enterprise | Contoso Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/contoso-overview.md | f1.keywords: - NOCSH Previously updated : 12/19/2023 Last updated : 09/06/2024 audience: ITPro Learn about the Contoso Corporation [on-premises IT infrastructure](contoso-infr ## See also [Microsoft 365 for enterprise overview](microsoft-365-overview.md)--[Test lab guides](m365-enterprise-test-lab-guides.md) |
| enterprise | Contoso Security Summary | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/contoso-security-summary.md | f1.keywords: - NOCSH Previously updated : 07/30/2024 Last updated : 09/06/2024 audience: ITPro To follow security best practices and Microsoft 365 for enterprise deployment re - Windows Hello for Business - Contoso deployed [Windows Hello for Business](/windows/security/identity-protection/hello-for-business/hello-identity-verification) to eventually eliminate the need for passwords through strong two-factor authentication on PCs and mobile devices running Windows 10 Enterprise. + Contoso deployed [Windows Hello for Business](/windows/security/identity-protection/hello-for-business/hello-identity-verification) to eventually eliminate the need for passwords through strong two-factor authentication on PCs and mobile devices running Windows 11 Enterprise. - Windows Defender Credential Guard To follow security best practices and Microsoft 365 for enterprise deployment re - Protection from malware with Microsoft Defender Antivirus - Contoso is using [Microsoft Defender Antivirus](/windows/security/threat-protection/windows-defender-antivirus/windows-defender-antivirus-in-windows-10) for malware protection and anti-malware management for PCs and devices running Windows 10 Enterprise. + Contoso is using [Microsoft Defender Antivirus](/windows/security/threat-protection/windows-defender-antivirus/windows-defender-antivirus-in-windows-10) for malware protection and anti-malware management for PCs and devices running Windows 11 Enterprise. - Secure email flow and mailbox audit logging with Microsoft Defender for Office 365 To follow security best practices and Microsoft 365 for enterprise deployment re - Central security dashboard for users with Windows Defender Security Center - Contoso deployed the [Windows Security app](/windows/security/threat-protection/windows-defender-security-center/windows-defender-security-center) to its PCs and devices running Windows 10 Enterprise so that users can see their security posture at a glance and take action. + Contoso deployed the [Windows Security app](/windows/security/threat-protection/windows-defender-security-center/windows-defender-security-center) to its PCs and devices running Windows 11 Enterprise so that users can see their security posture at a glance and take action. |
| enterprise | Contoso Win10 | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/contoso-win10.md | Title: "Windows 10 Enterprise deployment for Contoso" + Title: "Windows 11 Enterprise deployment for Contoso" f1.keywords: - NOCSH Previously updated : 09/13/2018 Last updated : 09/06/2024 audience: ITPro +- must-keep -description: Understand how Contoso used Microsoft Endpoint Configuration Manager to deploy in-place upgrades for Windows 10 Enterprise. +description: Understand how Contoso used Microsoft Endpoint Configuration Manager to deploy in-place upgrades for Windows 11 Enterprise. -# Windows 10 Enterprise deployment for Contoso +# Windows 11 Enterprise deployment for Contoso -Prior to the wide rollout of Microsoft 365 for enterprise, Contoso had Windows-compatible PCs and devices running a mixture of Windows 7 (10%), Windows 8.1 (65%), and Windows 10 (25%). Contoso wanted to upgrade their PCs for Windows 10 Enterprise take advantage of advanced security and lowered IT overhead from automated deployments of updates. +Prior to the wide rollout of Microsoft 365 for enterprise, Contoso had Windows-compatible PCs and devices running a mixture of Windows 8.1 (10%), Windows 10 (65%), and Windows 11 (25%). Contoso wanted to upgrade their PCs for Windows 11 Enterprise take advantage of advanced security and lowered IT overhead from automated deployments of updates. After assessing their infrastructure and business needs, Contoso identified these key requirements for the deployment: -- As many PCs and devices as possible should run Windows 10 Enterprise+- As many PCs and devices as possible should run Windows 11 Enterprise - Rollout of the in-place upgrades leverages existing Configuration Manager infrastructure-- Control over which versions of Windows 10 Enterprise to deploy and updates are done through rings+- Control over which versions of Windows 11 Enterprise to deploy and updates are done through rings - PCs and devices should stay up to date with minimal IT administrative costs and with minimal impact to end-users -Up to date is defined as the supported version of Windows 10 Enterprise that meets ContosoΓÇÖs business needs, which can be different from having all Windows-compatible PCs running the latest version of Windows 10 Enterprise. +Up to date is defined as the supported version of Windows 11 Enterprise that meets ContosoΓÇÖs business needs, which can be different from having all Windows-compatible PCs running the latest version of Windows 11 Enterprise. ## Deployment tools -Prior to and during in-place upgrades of Windows 10 Enterprise, Contoso used the following solutions of Windows Analytics: +Prior to and during in-place upgrades of Windows 11 Enterprise, Contoso used the following solutions of Windows Analytics: - Upgrade Readiness Prior to and during in-place upgrades of Windows 10 Enterprise, Contoso used the - Device Health Identifies devices that crash frequently, and therefore might need to be rebuilt or replaced and device drivers that are causing device crashes, with suggestions of alternative versions of those drivers that might reduce the number of crashes. Provides notification of Windows Information Protection misconfigurations that send prompts to end users.- -Contoso has an existing Configuration Manager (Current Branch) infrastructure. Configuration Manager scales for large environments and provides extensive control over installation, updates, and settings. It also has built-in features to make it easier and more efficient to deploy and manage Windows 10 Enterprise. ++Contoso has an existing Configuration Manager (Current Branch) infrastructure. Configuration Manager scales for large environments and provides extensive control over installation, updates, and settings. It also has built-in features to make it easier and more efficient to deploy and manage Windows 11 Enterprise. ## Planning process -Contoso used the Upgrade Readiness in Windows Analytics to determine the set of installed apps and their compatibility with Windows 10 Enterprise. +Contoso used the Upgrade Readiness in Windows Analytics to determine the set of installed apps and their compatibility with Windows 11 Enterprise. ## Deployment process -To complete the in-place upgrade deployment of Windows 10 Enterprise, Contoso implemented the following process, which includes best practice recommendations from Microsoft: +To complete the in-place upgrade deployment of Windows 11 Enterprise, Contoso implemented the following process, which includes best practice recommendations from Microsoft: 1. Enabled peer cache for Configuration Manager. 2. Created customized Windows packages based on images from the Volume Licensing Service Center. 3. Used Configuration Manager to deploy the Windows packages to distribution points across their network and deployed builds to the three validation and deployment staging groups. 4. Performed assessment of success for PCs and devices in the three validation and deployment staging rings using the Device Health and Update Compliance solutions of Windows Analytics.-5. Based on the Windows Analytics information, Contoso determined the version of Windows 10 Enterprise to deploy to the broad deployment group. +5. Based on the Windows Analytics information, Contoso determined the version of Windows 11 Enterprise to deploy to the broad deployment group. 6. Ran the Configuration Manager deployment task sequences to deploy the selected Windows package to the broad deployment group. 7. Monitored PCs and devices in the broad deployment group using the Device Health and Update Compliance solutions to address issues. Here is ContosoΓÇÖs in-place upgrade and ongoing updates deployment architecture. - + This infrastructure consists of: - Configuration Manager, which:- - Obtains images for Windows 10 Enterprise packages from the Microsoft Volume Licensing Center in the Microsoft Network. + - Obtains images for Windows 11 Enterprise packages from the Microsoft Volume Licensing Center in the Microsoft Network. - Is the central administration point for deployment packages. - Regional distribution points that are typically located in ContosoΓÇÖs regional hub offices. - Windows PCs and devices in various locations that receive and install the deployment packages for the in-place upgrade or ongoing updates based on group membership. ## Next step -Learn how Contoso is leveraging its Configuration Manager infrastructure to [deploy and keep current Microsoft 365 Apps for enterprise](contoso-o365pp.md) across its organization. +Learn how Contoso is leveraging its Configuration Manager infrastructure to [deploy and keep current Microsoft 365 Apps for enterprise](contoso-o365pp.md) across its organization. ## See also -[Windows 10 Enterprise](/windows/deployment/) +[Windows 11 Enterprise](/windows/deployment/) [Microsoft 365 for enterprise overview](microsoft-365-overview.md)--[Test lab guides](m365-enterprise-test-lab-guides.md) |
| enterprise | Use Powershell To Perform A Cutover Migration To Microsoft 365 | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/use-powershell-to-perform-a-cutover-migration-to-microsoft-365.md | Title: "Use PowerShell to perform a cutover migration to Microsoft 365" Previously updated : 08/10/2020 Last updated : 09/06/2024 audience: Admin search.appverid: - scotvorg - Ent_O365+- must-keep f1.keywords: - NOCSH description: Learn how to use PowerShell to move the contents from a source emai You can migrate the contents of user mailboxes from a source email system to Microsoft 365 all at once by using a cutover migration. This article walks you through the tasks for an email cutover migration by using Exchange Online PowerShell. -By reviewing the topic, [What you need to know about a cutover email migration to Microsoft 365](/Exchange/mailbox-migration/what-to-know-about-a-cutover-migration), you can get an overview of the migration process. When you're comfortable with the contents of that article, use this one to begin migrating mailboxes from one email system to another. +By reviewing the article [What you need to know about a cutover email migration to Microsoft 365](/Exchange/mailbox-migration/what-to-know-about-a-cutover-migration), you can get an overview of the migration process. When you're comfortable with the contents of that article, use this one to begin migrating mailboxes from one email system to another. > [!NOTE] > You can also use the <a href="https://go.microsoft.com/fwlink/p/?linkid=2059104" target="_blank">Exchange admin center</a> to perform a cutover migration. See [Perform a cutover migration of email to Microsoft 365](/Exchange/mailbox-migration/cutover-migration-to-office-365). By reviewing the topic, [What you need to know about a cutover email migration t Estimated time to complete this task: 2-5 minutes to create a migration batch. After the migration batch is started, the duration of the migration will vary based on the number of mailboxes in the batch, the size of each mailbox, and your available network capacity. For information about other factors that affect how long it takes to migrate mailboxes to Microsoft 365, see [Migration Performance](/Exchange/mailbox-migration/office-365-migration-best-practices). -You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the "Migration" entry in a table in the [Recipients Permissions](/exchange/recipients-permissions-exchange-2013-help) topic. +You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the "Migration" entry in a table in the [Recipients Permissions](/exchange/recipients-permissions-exchange-2013-help) article. To use the Exchange Online PowerShell cmdlets, you need to sign in and import the cmdlets into your local Windows PowerShell session. See [Connect to Exchange Online PowerShell](/powershell/exchange/connect-to-exchange-online-powershell) for instructions. For a full list of migration commands, see [Move and migration cmdlets](/powersh - **Disable Unified Messaging.** If the on-premises mailboxes you're migrating are enabled for Unified Messaging (UM), you have to disable UM on the mailboxes before you migrate them. You can then enable UM on the mailboxes after the migration is complete. -- **Security Groups and Delegates** The email migration service cannot detect whether on-premises Active Directory groups are security groups or not, so it cannot provision any migrated groups as security groups in Microsoft 365. If you want to have security groups in your Microsoft 365 tenant, you must first provision an empty mail-enabled security group in your Microsoft 365 tenant before starting the cutover migration. Additionally, this migration method only moves mailboxes, mail users, mail contacts, and mail-enabled groups. If any other Active Directory object, such as user that is not migrated to Microsoft 365, is assigned as a manager or delegate to an object being migrated, they must be removed from the object before you migrate.+- **Security Groups and Delegates** The email migration service can't detect whether on-premises Active Directory groups are security groups or not, so it can't provision any migrated groups as security groups in Microsoft 365. If you want to have security groups in your Microsoft 365 tenant, you must first provision an empty mail-enabled security group in your Microsoft 365 tenant before starting the cutover migration. Additionally, this migration method only moves mailboxes, mail users, mail contacts, and mail-enabled groups. If any other Active Directory object, such as user that isn't migrated to Microsoft 365, is assigned as a manager or delegate to an object being migrated, they must be removed from the object before you migrate. ### Step 2: Create a migration endpoint <a name="BK_Step2"> </a> |
| solutions | Ransomware Protection Microsoft 365 | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/solutions/ransomware-protection-microsoft-365.md | |