-description: "Get IT posters that describe the architectural models, deployment, and platform options for SharePoint, Exchange, Skype for Business, and Lync."

-# Architectural models for SharePoint, Exchange, Skype for Business, and Lync

-The IT posters in this article describe the architectural models and deployment options for SharePoint, Exchange, Skype for Business, and Lync. They also provide design information for deploying SharePoint in Microsoft Azure.

-

-By using Microsoft 365, you can provide familiar collaboration and communication services through the cloud. With a few exceptions, the user experience remains the same whether you're maintaining an on-premises deployment or using Microsoft 365.

-This unified user experience complicates the decision of where to place each workload. It also raises questions:

-

-

-

-

-

-

-> [!TIP]

-> Most posters in this article are available in multiple languages. Available languages include Chinese, English, French, German, Italian, Japanese, Korean, Portuguese, Russian, and Spanish. To download a poster in one of these languages, under the poster thumbnail image, select **More languages**.

-

-Let us know what you think! Send us email at [cloudadopt@microsoft.com](mailto:cloudadopt@microsoft.com).

-

-Use the following links to get the posters you need:

-

-

- - [Microsoft SharePoint 2016 architectural models](architectural-models-for-sharepoint-exchange-skype-for-business-and-lync.md#SP2016_ArchModel)

-

- - [SharePoint Server 2016 databases](architectural-models-for-sharepoint-exchange-skype-for-business-and-lync.md#SP2016_Databases)

-

- - [Microsoft Skype for Business 2015 architectural models](architectural-models-for-sharepoint-exchange-skype-for-business-and-lync.md#SfB2015_ArchModel)

-

-

- - [SharePoint 2013 platform options](architectural-models-for-sharepoint-exchange-skype-for-business-and-lync.md#SP2013_Options)

-

- - [Exchange 2013 platform options](architectural-models-for-sharepoint-exchange-skype-for-business-and-lync.md#Exch2013_options)

-

- - [Lync 2013 platform options](architectural-models-for-sharepoint-exchange-skype-for-business-and-lync.md#Lync2013_Options)

-

-

- - [Internet sites in Azure using SharePoint Server 2013](architectural-models-for-sharepoint-exchange-skype-for-business-and-lync.md#Azure_sharepoint2013)

-

- - [Design sample: Internet sites in Azure for SharePoint 2013](architectural-models-for-sharepoint-exchange-skype-for-business-and-lync.md#DesignSampleInternetSites)

-

- - [SharePoint disaster recovery to Azure](architectural-models-for-sharepoint-exchange-skype-for-business-and-lync.md#sharepoint_recovery_Azure)

-

-## Architectural models posters

-The IT posters for SharePoint 2016 and Skype for Business 2015 provide a way to compare deployment methods in an easy-to-print format. The posters list all configuration or platform options. They provide the following information for each option:

-

-

-

-

-

-

-<a name="SP2016_ArchModel"> </a>

-### Microsoft SharePoint Server 2016 Architectural Models

-|Item|Description|

-|||

-|[ ](https://www.microsoft.com/download/details.aspx?id=52650) <br/> [PDF](https://download.microsoft.com/download/4/F/A/4FA0F94B-EE2F-41DB-A047-D9864FEF41E9/SharePoint2016ArchitecturalModels.pdf) \| [Visio](https://download.microsoft.com/download/4/F/A/4FA0F94B-EE2F-41DB-A047-D9864FEF41E9/SharePoint2016ArchitecturalModels.vsdx) \| [More languages](https://www.microsoft.com/download/details.aspx?id=52650)|This IT poster describes the SharePoint Online, Azure, and SharePoint on-premises configurations that business decision makers and solutions architects need to know about. <br/><br/> - **SharePoint Online (SaaS)**: Consume SharePoint through a software as a service (SaaS) subscription model. <br/> - **SharePoint hybrid**: Move your SharePoint sites and apps to the cloud at your own pace. <br/> - **SharePoint in Azure (IaaS)**: Extend your on-premises environment into Azure, and deploy SharePoint 2016 servers there. (This model is recommended for high availability or disaster recovery environments and dev/test environments.) <br/> - **SharePoint on-premises**: Plan, deploy, maintain, and customize your SharePoint environment in a datacenter that you maintain.|

-

-<a name="SP2016_Databases"> </a>

-### SharePoint Server 2016 Databases

-|Item|Description|

-|||

-|[](https://www.microsoft.com/download/details.aspx?id=55041) <br/> [PDF](https://download.microsoft.com/download/D/5/D/D5DC1121-8BC5-4953-834F-1B5BB03EB691/DBrefguideSPS2016_tabloid.pdf) \| [Visio](https://download.microsoft.com/download/D/5/D/D5DC1121-8BC5-4953-834F-1B5BB03EB691/DBrefguideSPS2016_tabloid.vsdx) \| [More languages](https://www.microsoft.com/download/details.aspx?id=55041)|This IT poster is a quick reference for SharePoint Server 2016 databases. You'll see details for each database: <br/><br/> - Size <br/> - Scaling guidance <br/> - I/O patterns <br/> - Requirements <br/><br/> The first page shows the SharePoint system databases and the service applications that have multiple databases. The second page shows all of the service applications that have single databases. <br/><br/> For more information, see [Database types and descriptions in SharePoint Server 2016](/SharePoint/technical-reference/database-types-and-descriptions).|

-

-<a name="SfB2015_ArchModel"> </a>

-### Microsoft Skype for Business 2015 Architectural Models

-|Item|Description|

-|||

-|[](https://www.microsoft.com/download/details.aspx?id=55022) <br/> [PDF](https://download.microsoft.com/download/7/7/4/7741262C-A60D-41F7-863B-99BF5964FBFE/Skype%20for%20Business%20Architectural%20Models.pdf) \| [Visio](https://download.microsoft.com/download/7/7/4/7741262C-A60D-41F7-863B-99BF5964FBFE/Skype%20for%20Business%20Architectural%20Models.vsd) \| [More languages](https://www.microsoft.com/download/details.aspx?id=55022)|This poster describes Skype for Business Online, on-premises, hybrid, and cloud private branch exchange (PBX). It also describes integration with Exchange and SharePoint configurations that business decision makers and solutions architects need to know about. <br/><br/> The poster is intended for IT pros to raise awareness of the fundamental architectural models through which Skype for Business Online and Skype for Business on-premises can be consumed. <br/><br/>Start with the configuration that best suits your organization's needs and plans. Consider and use other configurations as needed. For example, you might want to consider integration with Exchange and SharePoint or a solution that takes advantage of the Microsoft cloud PBX offering.|

-

-## Platform options posters

-The IT posters for SharePoint 2013, Exchange 2013, and Lync 2013 provide a way to compare the deployment methods at a glance. Each poster lists all of the configurations or platform options. It provides the following information for each option:

-

-

-

-

-

-

-<a name="SP2013_Options"> </a>

-## SharePoint 2013 Platform Options

-|Item|Description|

-|||

-|[](https://www.microsoft.com/download/details.aspx?id=40332) <br/> [PDF](https://go.microsoft.com/fwlink/p/?LinkId=324594) \| [Visio](https://go.microsoft.com/fwlink/p/?LinkId=324593) \| [More languages](https://www.microsoft.com/download/details.aspx?id=40332)|For business decision makers and architects, this poster shows the platform options for SharePoint 2013, SharePoint in Microsoft 365, on-premises hybrid with Microsoft 365, Azure, and on-premises-only deployments. It includes an overview of each architecture, recommendations, license requirements, and lists of architect and IT pro tasks for each platform. The poster highlights several SharePoint solutions on Azure.|

-

-<a name="Exch2013_options"> </a>

-## Exchange 2013 Platform Options

-|Item|Description|

-|||

-|[ ](https://www.microsoft.com/download/details.aspx?id=42676) <br/> [PDF](https://go.microsoft.com/fwlink/p/?LinkID=398740) \| [Visio](https://go.microsoft.com/fwlink/p/?LinkID=398742) \| [More languages](https://www.microsoft.com/download/details.aspx?id=42676)|For business decision makers and architects, this poster describes the platform options for Exchange 2013. Customers can choose from Exchange Online with Microsoft 365, hybrid Exchange, Exchange Server on-premises, and hosted Exchange. The poster details each architectural option, including the ideal scenarios for each, the license requirements, and IT pro responsibilities.|

-

-<a name="Lync2013_Options"> </a>

-## Lync 2013 Platform Options

-|Item|Description|

-|||

-|[ ](https://www.microsoft.com/download/details.aspx?id=41677) <br/> [PDF](https://go.microsoft.com/fwlink/p/?LinkID=391837) \| [Visio](https://go.microsoft.com/fwlink/p/?LinkID=391839) \| [More languages](https://www.microsoft.com/download/details.aspx?id=41677)|For business decision makers and architects, this poster describes the platform options for Lync 2013. Customers can choose from Lync Online with Microsoft 365, hybrid Lync, Lync Server on-premises, and hosted Lync. The IT poster details each architectural option, including the ideal scenarios for each, the license requirements, and IT pro responsibilities.|

-

-<a name="Lync2013_Options"> </a>

-## SharePoint in Azure solutions posters

-The IT posters for SharePoint in Azure show Azure-based solutions that use SharePoint Server 2013.

-

-<a name="Azure_sharepoint2013"> </a>

-### Internet Sites in Microsoft Azure Using SharePoint Server 2013

-|Item|Description|

-|||

-|[|

-

-<a name="DesignSampleInternetSites"> </a>

-### Internet sites in Azure for SharePoint 2013

-|Item|Description|

-|||

-|[|

-

-<a name="sharepoint_recovery_Azure"> </a>

-### SharePoint Disaster Recovery to Microsoft Azure

-|Item|Description|

-|||

-|[|

-

-## See also

-

-

-

-description: Use this roadmap to set up client and server software for Microsoft 365.

-# Client and server software roadmap for Microsoft 365

-Most enterprise organizations have a heterogeneous environment that includes multiple releases of operating systems, client software, and server software. Microsoft 365 for Enterprise includes the most secure versions of the key components of your IT infrastructure. It also includes productivity features that are designed to take advantage of cloud technologies.

-To maximize the business value of the Microsoft 365 for Enterprise integrated suite of products, begin planning and implementing a strategy to migrate releases of:

->[!Note]

->Support for Windows 7 ended on *January 14, 2020*. For more information, see the [end-of-support details](https://support.microsoft.com/help/4057281/windows-7-support-will-end-on-january-14-2020).

->

-As you accomplish these migrations over time, your organization comes closer to the vision of the [modern workplace](https://www.microsoft.com/microsoft-365/blog/2018/04/27/making-it-simpler-with-a-modern-workplace/). This secure and integrated environment can help you unlock teamwork and creativity in your organization. Microsoft 365 for Enterprise enables and empowers you all along the way.

-## Migration for Office client products

-Organizations both large and small often use a combination of older versions of Office client products, such as Word, Excel, and PowerPoint. These older versions:

-Microsoft 365 for Enterprise includes Microsoft 365 Apps for enterprise. This version of the Office client products is available with a Microsoft 365 for Enterprise license. It's installed and updated from the Microsoft cloud. Microsoft 365 Apps for enterprise includes security updates and the latest features. For more information, see [About Microsoft 365 Apps for enterprise](/deployoffice/about-microsoft-365-apps).

-### Office 2007

-For versions of Office in the Office 2007 release, the end of support has already passed. For more information, see [Office 2007 end-of-support roadmap](/deployoffice/office-2007-end-support-roadmap).

-Rather than upgrading your computers that run Office 2007 to Office 2010, Office 2013, or Office 2016, consider taking the following steps:

-1. Get and assign a Microsoft 365 license for your users.

-2. Uninstall Office 2007 on their computers.

-3. Install Microsoft 365 Apps for enterprise, either individually or during an IT rollout. For more information, see [Deployment guide for Microsoft 365 Apps](/deployoffice/deployment-guide-microsoft-365-apps).

-Microsoft 365 Apps for enterprise installs updates automatically. It can take advantage of cloud-based services for enhanced security and productivity.

-### Office 2010

-For versions of Office in the Office 2010 release, support ended on *October 13, 2020*. For more information, see [Office 2010 end-of-support roadmap](/deployoffice/office-2010-end-support-roadmap).

-You might consider upgrading your computers that run Office 2010 to Office 2013 or Office 2016. However, both of those versions must be manually updated. So consider taking the following steps instead:

-1. Get and assign a Microsoft 365 license for your users.

-2. Uninstall Office 2010 on their computers.

-3. Install Microsoft 365 Apps for enterprise, either individually or during an IT rollout. For more information, see [Deployment guide for Microsoft 365 Apps](/deployoffice/deployment-guide-microsoft-365-apps).

-Microsoft 365 Apps for enterprise automatically installs both security updates and new feature updates. It can take advantage of cloud-based services in Microsoft 365 for enhanced security and productivity.

-### Office 2013 and Office 2016

-See the [end-of-support roadmap for Office 2013](/lifecycle/products/microsoft-office-2013). The end of support for Office 2016 hasn't yet been determined. In these versions, like Office 2010, you must still [install security updates](https://support.office.com/article/install-office-updates-2ab296f3-7f03-43a2-8e50-46de917611c5). This task might not scale well, depending on the size of your organization.

-Rather than keeping your computers current with the latest security updates for Office 2013 or Office 2016, or updating your computers from Office 2013 to Office 2016, consider taking the following steps:

-1. Get and assign a Microsoft 365 license for your users.

-2. Uninstall Office 2013 or Office 2016 on their computers.

-3. Install Microsoft 365 Apps for enterprise, either individually or during an IT rollout. For more information, see [Deployment guide for Microsoft 365 Apps](/deployoffice/deployment-guide-microsoft-365-apps).

-Microsoft 365 Apps for enterprise installs both security updates and new feature updates automatically. It can take advantage of cloud-based services in Microsoft 365 for enhanced security and productivity.

-## Migration for Office server products

-Both large and small organizations often use a combination of older versions of the Office server products, such as Exchange Server and SharePoint Server. These older versions:

-Microsoft 365 for Enterprise includes cloud-based versions of Office server services that use some of the same tools as on-premises versions of Office server software, such as web browsers and the Outlook client. These services are automatically updated for security. So your IT personnel save the time it takes to maintain and update on-premises servers. These services also offer new feature enhancements that aren't present in Office server software.

-Use the following resources for information about migrating users and data for specific Microsoft 365 workloads:

-### Office 2007 server products

-For server products in the Office 2007 release, the end of support has already passed. See these articles for details:

-Rather than upgrading your server products in the Office 2007 release with server products in the releases for Office 2010, Office 2013, or Office 2016, consider taking the following steps:

-1. Migrate the data on your Office 2007 servers to Microsoft 365. For more information or help, hire a Microsoft partner.

-2. Roll out the new functionality and work processes to your users.

-3. When you no longer need the on-premises servers running Office 2007 server products, decommission them.

-### Office 2010 server products

-Support for [Exchange Server 2010](exchange-2010-end-of-support.md) ended on *October 13, 2020*.

-The end of support for [SharePoint Server 2010](upgrade-from-sharepoint-2010.md) is *April 13, 2021*.

-Rather than upgrading these server products in the Office 2010 release with server products in the releases for Office 2013 or Office 2016, consider taking the following steps:

-1. Migrate the data on your Office 2010 servers to Microsoft 365. For more information, see [FastTrack for Microsoft 365](https://fasttrack.microsoft.com/microsoft365) or hire a Microsoft partner.

-2. Roll out the new functionality and work processes to your users.

-3. When you no longer need the on-premises servers running Office 2010 server products, decommission them.

-### Office 2013 server products

-For server products in the Office 2013 release, the end of support hasn't been determined. Rather than upgrading your server products in the Office 2013 release with server products in the Office 2016 release, consider taking the following steps:

-1. Migrate the data on your Office 2013 servers to Microsoft 365. For more information, see [FastTrack for Microsoft 365](https://fasttrack.microsoft.com/microsoft365) or hire a Microsoft partner.

-2. Roll out the new functionality and work processes to your users.

-3. When you no longer need the on-premises servers running Office 2013 server products, decommission them.

-### Office 2016 server products

-For server products in the Office 2016 release, the end of support hasn't been determined. To take advantage of cloud-based service and enhancements to digitally transform your business, consider taking the following steps:

-1. Migrate the data on your Office 2016 servers to Microsoft 365. For more information, see [FastTrack for Microsoft 365](https://fasttrack.microsoft.com/microsoft365) or hire a Microsoft partner.

-2. Roll out the new functionality and work processes to your users.

-3. When you no longer need the on-premises servers running Office 2016 server products, decommission them.

-## Migration for Windows 7 and 8.1

-Support ended for Windows 7 on *January 14, 2020*. To migrate your devices that run Windows 7 or Windows 8.1, you can do an in-place upgrade.

-For additional methods, see [Windows 10 deployment scenarios](/windows/deployment/windows-10-deployment-scenarios). You can also [plan for Windows 10 deployment](/windows/deployment/planning/) on your own.

-## Office 2010 clients and servers and Windows 7

-Here's a visual summary of the upgrade, migration, and move-to-cloud options for Office 2010 clients and servers and Windows 7:

-[](https://download.microsoft.com/download/2/7/d/27da4118-32ae-4ffe-90d8-a61e7c895ba0/Office2010Windows7EndOfSupport.pdf)

-This one-page poster is a quick way to understand the paths you can take to manage the end of support for Office 2010 client and server products and Windows 7. The preferred paths are supported in Microsoft 365 for Enterprise.

-You can [download this poster](https://download.microsoft.com/download/2/7/d/27da4118-32ae-4ffe-90d8-a61e7c895ba0/Office2010Windows7EndOfSupport.pdf) and print it in letter size, legal size, or tabloid (11 x 17) size.

-## Transition your entire organization

-To get a better picture of how to move your entire organization to the products and services in Microsoft 365 for Enterprise, download this transition poster:

-[](https://download.microsoft.com/download/2/c/7/2c7bcc04-aae3-4604-9707-1ffff66b9851/transition-org-to-m365.pdf)

-This two-page poster is a quick way to inventory your existing infrastructure. Use it to get guidance for moving to a product or service in Microsoft 365 for Enterprise. It shows Windows and Office products and other infrastructure and security elements such as device management, identity and threat protection, and information and compliance protection.

-## How Microsoft migrated to Microsoft 365 for Enterprise

-See how IT experts at Microsoft migrated the company to Microsoft 365 for Enterprise:

-description: "Learn about your options after Exchange Server 2007 end of support, and start planning migration to Microsoft 365, Office 365, or Exchange 2016."

-# Exchange 2007 end of support roadmap

-*This article applies to both Microsoft 365 Enterprise and Office 365 Enterprise.*

-Exchange Server 2007 reached end of support in April 2017. If you haven't started your migration from Exchange 2007 to Microsoft 365, Office 365, or Exchange 2016, now's the time to start planning.

-## What does *end of support* mean?

-Exchange Server, like almost all Microsoft products, has a support lifecycle during which we provide new features, bug fixes, security fixes, and so on. This lifecycle typically lasts for 10 years from the product's initial release. The end of this lifecycle is known as the product's end of support. Since Exchange 2007 reached its end of support on April 11, 2017, Microsoft no longer provides:

-Your installation of Exchange 2007 will continue to run after the end-of-support date. But because there are no new updates or support, we strongly recommend that you migrate from Exchange 2007 as soon as possible.

-For more information about Office 2007 servers nearing the end of support, see [Plan your upgrade from Office 2007 servers and products](upgrade-from-office-2007-servers-and-products.md).

-## What are my options?

-You can:

-The following sections explore each option in more detail.

-### Migrate to Microsoft 365

-Migrating your email to Microsoft 365 is the best and simplest option to help retire your Exchange 2007 deployment. With a migration to Microsoft 365, you can make a single hop from 10-year-old technology to state-of-the-art features, including:

-Microsoft 365 also gets new features and experiences first, so you and your users can usually start using them right away. And you won't have to worry about:

-#### How should I migrate to Microsoft 365?

-You have a few migration options. You need to consider a few things, including:

-This table shows your migration options and the most important factors that determine which method to use:

-|Migration option|Organization size|Duration|

-||||

-|Cutover migration|Fewer than 150 seats|A week or less|

-|Staged migration|More than 150 seats|A few weeks|

-|Full hybrid migration|Several hundred to thousands of seats|A few months or more|

-The following sections provide an overview of these methods. For more detail, see [Decide on a migration path](https://support.office.com/article/Decide-on-a-migration-path-0d4f2396-9cef-43b8-9bd6-306d01df1e27).

-#### Cutover migration

-In a cutover migration, you migrate all your mailboxes, distribution groups, contacts, and so on, to Microsoft 365 at a preselected date and time. After the migration is complete, you shut down your on-premises Exchange servers and start using Microsoft 365 exclusively.

-Cutover migration is great for small organizations that don't have many mailboxes, want to get to Microsoft 365 quickly, and don't want to deal with some of the complexities of the other methods. But it should be completed in a week or less, and it requires users to reconfigure their Outlook profiles. Cutover migration can handle up to 2,000 mailboxes, but we strongly recommend you use it to migrate a maximum of 150 mailboxes. If you try to migrate more, you could run out of time to transfer all the mailboxes before your deadline, and your IT support staff may get overwhelmed with requests to help users reconfigure Outlook.

-If you're thinking about doing a cutover migration, here are things to consider:

-For more information about cutover migration, see:

-#### Staged migration

-In a staged migration, you have a few hundred or a few thousand mailboxes that you want to migrate to Microsoft 365, need to take a week or more to complete the migration, and don't need any of advanced hybrid migration features like shared Free/Busy calendar information.

-Staged migration is great for organizations that need to take more time to migrate their mailboxes to Microsoft 365 but still plan to complete the migration within a few weeks. You can migrate mailboxes in batches. You control how many and which mailboxes are migrated at a given time. You might batch mailboxes of users in the same department, for example, to make sure they're all moved at the same time. Or, you might leave executive mailboxes until the last batch. As with cutover migrations, your users will need to recreate their Outlook profiles.

-If you're thinking about doing a staged migration, here are things to consider:

-For more information about staged migration, see:

-#### Full hybrid

-In a full hybrid migration, your organization has many hundreds, up to tens of thousands, of mailboxes, and you want to move some or all of them to Microsoft 365. Because these migrations are typically longer-term, hybrid migrations make it possible to:

- - Be properly evaluated and processed by transport and compliance agents targeting internal messages.

- - Bypass anti-spam filters.

-Full hybrid migration is best for organizations that expect to stay in a hybrid configuration for many months or more. You'll get the features listed earlier in this section, plus directory synchronization, better integrated compliance features, and the ability to move mailboxes to and from Microsoft 365 by using online mailbox moves. Microsoft 365 becomes an extension of your on-premises organization.

-If you're thinking about doing a full hybrid migration, here are things to consider:

-If full hybrid migration sounds right for you, see the following resources to help with your migration:

-### Migrate to a newer version of Exchange Server

-We strongly believe that you can achieve the best value and user experience by migrating to Microsoft 365. But we also understand that some organizations need to keep their email on-premises. This could be because of regulatory requirements, to guarantee data isn't stored in a datacenter located in another country/region, or similar. If you choose to keep your email on-premises, you can migrate your Exchange 2007 environment to Exchange 2010, Exchange 2013, or Exchange 2016.

-If you can't migrate to Microsoft 365, we recommend that you migrate to Exchange 2016. Exchange 2016 includes all the features of previous releases of Exchange. It also most closely matches the experience available with Microsoft 365, although some features are available only in Microsoft 365. Check out just a few of the things you've been missing:

-|Exchange release|Features|

-|||

-|Exchange 2010| Role-Based Access Control (permissions without ACLs) <br/> Outlook Web App mailbox policies <br/> Ability to share free/busy and delegate calendars between organizations|

-|Exchange 2013| *Features from Exchange 2010 and ...* <br/> Simplified architecture that reduced the number of server roles to three (Mailbox, Client Access, Edge Transport) <br/> Data loss prevention policies (DLP) that help keep sensitive information from leaking <br/> Improved Outlook Web App experience|

-|Exchange 2016| *Features from Exchange 2013 and ...* <br/> Further simplified server roles to just Mailbox and Edge Transport <br/> Improved DLP along with integration with SharePoint <br/> Improved database resilience <br/> Online document collaboration|

-#### Which version should I migrate to?

-We recommend that you initially assume that you'll migrate to Exchange 2016. Then, use the following information to confirm your assumption or to rule out Exchange 2016. If you can't migrate to Exchange 2016 for some reason, do the same process with Exchange 2013, and so on.

-|Consideration|More Info|

-|||

-|End of support dates| Like Exchange 2007, each version of Exchange has its own end-of-support date: <br/> *Exchange 2010* - January 2020 <br/> *Exchange 2013* - April 2023 <br/> *Exchange 2016* - October 2025 <br/> The earlier the end of support, the sooner you'll need to perform another migration.|

-|Migration path to Exchange 2010 and 2013.|Here are the general phases for migrating to Exchange 2010 or Exchange 2013: <br/> - Install Exchange 2010 or 2013 into your existing Exchange 2007 organization. <br/>- Move services and other infrastructure to Exchange 2010 or 2013.<br/>- Move mailboxes and public folders to Exchange 2010 or 2013.<br/>- Decommission remaining Exchange 2007 servers.|

-|Migration path to Exchange 2016|Here are the general phases for migrating to Exchange 2016: <br/> - Install Exchange 2013 into your existing Exchange 2007 organization.<br/>- Move services and other infrastructure to Exchange 2013.<br/>- Move mailboxes and public folders to Exchange 2013.<br/>- Decommission remaining Exchange 2007 servers.<br/>- Install Exchange 2016 into your existing Exchange 2013 organization.<br/>- Move mailboxes, public folders, services, and other infrastructure to Exchange 2016 (order doesn't matter). Decommission remaining Exchange 2013 servers.<br/><br/> **Note:** Migrating from Exchange 2013 to Exchange 2016 is simple. The two versions have almost the same hardware requirements, and these versions are very compatible. So you can rebuild a server you bought for Exchange 2013 and install Exchange 2016 on it. For online mailbox moves, most users won't even notice that their mailbox was moved off the server and then back after you've rebuilt it with Exchange 2016.|

-|Version coexistence| When migrating to ... <br/> **Exchange 2016:** Exchange 2016 can't be installed in an organization that includes an Exchange 2007 server. You'll first need to migrate to Exchange 2010 or 2013 (we strongly recommend Exchange 2013), remove all Exchange 2007 servers, and then migrate to Exchange 2016. <br/> **Exchange 2010 or Exchange 2013:** You can install Exchange 2010 or Exchange 2013 into an existing Exchange 2007 organization. This enables you to install one or more Exchange 2010 or 2013 servers and perform your migration.|

-|Server hardware| Server hardware requirements have changed from Exchange 2007. Make sure your hardware is compatible. For details, see: <br/> [Exchange 2016 System Requirements](/Exchange/plan-and-deploy/system-requirements) <br/> [Exchange 2013 System Requirements](/exchange/exchange-2013-system-requirements-exchange-2013-help) <br/> [Exchange 2010 System Requirements](/previous-versions/office/exchange-server-2010/aa996719(v=exchg.141)) <br/> You'll find that the significant improvements in Exchange performance and the increased computing power and storage capacity in newer servers mean you'll likely need fewer servers to support the same number of mailboxes.|

-|Operating system version| The minimum supported operating system versions for each version are: <br/> **Exchange 2016** - Windows Server 2012 <br/> **Exchange 2013** - Windows Server 2008 R2 SP1 <br/> **Exchange 2010** - Windows Server 2008 SP2 <br/> Find more information about operating system support at [Exchange Supportability Matrix](/Exchange/plan-and-deploy/supportability-matrix).|

-|Active Directory forest functional level| The minimum supported Active Directory forest functional levels for each version are: <br/> **Exchange 2016** Windows Server 2008 R2 SP1 <br/> **Exchange 2013** Windows Server 2003 <br/> **Exchange 2010** Windows Server 2003 <br/> Find more information about forest functional level support at [Exchange Supportability Matrix](/Exchange/plan-and-deploy/supportability-matrix).|

-|Office client versions| The minimum supported Office client versions for each version are: <br/> **Exchange 2016** - Office 2010 (with the latest updates) <br/> **Exchange 2013** - Office 2007 SP3 <br/> **Exchange 2010** - Office 2003 <br/> Find more information about Office client support at [Exchange Supportability Matrix](/Exchange/plan-and-deploy/supportability-matrix).|

-#### How do I migrate?

-If you decided to keep your email on-premises, use the following resources to help with your migration:

-## Get help

-If you're migrating to Microsoft 365, you might be eligible to use our Microsoft FastTrack service. FastTrack provides best practices, tools, and resources to make your migration to Microsoft 365 as seamless as possible. Best of all, a support engineer will walk you through your migration, from planning and design all the way to migrating your last mailbox. For more about FastTrack, see [Microsoft FastTrack](https://fasttrack.microsoft.com/).

-If you run into problems during your migration to Microsoft 365 and you aren't using FastTrack, or your migration to a newer version of Exchange Server, we're here to help. Here are some resources you can use:

-## Related topics

-[Resources to help you upgrade your Office 2007 servers and clients](upgrade-from-office-2007-servers-and-products.md)

-description: "Exchange 2010 has reached end of support. Use this planning roadmap to prepare to upgrade to Exchange Online or a newer version of Exchange Server on-premises."

-# Exchange 2010 end of support roadmap

-*This article applies to both Microsoft 365 Enterprise and Office 365 Enterprise.*

-Exchange Server 2010 reached its end of support on **October 13, 2020**. If you haven't already begun your migration from Exchange 2010 to Microsoft 365, Office 365, or Exchange 2016, now's the time to start planning.

-## What does *end of support* mean?

-Most Microsoft products have a support lifecycle during which they get new features, bug fixes, security fixes, and so on. This lifecycle typically lasts for 10 years from the product's initial release. The end of this lifecycle is known as the product's end of support. Because Exchange 2010 reached its end of support on October 13, 2020, Microsoft no longer provides:

-Your installation of Exchange 2010 will continue to run after this date. But because of the changes listed above, we strongly recommend that you migrate from Exchange 2010 as soon as possible.

-For more information about nearing the end of support, see [Resources to help you upgrade from Office 2010 servers and clients](upgrade-from-office-2010-servers-and-products.md).

-## What are my options?

-It's a great time to explore your options and prepare a migration plan. You can:

-> [!IMPORTANT]

-> If your organization chooses to migrate mailboxes to Microsoft 365 but plans to keep DirSync or Microsoft Entra Connect in place to continue managing user accounts from on-premises Active Directory, you need to keep at least one Microsoft Exchange server on-premises. If you remove all Exchange servers, you won't be able to make changes to Exchange recipients in Exchange Online because the source of authority remains in your on-premises Active Directory. Changes need to be made there. In this scenario, you have the following options:

->

-> - *Recommended:* If you migrated your mailboxes to Microsoft 365 and upgraded your servers by October 13, 2020, use Exchange 2010 to connect to Microsoft 365 and migrate mailboxes. Next, migrate Exchange 2010 to Exchange 2016, and decommission any remaining Exchange 2010 servers.

-> - If you didn't complete the mailbox migration and on-premises server upgrade by October 13, 2020, upgrade your on-premises Exchange 2010 servers to Exchange 2016 first. Then use Exchange 2016 to connect to Microsoft 365 and migrate mailboxes.

-> [!NOTE]

-> It's little more complicated, but you can also migrate mailboxes to Microsoft 365 while migrating your on-premises Exchange 2010 servers to Exchange 2016.

-Here are the three paths you can take to avoid the end of support for Exchange Server 2010.

-

-The following sections explore each option in more detail.

-## Migrate to Microsoft 365

-Migrating your email to Microsoft 365 is the best and simplest option to help you retire your Exchange 2010 deployment. With a migration to Microsoft 365, you can make a single hop from old technology to current features, including:

-Microsoft 365 also gets new features and experiences first, so your organization can start using them right away. Also, you won't have to worry about:

-### How should I migrate to Microsoft 365?

-Depending on your organization, you have a few options to get to Microsoft 365. First, you need to consider a few things, such as:

-This table shows your migration options and the most important factors that determine which method to use.

-|Migration option|Organization size|Duration|

-||||

-|Cutover migration|Fewer than 150 seats|A week or less|

-|Minimal hybrid migration|Fewer than 150 seats|A few weeks or less|

-|Full hybrid migration|More than 150 seats|A few weeks or more|

-The following sections give you an overview of these methods. For more information, see [Decide on a migration path](https://support.office.com/article/Decide-on-a-migration-path-0d4f2396-9cef-43b8-9bd6-306d01df1e27).

-### Cutover migration

-In a cutover migration, you migrate all your mailboxes, distribution groups, contacts, and so on, to Office 365 at a set date and time. When you're done, you shut down your on-premises Exchange servers and start using Microsoft 365 exclusively.

-Cutover migration is great for small organizations that don't have many mailboxes, want to get to Microsoft 365 quickly, and don't want to deal with the complexity of the other methods. But it should be completed in a week or less. And it requires users to reconfigure their Outlook profiles. Cutover migration can migrate up to 2,000 mailboxes, but we recommend you use it for a maximum of 150. If you try to migrate more, you could run out of time to transfer all the mailboxes before your deadline, and your IT support staff may get overwhelmed with requests to help users reconfigure Outlook.

-Here are things to consider about cutover migration:

-To learn more about cutover migration, see:

-### Minimal hybrid migration

-In a minimal hybrid, or express, migration you move a few hundred mailboxes to Microsoft 365 within a few weeks. This method doesn't support advanced hybrid-migration features like shared free/busy calendar information.

-Minimal hybrid migration is great for organizations that need to take more time to migrate their mailboxes to Microsoft 365, but still plan to complete the migration within a few weeks. You get some of the benefits of the more advanced *full-hybrid migration* without much of the complexity. You can control how many and which mailboxes to migrate at a given time. Microsoft 365 mailboxes will be created with the user names and passwords of the on-premises accounts. And, unlike cutover migrations, your users don't have to recreate their Outlook profiles.

-Here are things to consider about minimal hybrid migration:

-For more information, see [Use Minimal Hybrid to quickly migrate Exchange mailboxes to Office 365](/Exchange/mailbox-migration/use-minimal-hybrid-to-quickly-migrate).

-### Full hybrid

-In a full hybrid migration, you have many hundreds, up to tens of thousands, of mailboxes, and you move some or all to Microsoft 365. Because these migrations are typically longer-term, hybrid migrations make it possible to:

- - Be properly evaluated and processed by transport and compliance agents targeting internal messages.

- - Bypass anti-spam filters.

-Full hybrid migrations are best for organizations that expect to stay in a hybrid configuration for many months or more. You get the features listed earlier in this section, plus directory synchronization, better integrated compliance features, and the ability to move mailboxes to and from Microsoft 365 using online mailbox moves. Microsoft 365 becomes an extension of your on-premises organization.

-Things to consider about full-hybrid migration:

-> [!IMPORTANT]

-> If your organization chooses to migrate mailboxes to Microsoft 365 but plans to keep DirSync or Microsoft Entra Connect in place to continue managing user accounts from on-premises Active Directory, you need to keep at least one Exchange server on-premises. If all Exchange servers are removed, you won't be able to make changes to Exchange recipients in Exchange Online. This is because the source of authority remains in your on-premises Active Directory and changes need to be made there.

-If a full hybrid migration sounds right for you, see the following helpful resources:

-## Upgrade to a newer version of Exchange Server on-premises

-We strongly believe that you get the best value and user experience by migrating fully to Microsoft 365. But we understand that some organizations need to keep some Exchange Servers on-premises. This might be because of regulatory requirements, to guarantee data isn't stored in a foreign datacenter, because you have unique settings or requirements that can't be met in the cloud, or because you need Exchange to manage cloud mailboxes because you still use Active Directory on-premises. In any case, if you keep Exchange on-premises, you should ensure your Exchange 2010 environment is upgraded to at least Exchange 2013 or Exchange 2016.

-For the best experience, we recommend that you upgrade your remaining on-premises environment to Exchange 2016. You don't need to install Exchange Server 2013 if you want to go straight from Exchange Server 2010 to Exchange Server 2016.

-Exchange 2016 includes all the features of previous releases of Exchange. It most closely matches the experience available with Microsoft 365, although some features are available only in Microsoft 365. Check out just a few of the things you've been missing:

-|Exchange release|Features|

-|||

-|**Exchange 2013**|Simplified architecture reduces the number of server roles to three (Mailbox, Client Access, Edge Transport)|

-||Data loss prevention policies (DLP) that help keep sensitive information from leaking|

-||Improved Outlook Web App experience|

-|**Exchange 2016**|*Features from Exchange 2013 and ...*|

-||Further simplified server roles to just Mailbox and Edge Transport|

-||Improved DLP along with integration with SharePoint|

-||Improved database resilience|

-||Online document collaboration|

-|Consideration|More information|

-|||

-|End of support dates|Like Exchange 2010, each version of Exchange has its own end-of-support date: <br/><br/> Exchange 2013 - April 2023 <br/><br/> Exchange 2016 - October 2025 <br/><br/> The earlier the end-of-support date, the sooner you'll need to perform another migration. April 2023 is a lot closer than you think!|

-|Migration path to Exchange 2013 or 2016|The migration path from Exchange 2010 to a newer version is the same whether you choose Exchange 2013 or Exchange 2016: <br/><br/> Install Exchange 2013 or 2016 into your existing Exchange 2010 organization. <br/><br/> Move services and other infrastructure to Exchange 2013 or 2016. <br/><br/> Move mailboxes and public folders to Exchange 2013 or 2016 Decommission remaining Exchange 2010 servers.|

-|Version coexistence|When migrating to Exchange 2013 or Exchange 2016, you can install either version into an existing Exchange 2010 organization. This enables you to install one or more Exchange 2013 or Exchange 2016 servers and do your migration.|

-|Server hardware|Server hardware requirements have changed from Exchange 2010. Make sure your hardware is compatible. Find out more about hardware requirements for each version here: <br/><br/> [Exchange 2016 system requirements](/Exchange/plan-and-deploy/system-requirements?view=exchserver-2016&preserve-view=true) <br/><br/> [Exchange 2013 system requirements](/Exchange/exchange-2013-system-requirements-exchange-2013-help) <br/><br/> With the significant improvements in Exchange performance and the increased computing power and storage capacity in newer servers, you'll likely need fewer servers to support the same number of mailboxes.|

-|Operating system version|The minimum supported operating system versions for each version are: <br/><br/> Exchange 2016 - Windows Server 2012 <br/><br/> Exchange 2013 - Windows Server 2008 R2 SP1 <br/><br/> You can find more information about operating system support at [Exchange Supportability Matrix](/exchange/plan-and-deploy/supportability-matrix).|

-|Active Directory forest functional level|The minimum supported Active Directory forest functional levels for each version are: <br/><br/> Exchange 2016 - Windows Server 2008 R2 SP1 <br/><br/> Exchange 2013 - Windows Server 2003 <br/><br/> You can find more information about forest functional level support at [Exchange Supportability Matrix](/exchange/plan-and-deploy/supportability-matrix).|

-|Office client versions|The minimum supported Office client versions for each version are: <br/><br/> Exchange 2016 - Office 2010 (with the latest updates) <br/><br/> Exchange 2013 - Office 2007 SP3 <br/><br/> Find more information about Office client support at [Exchange Supportability Matrix](/exchange/plan-and-deploy/supportability-matrix).|

-Use the following resources to help with your migration:

-## Summary of options for Office 2010 client and servers and Windows 7

-For a visual summary of the upgrade, migrate, and move-to-the-cloud options for Office 2010 clients and servers and Windows 7, see the [end of support poster](https://download.microsoft.com/download/2/7/d/27da4118-32ae-4ffe-90d8-a61e7c895ba0/Office2010Windows7EndOfSupport.pdf).

-[](https://download.microsoft.com/download/2/7/d/27da4118-32ae-4ffe-90d8-a61e7c895ba0/Office2010Windows7EndOfSupport.pdf)

-This one-page poster illustrates the various paths you can take to respond to Office 2010 client and server products and Windows 7 reaching end of support, with preferred paths and option support in Microsoft 365 Enterprise highlighted.

-You can also [download](https://download.microsoft.com/download/2/7/d/27da4118-32ae-4ffe-90d8-a61e7c895ba0/Office2010Windows7EndOfSupport.pdf) this poster and print it in letter, legal, or tabloid (11 x 17) format.

-## What if I need help?

-If you're migrating to Microsoft 365, you might be eligible to use our Microsoft FastTrack service. FastTrack provides best practices, tools, and resources to make your migration to Microsoft 365 as seamless as possible. Best of all, you'll have a support engineer walk you through from planning and design to migrating your last mailbox. For more about FastTrack, see [Microsoft FastTrack](https://fasttrack.microsoft.com/).

-If you run into problems during your migration to Microsoft 365 and you aren't using FastTrack, or you're migrating to a newer version of Exchange Server, here are some resources you can use:

-## Related articles

-[Resources to help you upgrade from Office 2010 servers and clients](upgrade-from-office-2010-servers-and-products.md)

-description: "Exchange 2013 will reach its end of support in April 2023. Use this planning roadmap to prepare to upgrade to Exchange Online or to a later version of Exchange Server on-premises."

-# Exchange 2013 end of support roadmap

-*This article applies to both Microsoft 365 Enterprise and Office 365 Enterprise.*

-Exchange Server 2013 will reach its end of support on **April 11, 2023**. If you haven't already begun your migration from Exchange 2013 to Microsoft 365, Office 365, or Exchange 2019, now's the time to start planning.

-## What does *end of support* mean?

-Most Microsoft products have a support lifecycle during which they get new features, bug fixes, security fixes, and so on. This lifecycle typically lasts for 10 years from the product's initial release. The end of this lifecycle is known as the product's end of support. Because Exchange 2013 reaches its end of support on April 11, 2023, Microsoft will no longer provide the following after this date:

-Your installation of Exchange 2013 will continue to run after this date. But because of the changes listed above, we strongly recommend that you migrate from Exchange 2013 to Exchange 2019 as soon as possible.

-## What are my options?

-It's a great time to explore your options and prepare a migration plan. You can:

-> [!IMPORTANT]

-> If your organization chooses to migrate mailboxes to Microsoft 365 but plans to keep using Microsoft Entra Connect to manage user accounts in Active Directory, you need to keep at least one Microsoft Exchange server on-premises. If you remove all Exchange servers, you won't be able to make changes to Exchange recipients in Exchange Online because the source of authority is your on-premises Active Directory. In this scenario, you have the following options:

->

->- *Recommended:* Migrate your mailboxes to Microsoft 365 and upgrade your environment to Exchange 2019 by April 11, 2023. Use Exchange 2013 to connect to Microsoft 365 and migrate mailboxes. Next, upgrade from Exchange 2013 to Exchange 2019, and decommission servers running Exchange 2013.

->- If you can't complete a migration to Exchange Online and upgrade your on-premises servers by April 11, 2023, upgrade from Exchange 2013 to Exchange 2019 first and then use Exchange 2019 to migrate mailboxes to Microsoft 365.

-Here are the three paths you can take to avoid the end of support for Exchange Server 2013.

-## Migrate to Microsoft 365

-Migrating to Microsoft 365 is the best and simplest option to help you retire your Exchange 2013 deployment. With a migration to Microsoft 365, you can make a single hop from old technology to current features, including:

-Microsoft 365 also gets new features and experiences first, so your organization can start using them right away. Also, you won't have to worry about:

-### How should I migrate to Microsoft 365?

-Depending on your organization, you have a few options to get to Microsoft 365. First, you need to consider a few things, such as:

-This table shows your migration options and the most important factors that determine which method to use.

-<br>

-****

-|Migration option|Organization size|Duration|

-||||

-|Cutover migration|Fewer than 150 mailboxes|A week or less|

-|Minimal hybrid migration|Fewer than 150 mailboxes|A few weeks or less|

-|Full hybrid migration|More than 150 mailboxes|A few weeks or more|

-|

-The following sections give you an overview of these methods. For more information, see [Decide on a migration path](https://support.office.com/article/Decide-on-a-migration-path-0d4f2396-9cef-43b8-9bd6-306d01df1e27).

-### Cutover migration

-In a cutover migration, you migrate all your mailboxes, distribution groups, contacts, and so on, to Office 365 at a set date and time. When you're done, you shut down your on-premises Exchange servers and start using Microsoft 365 exclusively.

-Cutover migration is great for small organizations that don't have many mailboxes, want to get to Microsoft 365 quickly, and don't want to deal with the complexity of the other methods. But it should be completed in a week or less. And it requires users to reconfigure their Outlook profiles. Cutover migration can migrate up to 2,000 mailboxes, but we recommend you use it for a maximum of 150. If you try to migrate more, you could run out of time to transfer all the mailboxes before your deadline, and your IT support staff may get overwhelmed with requests to help users reconfigure Outlook.

-Here are things to consider about cutover migration:

-To learn more about cutover migration, see:

-### Minimal hybrid migration

-In a minimal hybrid, or express, migration you move a few hundred mailboxes to Microsoft 365 within a few weeks. This method doesn't support advanced hybrid-migration features like shared free/busy calendar information.

-Minimal hybrid migration is great for organizations that need to take more time to migrate their mailboxes to Microsoft 365, but still plan to complete the migration within a few weeks. You get some of the benefits of the more advanced *full-hybrid migration* without much of the complexity. You can control how many and which mailboxes to migrate at a given time. Microsoft 365 mailboxes will be created with the user names and passwords of the on-premises accounts. And, unlike cutover migrations, your users don't have to recreate their Outlook profiles.

-Here are things to consider about minimal hybrid migration:

-For more information, see [Use Minimal Hybrid to quickly migrate Exchange mailboxes to Office 365](/Exchange/mailbox-migration/use-minimal-hybrid-to-quickly-migrate).

-### Full hybrid

-In a full hybrid migration, you have many hundreds, up to tens of thousands, of mailboxes, and you move some or all to Microsoft 365. Because these migrations are typically longer-term, hybrid migrations make it possible to:

- - Be properly evaluated and processed by transport and compliance agents targeting internal messages.

- - Bypass anti-spam filters.

-Full hybrid migrations are best for organizations that expect to stay in a hybrid configuration for many months or more. You get the features listed earlier in this section, plus directory synchronization, better integrated compliance features, and the ability to move mailboxes to and from Microsoft 365 using online mailbox moves. Microsoft 365 becomes an extension of your on-premises organization.

-Things to consider about full-hybrid migration:

-> [!IMPORTANT]

-> If your organization chooses to migrate mailboxes to Microsoft 365 but plans to keep Microsoft Entra Connect to manage user accounts in Active Directory, you need to keep at least one Exchange server on-premises. If all Exchange servers are removed, you won't be able to make changes to Exchange recipients. This is because the source of authority is Active Directory and changes need to be made there.

-If a full hybrid migration sounds right for you, see the following helpful resources:

-## Upgrade to a newer version of Exchange Server on-premises

-We strongly believe that you get the best value and user experience by migrating fully to Microsoft 365. But we understand that some organizations need to keep some Exchange servers on-premises. This might be because of regulatory requirements, to guarantee data isn't stored in a foreign datacenter, because you have unique settings or requirements that can't be met in the cloud, or because you need Exchange to manage cloud mailboxes because you still use Active Directory on-premises. In any case, if you keep Exchange on-premises, you should ensure your Exchange 2013 environment is upgraded.

-For the best experience, we recommend that you upgrade your remaining on-premises environment to Exchange 2019. You don't need to install Exchange Server 2016 because you can go directly from Exchange Server 2013 to Exchange Server 2019. Exchange 2019 most closely matches the experience available with Microsoft 365, although some features are available only in Microsoft 365.

-****

-Below are important things to know about upgrading Exchange 2013:

-|Item|More information|

-|||

-|End of support dates|Like Exchange 2013, each version of Exchange has its own end-of-support date: <p> Exchange 2013 - April 2023 <p> April 2023 is a lot closer than you think!|

-|Migration path to Exchange 2019|The migration path from Exchange 2013 to a newer version is simple: <p> Install Exchange 2019 into your existing Exchange 2013 organization. <p> Move services and data from Exchange 2013 to Exchange 2019 and decommission Exchange 2013 servers.|

-|Server hardware|Server hardware requirements have changed from Exchange 2013. Make sure your hardware is compatible. Find out more about hardware requirements here: <p> [Exchange 2019 system requirements](/exchange/plan-and-deploy/system-requirements?view=exchserver-2019&preserve-view=true) <p>With the significant improvements in Exchange performance and the increased computing power and storage capacity in newer servers, you'll likely need fewer servers to support the same number of mailboxes.|

-|Operating system version|The minimum supported operating system version for Exchange 2019 is Windows Server 2019. Windows Server 2022 support is coming soon <p> You can find more information about operating system support at [Exchange Supportability Matrix](/exchange/plan-and-deploy/supportability-matrix).|

-|Active Directory forest functional level|The minimum supported Active Directory forest functional level is Windows Server 2012 R2. You can find more information about forest functional level support at [Exchange Supportability Matrix](/exchange/plan-and-deploy/supportability-matrix).|

-|Office client versions|The minimum supported Office client version is also documented in the [Exchange Supportability Matrix](/exchange/plan-and-deploy/supportability-matrix?view=exchserver-2019#clients&preserve-view=true).|

-|

-Use the following resources to help with your migration:

-## What if I need help?

-If you're migrating to Microsoft 365, you might be eligible to use our Microsoft FastTrack service. FastTrack provides best practices, tools, and resources to make your migration to Microsoft 365 as seamless as possible. Best of all, you'll have a support engineer walk you through from planning and design to migrating your last mailbox. For more about FastTrack, see [Microsoft FastTrack](https://fasttrack.microsoft.com/).

-If you run into problems during your migration to Microsoft 365 and you aren't using FastTrack, or you're migrating to a newer version of Exchange Server, here are some resources you can use:

-description: TBD.

-# Placeholder article

-This article is a placeholder for now.

-description: "This article contains resources for users using Office 2007 or Office 2010 to help them plan their upgrade."

-# Plan your upgrade from Office 2007 or Office 2010 servers and clients

-*This article applies to both Microsoft 365 for Enterprise and Office 365 for Enterprise.*

-If your organization uses old versions of Office products and servers, now is a great time to start planning your upgrade. Office 2007 products and services have reached their [end of support](upgrade-from-office-2007-servers-and-products.md). For Office 2010 products and

-For more information, see [Upgrade from Office 2010 servers and clients](upgrade-from-office-2010-servers-and-products.md).

-Use the resources in this article to get started on your upgrade.

-## What is Microsoft 365?

-[Microsoft 365](https://www.microsoft.com/microsoft-365) is a combination of innovative Office apps, intelligent cloud services, and world-class security that's designed to help you achieve more.

-Microsoft 365 includes the licenses and capabilities to help ensure that your organization is working on the latest Windows operating system. It also ensures that your Windows, iOS, and Android devices are enrolled with and secured by policies that require authentication and data protection. Additionally, Windows 10 and your Microsoft 365 Apps for Enterprise (previously named Office 365 ProPlus) client software is continually updated to include the latest features and security updates.

-

-Microsoft 365 is the way to digitally transform your business with constantly improving devices and productivity experiences that are enabled and secured by the Microsoft cloud.

-

-|Resource|Description|

-|||

-|[Microsoft 365](https://www.microsoft.com/microsoft-365)|Get information about the versions of Microsoft 365.|

-|[Microsoft 365 for Business documentation](../admin/index.yml)|Get detailed information about the version of Microsoft 365 for small and medium businesses.|

-|[Microsoft 365 for Education documentation](/microsoft-365/education/)|Get detailed information about the version of Microsoft 365 for educational organizations.|

-|[Microsoft 365 for Enterprise documentation](./index.yml)|Get detailed information about the version of Microsoft 365 for enterprise organizations.|

-|||

-## What happens if I don't upgrade?

-You can choose not to upgrade at this time. Your on-premises servers and applications will continue to run. But when you no longer receive security updates or support options, your organization could be vulnerable to security breaches. We strongly recommend that you plan your upgrade soon. You can upgrade to Microsoft 365 or to newer versions of your on-premises servers and applications.

-## What upgrade options are available?

-Organizations should consider several upgrade options:

- |Office 2007 products and services|Office 2010 products and services|

- |||

- |[Office 2007](/DeployOffice/office-2007-end-support-roadmap) (Desktop)|[Office 2010](/DeployOffice/office-2010-end-support-roadmap) (Desktop)|

- |[Exchange 2007](exchange-2007-end-of-support.md)|[Exchange 2010](exchange-2010-end-of-support.md)|

- |[SharePoint 2007](sharepoint-2007-end-of-support.md)|[SharePoint 2010](upgrade-from-sharepoint-2010.md)|

- |[Office Communications Server](/skypeforbusiness/plan-your-deployment/upgrade)|[Lync Server 2010](/skypeforbusiness/plan-your-deployment/upgrade)|

- |[Project Server 2007](project-server-2007-end-of-support.md)|[Project Server 2010](project-server-2010-end-of-support.md)|

- |[PerformancePoint Server 2007](pps-2007-end-of-support.md)||

-

-

-

-## Can I get help for my organization?

-If you want help with planning your upgrade, consider one or more of the following options:

-

-## I'm a home user. What do I do?

-If you're using Office 2007 or Office 2010 at home, consider the following upgrade options:

- [Office on the web](https://products.office.com/office-online/documents-spreadsheets-presentations-office-online) includes [Word for the web](https://go.microsoft.com/fwlink/p/?linkid=746664), [Excel for the web](https://go.microsoft.com/fwlink/p/?linkid=746665), [PowerPoint for the web](https://go.microsoft.com/fwlink/p/?linkid=746666), [OneNote for the web](https://go.microsoft.com/fwlink/p/?linkid=746674), [Sway](https://go.microsoft.com/fwlink/p/?linkid=746675), [Email](https://go.microsoft.com/fwlink/p/?linkid=746676), [Calendar](https://go.microsoft.com/fwlink/p/?linkid=746678), and [OneDrive](https://go.microsoft.com/fwlink/p/?linkid=746679). To get started, visit [Office.com](https://office.com) and sign in by using your [Microsoft account](https://account.microsoft.com/account). If you don't have a Microsoft account, you can create one at [Office.com](https://office.com).

- Support for Windows 7 [ended on January 14, 2020](https://www.microsoft.com/microsoft-365/windows/end-of-windows-7-support). The versions of Word, Excel, PowerPoint, Outlook, Publisher, and Access that are provided with Office 365 Home or Office 365 Personal and that run on Windows 7 devices receive security updates but not feature updates. To continue receiving feature updates for these applications, [upgrade your Windows 7 devices to Windows 10](https://support.microsoft.com/help/12435/windows-10-upgrade-faq).

-

- - If your Windows PC is running Windows 10, consider getting [Office Home & Student 2019](https://www.microsoft.com/p/office-home-student-2019/cfq7ttc0k7c8).

- - If your Windows PC is running Windows 7, 8, or 8.1 and you're not upgrading to Windows 10 now, consider getting Office Home & Student 2016 or another edition of Microsoft Office. You can get it from an authorized reseller.

-

- Support for Windows 7 [ended on January 14, 2020](https://www.microsoft.com/microsoft-365/windows/end-of-windows-7-support). Microsoft no longer provides security updates for it. Upgrade your Windows 7 devices to Windows 10 for continued security and feature updates and ongoing support.

-If you choose not to upgrade now, your Office apps will continue to run according to the [timelines](https://support.microsoft.com/lifecycle/search/13615). However, to get security updates or new and improved features, you need to upgrade.

-

-## Next steps

-

-## Related topics

-

-[Microsoft Lifecycle Policy](/lifecycle/)

-description: The roadmap to use PowerShell for Microsoft 365.

-# PowerShell roadmap for Microsoft 365

-PowerShell roadmap content

-## Next step

-TBD

-description: PerformancePoint Server 2007, ProClarity, and SharePoint Server 2007 have reached end of support. Read this article to help plan your BI solution upgrade.

-# PerformancePoint Server 2007 end of support roadmap

-*This article applies to both Microsoft 365 Enterprise and Office 365 Enterprise.*

-Office 2007 servers and applications have reached their end of support, including servers and applications that you might be using as part of your business intelligence (BI) solutions. The following table lists BI applications that are affected:

-

-|**Microsoft BI applications**|**Date support ended**|

-|:--|:--|

-|ProClarity Analytics Server 6.3 Service Pack 3 <br/> ProClarity Desktop Professional 6.3 <br/> ProClarity SharePoint Viewer 6.3 <br/> |July 11, 2017 <br/> |

-|SharePoint Server 2007 Service Pack 3 <br/> |October 10, 2017 <br/> |

-|PerformancePoint Server 2007 Service Pack 3 <br/> |January 9, 2018 <br/> |

-

-For more information, see [Resources to help you upgrade from Office 2007 servers and clients](upgrade-from-office-2007-servers-and-products.md).

-

-## What does *end of support* mean?

-Like most Microsoft products, PerformancePoint Server 2007 SP3, ProClarity software, and SharePoint Server 2007 SP3, have a support lifecycle, during which Microsoft provides new features, bug fixes, and security updates. The lifecycle for a product typically lasts for 10 years from the product's initial release. The end of that lifecycle is known as the product's end of support. As ProClarity, PerformancePoint Server, and SharePoint Server 2007 have reached their end of support, Microsoft no longer provides:

-

-

-

-

-

-Your installation of ProClarity, SharePoint Server 2007 SP3, and PerformancePoint Server 2007 SP3 will continue to run even though support has ended. However, we strongly recommend that you migrate from these applications as soon as possible.

-

-## What are my options?

-There have been lots of changes to Microsoft BI applications since 2007, and you have several options to consider, as summarized in the following table.

-

-|**If you were using this ...**|**Explore these options ...**|**And keep this in mind ...**|

-|:--|:--|:--|

-| PerformancePoint Server 2007 Monitoring &amp; Analytics capabilities, including:<br/>- PerformancePoint Monitoring Server <br/>- PerformancePoint Dashboard Designer<br/>- Dashboard Viewer for SharePoint Services (used for rendering PerformancePoint dashboards, scorecards, and reports)<br/> |**Excel with Excel in a browser** (in the cloud or on-premises). For an overview, see [BI capabilities in Excel and Microsoft 365](https://support.office.com/article/26c0548e-124c-4fd3-aab3-5f64568cb743.aspx).<br/><br/> **Power BI** (in the cloud or on-premises). For an overview, see [What is Power BI?](https://go.microsoft.com/fwlink/?linkid=841341) <br/><br/> **SQL Server Reporting Services** (on-premises). For an overview, see [SQL Server Reporting Services (SSRS): Create, deploy, and manage mobile and paginated reports](/sql/reporting-services/create-deploy-and-manage-mobile-and-paginated-reports). <br/><br/> **PerformancePoint Services** (on-premises). For an overview, see [What's new for PerformancePoint Services (SharePoint Server 2010)](/previous-versions/office/sharepoint-server-2010/ee661741(v=office.14)). <br/> |Excel is available as an online (cloud-based) or on-premises solution. Many reporting and dashboard needs can be met with Excel. <br/><br/> Power BI is available as an online or on-premises solution. Power BI isn't included in Microsoft 365. But you can start using Power BI for free. Later, depending on your data usage and business needs, you can upgrade to Power BI Pro with Microsoft 365 E5.<br/> <br/> Reporting Services and PerformancePoint Services are both on-premises solutions. <br/><br/> PerformancePoint Services is available in SharePoint Server 2010, SharePoint Server 2013, and SharePoint Server 2016. <br/> <br/> Some features and report types that were available in PerformancePoint Server 2007 aren't available in Excel, Power BI, Reporting Services, or PerformancePoint Services. Review the available features to determine the best solution for your business needs. <br/> |

-| ProClarity software, including:<br/>- ProClarity Desktop Professional<br/> - ProClarity Analytics Server<br/>- ProClarity SharePoint Viewer<br/> |**Work with a Microsoft partner** to identify a solution that best meets your needs. Visit the [Microsoft Partner Center](https://go.microsoft.com/fwlink/?linkid=841249). <br/><br/> You can also consider using Excel with Excel in a browser, Power BI, SQL Server Reporting Services, or PerformancePoint Services. <br/> |Several but not all features of ProClarity software are available in other Microsoft offerings, including Excel, Power BI, Reporting Services, and PerformancePoint Services. <br/> |

-|SharePoint Server 2007 KPIs (also called MOSS KPIs) <br/> |**Excel with Excel Services**. For an overview, see [Business intelligence in Excel and Excel Services (SharePoint Server 2013)](https://support.office.com/article/2740f10c-579d-4b40-a1d9-7beb5d38547c.aspx). <br/> |MOSS KPIs that were created using SharePoint Server 2007 can be used in SharePoint Server 2010, SharePoint Server 2013, and SharePoint Server 2016. But you can't create new MOSS KPIs. <br/> |

-|Excel 2007 <br/> |**Excel** (in the cloud or on-premises). For an overview, see [BI capabilities in Excel and Office 365](https://support.office.com/article/26c0548e-124c-4fd3-aab3-5f64568cb743.aspx). <br/><br/> **Power BI** (in the cloud or on-premises). For an overview, see [What is Power BI?](https://go.microsoft.com/fwlink/?linkid=841341) <br/> |Both Excel and Power BI offer your organization cloud-based and on-premises solutions, with support for a wide variety of data sources. <br/> |

-

-### Help selecting a solution

-With so many BI choices available, it might seem overwhelming to determine which option is best. We have an online guide available to help. See [Choosing Microsoft Business Intelligence (BI) tools for analysis and reporting](/sql/reporting-services/choosing-microsoft-business-intelligence-bi-tools-for-analysis-and-reporting).

-

-### What if I don't upgrade now?

-You can choose to not upgrade immediately. Your existing servers and applications will continue to run. But you won't receive any further updates, including security updates, since support has ended. And if something goes wrong with your server applications you won't be able to get help from Microsoft technical support.

-

-## How do I plan my upgrade?

-After you explore your upgrade options, the next step is to prepare an upgrade plan. The following sections include information and additional resources to help. You have four main options, including two that work both in the cloud or on-premises, and two that are on-premises-only:

-

-|**Option**|**In the cloud or on-premises?**|

-|:--|:--|

-|[Excel with SharePoint Server (on-premises)](#excel-with-sharepoint-server-on-premises) <br/> |Both <br/> |

-|[Power BI](#use-power-bi-in-the-cloud-or-on-premises)<br/> |Both <br/> |

-|[Reporting Services](#use-reporting-services-on-premises) <br/> |On-premises only <br/> |

-|[PerformancePoint Services](#use-performancepoint-services-on-premises) <br/> |On-premises only <br/> |

-

-### Use Excel (in the cloud or on-premises)

-With Excel, which is also known as *Excel Services* in SharePoint Server, you can view and use workbooks in a browser window, even if Excel isn't installed on the computer. You can use Excel to create reports, scorecards, and dashboards. Then, share your workbooks with others, who can use Excel in a browser, whether they're using SharePoint Online as part of Microsoft 365 or SharePoint Server on-premises. You can use data stored on-premises or in the cloud, which enables you to use a wide variety of data sources.

-

-The following table compares key advantages of using Excel with Microsoft 365 to using Excel with SharePoint Server. More information follows.

-

-|**Excel with Microsoft 365 (in the cloud)**|**Excel with SharePoint Server (on-premises)**|

-|:--|:--|

-|**You get the latest, greatest version of Excel**. With Microsoft 365, you get the latest version of Excel, which includes powerful new chart types, the ability to create charts and tables quickly and easily, and support for more data sources. <br/> <br/> **Setup is much simpler**. Excel is included with Microsoft 365 for business, so there's no heavy lifting on your part. Sign up and sign in, and you'll be up and running faster and more efficiently than if you upgrade your on-premises servers. <br/> <br/> **People have everywhere access to their workbooks**. People can securely view workbooks from wherever they are, using their computer, smart phone, and tablet. <br/> <br/> **There's more!** See [BI capabilities in Excel and Office 365](https://support.office.com/article/26c0548e-124c-4fd3-aab3-5f64568cb743.aspx). <br/> |**You manage your global settings**. As a SharePoint administrator, you can specify global settings, such as security, load balancing, session management, workbook caching, and external data connections. <br/> <br/> **You can use Excel Services with PerformancePoint Services**. You can configure Excel Services and PerformancePoint Services as part of your SharePoint Server installation, and include Excel Services reports in your PerformancePoint dashboards. <br/> <br/> **There's more!** See [Business intelligence in Excel and Excel Services (SharePoint Server 2013)](https://support.office.com/article/2740f10c-579d-4b40-a1d9-7beb5d38547c.aspx). <br/> |

-

-#### Excel with Microsoft 365 (in the cloud)

-If you move to Microsoft 365, you'll have the most up-to-date services and applications, including Excel 2016. PerformancePoint Services isn't available in Microsoft 365, so you'll be replacing your PerformancePoint dashboard content with Excel workbooks or other reports. The good news is that Excel 2016 has lots of new chart types, and it's easier than ever to create impressive dashboards in Excel. And new features are added regularly. To learn more, see [What's New in Excel 2016 for Windows](https://support.office.com/article/5fdb9208-ff33-45b6-9e08-1f5cdb3a6c73.aspx).

-

-Also, if you purchase 50 seats or more of Microsoft 365, the Microsoft FastTrack team can help you get set up. To learn more, visit [FastTrack](https://www.microsoft.com/fasttrack/microsoft-365).

-

-#### Excel with SharePoint Server (on-premises)

-If you upgrade to a newer version of SharePoint, you can use Excel with Excel Services or in a browser, as follows:

-

-

-

-

-You can configure PerformancePoint Services in your new version of SharePoint Server as well, and use that together with Excel.

-

-To learn more about your SharePoint upgrade options, see [SharePoint Server 2007 end of support Roadmap](sharepoint-2007-end-of-support.md).

-

-To learn more about Excel Services, see [Excel Services overview (SharePoint Server 2010)](/previous-versions/office/sharepoint-server-2010/ee424405(v=office.14)).

-

-### Use Power BI (in the cloud or on-premises)

-Power BI is a suite of business analytics tools to analyze data and share insights. With Power BI, you can use on-premises or online data sources to create interactive reports and dashboards. People can view and use your reports and dashboards on their computers or mobile devices.

-

-Power BI isn't part of Microsoft 365 or SharePoint Server. It's a separate offering that includes Power BI Desktop, Power BI gateways, and the Power BI service. Power BI also integrates with SharePoint Online. You can get started with Power BI for free. Based on your data usage and business needs, you can later upgrade to Power BI Pro with Microsoft 365 E5. To learn more, see [What is Power BI?](https://go.microsoft.com/fwlink/?linkid=841341)

-

-### Use Reporting Services (on-premises)

-SQL Server Reporting Services provides a robust reporting solution. You can configure Reporting Services in either native mode or SharePoint-integrated mode. You can use several different tools to author reports, including Report Designer, Report Builder, and Power View. With the latest release of SQL Server, you can also use SQL Server Mobile Report Publisher to deliver reports that scale to any screen size. This lets viewers consume reports on their mobile devices. To learn more, see [SQL Server Reporting Services (SSRS): Create, deploy, and manage mobile and paginated reports](/sql/reporting-services/create-deploy-and-manage-mobile-and-paginated-reports).

-

-### Use PerformancePoint Services (on-premises)

-PerformancePoint Server 2007 was sold separately from SharePoint Server 2007. Beginning with SharePoint Server 2010, PerformancePoint Services is a service application in SharePoint Server. So, you don't have to purchase separate server licenses or hardware to use PerformancePoint Services.

-

-To move from PerformancePoint Server 2007 to PerformancePoint Services, you move to a more recent version of SharePoint Server and configure PerformancePoint Services. The version of SharePoint Server that you move to determines whether you can import your existing dashboard content from PerformancePoint Server 2007 to PerformancePoint Services.

-

-

-

-To get started on your PerformancePoint Services upgrade plan, see the following resources:

-

-

-

- - [Plan for PerformancePoint Services (SharePoint Server 2010)](/previous-versions/office/sharepoint-server-2010/ee681486(v=office.14))

-

- - [PerformancePoint Services in SharePoint Server 2013 overview](/sharepoint/administration/performancepoint-services-overview)

-

- - [PerformancePoint Services in SharePoint Server 2016 overview](/sharepoint/administration/performancepoint-services-overview)

-

-When you upgrade to PerformancePoint Services, you get several new features and enhancements. PerformancePoint Services offers improved scorecards; new visualizations, such as the Decomposition Tree and KPI Details report; more chart types; better Time Intelligence filtering capabilities; and improved accessibility compliance. To learn more, see [What's new for PerformancePoint Services (SharePoint Server 2010)](/previous-versions/office/sharepoint-server-2010/ee661741(v=office.14)).

-

-## Where can I get help with my upgrade?

-Whether you upgrade on-premises or move to Microsoft 365, we recommend that you work with a Microsoft partner. A qualified partner can help you identify the solution that best meets your business needs and help with your deployment. Visit the [Microsoft Partner Center](https://go.microsoft.com/fwlink/?linkid=841249), and use the search filters to find a solution provider.

-

-## Related topics

-[Resources to help you upgrade from Office 2007 servers and clients](upgrade-from-office-2007-servers-and-products.md)

-description: On October 10, 2017, support ended for Project Server 2007, Project Portfolio Server, and Project 2007. Use this article to plan your upgrade now.

-# Project Server 2007 end of support roadmap

-*This article applies to both Microsoft 365 Enterprise and Office 365 Enterprise.*

-Support ended for Office 2007 servers and applications in 2017, and you need to consider plans for migration. If you're currently using Project Server 2007 and related products, note the following end-of-support dates:

-

-|**Product**|**End of support date**|

-|:--|:--|

-|Project Server 2007 <br/> |October 10, 2017 <br/> |

-|Project Portfolio Server 2007 <br/> |October 10, 2017 <br/> |

-|Project 2007 Standard <br/> |October 10, 2017 <br/> |

-|Project 2007 Professional <br/> |October 10, 2017 <br/> |

-

-For more information about Office 2007 servers reaching retirement, see [Upgrade from Office 2007 servers and client products](upgrade-from-office-2007-servers-and-products.md).

-

-## What does *end of support* mean?

-Most Microsoft products have a support lifecycle during which they get new features, bug fixes, security fixes, and so on. This lifecycle typically lasts for 10 years from the product's initial release. The end of this lifecycle is known as the product's end of support. Because Project Server 2007 reached its end of support on October 10, 2017, Microsoft no longer provides:

-

-

-

-

-

-Your installation of Project Server 2007 will continue to run after this date. But because of the changes listed previously, we strongly recommend that you migrate from Project Server 2007 as soon as practical.

-

-## What are my options?

-If you're using Project Server 2007, you need to explore your migration options, which are:

-

-

-

-|**Why would I prefer to migrate to Project Online**|**Why would I prefer to migrate to Project Server 2016**|

-|:--|:--|

-| I have mobile users. <br/> <br/>Costs to migrate are a significant concern (hardware, software, hours, and effort to implement). <br/><br/> After migration, costs to maintain my environment are a major concern (for example, automatic updates, guaranteed uptime, and so on). <br/> | Business rules restrict me from operating my business in the cloud.<br/><br/> I need control of updates to my environment. |

-

-> [!NOTE]

-> For more information about options for moving from your Office 2007 servers, see [Resources to help you upgrade from Office 2007 servers and clients](upgrade-from-office-2007-servers-and-products.md). Note that Project Server doesn't support a hybrid configuration, because Project Server and Project Online can't share the same resource pool.

-

-## Important considerations when you migrate from Project Server 2007

-Consider the following when you plan to migrate from Project Server 2007:

-

-

-

-

-## Migrate to Project Online

-If you choose to migrate from Project Server 2007 to Project Online, you can do the following to manually migrate your project plan data:

-

-1. Save your project plans from Project Server 2003 to .mpp format.

-

-2. In Project Professional 2013, Project Professional 2016, or the Project Online Desktop Client, open each .mpp file, and then save and publish it to Project Online.

-

-You can manually create your Microsoft Project Web App (PWA) configuration in Project Online. For example, recreate any needed custom fields or enterprise calendars. Microsoft Partners can also help with this process.

-

-Key resources:

-

-|**Resource**|**Description**|

-|:--|:--|

-|[Get started with Project Online](https://support.office.com/article/e3e5f64f-ada5-4f9d-a578-130b2d4e5f11) <br/> |How to set up and use Project Online <br/> |

-|[Project Online Service Descriptions](/office365/servicedescriptions/project-online-service-description/project-online-service-description) <br/> |Information about the different Project Online plans that are available to you <br/> |

-

-## Migrate to a newer on-premises version of Project Server

-We strongly believe that you get the best value and user experience by migrating to Project Online. But we also understand that some organizations need to keep project data in an on-premises environment. If you choose to keep your project data on-premises, you can migrate your Project Server 2007 environment to Project Server 2010, Project Server 2013, or Project Server 2016.

-

-If you can't migrate to Project Online, we recommend that you migrate to Project Server 2016. Project Server 2016 includes all the features of previous releases of Project Server. It most closely matches the experience available with Project Online, although some features are available only in Project Online.

-

-After each migration, you should check that your data migrated successfully.

-

-> [!NOTE]

->

-

-### How do I migrate to Project Server 2016?

-Architectural differences between Project Server 2007 and Project Server 2016 prevent a direct migration path. So you have to migrate your Project Server 2007 data to each successive version of Project Server until you reach Project Server 2016.

-

-Follow these steps to Project Server 2016:

-

-1. Migrate from Project Server 2007 to Project Server 2010.

-

-2. Migrate from Project Serve 2010 to Project Server 2013.

-

-3. Migrate from Project Server 2013 to Project Server 2016.

-

-After each migration, make sure that your data migrated successfully.

-

-### Step 1: Migrate from Project Server 2007 to Project Server 2010

-For a comprehensive description of what you need to do to upgrade from Project Server 2007 to Project Server 2010, see [Upgrade to Project Server 2010](/previous-versions/office/project-server-2010/gg502590(v=office.14)).

-

-Key resources:

-

-|**Resource**|**Description**|

-|:--|:--|

-|[Project Server 2010 upgrade overview](/previous-versions/office/project-server-2010/ee662496(v=office.14)) <br/> |A high-level view of what you need to do to upgrade from Project Server 2007 to Project Server 2010 <br/> |

-|[Plan to Upgrade to Project Server 2010](/previous-versions/office/project-server-2010/ff603505(v=office.14)) <br/> |Planning considerations when you upgrade from Project Server 2007 to Project Server 2010, including System Requirements <br/> |

-

-#### How do I upgrade?

-For details, see [Upgrade to Project Server 2010](/previous-versions/office/project-server-2010/gg502590(v=office.14)). But it's important to understand that there are two distinct methods you can use to upgrade:

-

-

- - **Database-attach *full upgrade*** - Migrates the project data stored in the Office Project Server 2007 databases, plus the Microsoft Project Web App site data stored in a SharePoint content database.

-

- - **Database-attach *core upgrade*** - Migrates only the project data stored in the Project Server databases.

-

-

-Additional resources:

-

-

-

-

-

-### Step 2: Migrate to Project Server 2013

-After you verify that your data migrated successfully, the next step is to migrate to Project Server 2013.

-

-For a comprehensive description of what you need to do to upgrade from Project Server 2010 to Project Server 2013, see [Upgrade to Project Server 2013](/project/upgrade-to-project-server-2016).

-

-Key resources:

-

-|**Resource**|**Description**|

-|:--|:--|

-|[Overview of the Project Server 2013 upgrade process](/project/upgrade-to-project-server-2016) <br/> |Overview of what you need to do to upgrade from Project Server 2010 to Project Server 2013 <br/> |

-|[Plan to upgrade to Project Server 2013](/project/plan-for-upgrade-to-project-server-2016) <br/> |Planning considerations when you upgrade from Project Server 2010 to Project Server 2013, including System Requirements <br/> |

-

-#### Things to know about upgrading to this version

-[What's new in Project Server 2013 upgrade](/project/what-s-new-in-project-server-2013-upgrade) describes important changes for upgrade for this version. The most notable are:

-

-

-

-

-Additional resources:

-

-

-

-

-

-### Step 3: Migrate to Project Server 2016

-After you verify that your data migrated successfully, the next step is to migrate to Project Server 2016.

-

-For a comprehensive description of what you need to do to upgrade from Project Server 2013 to Project Server 2016, see [Upgrade to Project Server 2016](/project/upgrading-to-project-server-2016).

-

-Key resources:

-

-|**Resource**|**Description**|

-|:--|:--|

-|[Overview of the Project Server 2016 upgrade process](/previous-versions/office/project-server-2010/ee662104(v=office.14)) <br/> |Overview of what you need to do to upgrade from Project Server 2013 to Project Server 2016 <br/> |

-|[Plan for upgrade to Project Server 2016](/project/plan-for-upgrade-to-project-server-2016) <br/> |Planning considerations you upgrade from Project Server 2013 to Project Server 2016 <br/> |

-

-#### Things to know about upgrading to this version

-[Things you need to know about Project Server 2016 upgrade](/project/plan-for-upgrade-to-project-server-2016) tells you some important changes for upgrade for this version, which include:

-

-

-

-## Migrate from Portfolio Server 2007

-Project Portfolio Server 2007 was used with Project Server 2007 for portfolio strategy, prioritization, and optimization. No additional versions of Project Portfolio Server were created after this version. However, portfolio management features are available in Project Server 2016 and the Premium version of Project Online. But data from Project Portfolio Server 2007 can't be migrated to either. Data such as business drivers will have to be recreated.

-

-Other resources:

-

-

-

-## Related topics

-[SharePoint Server 2007 end of support Roadmap](sharepoint-2007-end-of-support.md)

-

-[Resources to help you upgrade from Office 2007 servers and clients](upgrade-from-office-2007-servers-and-products.md)

-description: "Support ends for Project Server 2010 ends on April 13, 2021. Use this article as a guide to upgrade to Project Online or a newer version of Project Server on-premises."

-# Project Server 2010 end of support roadmap

-*This article applies to both Microsoft 365 Enterprise and Office 365 Enterprise.*

-Project Server 2010 will reach end of support on **April 13, 2021**. This date was extended from the previous end-of-support date of October 13, 2020. If you're currently using Project Server 2010, note that these related products have the following end-of-support dates:

-|Product |End of support date|

-|||

-|Project 2010 Standard|October 13, 2020|

-|Project 2010 Professional|October 13, 2020|

-For more information about reaching end of support, see [Upgrade from Office 2010 servers and client products](plan-upgrade-previous-versions-office.md).

-## What does *end of support* mean?

-Almost all Microsoft products have a support lifecycle, during which they get new features, bug fixes, and security updates. This lifecycle typically lasts for 10 years from the product's initial release. The end of this lifecycle is known as the product's end of support. After Project Server 2010 reaches its end of support on April 13, 2021, Microsoft will no longer provide:

-Your installation of Project Server 2010 will continue to run after this date. But, because of the changes listed previously, we strongly recommend that you migrate from Project Server 2010 as soon as possible.

-## What are my options?

-Your migration options are:

-Here are the two paths you can take to avoid the end of support for Project Server 2010.

-

-|Why would I prefer to migrate to Project Server 2019?|Why would I prefer to migrate to Project Online?|

-|||

-|Business rules restrict me from operating my business in the cloud. <br/><br/> I need control of updates to my environment.|I have mobile or remote users.<br/><br/> Costs to migrate on-premises servers are a significant concern (hardware, software, time and effort to implement, and so on.). <br/><br/> After migration, costs to maintain my environment are a concern (for example, automatic updates, guaranteed uptime, and so on).|

-> [!NOTE]

-> For more information about your migration options, see [Resources to help you upgrade from Office 2010 servers and clients](upgrade-from-office-2010-servers-and-products.md). Note that Project Server doesn't support hybrid configuration because Project Server and Project Online can't share the same resource pool.

-### What are my options for Project client?

-If you're using Project Professional 2010 or Project Standard 2010, your options are:

-#### Move to a newer version of Project client

-If you're migrating from Project Standard 2010, you can move to a newer version of Project Standard (Project Standard 2016 or Project Standard 2019). We recommend you move to the newest version to take advantage of the latest features. Migrating to a less-current version (Project Standard 2016) also means you'll need to migrate again sooner.

-Similarly, if you're migrating from Project Professional 2010, you can move to a newer version (Project Professional 2019 or Project Professional 2016). Again, move to the newest version if possible. If you use Project Professional to connect to Project Server, make sure you migrate to a version of Project Professional that connects with the version of Project Server that you use.

-Project Professional 2010 users can also migrate to the Project Online Desktop client, which is a subscription-based version of Project Professional 2019. It's included in Project Plan 3 and Project Plan 5 subscriptions.

-#### Move to an online solution

-You can also migrate from Project Professional 2010 or Project Standard 2010 to a Project subscription-based online solution. Both Project Plan 3 and Plan 5 include Project Online and the latest cloud offering, [Project for the web](https://support.office.com/article/what-can-you-do-with-project-for-the-web-b30f5442-be5f-43d2-9072-c95bff778ea1). Both offer new features and benefits that are worth exploring.

-For more information about features and licenses, see [Microsoft Project service description](/office365/servicedescriptions/project-online-service-description/project-online-service-description).

-## Important considerations for migrating from Project Server 2010

-Consider the following when you plan to migrate from Project Server 2010:

-## Migrate to Project Online

-If you choose to migrate from Project Server 2010 to Project Online, you can follow these steps to manually migrate your project plan data:

-1. Save your project plans from Project Server 2010 to .mpp format.

-2. Using Project Professional 2016, Project Professional 2019, or the Project Online Desktop Client, open each .mpp file, and then save and publish it to Project Online.

-You can manually create your PWA configuration in Project Online (for example, recreate any needed custom fields or enterprise calendars). Microsoft solution providers can also help with this process.

-Key resources:

-|Resource|Description|

-|||

-|[Get started with Project Online](https://support.office.com/article/e3e5f64f-ada5-4f9d-a578-130b2d4e5f11)|How to set up and use Project Online|

-|[Project Online Service Description](/office365/servicedescriptions/project-online-service-description/project-online-service-description)|Information about the different Project Online plans available|

-## Migrate to a newer on-premises version of Project Server

-We strongly believe that you get the best value and user experience by migrating to Project Online. But we also understand some organizations need to keep project data on-premises. If you choose to keep your project data on-premises, you can migrate your Project Server 2010 environment to Project Server 2013, Project Server 2016, or Project Server 2019.

-If you can't migrate to Project Online, we recommend that you migrate to Project Server 2019. Project Server 2019 includes most of the key features in previous releases of Project Server. And it most closely matches the experience available with Project Online, although some features are available only in Project Online.

-After you complete each migration, make sure that your data migrated successfully.

-> [!NOTE]

-> If you're limited to an on-premises solution and considering only migrating to Project Server 2013, beware that this version only has a few more years of support left. The end of support date for Project Server 2013 with Service Pack 2 October 13, 2023. For more information about end-of-support dates, see [Microsoft Product Lifecycle Policy](/lifecycle/).

-### How do I migrate to Project Server 2019?

-The architectural differences between Project Server 2010 and Project Server 2019 prevent a direct migration path. So you'll need to migrate your Project Server 2010 data to each successive version of Project Server until you reach Project Server 2019. Steps to upgrade Project Server 2010 to Project Server 2019:

-1. Migrate to Project Server 2013.

-2. Migrate from Project Serve 2013 to Project Server 2016.

-3. Migrate from Project Server 2016 to Project Server 2019.

-After you complete each migration, make sure that your data migrated successfully.

-### Step 1: Migrate to Project Server 2013

-For a comprehensive information about upgrading from Project Server 2010 to Project Server 2013, see [Upgrade to Project Server 2013](/project/upgrade-to-project-server-2016).

-Key resources:

- Get a high-level overview of how to upgrade from Project Server 2010 to Project Server 2013.

- Look at planning considerations when upgrading from Project Server 2010 to Project Server 2013, including system requirements.

- - There's no in-place upgrade to Project Server 2013. The database-attach method is the only supported way to upgrade from Project Server 2010 to Project Server 2013.

- - The upgrade process will not only convert your Project Server 2010 data to Project Server 2013 format but will also consolidate the four Project Server 2010 databases into a single Project Web App database.

- - Both SharePoint Server 2013 and Project Server 2013 changed to claims-based authentication from the previous version. If you're using classic authentication, you'll need to consider this when you upgrade. For more information, see [Migrate from classic-mode to claims-based authentication in SharePoint 2013](/sharepoint/upgrade-and-update/migrate-from-classic-mode-to-claims-based-authentication-in-sharepoint-2013).

-Key resources:

-### Step 2: Migrate to Project Server 2016

-After you move to Project Server 2013 and verify that your data has migrated successfully, the next step is to migrate to Project Server 2016.

-For more information, see [Upgrade to Project Server 2016](/Project/upgrade-to-project-server-2016).

-Key resources:

- Understand what you need to do to upgrade from Project Server 2013 to Project Server 2016.

- Look at the planning considerations to make when upgrading from Project Server 2013 to Project Server 2016.

-[Things you need to know about Project Server 2016 upgrade](/project/plan-for-upgrade-to-project-server-2016#thingknow) covers important changes for upgrading to this version, which include:

-### Step 3: Migrate to Project Server 2019

-After you migrate to Project Server 2016 and verify that your data migrated successfully, the next step is to migrate your data to Project Server 2019.

-To learn what you need to do to upgrade from Project Server 2016 to Project Server 2019, see [Upgrade to Project Server 2019](/Project/upgrade-to-project-server-2016).

-Key resources:

- Get a high-level understanding of what you need to do to upgrade from Project Server 2013 to Project Server 2016.

- Look at planning considerations for upgrading from Project Server 2016 to Project Server 2019.

- - The upgrade process will migrate your data from your Project Server 2016 database to the SharePoint Server 2019 Content database. Project Server 2019 will no longer create its own Project Server database in the SharePoint Server farm.

- - After the upgrade, be aware of several changes in Project Web App. For details, see [What's new in Project Server 2019](/project/what-s-new-for-it-pros-in-project-server-2019#PWAChanges).

-**Other resources**:

-## Summary of options for Office 2010 client and servers and Windows 7

-For a visual summary of the upgrade, migrate, and move-to-the-cloud options for Office 2010 clients and servers and Windows 7, see the [end of support poster](https://download.microsoft.com/download/2/7/d/27da4118-32ae-4ffe-90d8-a61e7c895ba0/Office2010Windows7EndOfSupport.pdf).

-[](https://download.microsoft.com/download/2/7/d/27da4118-32ae-4ffe-90d8-a61e7c895ba0/Office2010Windows7EndOfSupport.pdf)

-This poster illustrates the various paths you can take to avoid end of support for Office 2010 client and server products and Windows 7, with preferred paths and option support in Microsoft 365 Enterprise highlighted.

-You can also [download](https://download.microsoft.com/download/2/7/d/27da4118-32ae-4ffe-90d8-a61e7c895ba0/Office2010Windows7EndOfSupport.pdf) this poster and print it in letter, legal, or tabloid (11 x 17) format.

-## Related topics

-[Upgrading from SharePoint 2010](upgrade-from-sharepoint-2010.md)

-[Upgrade from Office 2010 servers and clients](upgrade-from-office-2010-servers-and-products.md)

-description: "Support ends for Project Server 2013 on April 11, 2023. Use this article as a guide to upgrade to Project Online or a newer version of Project Server on-premises."

-# Project Server 2013 end of support roadmap

-Project Server 2013 will reach end of support on **April 11, 2023**. If you're currently using Project Server 2013, note that Project 2013 desktop app also has the same end-of-support dates.

-## What does *end of support* mean?

-Almost all Microsoft products have a support lifecycle, during which they get new features, bug fixes, and security updates. This lifecycle typically lasts for 10 years from the product's initial release. The end of this lifecycle is known as the product's end of support. After Project Server 2013 reaches its end of support on April 11, 2023, Microsoft will no longer provide:

-Your installation of Project Server 2013 will continue to run after this date. But, because of the changes listed previously, we strongly recommend that you migrate from Project Server 2013 as soon as possible.

-## What are my options?

-Your migration options are:

-|Why would I prefer to migrate to Project Server 2019?|Why would I prefer to migrate to Project Online?|

-|||

-|Business rules restrict me from operating my business in the cloud. <br/><br/> I need control of updates to my environment.|I have mobile or remote users.<br/><br/> Costs to migrate on-premises servers are a significant concern (hardware, software, time and effort to implement, and so on.). <br/><br/> After migration, costs to maintain my environment are a concern (for example, automatic updates, guaranteed uptime, and so on).|

-> [!NOTE]

-> Project Server doesn't support hybrid configuration because Project Server and Project Online can't share the same resource pool.

-## Important considerations for migrating from Project Server 2013

-Consider the following when you plan to migrate from Project Server 2013:

-## Migrate to Project Online

-If you choose to migrate from Project Server 2013 to Project Online, you can follow these steps to manually migrate your project plan data:

-1. Save your project plans from Project Server 2013 to .mpp format.

-2. Using Project Professional 2016, Project Professional 2019, or the Project Online Desktop Client, open each .mpp file, and then save and publish it to Project Online.

-You can manually create your PWA configuration in Project Online (for example, recreate any needed custom fields or enterprise calendars). Microsoft solution providers can also help with this process.

-Key resources:

-|Resource|Description|

-|||

-|[Get started with Project Online](https://support.office.com/article/e3e5f64f-ada5-4f9d-a578-130b2d4e5f11)|How to set up and use Project Online|

-|[Project Online Service Description](/office365/servicedescriptions/project-online-service-description/project-online-service-description)|Information about the different Project Online plans available|

-## Migrate to a newer on-premises version of Project Server

-We strongly believe that you get the best value and user experience by migrating to Project Online. But we also understand some organizations need to keep project data on-premises. If you choose to keep your project data on-premises, you can migrate your Project Server 2013 environment to Project Server 2016, Project Server 2019, or Project Server Subscription Edition.

-If you can't migrate to Project Online, we recommend that you migrate to Project Server Subscription Edition which includes most of the key features in previous releases of Project Server. And it most closely matches the experience available with Project Online, although some features are available only in Project Online. Additional factors to consider are:

-After you complete each migration, make sure that your data migrated successfully.

-### How do I migrate to Project Server Subscription Edition?

-The architectural differences between Project Server 2013 and Project Server Subscription Edition prevent a direct migration path. So you'll need to migrate your Project Server 2013 data first to Project Server 2016, and then to Project Server Subscription Edition.

-1. Migrate to Project Server 2016.

-2. Migrate from Project Server 2016 to Project Server Subscription Edition.

-After you complete each migration, make sure that your data migrated successfully.

-### Step 1: Migrate to Project Server 2016

-For a comprehensive information about upgrading from Project Server 2013 to Project Server 2016, see [Upgrade to Project Server 2016](/project/upgrade-to-project-server-2016).

-Key resources:

-### Step 2: Migrate to Project Server Subscription Edition

-After you move to Project Server 2016 and verify that your data has migrated successfully, the next step is to migrate to Project Server Subscription Edition.

-For more information, see [Upgrade to Project Server Subscription Edition](/project/upgrade-project-server-subscription-edition).

-Key resources:

-description: Support for SharePoint Server 2007 ended in October 2017. In this article, learn about your upgrade, migration, and support options.

-# SharePoint Server 2007 end of support roadmap

-*This article applies to both Microsoft 365 Enterprise and Office 365 Enterprise.*

-On **October 10, 2017**, Microsoft Office SharePoint Server 2007 reached end of support. If you haven't migrated from SharePoint Server 2007 to Microsoft 365 or a newer version of SharePoint Server on-premises, now's the time to start planning. This article provides resources to help you migrate data to SharePoint Online or upgrade your SharePoint Server on-premises.

-

-## What does *end of support* mean?

-SharePoint Server, like most Microsoft products, has a support lifecycle, during which Microsoft provides new features, bug fixes, security fixes, and so on. This lifecycle typically lasts for 10 years from the product's initial release. The end of this lifecycle is known as the product's end of support. After the end of support, Microsoft no longer provides:

-

-

-

-

-

-Your SharePoint Server 2007 farm will still be operational after October 10, 2017, but no further updates, patches, or fixes will be released for the product, including security patches/fixes. Microsoft Support has fully shifted its support efforts to more-recent versions of the product. Because your installation is no longer supported or patched, you should upgrade the product or migrate important data.

-

-> [!TIP]

-> If you haven't already planned for upgrade or migration, see: [SharePoint 2007 migration options to consider](sharepoint-2007-migration-options.md) for some examples of where to begin. You can also search for [Microsoft Partners](https://go.microsoft.com/fwlink/?linkid=841249) who can help with upgrade or Microsoft 365 migration (or both).

-

-For more information about Office 2007 servers and the end of support, see [Resources to help you upgrade from Office 2007 servers and clients](upgrade-from-office-2007-servers-and-products.md).

-

-## What are my options?

-Your first stop should be the [Product Lifecycle site](/lifecycle/products/?alpha=Microsoft+Office+SharePoint+Server+2007). If you have an on-premises Microsoft product that's aging, check its end of support date so that you have a year or so to schedule an upgrade or migration. When you choose the next step, consider what product features would be good enough, better, and best. Here's an example:

-

-|**Good**|**Better**|**Best**|

-|:--|:--|:--|

-|SharePoint Server 2010 <br/> |SharePoint Server 2013 <br/> |SharePoint Online <br/> |

-||SharePoint Hybrid <br/> |SharePoint Server 2016 <br/> |

-| | |SharePoint Hybrid <br/> |

-

-If you choose a "good enough" option, you'll soon need to begin planning for another upgrade after migration from SharePoint Server 2007 is completed.

->[!NOTE]

->End-of-support dates are subject to change. Check the [Product Lifecycle site](https://support.microsoft.com/lifecycle).

-

-## Where can I go next?

-SharePoint Server can be installed on-premises on your own servers. Or you can use SharePoint Online, which is an online service that's part of Microsoft 365. Your options are:

-

-

-

-

-

-Be aware of hidden costs associated with maintaining a server farm, maintaining or migrating customizations, and upgrading the hardware that SharePoint Server needs. Having an on-premises SharePoint Server farm is rewarding if it's necessary. But if you run your farm on legacy SharePoint Servers without heavy customization, you can benefit from migration to SharePoint Online.

-

-> [!IMPORTANT]

-> There's another option if the content in SharePoint 2007 is infrequently used. Some SharePoint Administrators choose to create a Microsoft 365 subscription, set up a new SharePoint Online site, and then cut away from SharePoint 2007 cleanly, taking only essential documents to the fresh SharePoint Online sites. Data can then be drained from the SharePoint 2007 site into archives. Consider how your users work with data from your SharePoint 2007 installation. There may be creative ways to manage your needs.

-

-|**SharePoint Online (SPO)**|**SharePoint Server on-premises**|

-|:--|:--|

-|High cost in time (plan / execution/verification) <br/> |High cost in time (plan / execution/verification) <br/> |

-|Lower cost in funds (no hardware purchases) <br/> |Higher cost in funds (hardware + devs/admins) <br/> |

-|One-time cost in migration <br/> |One-time cost repeated per future migration <br/> |

-|Low total cost of ownership/maintenance <br/> |High total cost of ownership/maintenance <br/> |

-

-When you migrate to Microsoft 365, the one-time move will have a heavier cost up-front, while you organize data and decide what to take to the cloud and what to leave behind. But future upgrades will be automatic, and you'll no longer need to manage hardware and software updates. Also, the up time of your farm will be backed by a Microsoft Service Level Agreement ([SLA](/office365/servicedescriptions/office-365-platform-service-description/service-level-agreement)).

-

-### Migrate to SharePoint Online

-Make sure that SharePoint Online has all the features you need. See [Microsoft 365 and Office 365 service descriptions](/office365/servicedescriptions/office-365-service-descriptions-technet-library).

-

-You can't migrate directly from SharePoint 2007 to SharePoint Online. Your move to SharePoint Online would be done manually. If you upgrade to SharePoint Server 2013 or SharePoint Server 2016, you might use the SharePoint Migration API (to migrate information into OneDrive for Business, for example).

-

-|**Online pro**|**Online con**|

-|:--|:--|

-|Microsoft supplies SPO hardware and all hardware administration. <br/> |Available features may differ between SharePoint Server on-premises and SPO. <br/> |

-|You're the SharePoint admin or global admin of your subscription and can assign administrators to SPO sites. <br/> |Some actions available to a farm administrator in SharePoint Server on-premises don't exist or aren't necessarily included in the SharePoint Administrator role in Microsoft 365. <br/> |

-|Microsoft applies patches, fixes, and updates to underlying hardware and software. <br/> |Because there's no access to the underlying file system in the service, customization is limited. <br/> |

-|Microsoft publishes [Service level agreements](/office365/servicedescriptions/office-365-platform-service-description/service-level-agreement) and moves quickly to resolve service-level incidents. <br/> |Backup and restore and other recovery options are automated by the service in SharePoint Online. Backups are overwritten if not used. <br/> |

-|Security testing and server performance tuning are carried out on an ongoing basis in the service by Microsoft. <br/> |Changes to the user interface and other SharePoint features are installed by the service and may need to be toggled on or off. <br/> |

-|Microsoft 365 meets many industry standards: [Microsoft compliance offerings](/compliance/regulatory/offering-home). <br/> |[FastTrack](https://www.microsoft.com/fasttrack/microsoft-365) assistance for migration is limited. <br/> Much of the upgrade will be manual or via the SPO Migration API described in the [SharePoint Online and OneDrive Migration Content Roadmap](/sharepointmigration/upload-on-premises-content-to-sharepoint-online-using-powershell-cmdlets). <br/> |

-|Microsoft Support engineers and datacenter employees won't have unrestricted admin access to your subscription. <br/> |There can be additional costs if hardware needs to be upgraded to support the newer version of SharePoint, or if a secondary farm is required for upgrade. <br/> |

-|Partners can assist with the one-time job of migrating your data to SharePoint Online. <br/> ||

-|Online products are updated automatically. Although features may deprecate, there's no true end of support. <br/> ||

-

-If you've decided to create a new Microsoft 365 site and will manually migrate data to it as is needed, check your [Microsoft 365 options](https://www.microsoft.com/microsoft-365/).

-

-### Upgrade SharePoint Server on-premises

-There's no way to skip versions in SharePoint Upgrades. Upgrades go serially:

-

-

-To go from SharePoint 2007 to SharePoint Server 2016 means a significant investment of time and will involve costs in hardware (SQL servers must also be upgraded), software, and administration. Customizations will need to be upgraded or abandoned.

-

-> [!NOTE]

-> It's possible to maintain your end-of-life SharePoint 2007 farm, install a SharePoint Server 2016 farm on new hardware (so the separate farms run side-by-side), and then plan and execute a manual migration of content (for downloading and re-uploading content, for example). But beware of some of the pitfalls of manual moves, such as moves of documents replacing the last-modified account with the alias of the account doing the manual move. Also consider the work that must be done ahead of time, such as recreating sites, subsites, permissions, and list structures. Consider in advance what data you can move into storage or delete to reduce the impact of migration.

-

-It's important to clean up your environment before you upgrade. Be certain your existing farm is functional before you upgrade, and certainly before you decommission!

-

-Remember to review the *supported and unsupported upgrade paths*:

-

-

-

-

-If you have customizations, it's critical to have a plan for each step in the migration path:

-

-

-

-

-|**On-premises pro**|**On-premises con**|

-|:--|:--|

-|Full control of all aspects of your SharePoint Farm, from the server hardware up. <br/> |All breaks and fixes are the responsibility of your company (you can engage paid Microsoft Support if your product is not past end of support). <br/> |

-|Full feature set of SharePoint Server on-premises with the option to connect your on-premises farm to a SharePoint Online subscription via hybrid. <br/> |Upgrade, patches, security fixes, and all maintenance of SharePoint Server managed on-premises. <br/> |

-|Full access for greater customization. <br/> |[Microsoft compliance offerings](/compliance/regulatory/offering-home) must be manually configured on-premises. <br/> |

-|Security testing, and server performance tuning is carried out on your premises (under your control). <br/> |Microsoft 365 may make features available to SharePoint Online that don't interoperate with SharePoint Server on-premises. <br/> |

-|Partners can assist with migrating data to the next version of SharePoint Server (and beyond). <br/> |Your SharePoint Server sites won't automatically use [SSL/TLS](/SharePoint/security-for-sharepoint-server/enable-tls-1-1-and-tls-1-2-support-in-sharepoint-server-2016) certificates as is seen in SharePoint Online. <br/> |

-|Full control of naming conventions, back up and restore, and other recovery options in SharePoint Server on-premises. <br/> |SharePoint Server on-premises is sensitive to product lifecycles. <br/> |

-

-### Upgrade resources

-Make sure your environment meets hardware and software requirements, and then follow supported upgrade methods.

-

-

- [SharePoint Server 2010](/previous-versions/office/sharepoint-server-2010/cc262485(v=office.14)) | [SharePoint Server 2010](/previous-versions/office/sharepoint-server-2010/cc262485(v=office.14)) | [SharePoint Server 2013](/sharepoint/install/hardware-software-requirements-2013) | [SharePoint Server 2016](/SharePoint/install/hardware-and-software-requirements)

-

-

- [SharePoint Server 2007](/previous-versions/office/sharepoint-2007-products-and-technologies/cc262787(v=office.12)) | [SharePoint Server 2010](/previous-versions/office/sharepoint-server-2010/cc262787(v=office.14)) | [SharePoint Server 2013](/SharePoint/install/software-boundaries-and-limits) | [SharePoint Server 2016](/sharepoint/install/software-boundaries-limits-2019)

-

-

- [SharePoint Server 2007](/previous-versions/office/sharepoint-2007-products-and-technologies/cc303420(v=office.12)) | [SharePoint Server 2010](/previous-versions/office/sharepoint-server-2010/cc303420(v=office.14)) | [SharePoint Server 2013](/SharePoint/upgrade-and-update/upgrade-to-sharepoint-server-2016) | [SharePoint Server 2016](/SharePoint/upgrade-and-update/upgrade-to-sharepoint-server-2016)

-

-### Create a SharePoint hybrid solution between SharePoint Online and on-premises

-If the answer to your migration needs is somewhere between the self-control offered by on-premises and the lower cost of ownership offered by SharePoint Online, you can connect SharePoint Server 2013 or 2016 farms to SharePoint Online through hybrids. [Learn about SharePoint hybrid solutions](https://support.office.com/article/4c89a95a-a58c-4fc1-974a-389d4f195383.aspx).

-

-If you decide that a hybrid SharePoint Server farm will benefit your business, familiarize yourself with the existing types of hybrids and how to configure the connection between your on-premises SharePoint farm and your Microsoft 365 subscription.

-

-| Option | Description |

-|:--|:--|

-[Microsoft compliance offerings](/compliance/regulatory/offering-home) <br/> |[FastTrack](https://www.microsoft.com/fasttrack/microsoft-365) assistance for migration is limited. <br/> Much of the upgrade will be manual, or via the SPO Migration API described in the [SharePoint Online and OneDrive Migration Content Roadmap](/sharepointmigration/upload-on-premises-content-to-sharepoint-online-using-powershell-cmdlets). <br/> |

-|Microsoft Support engineers and data center employees don't have unrestricted admin access to your subscription.<br/> |There can be additional costs if hardware infrastructure needs to be upgraded to support the newer version of SharePoint, or if a secondary farm is required for upgrade. <br/> |

-|Partners can assist with the one-time job of migrating your data to SharePoint Online. <br/> ||

-|Online products are updated automatically across the service. Though features may deprecate, there's no true end of support.<br/> ||

-

-If you've decided to create a new Microsoft 365 site and will manually migrate data to it as is needed, check your [Microsoft 365 options](https://www.microsoft.com/microsoft-365/).

-

-### Upgrade SharePoint Server on-premises

-There's no way to skip versions in SharePoint Upgrades. Upgrades go serially:

-

-

-To go from SharePoint 2007 to SharePoint Server 2016 will mean a significant investment of time and will involve costs for hardware (SQL servers must also be upgraded), software, and administration. Customizations will need to be upgraded or abandoned.

-

-> [!NOTE]

-> It's possible to maintain your end-of-life SharePoint 2007 farm, install a SharePoint Server 2016 farm on new hardware (so the separate farms run side-by-side), and then plan and execute a manual migration of content (for downloading and re-uploading content, for example). But beware of potential pitfalls of manual moves, such as moves of documents replacing the last-modified account with the alias of the account doing the manual move, and the work that must be done ahead of time, such as recreating sites, subsites, permissions and list structures. Consider what data you can move into storage or delete to reduce the impact of migration.

-

-Clean your environment prior to upgrade. Be certain your existing farm is functional before you upgrade and certainly before you decommission!

-

-Remember to review the *supported and unsupported upgrade paths*:

-

-

-

-

-If you have *customizations*, it's critical you have a plan your upgrade for each step in the migration path:

-

-

-

-

-|**On-premises Pro**|**On-premises Con**|

-|:--|:--|

-|Full control of all aspects of your SharePoint Farm, from the server hardware up. <br/> |All breaks and fixes are the responsibility of your company. (You can engage paid Microsoft Support if your product isn't past end of support.) <br/> |

-|Full feature set of SharePoint Server on-premises with the option to connect your on-premises farm to a SharePoint Online subscription via hybrid. <br/> |Upgrade, patches, security fixes, and all maintenance of SharePoint Server managed on-premises. <br/> |

-|Full access for greater customization. <br/> |[Microsoft compliance offerings](/compliance/regulatory/offering-home) must be manually configured on-premises. <br/> |

-|Security testing and server performance tuning are carried out on your premises under your control. <br/> |Microsoft 365 may make features available to SharePoint Online that don't interoperate with SharePoint Server on-premises <br/> |

-|Partners can help migrate data to the next version of SharePoint Server (and beyond). <br/> |Your SharePoint Server sites will not automatically use [SSL/TLS](/SharePoint/security-for-sharepoint-server/enable-tls-1-1-and-tls-1-2-support-in-sharepoint-server-2016) certificates as is seen in SharePoint Online. <br/> |

-|Full control of naming conventions, back up and restore, and other recovery options in SharePoint Server on-premises. <br/> |SharePoint Server on-premises is sensitive to product lifecycles. <br/> |

-

-### Upgrade resources

-Make sure that your environment meets hardware and software requirements. Then follow the supported upgrade methods.

-

-

- [SharePoint Server 2010](/previous-versions/office/sharepoint-server-2010/cc262485(v=office.14)) | [SharePoint Server 2010](/previous-versions/office/sharepoint-server-2010/cc262485(v=office.14)) | [SharePoint Server 2013](/sharepoint/install/hardware-software-requirements-2013) | [SharePoint Server 2016](/SharePoint/install/hardware-and-software-requirements)

-

-

- [SharePoint Server 2007](/previous-versions/office/sharepoint-2007-products-and-technologies/cc262787(v=office.12)) | [SharePoint Server 2010](/previous-versions/office/sharepoint-server-2010/cc262787(v=office.14)) | [SharePoint Server 2013](/SharePoint/install/software-boundaries-and-limits) | [SharePoint Server 2016](/sharepoint/install/software-boundaries-limits-2019)

-

-

- [SharePoint Server 2007](/previous-versions/office/sharepoint-2007-products-and-technologies/cc303420(v=office.12)) | [SharePoint Server 2010](/previous-versions/office/sharepoint-server-2010/cc303420(v=office.14)) | [SharePoint Server 2013](/SharePoint/upgrade-and-update/upgrade-to-sharepoint-server-2016) | [SharePoint Server 2016](/SharePoint/upgrade-and-update/upgrade-to-sharepoint-server-2016)

-

-### Create a SharePoint hybrid solution between SharePoint Online and on-premises

-If the answer to your migration needs is somewhere between the self-control offered by on-premises and the lower cost of ownership offered by SharePoint Online, you can connect SharePoint Server 2013 or 2016 farms to SharePoint Online through hybrids. [Learn about SharePoint hybrid solutions](https://support.office.com/article/4c89a95a-a58c-4fc1-974a-389d4f195383.aspx)

-

-If you decide that a hybrid SharePoint Server farm will benefit your business, familiarize yourself with the existing types of hybrids and how to configure the connection between your on-premises SharePoint farm and your Microsoft 365 subscription.

-

-One good way to see how this works is to create a Microsoft 365 dev/test environment, which you can set up with [Test Lab Guides](m365-enterprise-test-lab-guides.md). After you get a trial or purchased Microsoft 365 subscription, you can create the site collections, webs, and document libraries in SharePoint Online to which you can migrate data. You can migrate manually, by use of the Migration API, or, if you want to migrate My Site content to OneDrive for Business, through the hybrid wizard.

-

-> [!NOTE]

-> Remember that to use the hybrid option, your SharePoint 2007 farm will need to be upgraded, on-premises, to either SharePoint Server 2013 or SharePoint Server 2016.

-

-## Related topics

-[Troubleshoot and resume upgrade (Office SharePoint Server 2007)](/previous-versions/office/sharepoint-2007-products-and-technologies/cc262967(v=office.12))

-

-[Troubleshoot upgrade issues (SharePoint Server 2010)](/previous-versions/office/sharepoint-server-2010/cc262967(v=office.14))

-

-[Troubleshoot database upgrade issues in SharePoint 2013](/SharePoint/upgrade-and-update/troubleshoot-database-upgrade-issues-in-sharepoint-2013)

-

-[Search for Microsoft Partners to help with Upgrade](https://go.microsoft.com/fwlink/?linkid=841249)

-

-[Resources to help you upgrade from Office 2007 servers and clients](upgrade-from-office-2007-servers-and-products.md)

-description: "This article contains information for users using SharePoint Server 2007 to help them plan their upgrade."

-# SharePoint 2007 migration options to consider

-*This article applies to both Microsoft 365 Enterprise and Office 365 Enterprise.*

-Microsoft SharePoint 2007 and SharePoint Server 2007 have reached end of support. It's time to upgrade! This article provides information about your migration options.

-

-## Common upgrade strategies for SharePoint

-There are multiple methods to upgrade a SharePoint Server environment. If you have a Microsoft Office SharePoint Server 2007 farm, here are some examples of the upgrade methods:

-

-

-

-

-

-

-

-

-

-What works best for you?

-

-Your knowledge of what your farm does and is used for is a tactical strength when it comes to upgrade. The way people use the SharePoint Farm will help you choose from your options.

-

-> [!TIP]

-> Microsoft Office SharePoint Server 2007 also has a gradual upgrade not covered here. To see a list of step-specific upgrade articles see the [SharePoint Server 2007 end of support Roadmap](sharepoint-2007-end-of-support.md).

-

-Remember to check the [Product Lifecycle](https://support.microsoft.com/lifecycle/search) and System Requirements for whatever version of SharePoint you're upgrading to. This is so you'll be aware when the next upgrade will be necessary (for example, if you pause at a legacy product like SharePoint Server 2010 to plan for more upgrades, be sure you know its end of support date), and to be certain you have hardware that supports your plan.

-

-If you're planning to transition some, or all, of your SharePoint sites to Microsoft 365 in the Cloud, this is a time to bookmark a link to the [Microsoft 365 and Office 365 service descriptions](/office365/servicedescriptions/office-365-service-descriptions-technet-library). You'll need the Service Descriptions to learn about SharePoint Online features and how they might differ from on-premises SharePoint Server. Upgrade functional Microsoft Office SharePoint Server 2007 farms. If your installation has sites that are broken, fix them prior to upgrade.

-

-## A note about managing risk

-Methods like 'side-by-side' are important in the scheme of upgrade logic. When you upgrade side by side, you maintain your Microsoft Office SharePoint Server 2007 farm, but build up a farm the next version from it (SharePoint Server 2010) on new hardware. This helps in three ways:

-

-1. You have a place to take backups of your Microsoft Office SharePoint Server 2007 databases to upgrade them separately, by using database attach.

-

-2. If you figure out that only a few critical document libraries and other information are in use on your Microsoft Office SharePoint Server 2007 farm, you can choose to manually move data from Microsoft Office SharePoint Server 2007 to SharePoint Server 2010, or take only specific sites and webs to the next version (which can make your job easier).

-

-3. The less you do to the Microsoft Office SharePoint Server 2007 server farm, directly, the safer the data that farm contains as you upgrade.

-

-Methods like In-Place upgrade will act directly on your Microsoft Office SharePoint Server 2007 farm, giving you fewer easy options to abandon a path and begin again with your pristine environment. As much as possible, build in some safety measures (like taking and testing backups of the original environment). For example, if your Microsoft Office SharePoint Server 2007 farm is virtual, and is duplicated for the purposes of backup and restore, then back-up and restore the most current databases prior to your service window for the upgrade. Knowing that you have the option to restore database backups will not only give you a failsafe, it can give you peace of mind.

-

-> [!TIP]

-> Best practices documents for upgrade exist for [Microsoft Office SharePoint Server 2007](/previous-versions/office/sharepoint-2007-products-and-technologies/cc261992(v=office.12)), [SharePoint Server 2010](/previous-versions/office/sharepoint-server-2010/cc261992(v=office.14)), [SharePoint Server 2013](/SharePoint/upgrade-and-update/best-practices-for-upgrading-from-sharepoint-2010-to-sharepoint-2013), and [SharePoint Server 2016](/SharePoint/upgrade-and-update/best-practices-for-upgrade). You can also search for [Microsoft Partners](https://partnercenter.microsoft.com/pcv/search) who have experience with upgrades or Microsoft 365 migrations.

-

-## Make your plan

-If you need to upgrade, you need a plan, and one-size doesn't fit all in these cases. Your plan may be as simple as 'Create a Microsoft 365 subscription with SharePoint Online, register a domain, and redirect people to save their files there'. And it may not be. That decision is yours, and it's down to what you and your users really need.

-

-> [!NOTE]

-> It's risky to run on software whose lifecycle has ended. Products that are out of support are no longer patched when issues are found. This also means that if new security threats arise, there will be no security patches or fixes because the end-of-lifecycle products are no longer supported. Please avoid that situation!

-

-### First, know your farm

-When upgrading, your decision-making should be based on what your farm does for your organization. What need does it satisfy? What's its role? Each farm in your company may have a different role. Some of your SharePoint farms may be *critical*, some may be file archives--there for safe-keeping. Or, if your farm fills many roles at once, then you may need to know what site collections, webs, or even document libraries do, any customizations, and how important they are. Analyzing your data at this level may seem like much work, but it saves time and effort to master your domain before you upgrade, or migrate, it. Once you know all the moving parts, and the most important bits, you'll also know what you've outgrown and can leave behind. That knowledge will only benefit you going forward.

-

-So, what are users saying is most important about your SharePoint Server farm?

-

-

-

-

-

-

-

-If you run something essential to your business from your SharePoint farm, say it acts like a large catalog of critical data about client service requirements, you may put a tick beside 'Critical apps', but also 'Availability'--that is, your business would be impacted if you couldn't use SharePoint for a while. Likewise, you might check 'Customizations' because the critical services your farm offers are based on custom code, site definitions, or many customizations that work together.

-

-If SharePoint met those needs without your involvement outside of using what's built in to the software, and you generally update it and carry out normal administration and maintenance, you may have chosen 'Built-in SharePoint'--this may also be your reason for sitting on an older version of SharePoint. In other words, it already does what you need it to and you haven't needed to upgrade until now, at Microsoft Office SharePoint Server 2007 end of support.

-

-When you bullet-list these things, you create criteria for your upgrade. In other words, any upgrade would have to meet this bar to be considered. This gives you a way to rule out methods that don't currently fit your needs.

-

-### A simple sample plan

-There may need to be wider consensus with leadership and other admins on the path your SharePoint Upgrade will take. SharePoint Server Administrators often cooperate with Microsoft SQL Server admins, work with Networking and Security teams, and more. Where there are many stakeholders, you may need to build agreement for, or adjust, your upgrade and migration plan. For example, if you migrate data so that part of your company uses SharePoint Online in Microsoft 365, there will likely need to be performance tuning or testing inside your network. Affected teams should be informed ahead of time.

-

-In my simple sample, I show a SharePoint administrator's proposal and then list out the plan that all the stakeholders agreed upon. For clarity, document your agreements and decisions.

-

-The plan starts after an in-depth analysis of a farm, and tries to identify the role of the farm, pain points, and other important information that will lead to narrowing down some upgrade options. Afterward, an upgrade proposal is made by SharePoint administrator, and stakeholders agree on an action plan.

-

-My 'most important' bullet list:

-

-

-

-

-

-

-

-

- **My upgrade and migration choices:**

-

-| Yes | No |

-|:--|:--|

-|Upgrade databases with database attach <br/> |In-place upgrade <br/> |

-|Upgrade with farms side by side <br/> |Hybrid Upgrade <br/> |

-|Migration API to SPO in Microsoft 365 (for personal site data) <br/> |SharePoint Hybrid (not needed yet) <br/> |

-|Some manual data migrations to SharePoint Online for critical data <br/> |FastTrack wizard upgrade to Microsoft 365 <br/> |

-

- **My proposed plan:**

-

-Upgrade on-premises, with versions of SharePoint side-by-side, some virtualized, so that we can upgrade the databases first. Go from SharePoint 2007 to SharePoint 2010. Admins and Devs test the resulting farm. Users test the resulting farm. Fix any show-stopping issues during this time. Again, side-by-side, upgrade SharePoint 2010 databases to SharePoint 2013. Test. User test/pilot. Fix any show-stopping issues during this time.

-

-

-

-

-Otherwise, continue with a side-by-side upgrade to SharePoint Server 2016.

-

-> [!NOTE]

-> In between recommendations made by the administrators planning the upgrade and the actual process are the conversations that happen with other stakeholders on which the upgrade relies. For example, sometimes economics force administrators to change their plans. Whatever the final decision is, you should document what the agreed-upon plan is, going forward. It might look something like this:

-

- **My action plan:**

-

-On-premises, we use a virtual environment to build default SharePoint Server 2010, and 2013. SharePoint Server 2016 will be built on new hardware that meets system requirements for 2016. We will do database attaches to upgrade databases from SharePoint 2007 through all versions between it and SharePoint Server 2016. Core customizations are being recreated for and tested in the SharePoint Server 2016 environment at this time, if native features don't already meet our needs. If we are successful, we will have an on-premises farm on new hardware with upgraded databases, and fewer customizations. We'll attach the upgraded content databases to new site collections in SharePoint Server 2013, test, user test/pilot, and then do a DNS cut-over to the new SharePoint Server 2016 environment for live use.

-

-

-

-

-More detailed steps, or a number of links to specific upgrade directions should follow a plan. The MOSS 2007 computer should not be decommissioned, and virtual environments should be maintained for the sake of comparison; however, the upgrade will be complete when users are redirected to SharePoint Server 2016.

-

-Often major factors in choosing a method are the total cost of the upgrade and the cost in time (you'll see more on this in the SharePoint Migration Roadmap article). However, planning ahead will benefit you greatly in setting expectations, choosing wisely, and framing what success will look like.

-

-## Related links

-[Resources to help you upgrade from Office 2007 servers and clients](upgrade-from-office-2007-servers-and-products.md)

-

-[Microsoft Lifecycle Policy and Lifecycle search](https://support.microsoft.com/lifecycle)

-

-[Search for Microsoft Partners who can help with upgrade or migration](https://partnercenter.microsoft.com/pcv/search)

-description: As an admin, find help to set up parts of Skype for Business Online, including your network, meetings and IM, and external access for users.

-# Skype for Business Online in Office 365 - Admin Help

-## We're here to help!

-As an admin for Office 365 for business, you get free access to our knowledgeable support agents. If you don't find the information you need on this web site, **[Contact support for business products - Admin Help](https://support.office.com/article/32a17ca7-6fa0-4870-8a8d-e25ba4ccfd4b)**

-

-## Let your users contact external Skype or Skype for Business users

-You can let people who are using Skype for Business contact users from outside your organization and add them to their list of Skype for Business contacts. After they add them to their contact list, they can see if they are online and IM with them, hold meetings and share desktops. For instructions see:

-

-

-

-## Improve call and video quality

-Are your users experiencing dropped calls? Is the quality of audio, video, and application sharing poor? Skype for Business is greatly impacted by the quality of end-to-end network connectivity. For the best experience, it is important to make sure there is a high-quality connection between your company network and Skype for Business Online. To learn more, see **[Tune Skype for Business Online performance](tune-skype-for-business-online-performance.md)**.

-

-Also see:

-

-

-

-## Set up Skype for Business Online

-

-

-

-

-## Fix problems for your users

-

-

-

-

-

-

-## Help your users get started quickly!

-

-

-

-

-

- **For more articles for users, see [Skype for Business help](https://support.office.com/article/4fbe07ce-6b15-4a06-bcf0-baea57890410).**

-

-description: This article provides links for system administrators planning for network bandwidth requirements or improving the performance of Skype for Business Online.

-# Tune Skype for Business Online performance

-This article provides links for system administrators who want to plan for network bandwidth requirements, or who need to improve the performance of Skype for Business Online.

-

-## Fine tuning Skype for Business Online performance

-## More ways to improve Skype for Business Online performance

-## Articles on setting up Skype for Business Online

-## See also

-[Network planning and performance tuning for Office 365](network-planning-and-performance.md)

-

-[Optimizing your network for Skype for Business Online](/skypeforbusiness/optimizing-your-network/optimizing-your-network)

-description: Find information and resources to upgrade from Lync Server 2013. Support ends April 11, 2023.

-# Upgrading from Lync Server 2013

-Microsoft Lync Server 2013 will reach end of support on **April 11, 2023**. This article provides resources to help you upgrade your existing Lync Server deployment to Microsoft Teams or Skype for Business on-premises.

-## What is *end of support*?

-Most Microsoft products have a support lifecycle, during which they get new features, bug fixes, security fixes, and so on. After the end-of-support date, the product doesn't stop working, but Microsoft no longer provides:

-That means there will be no further updates, patches, or fixes for the product (including security patches/fixes). Microsoft Support will have fully shifted its support efforts to more recent versions.

-## Plan ahead

-Check the dates that support ends on the [Product Lifecycle site](/lifecycle/products/microsoft-lync-server-2013). Plan your upgrades or migrations with these dates in mind. Remember that your product *won't stop working* at the date listed. But because your installation will no longer be patched after that date, you'll want to plan a smooth transition to the next version of the product. The table below lists the options available to you.

-|End of support product|Supported|Recommended|

-||||

-|Lync Server 2013|Upgrade to Skype for Business Server 2015 or 2019|Upgrade to Microsoft Teams

-## What's next?

-We recommend upgrading to Microsoft Teams. Microsoft Teams extends the capabilities of Lync Server, bringing together chat, meetings, calling, collaboration, app integration, and file storage into a single interface. Teams helps streamline the way users get things done, improving user satisfaction and accelerating business outcomes. WeΓÇÖre continually expanding TeamsΓÇÖ capabilities to enable you to communicate and collaborate in new ways, break down organizational and geographical barriers, and drive efficiency in process and decision making.

-If you can't upgrade to Microsoft Teams, you can upgrade to Skype for Business Server 2015 or 2019. A key planning consideration to know is that both of these products will reach end of support on October 14, 2025. For more information, see the following support lifecycle pages:

-### Upgrade to Microsoft Teams

-We have detailed guidance on upgrading to Microsoft Teams from your on-premises deployment. First, let's cover some key technical requirements. You will need to establish hybrid connectivity, which will enable you to move your users to Teams. [Plan hybrid connectivity](/SkypeForBusiness/hybrid/plan-hybrid-connectivity) gives an overview of setting up a hybrid environment. Even though the article is focused on Skype for Business, all the concepts apply to Lync Server 2013 as well. See the [server version requirements](/SkypeForBusiness/hybrid/plan-hybrid-connectivity#server-version-requirements) section for Lync Server 2013-specific details.

-You also need to ensure that your Lync Server 2013 deployment is fully up to date. We publish a [list of all the latest updates for Lync Server 2013](https://support.microsoft.com/topic/updates-for-lync-server-2013-a2a042ac-79f0-2665-7453-0a541fb25164) However, the following update is a pre-requisite for an upgrade to Microsoft Teams:

-Even though the user experience in Microsoft Teams is far richer and superior to Lync, it is also dramatically different. Therefore, you'll also need to prepare your organization and your users to ensure a rapid adoption of Microsoft Teams. We have a wealth of information available on how to prepare your organization, plan your upgrade to Teams, and ensure a successful rollout.

-**We recommend that you start at our [Teams upgrade portal](/MicrosoftTeams/upgrade-skype-teams)** where you can find technical information, training resources, links to Ignite sessions, available help resources, case studies and more.

-### Upgrade to Skype for Business Server

-The path to Skype for Business Server is going to be different depending on the version you choose to upgrade to. Skype for Business Server 2015 supports an in-place upgrade from Lync Server 2013. On the other hand, in order to upgrade to Skype for Business Server 2019, you first will need to introduce Skype for Business Server 2019 to your Lync Server 2013 installation via adding one or more new servers, and then transfer operations to the new 2019 servers you've added.

-One important point to consider is that the current support phase for each product: Skype for Business 2019 is in mainstream support and Skype for Business 2015 is currently in extended support. Therefore, we recommend upgrading to Skype for Business Server 2019. To learn more about the difference between mainstream and extended support, see [Fixed Lifecycle Policy](/lifecycle/policies/fixed).

-See the following resources for detailed information about each upgrade scenario.

-description: This article provides resources to help you upgrade from Office 2007 servers and clients, as support for Office 2007 has ended.

-# Resources to help you upgrade from Office 2007 servers and clients

-*This article applies to both Microsoft 365 Enterprise and Office 365 Enterprise.*

-If you're using Office 2007 products and services, be aware that support for these applications has ended. Consider moving to the Microsoft cloud, starting with Microsoft 365. Use this article as a starting point to review your options and plan your upgrade.

-

-## Office 2007 planning roadmaps

-

-Support has ended for Office 2007 products and services. The following roadmaps can help you plan your upgrade now.

-|**Planning content**|**Date support ended**|

-|:--|:--|

-|[Office 2007 end of support roadmap](/DeployOffice/office-2007-end-support-roadmap) <br/> |October 10, 2017 <br/> |

-|[Exchange 2007 end of support roadmap](exchange-2007-end-of-support.md) <br/> |April 11, 2017 <br/> |

-|[SharePoint Server 2007 end of support roadmap](sharepoint-2007-end-of-support.md) <br/> |October 10, 2017 <br/> |

-|[Project Server 2007 end of support roadmap](project-server-2007-end-of-support.md) <br/> |October 10, 2017 <br/> |

-|[Upgrade from Office Communications Server](/SkypeForBusiness/plan-your-deployment/upgrade) <br/> |January 8, 2018 <br/> |

-|[PerformancePoint Server 2007 end of support roadmap](pps-2007-end-of-support.md) <br/> |January 9, 2018 <br/> |

-

-After support ends for a Microsoft product, there are no more:

-Whether you're an enterprise organization or an individual home user, you have several options to consider.

-## I'm a home user. What do I do?

-If you're using Office 2007 products and applications at home, see [this information](plan-upgrade-previous-versions-office.md#im-a-home-user-what-do-i-do).

-

-## Related topics

-[Video: What is Microsoft 365?](https://support.office.com/article/847caf12-2589-452c-8aca-1c009797678b.aspx)

-

-[Microsoft Lifecycle Policy](/lifecycle/)

-[Plan your upgrade from Office 2007 or Office 2010 servers and clients](plan-upgrade-previous-versions-office.md)

-description: Start planning your upgrade from Office 2010 servers and client applications, as support is ending soon and custom support agreements aren't available.

-# Resources to help you upgrade from Office 2010 servers and clients

-*This article applies to both Microsoft 365 Enterprise and Office 365 Enterprise.*

-Office 2010 and Exchange 2010 reached their end of support on **October 13, 2020**.

-SharePoint 2010 and Project Server 2010 will reach their end of support on **April 13, 2021**.

-While you plan your upgrade, consider moving to Microsoft 365.

-For a visual summary of the upgrade, migration, and move-to-the-cloud options for Office 2010 clients and servers and Windows 7, see the [end of support poster](https://download.microsoft.com/download/2/7/d/27da4118-32ae-4ffe-90d8-a61e7c895ba0/Office2010Windows7EndOfSupport.pdf).

-[](https://download.microsoft.com/download/2/7/d/27da4118-32ae-4ffe-90d8-a61e7c895ba0/Office2010Windows7EndOfSupport.pdf)

-This one-page poster summarizes the various paths you can take to handle Office 2010 client and server products and Windows 7 from reaching end of support. Preferred paths and option support in Microsoft 365 Enterprise are highlighted.

-You can also [download](https://download.microsoft.com/download/2/7/d/27da4118-32ae-4ffe-90d8-a61e7c895ba0/Office2010Windows7EndOfSupport.pdf) this poster and print it in letter, legal, or tabloid (11 x 17) format.

-## Office 2010 client and server upgrade planning

-|For this product|With this end of support date|See this resource|

-||||

-|Office 2010 (including Word 2010, Excel 2010, PowerPoint 2010, and Outlook 2010)|October 13, 2020 |[Office 2010 end of support roadmap](/DeployOffice/office-2010-end-support-roadmap)|

-|Exchange Server 2010|October 13, 2020|[Exchange 2010 end of support roadmap](exchange-2010-end-of-support.md)|

-|SharePoint 2010 or SharePoint Server 2010|April 13, 2021|[Upgrading from SharePoint 2010](upgrade-from-sharepoint-2010.md)|

-|Project Server 2010|April 13, 2021|[Project Server 2010 end of support roadmap](project-server-2010-end-of-support.md)|

-|Lync Server 2010|April 13, 2021|[Plan to upgrade to Skype for Business Server](/skypeforbusiness/plan-your-deployment/upgrade)|

-## I'm a home user. What do I do?

-If you use Office 2010 products and applications at home, see [this information](plan-upgrade-previous-versions-office.md#im-a-home-user-what-do-i-do).

-## Related topics

-[Video: What is Microsoft 365?](https://support.office.com/article/847caf12-2589-452c-8aca-1c009797678b.aspx)

-[Microsoft Lifecycle Policy](/lifecycle/)

-[Plan your upgrade from Office 2007 or Office 2010 servers and clients](plan-upgrade-previous-versions-office.md)

-description: Find information and resources to upgrade from SharePoint 2010 and SharePoint Server 2010. Support for both ends April 13, 2021.

-# Upgrading from SharePoint 2010

-*This article applies to both Microsoft 365 Enterprise and Office 365 Enterprise.*

-Microsoft SharePoint 2010 and SharePoint Server 2010 will reach end of support on **April 13, 2021**. This article provides resources to help you migrate your existing SharePoint Server 2010 data to SharePoint Online in Microsoft 365 or upgrade your on-premises SharePoint Server 2010 environment.

-## What is *end of support*?

-Most Microsoft products have a support lifecycle, during which they get new features, bug fixes, security fixes, and so on. After the end-of-support date, the product doesn't stop working, but Microsoft no longer provides:

-That means there will be no further updates, patches, or fixes for the product (including security patches/fixes). Microsoft Support will have fully shifted its support efforts to more recent versions.

-As the end of support of SharePoint Server 2010 approaches, delete data you no longer need before you upgrade the product and migrate your important data.

-> [!NOTE]

-> A software lifecycle typically lasts for ten years from the initial release. [Microsoft solution providers](https://go.microsoft.com/fwlink/?linkid=841249) can help you upgrade to the next version of the software or migrate to Microsoft 365 migration (or both). Make sure you're aware of end-of-support dates for critical underlying technologies as well, particularly for the version of Microsoft SQL Server you're using with SharePoint. For more information, see [Fixed Lifecycle Policy](https://support.microsoft.com/help/14085).

-## Plan ahead

-Check the dates that support ends on the [Product Lifecycle site](https://support.microsoft.com/lifecycle/search?alpha=SharePoint%20Server%202010). Plan your upgrades or migrations with these dates in mind. Remember that your product *won't stop working* at the date listed. But because your installation will no longer be patched after that date, you'll want to plan a smooth transition to the next version of the product.

-This matrix helps plot a course among migration options:

-|End of support product|Good |Best|

-||||

-|SharePoint Server 2010|SharePoint Server 2013 (on-premises)|SharePoint Online|

-||SharePoint Server 2013 hybrid with SharePoint Online|SharePoint Server 2016 (on-premises)|

-|||SharePoint Cloud Hybrid Search|

-If you choose an option on the low end of the scale (good), you'll need to start planning for another upgrade soon after your migration from SharePoint Server 2010.

-Here are the three paths you can take to avoid the end of support for SharePoint Server 2010.

-

-> [!NOTE]

-> End of support for SharePoint Server 2010 and SharePoint Foundation 2010 is currently scheduled for April 13, 2021. But make sure to check the [Product Lifecycle site](https://support.microsoft.com/lifecycle) for the most-current dates.

-## What's next?

-SharePoint Server 2013 and SharePoint Foundation 2013 can be installed on-premises on your own servers. Or you can use SharePoint Online, which is an online service that's part of Microsoft 365. You can choose to:

-Consider the hidden costs of maintaining a server farm, including maintaining or migrating customizations and upgrading hardware. If you've accounted for these factors, it will be easier to upgrade on-premises. If you run your farm on legacy SharePoint Servers without heavy customization, you could benefit from a planned migration to SharePoint Online. For an on-premises SharePoint Server environment, you can also consider moving some data in SharePoint Online to reduce hardware management overhead.

-> [!NOTE]

-> SharePoint administrators can create a Microsoft 365 Subscription, set up new SharePoint Online sites, and then cut away from SharePoint Server 2010 cleanly, taking only essential documents to the fresh sites. Then, any remaining data can be drained from the SharePoint Server 2010 site into on-premises archives.

-|SharePoint Online|SharePoint Server on-premises|

-|||

-|High cost in time (plan/execution/verification)|High cost in time (plan/execution/verification)|

-|Lower cost in funds (no hardware purchases)|Higher cost in funds (hardware purchases)|

-|One-time cost in migration|One-time cost repeated per future migration|

-|Low total cost of ownership/maintenance|High total cost of ownership/maintenance|

-A one-time move to Microsoft 365 will have a higher cost while you organize data and decide what to take to the cloud and what to leave behind. But after your data is migrated, future upgrades will be automatic, as you'll no longer need to manage hardware and software updates. And the up time of your farm will be backed by a [Microsoft service level agreement (SLA)](/office365/servicedescriptions/office-365-platform-service-description/service-level-agreement).

-### Migrate to SharePoint Online

-Make sure SharePoint Online offers all the features you need. See [SharePoint service description](/office365/servicedescriptions/sharepoint-online-service-description/sharepoint-online-service-description).

-You can't migrate directly from SharePoint Server 2010 (or SharePoint Foundation 2010) to SharePoint Online. So much of the migration work is manual. But this stage gives you the opportunity to prune data and sites that are no longer needed before the move. You can archive other data into storage.

-Remember that SharePoint Server 2010 and SharePoint Foundation 2010 won't stop working at end of support. So administrators can have a period when SharePoint is still running if their customers forget to move some of their data.

-If you upgrade to SharePoint Server 2013 or SharePoint Server 2016 and decide to put data into SharePoint Online, you might use the [SharePoint Migration API](https://support.office.com/article/Upload-on-premises-content-to-SharePoint-Online-using-PowerShell-cmdlets-555049c6-15ef-45a6-9a1f-a1ef673b867c?ui=en-US&amp;rs=en-US&amp;ad=US) to migrate information into OneDrive for Business.

-|SharePoint Online advantage|SharePoint Online disadvantage|

-|||

-|Microsoft supplies SPO hardware and all hardware administration.|Available features may differ between SharePoint Server on-premises and SPO.|

-|You're the SharePoint admin or global admin of your subscription and can assign administrators to SPO sites.|Some actions available to a farm administrator in SharePoint Server on-premises don't exist (or aren't necessary) in the SharePoint Administrator role in Microsoft 365. But SharePoint Administration, Site Collection Administration, and Site Ownership are local to your org.|

-|Microsoft applies patches, fixes, and updates to underlying hardware and software, including SQL servers on which SharePoint Online runs.|Because there's no access to the underlying file system in the service, customization is limited.|

-|Microsoft publishes [service level agreements](/office365/servicedescriptions/office-365-platform-service-description/service-level-agreement) and moves quickly to resolve service-level incidents.|Backup and restore and other recovery options are automated by the service in SharePoint Online. Backups are overwritten if not used.|

-|Security testing and server performance tuning are carried out continuously in the service by Microsoft.|Changes to the user interface and other SharePoint features are installed by the service and may need to be toggled on or off.|

-|Microsoft 365 meets many industry standards: [Microsoft compliance offerings](/compliance/regulatory/offering-home).|[FastTrack](https://go.microsoft.com/fwlink/?linkid=518597) assistance for migration is limited. <br/> Much of the upgrade will be manual or via the SPO Migration API described in the [SharePoint Online and OneDrive Migration Content Roadmap](/sharepointmigration/upload-on-premises-content-to-sharepoint-online-using-powershell-cmdlets).|

-|Microsoft Support engineers and datacenter employees don't have unrestricted admin access to your subscription.|There can be additional costs if hardware infrastructure needs to be upgraded to support the newer version of SharePoint or if a secondary farm is required for upgrade.|

-|Solution providers can help with the one-time job of migrating your data to SharePoint Online.|Not all changes to SharePoint Online are within your control. After migration, design differences in menus, libraries, and other features may temporarily affect usability.|

-|Online products are updated automatically across the service. Features may deprecate, but there's no true end of support lifecycle.|There's an end-of-support lifecycle for SharePoint Server or SharePoint Foundation as well as underlying SQL servers.|

-If you've decided to create a new Microsoft 365 site and will manually migrate data to it as is needed, check your [Microsoft 365 options](https://www.microsoft.com/microsoft-365/).

-### Upgrade SharePoint Server on-premises

-As of SharePoint Server 2019, upgrades must go *serially*. There's no way to upgrade from SharePoint Server 2010 to SharePoint Server 2016 or to SharePoint 2019 directly. Serial upgrade path:

-It will take time and planning to follow the entire path from SharePoint 2010 to SharePoint Server 2016. Upgrades involve costs for hardware (SQL servers must also be upgraded), software, and administration. Also, customizations may need to be upgraded or even abandoned. Be sure that you document critical customizations before you upgrade your SharePoint Server farm.

-> [!NOTE]

-> It's possible to maintain your end-of-support SharePoint 2010 farm, install a SharePoint Server 2016 farm on new hardware (so the separate farms run side-by-side), and then plan and execute a manual migration of content (for downloading and re-uploading content, for example). But there are potential pitfalls to these manual moves, such as documents coming from 2010 having a current last-modified account with the alias of the account that does the manual move. And some work must be done ahead of time, such as recreating sites, subsites, permissions, and list structures. Be sure to clean your environment prior to upgrade. Consider what data you can move into storage or no longer need. This can reduce the impact of migration. Be certain your existing farm is functional before you upgrade, and (certainly) before you decommission!

-Remember to review the *supported and unsupported upgrade paths*:

-If you have *customizations*, it's critical that you plan for each step in the migration path:

-|On-premises advantage|On-premises disadvantage|

-|||

-|Full control of all aspects of your SharePoint Farm (and its SQL), from the server hardware up.|All breaks and fixes are the responsibility of your company. But you can engage paid Microsoft Support if your product isn't past end of support.|

-|Full feature set of SharePoint Server on-premises with the option to connect your on-premises farm to a SharePoint Online subscription via hybrid.|Upgrade, patches, security fixes, hardware upgrades, and all maintenance of SharePoint Server and its SQL farm are managed on-premises.|

-|Full access for greater customization options than with SharePoint Online.|[Microsoft compliance offerings](/compliance/regulatory/offering-home) must be manually configured on-premises.|

-|Security testing and server performance tuning are carried out on your premises under your control.|Microsoft 365 may make features available to SharePoint Online that don't interoperate with SharePoint Server on-premise.|

-|Solution providers can help migrate data to the next version of SharePoint Server (and beyond).|Your SharePoint Server sites will not automatically use [SSL/TLS](/SharePoint/security-for-sharepoint-server/enable-tls-1-1-and-tls-1-2-support-in-sharepoint-server-2016) certificates as is seen in SharePoint Online.|

-|Full control of naming conventions and backup and restore and other recovery options in SharePoint Server on-premises.|SharePoint Server on-premises is sensitive to product lifecycles.|

-### Upgrade resources

-Begin by comparing hardware and software requirements. If your current environment doesn't meet basic requirements, you may have to upgrade the hardware in the farm or the SQL servers first.

-You may decide to move some of your sites to the "evergreen" hardware of SharePoint Online. Once you've made your assessment, follow supported upgrade paths and methods.

- [SharePoint Server 2010](/previous-versions/office/sharepoint-server-2010/cc262485(v=office.14)) | [SharePoint Server 2013](/sharepoint/install/hardware-software-requirements-2013) | [SharePoint Server 2016](/SharePoint/install/hardware-and-software-requirements)

- [SharePoint Server 2010](/previous-versions/office/sharepoint-server-2010/cc262787(v=office.14)) | [SharePoint Server 2013](/SharePoint/install/software-boundaries-and-limits) | [SharePoint Server 2016](/sharepoint/install/software-boundaries-limits-2019)

- [SharePoint Server 2010](/previous-versions/office/sharepoint-server-2010/cc303420(v=office.14)) | [SharePoint Server 2013](/SharePoint/upgrade-and-update/upgrade-to-sharepoint-server-2016) | [SharePoint Server 2016](/SharePoint/upgrade-and-update/upgrade-to-sharepoint-server-2016)

-### Create a hybrid solution with SharePoint Online and SharePoint Server on-premises

-A hybrid setup provides the best of both on-premises and online for some migration needs. You can connect SharePoint Server 2013, 2016, or 2019 farms to SharePoint Online to create a SharePoint hybrid: [Learn about SharePoint hybrid solutions](https://support.office.com/article/4c89a95a-a58c-4fc1-974a-389d4f195383.aspx).

-If a hybrid SharePoint Server farm is your migration goal, figure what sites and users to move online and which need to remain on-premises. Ranking your SharePoint Server farm content as high, medium, or low impact to your company can help with this decision. You may only need to share user accounts for login and the SharePoint Server search index with SharePoint Online. But this factor may not be clear until you look at how your sites are used. If your company later decides to migrate all your content to SharePoint Online, you can move all remaining accounts and data online and decommission your on-premises farm. Management/administration of the SharePoint farm will be done through Microsoft 365 consoles from that point on.

-Be sure to familiarize yourself with the existing types of hybrids and how to configure the connection between your on-premises SharePoint farm and your Microsoft 365 subscription.

-|Option|Description|

-|||

-|[Microsoft compliance offerings](/compliance/regulatory/offering-home).|[FastTrack](https://www.microsoft.com/fasttrack/microsoft-365) assistance for migration is limited.<br/><br/> Much of the upgrade will be manual or via the SPO Migration API described in the [SharePoint Online and OneDrive Migration Content Roadmap](/sharepointmigration/upload-on-premises-content-to-sharepoint-online-using-powershell-cmdlets).|

-|Microsoft Support engineers and datacenter employees don't have unrestricted admin access to your subscription.|There may be additional costs if hardware infrastructure needs to be upgraded to support the newer version of SharePoint, or if a secondary farm is required.|

-|Partners can assist with the one-time job of migrating your data to SharePoint Online.||

-|Online products are updated automatically across the service. Features may deprecate, but there's no true end of support.||

-If you've decided to create a new Microsoft 365 site and manually migrate data to it as is needed, check your [Microsoft 365 options](https://www.microsoft.com/microsoft-365/).

-### Upgrade SharePoint Server on-premises

-There's no way to skip versions in SharePoint Upgrades. That means upgrades go serially:

-To take the entire path from SharePoint 2007 to SharePoint Server 2016 will mean a significant investment of time and will involve hardware (SQL servers must also be upgraded), software, and administration costs. Customizations will need to be upgraded or abandoned, according to the criticality of the feature.

-> [!NOTE]

-> It's possible to maintain your end-of-life SharePoint 2007 farm, install a SharePoint Server 2016 farm on new hardware (so the separate farms run side-by-side), and then plan and execute a manual migration of content (for downloading and re-uploading content, for example). But there are some drawbacks to these manual moves, such as moves of documents replacing the last modified account with the alias of the account that does the manual move. And much work must be done ahead of time, such as recreating sites, subsites, permissions, and list structures. In any case, consider what data you can move into storage or no longer need to reduce the impact of migration.

-Make sure to clean your environment prior to upgrade. Be certain your existing farm is functional before you upgrade, and certainly before you decommission!

-Remember to review the *supported and unsupported upgrade paths*:

-If you have *customizations*, it's critical to plan your upgrade for each step in the migration path:

-|On-premises pro|On-premises con|

-|||

-|Full control of all aspects of your SharePoint Farm, from the server hardware up.|All breaks and fixes are the responsibility of your company. (But you can engage paid Microsoft Support if your product isn't past end of support.)|

-|Full feature set of SharePoint Server on-premises with the option to connect your on-premises farm to a SharePoint Online subscription via hybrid.|Upgrade, patches, security fixes, and all maintenance of SharePoint Server managed on-premises.|

-|Full access for greater customization.|[Microsoft compliance offerings](/compliance/regulatory/offering-home) must be manually configured on-premises.|

-|Security testing and server performance tuning is carried out on your premises under your control.|Microsoft 365 may make features available to SharePoint Online that don't interoperate with SharePoint Server on-premises.|

-|Partners can help migrate data to the next version of SharePoint Server (and beyond).|Your SharePoint Server sites will not automatically use [SSL/TLS](/SharePoint/security-for-sharepoint-server/enable-tls-1-1-and-tls-1-2-support-in-sharepoint-server-2016) certificates as is seen in SharePoint Online.|

-|Full control of naming conventions and backup and restore and other recovery options in SharePoint Server on-premises.|SharePoint Server on-premises is sensitive to product lifecycles.|

-### Upgrade resources

-Begin by knowing that you meet hardware and software requirements, then follow supported upgrade methods.

- [SharePoint Server 2010](/previous-versions/office/sharepoint-server-2010/cc262485(v=office.14)) | [SharePoint Server 2010](/previous-versions/office/sharepoint-server-2010/cc262485(v=office.14)) | [SharePoint Server 2013](/sharepoint/install/hardware-software-requirements-2013) | [SharePoint Server 2016](/SharePoint/install/hardware-and-software-requirements)

- [SharePoint Server 2007](/previous-versions/office/sharepoint-2007-products-and-technologies/cc262787(v=office.12)) | [SharePoint Server 2010](/previous-versions/office/sharepoint-server-2010/cc262787(v=office.14)) | [SharePoint Server 2013](/SharePoint/install/software-boundaries-and-limits) | [SharePoint Server 2016](/sharepoint/install/software-boundaries-limits-2019)

- [SharePoint Server 2007](/previous-versions/office/sharepoint-2007-products-and-technologies/cc303420(v=office.12)) | [SharePoint Server 2010](/previous-versions/office/sharepoint-server-2010/cc303420(v=office.14)) | [SharePoint Server 2013](/SharePoint/upgrade-and-update/upgrade-to-sharepoint-server-2016) | [SharePoint Server 2016](/SharePoint/upgrade-and-update/upgrade-to-sharepoint-server-2016)

-### Create a SharePoint hybrid solution between SharePoint Online and on-premises

-If the answer to your migration needs is somewhere between the control offered by on-premises and the lower cost of ownership offered by SharePoint Online, you can connect SharePoint Server 2013 or 2016 farms to SharePoint Online through hybrids. [Learn about SharePoint hybrid solutions](https://support.office.com/article/4c89a95a-a58c-4fc1-974a-389d4f195383.aspx)

-If you decide that a hybrid SharePoint Server farm will benefit your business, familiarize yourself with the existing types of hybrids and how to configure the connection between your on-premises SharePoint farm and your Microsoft 365 subscription.

-You may want to create a Microsoft 365 dev/test environment, which you can set up with [Test Lab Guides](m365-enterprise-test-lab-guides.md). After you get a trial or purchased Microsoft 365 subscription, you can create the site collections, webs, and document libraries in SharePoint Online to which you can migrate data. You can migrate manually, by use of the Migration API, or, if you want to migrate My Site content to OneDrive for Business, through the hybrid wizard.

-> [!NOTE]

-> To use the hybrid option, your SharePoint Server 2010 farm must first be upgraded on-premises to SharePoint Server 2013 or 2016. SharePoint Foundation 2010 and SharePoint Foundation 2013 don't support hybrid connections with SharePoint Online.

-## Summary of options for Office 2010 client and servers and Windows 7

-For a visual summary of the upgrade, migrate, and move-to-the-cloud options for Office 2010 clients and servers and Windows 7, see the [end of support poster](https://download.microsoft.com/download/2/7/d/27da4118-32ae-4ffe-90d8-a61e7c895ba0/Office2010Windows7EndOfSupport.pdf).

-[](https://download.microsoft.com/download/2/7/d/27da4118-32ae-4ffe-90d8-a61e7c895ba0/Office2010Windows7EndOfSupport.pdf)

-This poster illustrates the various paths you can take to avoid Office 2010 client and server products and Windows 7 end of support, with preferred paths and option supports in Microsoft 365 Enterprise highlighted.

-You can also [download](https://download.microsoft.com/download/2/7/d/27da4118-32ae-4ffe-90d8-a61e7c895ba0/Office2010Windows7EndOfSupport.pdf) this poster and print it in letter, legal, or tabloid (11 x 17) format.

-## Related articles

-[Resources to help you upgrade from Office 2007 or 2010 servers and clients](upgrade-from-office-2010-servers-and-products.md)

-[Overview of the upgrade process from SharePoint 2010 to SharePoint 2013](/SharePoint/upgrade-and-update/overview-of-the-upgrade-process-from-sharepoint-2010-to-sharepoint-2013)

-[Best practices for upgrading from SharePoint 2010 to SharePoint 2013](/SharePoint/upgrade-and-update/best-practices-for-upgrading-from-sharepoint-2010-to-sharepoint-2013)

-[Troubleshoot database upgrade issues in SharePoint 2013](/SharePoint/upgrade-and-update/troubleshoot-database-upgrade-issues-in-sharepoint-2013)

-[Search for Microsoft solution providers to help with your upgrade](https://go.microsoft.com/fwlink/?linkid=841249)

-[Updated Product Servicing Policy for SharePoint 2013](/SharePoint/product-servicing-policy/updated-product-servicing-policy-for-sharepoint-2013)

-[Updated Product Servicing Policy for SharePoint Server 2016](/SharePoint/product-servicing-policy/updated-product-servicing-policy-for-sharepoint-server-2016)

-description: Find information and resources to upgrade from SharePoint Server 2013 and SharePoint Foundation 2013. Support for both ends April 11, 2023.

-# Upgrading from SharePoint 2013

-Both Microsoft SharePoint Server 2013 and SharePoint Foundation 2013 will reach end of support on **April 11, 2023**. This article provides resources to help you migrate your existing SharePoint Server data to SharePoint Online in Microsoft 365 or upgrade your on-premises SharePoint 2013 environment. For the rest of this article, we'll use SharePoint 2013 to refer to both SharePoint Server 2013 and SharePoint Foundation 2013.

-## What is *end of support*?

-Most Microsoft products have a support lifecycle, during which they get new features, bug fixes, security fixes, and so on. After the end-of-support date, the product doesn't stop working, but Microsoft no longer provides:

-That means there will be no further updates, patches, or fixes for the product (including security patches/fixes). Microsoft Support will have fully shifted its support efforts to more recent versions.

-> [!NOTE]

-> A software lifecycle typically lasts for five years of mainstream support from the initial release, and potentially up to an additional 5 years of extended support. [Microsoft solution providers](https://go.microsoft.com/fwlink/?linkid=841249) can help you upgrade to the next version of the software or migrate to Microsoft 365 (or both). Make sure you're aware of end-of-support dates for critical underlying technologies as well, particularly for the version of Microsoft SQL Server you're using with SharePoint. For more information, see [Fixed Lifecycle Policy](https://support.microsoft.com/help/14085).

-## Plan ahead

-Check the dates that support ends on the Product Lifecycle site for [SharePoint Server 2013](/lifecycle/products/sharepoint-server-2013) and [SharePoint Foundation 2013](/lifecycle/products/sharepoint-foundation-2013). Plan your upgrades or migrations with these dates in mind. Remember that your product *won't stop working* at the date listed. But because your installation will no longer be patched after that date, you'll want to plan a smooth transition to the next version of the product. The table below lists the options available to you.

-|End of support product|Good|Better|Best|

-|||||

-|SharePoint Server 2013<BR>SharePoint Foundation 2013|Upgrade to SharePoint Server 2016 or 2019|Upgrade to SharePoint Server Subscription Edition|Migrate to SharePoint in Microsoft 365

-## What's next?

-We recommend migrating to SharePoint in Microsoft 365 to take advantage of the latest collaboration, intelligence, and security solutions in Microsoft 365. The modern experience features in Microsoft 365 are designed to be compelling, flexible, and performant.

-If you have a need to maintain an on-premises SharePoint deployment, we recommend a hybrid deployment that will enable you to migrate as much of SharePoint functionality as you can to SharePoint in Microsoft 365. See [SharePoint hybrid](/sharepoint/hybrid/hybrid) to learn about and plan for a hybrid implementation.

-### Migrate to SharePoint in Microsoft 365

-You can use the SharePoint Migration Tool (SPMT) to migrate your sites and content to SharePoint in Microsoft 365. We have an extensive library of content that can help you plan ahead, perform your migration, and troubleshoot any issues you may come across. [Overview of the SharePoint Migration Tool](/sharepointmigration/introducing-the-sharepoint-migration-tool) is a good place to start.

-### Upgrade to SharePoint Server Subscription Edition

-Even though there isn't a direct path to upgrade from SharePoint 2013 to the Subscription Edition, this still is the second best option. The primary reason is that SharePoint Server Subscription Edition introduces a continuous update model that eliminates the need to release new major versions of SharePoint Server going forward.

-To upgrade to Subscription Edition, you must be running SharePoint Server 2016 or 2019. Since there also isn't a direct path from SharePoint 2013 to 2019 either, your best option is to upgrade to 2016 first and then upgrade to Subscription Edition. See the links below to learn more about and plan your upgrade to Subscription Edition:

-Even if you have a need to maintain an on-premises SharePoint deployment, we recommend that you migrate parts of your sites or content to Microsoft 365 with [SharePoint hybrid](/sharepoint/hybrid/hybrid) implementation to start taking advantage of the modern collaboration experiences, security and compliance features in Microsoft 365.

-### Upgrade to SharePoint Server 2016 or 2019

-Both SharePoint Server 2016 and 2019 are supported platforms if you plan to maintain your on-premises SharePoint deployment beyond the end of support for 2013. However, **both versions will reach end of support on July 14, 2026**. This means that you will need to plan another upgrade within 3 years after the end of support date for 2013. Here are the support lifecycle pages for both products:

-To learn more and plan your upgrade, see the following articles:

-Even if you have a need to maintain an on-premises SharePoint deployment, we recommend that you migrate parts of your sites or content to Microsoft 365 with [SharePoint hybrid](/sharepoint/hybrid/hybrid) implementation to start taking advantage of the modern collaboration experiences, security and compliance features in Microsoft 365.

-description: Plan your upgrade from Office 2013 clients and servers, because support ends on April 11, 2023.

-# Resources to help you upgrade from Office 2013 clients and servers

-If you're using Office 2013 clients and servers, be aware that ***support ends on April 11, 2023***. If you haven't already begun to upgrade from them to newer versions, we recommend you start now.

-As you plan your upgrade, consider moving to Microsoft 365.

-## Upgrade planning resources

-The following table provides links to planning resources to help you upgrade from these Office 2013 clients and servers.

-|Product|Planning resource|

-|||

-|Office 2013 (desktop apps)<br/>Project 2013<br/>Visio 2013|[Plan an upgrade from older versions of Office to Microsoft 365 Apps](/deployoffice/endofsupport/plan-upgrade-older-versions-office)|

-|Exchange Server 2013|[Exchange 2013 end of support roadmap](exchange-2013-end-of-support.md)|

-|SharePoint Server 2013 <br/> SharePoint Foundation 2013|[Upgrading from SharePoint 2013](upgrade-from-sharepoint-2013.md)|

-|Project Server 2013|[Project Server 2013 end of support roadmap](project-server-2013-end-of-support.md)|

-|Lync Server 2013|[Upgrading from Lync Server 2013](upgrade-from-lync-2013.md)|

-We also recommend business and enterprise customers use the deployment benefits provided by Microsoft and Microsoft Certified Partners, including [Microsoft FastTrack](https://www.microsoft.com/fasttrack) for cloud migrations.

-> [!NOTE]

-> If you use Office 2013 products and applications at home, [review this information](plan-upgrade-previous-versions-office.md#im-a-home-user-what-do-i-do) for your upgrade choices.

-## Related articles

-description: This article contains information for using lean popouts to improve message download performance in Outlook on the web.

-# Use lean popouts to reduce memory used when reading mail messages

-This article contains information for improving message download performance in Outlook on the web. This article is part of the [Network planning and performance tuning for Office 365](./network-planning-and-performance.md) project.

-

-As an Office 365 **Application Admin**, **Global admin**, or **User Admin**, you can configure Outlook on the web to deliver _lean popouts_, a smaller, less memory-intensive version of certain email messages in Microsoft Edge or Internet Explorer. When lean popouts are configured for Outlook on the web, server-side rendered components are loaded that optimize performance.

-

-> [!NOTE]

-> As of March 2018, lean popouts are not available for messages that specify usage rights restrictions, such as Information Rights Management (IRM).

-

-These features will continue to work in the main window but are not available in lean popouts:

-

-

-

-## To configure lean popouts for all users within your Office 365 organization

-

-1. [Connect to Exchange Online PowerShell](/powershell/exchange/connect-to-exchange-online-powershell).

-

-2. Run the [Set-OrganizationConfig](/powershell/module/exchange/set-organizationconfig) cmdlet with the LeanPopoutEnabled parameter as follows:

- ```powershell

- Set-OrganizationConfig -LeanPopoutEnabled <$true |$false >

- ```

- For example, to enable lean popouts for all users in your organization:

-

- ```powershell

- Set-OrganizationConfig -LeanPopoutEnabled $true

- ```

- To disable lean popouts for all users in your organization:

- ```powershell

- Set-OrganizationConfig -LeanPopoutEnabled $false

- ```

-|Audit: logs and events |**Audit** logs for all events: search and export Microsoft 365 service events for security and compliance investigations <ol><li>use the [compliance admin center](https://compliance.microsoft.com/auditlogsearch)<li>search audit logs for "loop" or "fluid"<li>further filter exported results by "SourceFileExtension":"loop" or "SourceFileExtension":"fluid"|**Audit** logs for all events: search and export Microsoft 365 service events for security and compliance investigations <ol><li>use the [compliance admin center](https://compliance.microsoft.com/auditlogsearch)<li>search audit logs for Loop ApplicationID `a187e399-0c36-4b98-8f04-1edc167a0996`|

- :::image type="content" source="images/85f56004dc6bd1679c3d2c063e36cb80.png" alt-text="The Check Results Summary page" lightbox="images/85f56004dc6bd1679c3d2c063e36cb80.png":::

- :::image type="content" source="images/app-settings.png" alt-text="The application settings pane in the Microsoft Defender portal." lightbox="images/app-settings.png":::

- > 

- > 

- > :::image type="content" source="images/363bf30f7d69a94db578e8af0ddd044b.png" alt-text="The Add group pane in the Add App page in the Microsoft Intune admin center portal" lightbox="images/363bf30f7d69a94db578e8af0ddd044b.png":::

- :::image type="content" source="images/86cbe56f88bb6e93e9c63303397fc24f.png" alt-text="The application status pane in the Microsoft Intune admin center portal" lightbox="images/86cbe56f88bb6e93e9c63303397fc24f.png":::

- :::image type="content" source="images/513cf5d59eaaef5d2b5bc122715b5844.png" alt-text="The Device install status page in the Microsoft Defender 365 portal" lightbox="images/513cf5d59eaaef5d2b5bc122715b5844.png":::

- :::image type="content" source="images/7cf9311ad676ec5142002a4d0c2323ca.jpg" alt-text="The Microsoft Defender ATP icon listed in the Search pane" lightbox="images/7cf9311ad676ec5142002a4d0c2323ca.jpg":::

- :::image type="content" source="images/9fe378a1dce0f143005c3aa53d8c4f51.png" alt-text="A device in the Microsoft Defender for Endpoint portal" lightbox="images/9fe378a1dce0f143005c3aa53d8c4f51.png":::

- :::image type="content" source="images/579ff59f31f599414cedf63051628b2e.png" alt-text="The application-adding pane in the Microsoft Intune admin center portal" lightbox="images/579ff59f31f599414cedf63051628b2e.png":::

- :::image type="content" source="images/0f79cb37900b57c3e2bb0effad1c19cb.png" alt-text="The Managed Google Play page in the Microsoft Intune admin center portal" lightbox="images/0f79cb37900b57c3e2bb0effad1c19cb.png":::

- > :::image type="content" source="images/07e6d4119f265037e3b80a20a73b856f.png" alt-text="The page of Managed Google Play in the Microsoft Intune admin center portal" lightbox="images/07e6d4119f265037e3b80a20a73b856f.png":::

- :::image type="content" source="images/206b3d954f06cc58b3466fb7a0bd9f74.png" alt-text="The permissions approval page in the Microsoft Defender 365 portal" lightbox="images/206b3d954f06cc58b3466fb7a0bd9f74.png":::

- > :::image type="content" source="images/34e6b9a0dae125d085c84593140180ed.png" alt-text="The Sync pane in the Microsoft Defender 365 portal" lightbox="images/34e6b9a0dae125d085c84593140180ed.png":::

- :::image type="content" source="images/9fc07ffc150171f169dc6e57fe6f1c74.png" alt-text="The application sync status pane in the Android apps page in the Microsoft Defender 365 portal" lightbox="images/9fc07ffc150171f169dc6e57fe6f1c74.png":::

- :::image type="content" source="images/android-mem.png" alt-text="The App configuration policies pane in the Microsoft Intune admin center portal" lightbox="images/android-mem.png":::

- :::image type="content" source="images/android-create-app.png" alt-text=" Screenshot of the Associated app details pane." lightbox="images/android-create-app.png":::

- :::image type="content" source="images/android-select-group.png" alt-text="The Selected groups pane" lightbox="images/android-select-group.png":::

- :::image type="content" source="images/1autosetupofvpn.png" alt-text="The Configuration profiles menu item in the Policy pane" lightbox="images/1autosetupofvpn.png":::

- :::image type="content" source="images/2autosetupofvpn.png" alt-text="The devices configuration profile Name and Description fields in the Basics pane" lightbox="images/2autosetupofvpn.png":::

- :::image type="content" source="images/3autosetupofvpn.png" alt-text="The Connectivity pane under the Configuration settings tab" lightbox="images/3autosetupofvpn.png":::

- :::image type="content" source="images/4autosetupofvpn.png" alt-text="Screenshot of the devices configuration profile Assignment pane in the Device restrictions." lightbox="images/4autosetupofvpn.png":::

- :::image type="content" source="images/5autosetupofvpn.png" alt-text="A devices configuration profile 's provision for Review + create" lightbox="images/5autosetupofvpn.png":::

- > :::image type="content" source="images/900c0197aa59f9b7abd762ab2b32e80c.png" alt-text="The device installation status pane" lightbox="images/900c0197aa59f9b7abd762ab2b32e80c.png":::

- :::image type="content" source="images/9fe378a1dce0f143005c3aa53d8c4f51.png" alt-text="The Microsoft Defender for Endpoint portal" lightbox="images/9fe378a1dce0f143005c3aa53d8c4f51.png":::

- > 

- > 

- :::image type="content" source="images/api-flow-1.png" alt-text="The New flow pane under My flows menu item in the Microsoft Defender 365 portal" lightbox="images/api-flow-1.png":::

- :::image type="content" source="images/api-flow-2.png" alt-text=" The Choose your flow's trigger section in the Microsoft Defender 365 portal" lightbox="images/api-flow-2.png" :::

- :::image type="content" source="images/api-flow-4.png" alt-text="The Alerts pane" lightbox="images/api-flow-4.png":::

- :::image type="content" source="images/api-flow-5.png" alt-text="The Actions pane" lightbox="images/api-flow-5.png":::

- :::image type="content" source="../images/add-permission.png" alt-text="The API permissions option under the Manage pane in the Microsoft Entra admin center" lightbox="../images/add-permission.png":::

- :::image type="content" source="../images/application-permissions.png" alt-text="The permission type and settings panes in the Request API permissions page" lightbox="../images/application-permissions.png":::

- :::image type="content" source="../images/app-and-tenant-ids.png" alt-text="The application details pane under the Overview menu item in the Microsoft Entra admin center" lightbox="../images/app-and-tenant-ids.png":::

- :::image type="content" source="../images/api-jwt-ms.png" alt-text="The Decoded Token pane for jwt.ms" lightbox="../images/api-jwt-ms.png":::

- :::image type="content" alt-text="add permission." source="../images/add-permission.png" lightbox="../images/add-permission.png":::

- :::image type="content" source="../images/application-permissions-public-client.png" alt-text="The application type and permissions panes" lightbox="../images/application-permissions-public-client.png":::

- :::image type="content" source="../images/app-and-tenant-ids.png" alt-text="The created app ID" lightbox="../images/app-and-tenant-ids.png":::

- :::image type="content" source="../images/add-permission.png" alt-text="The Add a permission option" lightbox="../images/add-permission.png":::

- :::image type="content" source="../images/application-permissions.png" alt-text="The option that allows to add a permission" lightbox="../images/application-permissions.png":::

- :::image type="content" source="../images/app-id.png" alt-text="The create application's ID" lightbox="../images/app-id.png":::

- :::image type="content" source="../images/app-consent-partner.png" alt-text="The Accept button" lightbox="../images/app-consent-partner.png":::

- :::image type="content" source="../images/add-permission.png" alt-text="The API permissions pane" lightbox="../images/add-permission.png":::

- :::image type="content" source="../images/application-permissions.png" alt-text="The application permission information pane" lightbox="../images/application-permissions.png":::

- :::image type="content" source="../images/app-and-tenant-ids.png" alt-text="The created app and tenant IDs" lightbox="../images/app-and-tenant-ids.png":::

-> :::image type="content" source="images/asr-defender365-05b-mem1.png" alt-text="The *Endpoint security menu item on the Overview page" lightbox="images/asr-defender365-05b-mem1.png":::

-| In the <a href="https://go.microsoft.com/fwlink/p/?linkid=2077139" target="_blank">Microsoft Defender portal</a>, choose **Action center**. <p>:::image type="content" source="images/action-center-nav-new.png" alt-text="The navigation pane to the Action Center in the Microsoft Defender portal" lightbox="images/action-center-nav-new.png"::: | In the Microsoft Defender portal, choose **Automated investigations** > **Action center**. <p>:::image type="content" source="images/action-center-nav-old.png" alt-text="An older version of the navigation pane to the Action Center in the Microsoft Defender portal" lightbox="images/action-center-nav-old.png"::: |

-|Windows Server 2012 R2|||

-|Windows Server 2016|Built-in||

-Microsoft Defender for Endpoint will collect information from your configured devices and store it in a customer-dedicated and segregated tenant specific to the service for administration, tracking, and reporting purposes.

-The Defender for Endpoint service utilizes state-of-the-art data protection technologies which are based on Microsoft Azure infrastructure.

-Defender for Endpoint operates in the Microsoft Azure data centers in the European Union, the United Kingdom, the United States, or in Australia. Customer data collected by the service may be stored in: (a) the geo-location of the tenant as identified during provisioning or, (b) the geo-location as defined by the data storage rules of an online service if this online service is used by Defender for Endpoint to process such data. For more information, see [Where your Microsoft 365 customer data is stored](/microsoft-365/enterprise/o365-data-locations).

-Additionally, Microsoft conducts background verification checks of certain operations personnel, and limits access to applications, systems, and network infrastructure in proportion to the level of background verification. Operations personnel follow a formal process when they are required to access a customer's account or related information in the performance of their duties.

-Data from Microsoft Defender for Endpoint is retained for 180 days, visible across the portal. However, in the advanced hunting investigation experience, it's accessible via a query for a period of 30 days.

-Your data will be kept and will be available to you while the license is under grace period or suspended mode. At the end of this period, that data will be erased from Microsoft's systems to make it unrecoverable, no later than 180 days from contract termination or expiration.

-<td><center><a href="microsoft-defender-endpoint.md#ai"><img src="images/air-icon.png" alt="Automated investigation and remediation"><br> <b>Automated investigation and remediation</b></a></center></td>

-Windows 11|||

-Windows 10, version 21H1 and above|||

-Windows 10, version 20H2 (with [KB4586853](https://support.microsoft.com/help/4586853) ¹)|||

-Windows 10, version 2004 (with [KB4586853](https://support.microsoft.com/help/4586853) ¹)| <br /> Note: [Deprecated](/lifecycle/announcements/windows-10-version-2004-end-of-servicing), please upgrade| <br /> Note: [Deprecated](/lifecycle/announcements/windows-10-version-2004-end-of-servicing), please upgrade| <br /> Note: [Deprecated](/lifecycle/announcements/windows-10-version-2004-end-of-servicing), please upgrade

-Windows 10, version 1909 (with [KB4586819](https://support.microsoft.com/help/4586819) ¹)| <br /> Note: [Deprecated](/lifecycle/announcements/windows-10-1909-end-of-servicing), please upgrade| <br /> Note: [Deprecated](/lifecycle/announcements/windows-10-1909-end-of-servicing), please upgrade| <br /> Note: [Deprecated](/lifecycle/announcements/windows-10-1909-end-of-servicing), please upgrade

-Windows 10, version 1903 (with [KB4586819](https://support.microsoft.com/help/4586819) ¹)| <br /> Note: [Deprecated](/lifecycle/announcements/windows-10-1903-end-of-servicing), please upgrade| <br /> Note: [Deprecated](/lifecycle/announcements/windows-10-1903-end-of-servicing), please upgrade| <br /> Note: [Deprecated](/lifecycle/announcements/windows-10-1903-end-of-servicing), please upgrade

-Windows 10, version 1809 (with [KB4586839](https://support.microsoft.com/help/4586839) ¹)| <br /> Note: [Deprecated](/lifecycle/announcements/windows-10-1803-1809-end-of-servicing), please upgrade| <br /> Note: [Deprecated](/lifecycle/announcements/windows-10-1803-1809-end-of-servicing), please upgrade| <br /> Note: [Deprecated](/lifecycle/announcements/windows-10-1803-1809-end-of-servicing), please upgrade

-Windows 10, version 1803 (with [KB4598245](https://support.microsoft.com/help/4598245) ¹)| <br /> Note: [Deprecated](/lifecycle/announcements/windows-10-1803-1809-end-of-servicing), please upgrade| <br /> Note: [Deprecated](/lifecycle/announcements/windows-10-1803-1809-end-of-servicing), please upgrade| <br /> Note: [Deprecated](/lifecycle/announcements/windows-10-1803-1809-end-of-servicing), please upgrade

-Windows 10, version 1709| <br /> Note: Won't be supported| With [KB4499147](https://support.microsoft.com/help/4499147) ¹ <br /> Note: [Deprecated](/lifecycle/announcements/revised-end-of-service-windows-10-1709), please upgrade| <br /> Note: Won't be supported

-Windows 10, version 1703 and earlier| <br /> Note: Won't be supported| <br /> Note: Won't be supported| <br /> Note: Won't be supported

-Windows Server 2022|||

-Windows Server 2019 (with [KB4586839](https://support.microsoft.com/help/4586839) ¹)|||

-Windows Server 2016 (Modern) ²|||

-Windows Server 2012 R2 (Modern) ²|||

-Windows Server 2016 (Legacy) ³|||

-Windows Server 2012 R2 (Legacy) ³|||

-Windows Server 2008 R2 SP1 (Legacy) ³|||

-Windows 8.1 Enterprise (Legacy) ³|||

-Windows 8 Pro (Legacy) ³|||

-Windows 7 SP1 Enterprise (Legacy) ³|||

-Windows 7 SP1 Pro (Legacy) ³|||

-Linux|||

-macOS|||

-Android| <br /> | <br /> | <br />

-iOS| <br /> | <br /> | <br />

-Windows Server 2022|||

-Windows Server 2019|||

-Windows Server 2016|||

-Windows Server 2012 R2|||

-Windows Server 2008 R2 SP1|||

-|Microsoft Secure Score|¹|||

-|Microsoft Threat Experts||||

-|Microsoft Defender for Endpoint Security Configuration Management||||

-|Reports: Web content filtering||||

-|Reports: Device health||||

-|Web Protection (Anti-Phishing and custom indicators)||||

-|Malware Protection (Android-Only)||||

-|Jailbreak Detection (iOS-Only)||||

-|Conditional Access/Conditional Launch||||

-|Support for MAM||||

-|Privacy Controls||||

-|Microsoft Defender Vulnerability Management core capabilities <br/> (included in Defender for Endpoint Plan 2) | ¹|||

-|Microsoft Defender Vulnerability Management premium capabilities ||||

- > :::image type="content" source="images/access-properties.png" alt-text="The Properties page" lightbox="images/access-properties.png":::

-The **Logged on users** card shows how many users have logged on in the past 30 days, along with the most and least frequent users. Selecting the **See all users** link opens the details pane, which displays information such as user type, sign-in type, and when the user was first and last seen. For more information, see [Investigate user entities](investigate-user.md).

-Note that a grey circle indicates that the data is unknown.

- :::image type="content" source="images/addiosconfig.png" alt-text="Add configuration policy." lightbox="images/addiosconfig.png":::

- :::image type="content" source="images/addiosconfigvalue.png" alt-text="Add configuration value." lightbox="images/addiosconfigvalue.png":::

- :::image type="content" source="images/app-settings.png" alt-text="The application settings" lightbox="images/app-settings.png":::

- :::image type="icon" source="images/41627a709700c324849bf7e13510c516.png":::

-Open the Defender for Endpoint application and navigate to **Manage settings** \> **Add or Remove Exclusion...**, as shown in the following screenshot:

-Select the type of exclusion that you wish to add and follow the prompts.

- :::image type="content" source="images/agree-license.png" alt-text="Screenshot that shows the acceptance of the agreement.":::

- :::image type="content" source="images/a347307458d6a9bbfa88df7dbe15398f.png" alt-text="The configuration settings1" lightbox="images/a347307458d6a9bbfa88df7dbe15398f.png":::

- :::image type="content" source="images/718b9d609f9f77c8b13ba88c4c0abe5d.png" alt-text="The configuration settings2" lightbox="images/718b9d609f9f77c8b13ba88c4c0abe5d.png":::

- :::image type="content" source="images/ae3597247b6bc7c5347cf56ab1e820c0.png" alt-text="The configuration settings3" lightbox="images/ae3597247b6bc7c5347cf56ab1e820c0.png":::

- :::image type="content" source="images/4922c0fcdde4c7f73242b13bf5e35c19.png" alt-text="The configuration settings4" lightbox="images/4922c0fcdde4c7f73242b13bf5e35c19.png":::

- :::image type="content" source="images/5856b765a6ce677caacb130ca36b1a62.png" alt-text="The configuration settings6" lightbox="images/5856b765a6ce677caacb130ca36b1a62.png":::

- :::image type="content" source="images/3ced5383a6be788486d89d407d042f28.png" alt-text="The configuration settings7" lightbox="images/3ced5383a6be788486d89d407d042f28.png":::

- :::image type="content" source="images/54be9c6ed5b24cebe628dc3cd9ca4089.png" alt-text="The configuration settings8" lightbox="images/54be9c6ed5b24cebe628dc3cd9ca4089.png":::

- :::image type="content" source="images/6fd0cb2bbb0e60a623829c91fd0826ab.png" alt-text="The configuration settings9" lightbox="images/6fd0cb2bbb0e60a623829c91fd0826ab.png":::

- :::image type="content" source="images/644e0f3af40c29e80ca1443535b2fe32.png" alt-text="A new profile." lightbox="images/644e0f3af40c29e80ca1443535b2fe32.png":::

- :::image type="content" source="images/4137189bc3204bb09eed3aabc41afd78.png" alt-text="Add custom schema." lightbox="images/4137189bc3204bb09eed3aabc41afd78.png":::

- :::image type="content" source="images/a6f9f556037c42fabcfdcb1b697244cf.png" alt-text="Upload schema." lightbox="images/a6f9f556037c42fabcfdcb1b697244cf.png":::

- :::image type="content" source="images/817b3b760d11467abe9bdd519513f54f.png" alt-text="The chosen managed settings." lightbox="images/817b3b760d11467abe9bdd519513f54f.png":::

- :::image type="content" source="images/a14a79efd5c041bb8974cb5b12b3a9b6.png" alt-text="The page on which you change the settings values." lightbox="images/a14a79efd5c041bb8974cb5b12b3a9b6.png":::

- :::image type="content" source="images/9fc17529e5577eefd773c658ec576a7d.png" alt-text="The Configuration profile scope." lightbox="images/9fc17529e5577eefd773c658ec576a7d.png":::

- :::image type="content" source="images/6f093e42856753a3955cab7ee14f12d9.png" alt-text="The page on which you can save the Configuration settings." lightbox="images/6f093e42856753a3955cab7ee14f12d9.png":::

- :::image type="content" source="images/644e0f3af40c29e80ca1443535b2fe32.png" alt-text="The page displaying a new profile." lightbox="images/644e0f3af40c29e80ca1443535b2fe32.png":::

- :::image type="content" source="images/3160906404bc5a2edf84d1d015894e3b.png" alt-text="The MDATP MDAV configuration settings." lightbox="images/3160906404bc5a2edf84d1d015894e3b.png":::

- :::image type="content" source="images/6f85269276b2278eca4bce84f935f87b.png" alt-text="The configuration settings plist file." lightbox="images/6f85269276b2278eca4bce84f935f87b.png":::

- :::image type="content" source="images/526e978761fc571cca06907da7b01fd6.png" alt-text="The prompt to choose the plist file." lightbox="images/526e978761fc571cca06907da7b01fd6.png":::

- :::image type="content" source="images/98acea3750113b8dbab334296e833003.png" alt-text="The mdatpmdav configuration settings." lightbox="images/98acea3750113b8dbab334296e833003.png":::

- :::image type="content" source="images/0adb21c13206861ba9b30a879ade93d3.png" alt-text="The configuration setting upload." lightbox="images/0adb21c13206861ba9b30a879ade93d3.png":::

- > :::image type="content" source="images/8e69f867664668796a3b2904896f0436.png" alt-text="The prompt to upload the intune file related to the configuration settings." lightbox="images/8e69f867664668796a3b2904896f0436.png":::

- :::image type="content" source="images/1b6b5a4edcb42d97f1e70a6a0fa48e3a.png" alt-text="The option to save the image related to the configuration settings." lightbox="images/1b6b5a4edcb42d97f1e70a6a0fa48e3a.png":::

- :::image type="content" source="images/33e2b2a1611fdddf6b5b79e54496e3bb.png" alt-text="The uploaded file related to the configuration settings." lightbox="images/33e2b2a1611fdddf6b5b79e54496e3bb.png":::

- :::image type="content" source="images/a422e57fe8d45689227e784443e51bd1.png" alt-text="The configuration settings page." lightbox="images/a422e57fe8d45689227e784443e51bd1.png":::

- :::image type="content" source="images/9fc17529e5577eefd773c658ec576a7d.png" alt-text="The scope for the configuration settings." lightbox="images/9fc17529e5577eefd773c658ec576a7d.png":::

- :::image type="content" source="images/6f093e42856753a3955cab7ee14f12d9.png" alt-text="The notification of configuration settings." lightbox="images/6f093e42856753a3955cab7ee14f12d9.png":::

- :::image type="content" source="images/7f9138053dbcbf928e5182ee7b295ebe.png" alt-text="The configuration settings mdatpmdav notifications tray." lightbox="images/7f9138053dbcbf928e5182ee7b295ebe.png":::

- :::image type="content" source="images/4bac6ce277aedfb4a674f2d9fcb2599a.png" alt-text="The configuration settings mdatpmdav notifications mau." lightbox="images/4bac6ce277aedfb4a674f2d9fcb2599a.png":::

- :::image type="content" source="images/441aa2ecd36abadcdd8aed03556080b5.png" alt-text="The page on which you can add values for the configuration settings." lightbox="images/441aa2ecd36abadcdd8aed03556080b5.png":::

- :::image type="content" source="images/09a275e321268e5e3ac0c0865d3e2db5.png" alt-text="The page on which you can save values for the configuration settings contoso machine group." lightbox="images/09a275e321268e5e3ac0c0865d3e2db5.png":::

- :::image type="content" source="images/4d2d1d4ee13d3f840f425924c3df0d51.png" alt-text="The page that displays the completion notification of the configuration settings." lightbox="images/4d2d1d4ee13d3f840f425924c3df0d51.png":::

- :::image type="content" source="images/633ad26b8bf24ec683c98b2feb884bdf.png" alt-text="The completed configuration settings." lightbox="images/633ad26b8bf24ec683c98b2feb884bdf.png":::

- :::image type="content" source="images/1f72e9c15eaafcabf1504397e99be311.png" alt-text="The configuration setting application and custom settings." lightbox="images/1f72e9c15eaafcabf1504397e99be311.png":::

- :::image type="content" source="images/1213872db5833aa8be535da57653219f.png" alt-text="The configuration setting preference domain." lightbox="images/1213872db5833aa8be535da57653219f.png":::

- :::image type="content" source="images/335aff58950ce62d1dabc289ecdce9ed.png" alt-text="The prompt to choose the file regarding configuration setting." lightbox="images/335aff58950ce62d1dabc289ecdce9ed.png":::

- :::image type="content" source="images/a26bd4967cd54bb113a2c8d32894c3de.png" alt-text="The mdatpmdavmau settings." lightbox="images/a26bd4967cd54bb113a2c8d32894c3de.png":::

- :::image type="content" source="images/4239ca0528efb0734e4ca0b490bfb22d.png" alt-text="The upload of the file regarding configuration setting." lightbox="images/4239ca0528efb0734e4ca0b490bfb22d.png":::

- :::image type="content" source="images/4ec20e72c8aed9a4c16912e01692436a.png" alt-text="The page displaying the upload option for the file regarding configuration setting." lightbox="images/4ec20e72c8aed9a4c16912e01692436a.png":::

- :::image type="content" source="images/253274b33e74f3f5b8d475cf8692ce4e.png" alt-text="The page displaying the save option for the file regarding configuration setting." lightbox="images/253274b33e74f3f5b8d475cf8692ce4e.png":::

- :::image type="content" source="images/10ab98358b2d602f3f67618735fa82fb.png" alt-text="The Scope tab for the configuration settings." lightbox="images/10ab98358b2d602f3f67618735fa82fb.png":::

- :::image type="content" source="images/56e6f6259b9ce3c1706ed8d666ae4947.png" alt-text="The option to add deployment targets." lightbox="images/56e6f6259b9ce3c1706ed8d666ae4947.png":::

- :::image type="content" source="images/38c67ee1905c4747c3b26c8eba57726b.png" alt-text="The page on which you add more values to the configuration settings." lightbox="images/38c67ee1905c4747c3b26c8eba57726b.png":::

- :::image type="content" source="images/321ba245f14743c1d5d51c15e99deecc.png" alt-text="The page on which you can add more values to the configuration settings." lightbox="images/321ba245f14743c1d5d51c15e99deecc.png":::

- :::image type="content" source="images/264493cd01e62c7085659d6fdc26dc91.png" alt-text="The profile for which settings are to be configured." lightbox="images/264493cd01e62c7085659d6fdc26dc91.png":::

- :::image type="content" source="images/715ae7ec8d6a262c489f94d14e1e51bb.png" alt-text="The configuration privacy policy control." lightbox="images/715ae7ec8d6a262c489f94d14e1e51bb.png":::

- :::image type="content" source="images/22cb439de958101c0a12f3038f905b27.png" alt-text="The configuration setting privacy preference policy control details." lightbox="images/22cb439de958101c0a12f3038f905b27.png":::

- :::image type="content" source="images/6de50b4a897408ddc6ded56a09c09fe2.png" alt-text="The save operation for the configuration setting." lightbox="images/6de50b4a897408ddc6ded56a09c09fe2.png":::

- :::image type="content" source="images/2c49b16cd112729b3719724f581e6882.png" alt-text="The page depicting the scope for the configuration setting." lightbox="images/2c49b16cd112729b3719724f581e6882.png":::

- :::image type="content" source="images/57cef926d1b9260fb74a5f460cee887a.png" alt-text="The page depicting the configuration setting." lightbox="images/57cef926d1b9260fb74a5f460cee887a.png":::

- :::image type="content" source="images/368d35b3d6179af92ffdbfd93b226b69.png" alt-text="The configuration setting contoso machine group." lightbox="images/368d35b3d6179af92ffdbfd93b226b69.png":::

- :::image type="content" source="images/809cef630281b64b8f07f20913b0039b.png" alt-text="The configuration setting contoso machine-group." lightbox="images/809cef630281b64b8f07f20913b0039b.png":::

- :::image type="content" source="images/6c8b406ee224335a8c65d06953dc756e.png" alt-text="The configuration setting illustration." lightbox="images/6c8b406ee224335a8c65d06953dc756e.png":::

- :::image type="content" source="images/6c8b406ee224335a8c65d06953dc756e.png" alt-text="The automatically generated social media post's description." lightbox="images/6c8b406ee224335a8c65d06953dc756e.png":::

- :::image type="content" source="images/0df36fc308ba569db204ee32db3fb40a.png" alt-text="The Target Computers selection pane." lightbox="images/0df36fc308ba569db204ee32db3fb40a.png":::

- :::image type="content" source="images/0dde8a4c41110dbc398c485433a81359.png" alt-text="The New macOS Configuration Profile pane." lightbox="images/0dde8a4c41110dbc398c485433a81359.png":::

- :::image type="content" source="images/0df36fc308ba569db204ee32db3fb40a.png" alt-text="The configuration settings sco tab." lightbox="images/0df36fc308ba569db204ee32db3fb40a.png":::

- :::image type="content" source="images/0dde8a4c41110dbc398c485433a81359.png" alt-text="The configuration settings adim." lightbox="images/0dde8a4c41110dbc398c485433a81359.png":::

- :::image type="content" source="images/8dde76b5463047423f8637c86b05c29d.png" alt-text="The file explorer wdav package." lightbox="images/8dde76b5463047423f8637c86b05c29d.png":::

- :::image type="content" source="images/990742cd9a15ca9fdd37c9f695d1b9f4.png" alt-text="The configuration settings for jamfpro." lightbox="images/990742cd9a15ca9fdd37c9f695d1b9f4.png":::

- :::image type="content" source="images/57aa4d21e2ccc65466bf284701d4e961.png" alt-text="The bird Description for an automatically generated package." lightbox="images/57aa4d21e2ccc65466bf284701d4e961.png":::

- :::image type="content" source="images/21de3658bf58b1b767a17358a3f06341.png" alt-text="The General tab for configuration settings." lightbox="images/21de3658bf58b1b767a17358a3f06341.png":::

- :::image type="content" source="images/1aa5aaa0a387f4e16ce55b66facc77d1.png" alt-text="The computer screen displaying the description for an automatically generated package." lightbox="images/1aa5aaa0a387f4e16ce55b66facc77d1.png":::

- :::image type="content" source="images/56dac54634d13b2d3948ab50e8d3ef21.png" alt-text="The limitation tab for the configuration settings." lightbox="images/56dac54634d13b2d3948ab50e8d3ef21.png":::

- :::image type="content" source="images/33f1ecdc7d4872555418bbc3efe4b7a3.png" alt-text="The configuration settings pack uploading process for the package related to the configuration settings." lightbox="images/33f1ecdc7d4872555418bbc3efe4b7a3.png":::

- :::image type="content" source="images/1626d138e6309c6e87bfaab64f5ccf7b.png" alt-text="An instance of uploading the package for configuration settings." lightbox="images/1626d138e6309c6e87bfaab64f5ccf7b.png":::

- :::image type="content" source="images/847b70e54ed04787e415f5180414b310.png" alt-text="The configuration settings new policy." lightbox="images/847b70e54ed04787e415f5180414b310.png":::

- :::image type="content" source="images/625ba6d19e8597f05e4907298a454d28.png" alt-text="The configuration settings - MDATP onboard." lightbox="images/625ba6d19e8597f05e4907298a454d28.png":::

- :::image type="content" source="images/68bdbc5754dfc80aa1a024dde0fce7b0.png" alt-text="The recurring check-in for the configuration settings." lightbox="images/68bdbc5754dfc80aa1a024dde0fce7b0.png":::

- :::image type="content" source="images/8fb4cc03721e1efb4a15867d5241ebfb.png" alt-text="The option to configure packages." lightbox="images/8fb4cc03721e1efb4a15867d5241ebfb.png":::

- :::image type="content" source="images/526b83fbdbb31265b3d0c1e5fbbdc33a.png" alt-text="The option to add more settings to MDATP MDA." lightbox="images/526b83fbdbb31265b3d0c1e5fbbdc33a.png":::

- :::image type="content" source="images/9d6e5386e652e00715ff348af72671c6.png" alt-text="The save option for the configuration settings." lightbox="images/9d6e5386e652e00715ff348af72671c6.png":::

- :::image type="content" source="images/8d80fe378a31143db9be0bacf7ddc5a3.png" alt-text="The Scope tab related to the configuration settings." lightbox="images/8d80fe378a31143db9be0bacf7ddc5a3.png":::

- :::image type="content" source="images/6eda18a64a660fa149575454e54e7156.png" alt-text="The option to add computer groups." lightbox="images/6eda18a64a660fa149575454e54e7156.png":::

- :::image type="content" source="images/1c08d097829863778d562c10c5f92b67.png" alt-text="The configuration settings - ad1." lightbox="images/1c08d097829863778d562c10c5f92b67.png":::

- :::image type="content" source="images/216253cbfb6ae738b9f13496b9c799fd.png" alt-text="The configuration settings - ad2." lightbox="images/216253cbfb6ae738b9f13496b9c799fd.png":::

- :::image type="content" source="images/99679a7835b0d27d0a222bc3fdaf7f3b.png" alt-text="The Contoso onboarding status with an option to complete it." lightbox="images/99679a7835b0d27d0a222bc3fdaf7f3b.png":::

- :::image type="content" source="images/632aaab79ae18d0d2b8e0c16b6ba39e2.png" alt-text="The policies page." lightbox="images/632aaab79ae18d0d2b8e0c16b6ba39e2.png":::

-At a glance you see information such as domain, risk level, OS platform, and other details for easy identification of devices most at risk.

-> Risk Level which can influence enforcement of conditional access and other security policies on Microsoft Intune, is available in Windows today.

-The device inventory opens on the **Computers and Mobile** tab. At a glance you see information such as device name, domain, risk level, exposure level, OS platform, onboarding status, sensor health state, and other details for easy identification of devices most at risk.

-At the top of each device inventory tab, you can see the total number of devices, the number of devices that aren't yet onboarded, and the number of devices that are identified as a higher risk to your organization. You can use this information to help you prioritize devices for security posture improvements.

-The counts on the top of each tab will be updated based on the current view.

-**Exposure level** | The exposure level reflects the current exposure of the device based on the cumulative impact of its pending security recommendations. The possible levels are low, medium, and high. Low exposure means your devices are less vulnerable from exploitation. </br> </br> If the exposure level says "No data available," there are a few reasons why:</br>- Device stopped reporting for more than 30 days. In that case it's considered inactive, and the exposure isn't computed.</br>- Device OS not supported - see [minimum requirements for Microsoft Defender for Endpoint](/microsoft-365/security/defender-endpoint/minimum-requirements).</br>- Device with stale agent (unlikely).

-**Exclusion state** | Filter the list based on whether or not the device is excluded. For more information, see [Exclude devices](exclude-devices.md).

-**Sensor health state** | Filter by the following sensor health states, for devices onboard to Microsoft Defender for Endpoint:</br> - **Active**: Devices that are actively reporting sensor data to the service.</br> - **Inactive**: Devices that stopped sending signals for more than seven days. </br> - **Misconfigured**: Devices that have impaired communications with service or are unable to send sensor data. </br> Misconfigured devices can further be classified to: </br> - No sensor data </br> - Impaired communications </br> For more information on how to address issues on misconfigured devices, see, [Fix unhealthy sensors](/microsoft-365/security/defender-endpoint/fix-unhealthy-sensors).</br></br> (_Computers and mobile only_)

-**Onboarding status** | Onboarding status indicates whether the device is currently onboarded to Microsoft Defender for Endpoint or not. Device discovery must be enabled for this filter to appear. You can filter by the following states: </br> - **Onboarded**: The endpoint is onboarded to Microsoft Defender for Endpoint. </br> - **Can be onboarded**: The endpoint was discovered in the network as a supported device, but it's not currently onboarded. Microsoft highly recommends onboarding these devices. </br> - **Unsupported**: The endpoint was discovered in the network, but isn't supported by Microsoft Defender for Endpoint. </br> - **Insufficient info**: The system couldn't determine the supportability of the device.</br></br> (_Computers and mobile only_)

-**Group** | Filter the list based on the group you're interested in investigating. </br></br> (_Computers and mobile only_)

-[Investigate devices in the Microsoft Defender for Endpoint Devices list](investigate-machines.md)

- :::image type="content" source="images/accessibility-and-plus-icon.png" alt-text="The Accessibility menu item and the Plus icon." lightbox="images/accessibility-and-plus-icon.png":::

- :::image type="content" source="images/applications-md-options.png" alt-text="The process of selecting Applications and Microsoft Defender." lightbox="images/applications-md-options.png":::

-### February-2024 (Engine: 1.1.24020.9 | Platform: 4.18.24020.xx)

-<td><center><a href="#ai"><img src="images/air-icon.png" alt="Automated investigation and remediation"><br> <b>Automated investigation and remediation</b></a></center></td>

- :::image type="content" source="images/91b738e4b97c4272fd6d438d8c2d5269.png" alt-text="The onboarding process" lightbox="images/91b738e4b97c4272fd6d438d8c2d5269.png":::

- :::image type="content" source="images/9736e0358e86bc778ce1bd4c516adb8b.png" alt-text="The antimalware policy" lightbox="images/9736e0358e86bc778ce1bd4c516adb8b.png":::

- :::image type="content" source="images/1566ad81bae3d714cc9e0d47575a8cbd.png" alt-text="The next-generation protection pane1" lightbox="images/1566ad81bae3d714cc9e0d47575a8cbd.png":::

- :::image type="content" source="images/36c7c2ed737f2f4b54918a4f20791d4b.png" alt-text="The next-generation protection pane3" lightbox="images/36c7c2ed737f2f4b54918a4f20791d4b.png":::

- :::image type="content" source="images/a28afc02c1940d5220b233640364970c.png" alt-text="The next-generation protection pane4" lightbox="images/a28afc02c1940d5220b233640364970c.png":::

- :::image type="content" source="images/5420a8790c550f39f189830775a6d4c9.png" alt-text="The next-generation protection pane5" lightbox="images/5420a8790c550f39f189830775a6d4c9.png":::

- :::image type="content" source="images/33f08a38f2f4dd12a364f8eac95e8c6b.png" alt-text="The next-generation protection pane6" lightbox="images/33f08a38f2f4dd12a364f8eac95e8c6b.png":::

- :::image type="content" source="images/41b9a023bc96364062c2041a8f5c344e.png" alt-text="The next-generation protection pane7" lightbox="images/41b9a023bc96364062c2041a8f5c344e.png":::

- :::image type="content" source="images/945c9c5d66797037c3caeaa5c19f135c.png" alt-text="The next-generation protection pane8" lightbox="images/945c9c5d66797037c3caeaa5c19f135c.png":::

- :::image type="content" source="images/3876ca687391bfc0ce215d221c683970.png" alt-text="The next-generation protection pane9" lightbox="images/3876ca687391bfc0ce215d221c683970.png":::

- :::image type="content" source="images/728c10ef26042bbdbcd270b6343f1a8a.png" alt-text="The Microsoft Configuration Manager console0" lightbox="images/728c10ef26042bbdbcd270b6343f1a8a.png":::

- :::image type="content" source="images/0a6536f2c4024c08709cac8fcf800060.png" alt-text="The Microsoft Configuration Manager console2" lightbox="images/0a6536f2c4024c08709cac8fcf800060.png":::

- :::image type="content" source="images/95d23a07c2c8bc79176788f28cef7557.png" alt-text="The Microsoft Configuration Manager console3" lightbox="images/95d23a07c2c8bc79176788f28cef7557.png":::

- :::image type="content" source="images/8999dd697e3b495c04eb911f8b68a1ef.png" alt-text="The Microsoft Configuration Manager console4" lightbox="images/8999dd697e3b495c04eb911f8b68a1ef.png":::

- :::image type="content" source="images/0ccfe3e803be4b56c668b220b51da7f7.png" alt-text="The Microsoft Configuration Manager console5" lightbox="images/0ccfe3e803be4b56c668b220b51da7f7.png":::

- :::image type="content" source="images/24bfb16ed561cbb468bd8ce51130ca9d.png" alt-text="The attack surface reduction rules reports2" lightbox="images/24bfb16ed561cbb468bd8ce51130ca9d.png":::

- :::image type="content" source="images/728c10ef26042bbdbcd270b6343f1a8a.png" alt-text="The System Center Configuration Manager1" lightbox="images/728c10ef26042bbdbcd270b6343f1a8a.png":::

- :::image type="content" source="images/0a6536f2c4024c08709cac8fcf800060.png" alt-text="The Exploit Guard policy1" lightbox="images/0a6536f2c4024c08709cac8fcf800060.png":::

- :::image type="content" source="images/95d23a07c2c8bc79176788f28cef7557.png" alt-text="The Exploit Guard policy2" lightbox="images/95d23a07c2c8bc79176788f28cef7557.png":::

- :::image type="content" source="images/8999dd697e3b495c04eb911f8b68a1ef.png" alt-text="The Microsoft Configuration Manager-1" lightbox="images/8999dd697e3b495c04eb911f8b68a1ef.png":::

- :::image type="content" source="images/0ccfe3e803be4b56c668b220b51da7f7.png" alt-text="The Microsoft Configuration Manager-2" lightbox="images/0ccfe3e803be4b56c668b220b51da7f7.png":::

- :::image type="content" source="images/728c10ef26042bbdbcd270b6343f1a8a.png" alt-text="The Microsoft Configuration Manager-3" lightbox="images/728c10ef26042bbdbcd270b6343f1a8a.png":::

- :::image type="content" source="images/a8b934dab2dbba289cf64fe30e0e8aa4.png" alt-text="The Microsoft Configuration Manager-4" lightbox="images/a8b934dab2dbba289cf64fe30e0e8aa4.png":::

- :::image type="content" source="images/0a6536f2c4024c08709cac8fcf800060.png" alt-text="The Microsoft Configuration Manager-5" lightbox="images/0a6536f2c4024c08709cac8fcf800060.png":::

- :::image type="content" source="images/95d23a07c2c8bc79176788f28cef7557.png" alt-text="The Microsoft Configuration Manager-6" lightbox="images/95d23a07c2c8bc79176788f28cef7557.png":::

- :::image type="content" source="images/8999dd697e3b495c04eb911f8b68a1ef.png" alt-text="The Microsoft Configuration Manager-7" lightbox="images/8999dd697e3b495c04eb911f8b68a1ef.png":::

- > :::image type="content" source="images/66f724598d9c3319cba27f79dd4617a4.png" alt-text="The Microsoft Intune admin center1" lightbox="images/66f724598d9c3319cba27f79dd4617a4.png":::

- > :::image type="content" source="images/149cbfdf221cdbde8159d0ab72644cd0.png" alt-text="The Microsoft Intune admin center3" lightbox="images/149cbfdf221cdbde8159d0ab72644cd0.png":::

- > :::image type="content" source="images/58dcd48811147feb4ddc17212b7fe840.png" alt-text="The Microsoft Intune admin center4" lightbox="images/58dcd48811147feb4ddc17212b7fe840.png":::

- > :::image type="content" source="images/a5b2d23bdd50b160fef4afd25dda28d4.png" alt-text="The Microsoft Intune admin center5" lightbox="images/a5b2d23bdd50b160fef4afd25dda28d4.png":::

- > :::image type="content" source="images/2466460812371ffae2d19a10c347d6f4.png" alt-text="The Microsoft Intune admin center7" lightbox="images/2466460812371ffae2d19a10c347d6f4.png":::

- > :::image type="content" source="images/289172dbd7bd34d55d24810d9d4d8158.png" alt-text="The Microsoft Intune admin center10" lightbox="images/289172dbd7bd34d55d24810d9d4d8158.png":::

- > :::image type="content" source="images/5a568b6878be8243ea2b9d82d41ed297.png" alt-text="The Microsoft Intune admin center11" lightbox="images/5a568b6878be8243ea2b9d82d41ed297.png":::

- > :::image type="content" source="images/6b728d6e0d71108d768e368b416ff8ba.png" alt-text="The Microsoft Intune admin center12" lightbox="images/6b728d6e0d71108d768e368b416ff8ba.png":::

- > :::image type="content" source="images/a7d738dd4509d65407b7d12beaa3e917.png" alt-text="The Microsoft Intune admin center13" lightbox="images/a7d738dd4509d65407b7d12beaa3e917.png":::

- > :::image type="content" source="images/3840b1576d6f79a1d72eb14760ef5e8c.png" alt-text="The Microsoft Intune admin center14" lightbox="images/3840b1576d6f79a1d72eb14760ef5e8c.png":::

- > :::image type="content" source="images/2055e4f9b9141525c0eb681e7ba19381.png" alt-text="The Microsoft Intune admin center15" lightbox="images/2055e4f9b9141525c0eb681e7ba19381.png":::

- > :::image type="content" source="images/48318a51adee06bff3908e8ad4944dc9.png" alt-text="The Microsoft Intune admin center16" lightbox="images/48318a51adee06bff3908e8ad4944dc9.png":::

- > :::image type="content" source="images/38180219e632d6e4ec7bd25a46398da8.png" alt-text="The Microsoft Intune admin center18" lightbox="images/38180219e632d6e4ec7bd25a46398da8.png":::

- > :::image type="content" source="images/522d9bb4288dc9c1a957392b51384fdd.png" alt-text="The Microsoft Intune admin center19" lightbox="images/522d9bb4288dc9c1a957392b51384fdd.png":::

- > :::image type="content" source="images/a5a71fd73ec389f3cdce6d1a6bd1ff31.png" alt-text="The Microsoft Intune admin center20" lightbox="images/a5a71fd73ec389f3cdce6d1a6bd1ff31.png":::

- > :::image type="content" source="images/6daa8d347c98fe94a0d9c22797ff6f28.png" alt-text="The Microsoft Intune admin center22" lightbox="images/6daa8d347c98fe94a0d9c22797ff6f28.png":::

- > :::image type="content" source="images/45cefc8e4e474321b4d47b4626346597.png" alt-text="The Microsoft Intune admin center23" lightbox="images/45cefc8e4e474321b4d47b4626346597.png":::

- > :::image type="content" source="images/2c2e87c5fedc87eba17be0cdeffdb17f.png" alt-text="The Microsoft Intune admin center24" lightbox="images/2c2e87c5fedc87eba17be0cdeffdb17f.png":::

- > :::image type="content" source="images/7a631d17cc42500dacad4e995823ffef.png" alt-text="The Microsoft Intune admin center25" lightbox="images/7a631d17cc42500dacad4e995823ffef.png":::

- > :::image type="content" source="images/5be573a60cd4fa56a86a6668b62dd808.png" alt-text="The Microsoft Intune admin center27" lightbox="images/5be573a60cd4fa56a86a6668b62dd808.png":::

- > :::image type="content" source="images/6104aa33a56fab750cf30ecabef9f5b6.png" alt-text="The Microsoft Intune admin center28" lightbox="images/6104aa33a56fab750cf30ecabef9f5b6.png":::

- > :::image type="content" source="images/6daa8d347c98fe94a0d9c22797ff6f28.png" alt-text="The Microsoft Intune admin center29" lightbox="images/6daa8d347c98fe94a0d9c22797ff6f28.png":::

- > :::image type="content" source="images/45cefc8e4e474321b4d47b4626346597.png" alt-text="The Microsoft Intune admin center30" lightbox="images/45cefc8e4e474321b4d47b4626346597.png":::

- > :::image type="content" source="images/8ee0405f1a96c23d2eb6f737f11c1ae5.png" alt-text="The Microsoft Intune admin center31" lightbox="images/8ee0405f1a96c23d2eb6f737f11c1ae5.png":::

- > [](images/43ab6aa74471ee2977e154a4a5ef2d39.png#lightbox)

- > [](images/55ecaca0e4a022f0e29d45aeed724e6c.png#lightbox)

- > [](images/18a50df62cc38749000dbfb48e9a4c9b.png#lightbox)

- > [](images/4e965749ff71178af8873bc91f9fe525.png#lightbox)

- > [](images/42acc69d0128ed09804010bdbdf0a43c.png#lightbox)

- > [](images/a621b699899f1b41db211170074ea59e.png#lightbox)

- > :::image type="content" source="images/88efb4c3710493a53f2840c3eac3e3d3.png" alt-text="The settings page-1" lightbox="images/88efb4c3710493a53f2840c3eac3e3d3.png":::

- > :::image type="content" source="images/9341428b2d3164ca63d7d4eaa5cff642.png" alt-text="The settings page-2" lightbox="images/9341428b2d3164ca63d7d4eaa5cff642.png":::

- :::image type="content" source="images/619fb877791b1fc8bc7dfae1a579043d.png" alt-text="The command line-2" lightbox="images/619fb877791b1fc8bc7dfae1a579043d.png":::

- :::image type="content" source="images/196a8e194ac99d84221f405d0f684f8c.png" alt-text="The command line-3" lightbox="images/196a8e194ac99d84221f405d0f684f8c.png":::

- :::image type="content" source="images/apply-to-each.png" alt-text="The application of the flow to the Get items element" lightbox="images/apply-to-each.png":::

- :::image type="content" source="images/apply-to-each-value.png" alt-text="The application of the flow to each condition" lightbox="images/apply-to-each-value.png":::

-|[Micro Focus ArcSight](https://go.microsoft.com/fwlink/?linkid=2113548)|Use Micro Focus ArcSight to pull Defender for Endpoint detections

-|[Aruba ClearPass Policy Manager](https://go.microsoft.com/fwlink/?linkid=2127544)|Ensure Defender for Endpoint is installed and updated on each endpoint before allowing access to the network

- :::image type="content" source="images/analysis-results-nothing500.png" alt-text="The deep analysis report showing detailed information across a number of categories" lightbox="images/analysis-results-nothing500.png":::

- 

-|[Attack Surface Reduction](attack-surface-reduction.md)|||||

-|Device Control|||||

-|[Firewall](host-firewall-reporting.md)|||||

-|[Network Protection](network-protection.md)||| ^[2]| ^[2]|

-|[Next-generation protection](next-generation-protection.md)|||||

-|[Tamper Protection](prevent-changes-to-security-settings-with-tamper-protection.md)|||||

-|[Web Protection](web-protection-overview.md)||| ^[2]| ^[2]|

-|[Advanced Hunting](../defender/advanced-hunting-overview.md)|||||

-|[Custom file indicators](indicator-file.md)|||||

-|[Custom network indicators](indicator-ip-domain.md)||| ^[2]| ^[2]|

-|[EDR Block](edr-in-block-mode.md)|||||

-|[Passive Mode](microsoft-defender-antivirus-compatibility.md)|||||

-|Sense detection sensor|||||

-|Endpoint & network device discovery|||||

-|[Vulnerability management](../defender-vulnerability-management/defender-vulnerability-management.md)|||||

-|[Automated Investigation & Response (AIR)](automated-investigations.md) |  |  |  |  |

-|[Device response capabilities: collect investigation package ](respond-machine-alerts.md) |  |  |  ^[3] |  ^[3] |

-|[Device response capabilities: run AV scan](respond-machine-alerts.md) |  |  |  |  |

-|[Device isolation](respond-machine-alerts.md) |  |  |  |  |

-|File response capabilities: collect file, deep analysis, block file, stop, and quarantine processes |  |  |  |  |

-|[Live Response](live-response.md) |  |  |  |  |

-| <br/>Phase 1: Prepare | [](switch-to-mde-phase-2.md)<br/>[Phase 2: Set up](switch-to-mde-phase-2.md) | [](switch-to-mde-phase-3.md)<br/>[Phase 3: Onboard](switch-to-mde-phase-3.md) |

-|[](switch-to-mde-phase-1.md)<br/>[Phase 1: Prepare](switch-to-mde-phase-1.md)|<br/>Phase 2: Set up|[](switch-to-mde-phase-3.md)<br/>[Phase 3: Onboard](switch-to-mde-phase-3.md)|

-| [](switch-to-mde-phase-1.md)<br/>[Phase 1: Prepare](switch-to-mde-phase-1.md) | [](switch-to-mde-phase-2.md)<br/>[Phase 2: Set up](switch-to-mde-phase-2.md) | <br/>Phase 3: Onboard |

- :::image type="content" source="images/analyzer-file.png" alt-text="The choose file button-2" lightbox="images/analyzer-file.png":::

- [](images/analyzer-commands.png#lightbox)

-description: Learn about the tables in the advanced hunting schema to understand the data you can run threat hunting queries on

-| **[EmailPostDeliveryEvents](advanced-hunting-emailpostdeliveryevents-table.md)** | Security events that occur post-delivery, after Microsoft 365 has delivered the emails to the recipient mailbox |

-|Microsoft Threat Experts| On engineering backlog| On engineering backlog| On engineering backlog|

- - _Use **Block sender** to [add senders to your own Blocked Senders list](#block-email-senders-from-quarantine)_: Membership in the **Security Reader**, **Quarantine Administrator** or **Security Administrator** role groups.

- - _Use **Block sender** to [add senders to your own Blocked Senders list](#block-email-senders-from-quarantine)_: Membership in the **Security Reader** or **Security Administrator** roles.

-**Q: How do we submit our packages to the Test Base team?**

-## Testing

-**A:** For Security update tests, we test against the **<ins>monthly pre-release security updates</ins>** on Windows, which is focused on keeping our users always secure and protected. For the Feature update tests, we test against the **<ins>bi-annual pre-release feature updates</ins>** which introduce new features and capabilities on Windows.

- 1. Run all testing job in one central script which doesnΓÇÖt have time limit, monitor the status from multiple Test Base artifact scripts.

-**A:** The goal of Test Base is to ensure our joint end customers don't face any issues. We work hard with Software Vendors to address any issues before the release, but in case the fix is not feasible we have other resolutions such as shims and blocks.