Service | Microsoft Docs article | Related commit history on GitHub | Change details |
---|---|---|---|
SharePoint | Get Started New Admin Center | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/get-started-new-admin-center.md | If you're used to working in the classic SharePoint admin center, to learn where |geo locations | [Advanced > Geo locations](https://admin.microsoft.com/sharepoint?page=geoLocations&modern=true) | | |access control | [Policies > Access control](https://admin.microsoft.com/sharepoint?page=accessControl&modern=true) | The new SharePoint admin center contains all the classic settings and more. | |data migration | [Migration](https://admin.microsoft.com/sharepoint?page=migration&modern=true) | The new Migration Manager lets you migrate from on-premises file shares and SharePoint Server sites as well as popular cloud providers. This feature isn't available if you're signed in as a global reader. [Learn more about Migrating content to Microsoft 365](/sharepointmigration/migrate-to-sharepoint-online) |-|User profiles, Search, Apps, BCS, Secure store, Records management, InfoPath, Configure hybrid (hybrid picker). | [More features](https://admin.microsoft.com/sharepoint?page=classicFeatures&modern=true) | | +|User profiles, Search, Apps, BCS, Secure store, Records management, InfoPath, Configure hybrid (Hybrid Configuration Wizard). | [More features](https://admin.microsoft.com/sharepoint?page=classicFeatures&modern=true) | | ## See also |
SharePoint | Sharepoint Azureb2b Integration | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/sharepoint-azureb2b-integration.md | Advantages of Azure AD B2B include: - If you've configured Google federation in Azure AD, federated users can now access SharePoint and OneDrive resources that you've shared with them. - SharePoint and OneDrive sharing is subject to the Azure AD organizational relationships settings, such as **Members can invite** and **Guests can invite**. As with Microsoft 365 Groups and Teams, if an Azure AD organizational relationship setting is more restrictive than a SharePoint or OneDrive setting, the Azure AD setting will prevail. -This integration isn't supported in the following Microsoft 365 -- Office 365 operated by 21Vianet-- GCC High and DoD-- > [!NOTE] - > At this time, customers in national and restricted clouds who enable Azure B2B Integration with SharePoint Online won't be able to share files and folders with recipients outside those environments. +> [!NOTE] +> This integration isn't supported in Office 365 operated by 21Vianet. ## Enabling the integration |
SharePoint | Sharepoint View In Edge | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/sharepoint-view-in-edge.md | Follow the steps below to use View in File Explorer in Microsoft Edge: 1. Verify that devices are on Microsoft Edge build 93 or later using [Find out which version of Microsoft Edge you have](https://support.microsoft.com/en-us/microsoft-edge/find-out-which-version-of-microsoft-edge-you-have-c726bee8-c42e-e472-e954-4cf5123497eb). -2. Enable the [ConfigureViewInFileExplorer](/deployedge/microsoft-edge-policies#configureviewinfileexplorer) policy for Microsoft Edge that allows URLs with the viewinfileexplorer: scheme to open WebDAV URLs in Windows File Explorer. +2. Ensure that Windows instances are joined to a Microsoft Active Directory domain, Windows 10 Pro, or Enterprise instances that are enrolled for device management. -3. Ensure that Window instances are joined to a Microsoft Active Directory domain, Windows 10 Pro, or Enterprise instances that are enrolled for device management. +3. Enable the [ConfigureViewInFileExplorer](/deployedge/microsoft-edge-policies#configureviewinfileexplorer) policy for Microsoft Edge that allows URLs with the viewinfileexplorer: scheme to open WebDAV URLs in Windows File Explorer. -4. Use the options below to enable View in File Explorer using group policy or Intune: +Use the options below to enable View in File Explorer using group policy or Intune: - **To enable by using group policy**: |
SharePoint | Private Key Management For Ssl Certificates | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/private-key-management-for-ssl-certificates.md | + + Title: "Private key management for SSL certificates" ++++ Last updated : 03/14/2023+audience: ITPro +f1.keywords: +- NOCSH +++ms.localizationpriority: medium ++ms.assetid: 88317397-e0cb-47c7-9093-7872bc685213 +description: "Learn how SSL certificate implements private key management." +++# Private key management for SSL certificates +++To better support least privileges scenarios and minimize the permissions given to certificate private keys, SharePoint Server Subscription Edition Version 23H1 applies more granular and sophisticated permission management for these private keys. The permissions will be based on the certificate assignments and will be dynamically updated when the certificate assignments change. ++For example, if a certificate is assigned to perform client certificate authentication to an Simple Mail Transfer Protocol (SMTP) server, SharePoint will ensure the process thatΓÇÖs connecting to the SMTP server has the necessary permissions to use the private key of that certificate. If a certificate is no longer assigned to perform client certificate authentication to an SMTP server, SharePoint will remove permissions for that process so it no longer has access to the private key of that certificate. ++The following APIs has been added +*Microsoft.SharePoint.Administration.CertificateManagement.SPServerCertificate* class to allow third-party integration with this functionality. |
SharePoint | Ssl Certificate Management | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/ssl-certificate-management.md | This article focuses on the following SSL certificate management operations: - [Certificates administration action logging](certificates-administrative-action-logging.md) - [SSL certificate management in central administration](ssl-certificate-management-in-central-administration.md) - [New health analyzer rules for SSL certificates](new-health-analyzer-rules-for-ssl-certificates.md)+- [Private key management for SSL certificates](private-key-management-for-ssl-certificates.md) |
SharePoint | Install And Configure Workflow For Sharepoint Server | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/governance/install-and-configure-workflow-for-sharepoint-server.md | description: "Learn how to install and configure workflow in SharePoint Server." [!INCLUDE[appliesto-2013-2016-2019-SUB-xxx-md](../includes/appliesto-2013-2016-2019-SUB-xxx-md.md)] -This article contains the information and procedures required to configure workflow in SharePoint Server. +This article contains the information and procedures required to configure Workflow Manager in SharePoint Server. ++> [!NOTE] +>There are two separate workflow engine products that power the SharePoint 2013 Workflow platform: Microsoft Workflow Manager and SharePoint Workflow Manager. Microsoft Workflow Manager is no longer available to be installed, whereas SharePoint Workflow Manager has been released to replace it. Hence, the instructions outlined in this document explain how to install SharePoint Workflow Manager. > [!IMPORTANT] > The steps in this article apply to SharePoint Server. The SharePoint 2013 Workflow platform is not supported in SharePoint Foundation 2013. > [!NOTE]-> You can watch a video series that walks through the process of installing and configuring the SharePoint 2013 Workflow platform. To view the videos, see [Video series: Install and configure Workflow in SharePoint Server 2013](video-series-install-and-configure-workflow-in-sharepoint-server-2013.md) +> You can watch a video series that walks through the process of installing and configuring the SharePoint 2013 Workflow platform. To view the videos, see [Video series: Install and configure Workflow in SharePoint Server 2013](video-series-install-and-configure-workflow-in-sharepoint-server-2013.md). Learn about [Workflows for SharePoint in Microsoft 365](../../SharePointOnline/extend-and-develop.md). ## Overview The only platform available when you first install SharePoint Server is the Shar |**Platform Type**|**Platform Framework**|**Requirements**| |:--|:--|:--| |**SharePoint 2010 Workflow** <br/> |Windows Workflow Foundation 3 <br/> |Installs automatically with SharePoint Server. <br/> |-|**SharePoint 2013 Workflow** <br/> |Windows Workflow Foundation 4 <br/> |Requires SharePoint Server and Workflow Manager. <br/> | -|**SharePoint 2013 Workflow - Project Server** <br/> |Windows Workflow Foundation 4 <br/> |Requires SharePoint Server, Workflow Manager, and Project Server. <br/> | +|**SharePoint 2013 Workflow** <br/> |Windows Workflow Foundation 4 <br/> |Requires SharePoint Workflow Manager or Microsoft Workflow Manager, and SharePoint Server. <br/> | +|**SharePoint 2013 Workflow - Project Server** <br/> |Windows Workflow Foundation 4 <br/> |Requires SharePoint Workflow Manager or Microsoft Workflow Manager, and Project server. <br/> | > [!NOTE] > Workflow Manager must be downloaded and installed separately from SharePoint Server. It does not install automatically when you install SharePoint Server. -## Install Workflow Manager +## New installation of SharePoint Workflow Manager -Workflow Manager may be installed on the same servers as SharePoint or on separate, dedicated servers. Workflow Manager can be deployed with the Web PI tool. For more information on Web PI, see [Using the Microsoft Web Platform Installer](/iis/install/web-platform-installer/using-the-microsoft-web-platform-installer). +SharePoint Workflow Manager may be installed on the same servers as SharePoint or on separate, dedicated servers. -## Install and configure SharePoint Server +### Prerequisites ++SharePoint Workflow Manager requires Azure Service Fabric, which must be installed before you run SharePoint Workflow Manager setup. If the Azure Service Fabric Runtime is not already installed, follow these steps below to install it: ++1. The minimum version of Azure Service Fabric Runtime supported by SharePoint Workflow Manager is 9.0.1048.9590, and you can download it from [Azure Service Fabric Runtime](https://download.microsoft.com/download/8/3/6/836E3E99-A300-4714-8278-96BC3E8B5528/9.0.1048.9590/Microsoft.Azure.ServiceFabric.WindowsServer.9.0.1048.9590.zip). Or you can find and download any higher version of its Windows Installer from [here](/azure/service-fabric/service-fabric-get-started#install-the-sdk-and-tools). +2. Open a PowerShell console as an elevated administrator and run the following command: ++ `.\ MicrosoftServiceFabric.9.0.1048.9590.exe /accepteula` ++3. To verify the Azure Service Fabric is installed, you should be able to find it in the Programs and Features of the Control Panel. ++> [!NOTE] +>SharePoint Workflow Manager supports the version 9.0 CU2 (9.0.1048.9590) of Azure Service Fabric and [higher versions](/azure/service-fabric/service-fabric-versions). You can install higher versions than that. If you want to directly upgrade your Azure Service Fabric without uninstallation, note that there are [upgrade dependencies](/azure/service-fabric/service-fabric-versions). If **Windows Fabric** is already installed on your machine, you must uninstall it before installing Azure Service Fabric. ++### Install SharePoint Workflow Manager ++SharePoint Workflow Manager and SharePoint Workflow Manager Client can be downloaded from [here](https://www.microsoft.com/download/details.aspx?id=104867). +Install both SharePoint Workflow Manager and SharePoint Workflow Manager Client on all servers in the Workflow Manager farm. +Install SharePoint Workflow Manager Client on all servers in the SharePoint Server farm. ++### Install and configure SharePoint Server <a name="section3"> </a> -Install and configure SharePoint Server. To do so, see [Install and deploy SharePoint 2013](../../Hub/index.yml). +Install and configure SharePoint Server. To do so, see [Install and deploy SharePoint Server Subscription Edition](../install/install.md). > [!NOTE]-> The SharePoint 2010 Workflow platform installs automatically when you install SharePoint Server. The SharePoint 2013 Workflow platform requires Workflow Manager and must be installed separately and then configured to work with your SharePoint Server farm. > To function correctly SharePoint 2013 Workflows require to have App Management Service and Site Subscription Service provisioned. It is not required to setup a wildcard certificate and DNS registration but both instances need to be running. - -## Configure Workflow Manager to work with the SharePoint Server farm +> The SharePoint 2010 Workflow platform installs automatically when you install SharePoint Server. The SharePoint 2013 Workflow platform requires either Microsoft Workflow Manager or SharePoint Workflow Manager and must be installed separately and then configured to work with your SharePoint Server farm. To function correctly SharePoint 2013 Workflows require that the App Management Service and Site Subscription Service are provisioned. It is not required to set up a wildcard certificate and DNS registration but both instances need to be running. ++### Configure SharePoint Workflow Manager to work with the SharePoint Server farm <a name="section5"> </a> -Consider the following two key factors before configuring Workflow Manager to work with SharePoint Server. +Consider the following two key factors before configuring SharePoint Workflow Manager to work with SharePoint Server. -- Is Workflow Manager installed on a server that is part of the SharePoint farm?+- Is SharePoint Workflow Manager installed on a server that is part of the SharePoint farm? -- Will communication between Workflow Manager and SharePoint Server use **HTTP** or **HTTPS** ? +- Will communication between SharePoint Workflow Manager and SharePoint Server use **HTTP** or **HTTPS** ? -These factors translate into four scenarios. Each scenario configures a SharePoint Server farm to communicate and function with the Workflow Manager farm. Follow the scenario that matches your circumstance. +These factors translate into four scenarios. Each scenario configures a SharePoint Server farm to communicate and function with the SharePoint Workflow Manager farm. Follow the scenario that matches your circumstance. -|Serial Number and Description|Serial Number and Description| +|Scenario Number and Description|Scenario Number and Description| |:--|:--|-|1: Workflow Manager is installed on a server that is part of the SharePoint Server farm. Communication takes place by using HTTP. <br/> |2: Workflow Manager is installed on a server that is part of the SharePoint Server farm. Communication takes place by using HTTPS. <br/> | -|3: Workflow Manager is installed on a server that is NOT part of the SharePoint Server farm. Communication takes place by using HTTP. <br/> |4: Workflow Manager is installed on a server that is NOT part of the SharePoint Server farm. Communication takes place by using HTTPS. <br/> | +|1: SharePoint Workflow Manager is installed on a server that is part of the SharePoint Server farm. Communication takes place by using HTTP. <br/> |2: SharePoint Workflow Manager is installed on a server that is part of the SharePoint Server farm. Communication takes place by using HTTPS. <br/> | +|3: SharePoint Workflow Manager is installed on a server that is NOT part of the SharePoint Server farm. Communication takes place by using HTTP. <br/> |4: SharePoint Workflow Manager is installed on a server that is NOT part of the SharePoint Server farm. Communication takes place by using HTTPS. <br/> | > [!NOTE] > For security reasons, we recommend HTTPS for a production environment. -> [!TIP] -> For information about least-privilege configuration, see [Least Privilege Configuration for Workflow Manager with SharePoint Server 2013](https://blogs.msdn.com/b/briangre/archive/2013/02/20/least-privilege-configuration-for-windows-azure-workflow-with-sharepoint-2013.aspx). - **To configure Workflow Manager on a server that is part of the SharePoint Server farm and on which communication takes place by using HTTP** +**To configure SharePoint Workflow Manager on a server that is part of the SharePoint Server farm and on which communication takes place by using HTTP** -1. Log on to the computer in the SharePoint Server farm where Workflow Manager was installed. +1. Sign-in to the computer in the SharePoint Server farm where SharePoint Workflow Manager was installed. 2. Open the SharePoint Management Shell as an administrator by right-clicking the **SharePoint Management Shell** and choosing **Run as administrator**. These factors translate into four scenarios. Each scenario configures a SharePoi Register-SPWorkflowService -SPSite "http://myserver/mysitecollection" -WorkflowHostUri "http://workflow.example.com:12291" -AllowOAuthHttp ``` -4. Log on to each server in the SharePoint Server farm. +4. Sign-in to each server in the SharePoint Server farm. Each server in the SharePoint Server farm must have the Workflow Manager Client installed. > [!NOTE]- > When you install Workflow Manager on a server it automatically installs the Workflow Manager Client on that server. You will still need to install the Workflow Manager Client on any additional servers. For example, if you have a farm that contains five servers and you install Workflow Manager on one of those servers you will still need to install the Workflow Manager Client on the four additional servers. + > When you install Workflow Manager on a server it automatically installs the Workflow Manager Client on that server. You will still need to install the Workflow Manager Client on any additional servers. For example, if you have a farm that contains five servers and you install SharePoint Workflow Manager on one of those servers you will still need to install the Workflow Manager Client on the four additional servers. -5. Install the Workflow Manager Client on each server in the SharePoint farm. - - Download and install the Workflow Manager Client here: [https://go.microsoft.com/fwlink/p/?LinkID=268376](https://go.microsoft.com/fwlink/p/?LinkID=268376) - - **To configure Workflow Manager on a server that is part of the SharePoint Server farm and on which communication takes place by using HTTPS** +5. Install the SharePoint Workflow Manager Client on each server in the SharePoint farm. + +**To configure SharePoint Workflow Manager on a server that is part of the SharePoint Server farm and on which communication takes place by using HTTPS** -1. Determine if you need to install Workflow Manager certificates in SharePoint. +1. Determine if you need to install SharePoint Workflow Manager certificates in SharePoint. - Under some circumstances, you have to obtain and install Workflow Manager certificates. If your installation requires that you obtain and install these certificates, you must complete that step before continuing. To learn whether you need to install certificates, and for instructions, see [Install Workflow Manager certificates in SharePoint Server](install-workflow-manager-certificates-in-sharepoint-server.md). + Under some circumstances, you have to obtain and install SharePoint Workflow Manager certificates. If your installation requires that you obtain and install these certificates, you must complete that step before continuing. To learn whether you need to install certificates, and for instructions, see [Install Workflow Manager certificates in SharePoint Server](install-workflow-manager-certificates-in-sharepoint-server.md). -2. Log into the computer in the SharePoint Server farm where Workflow Manager was installed. +2. Sign-in to the computer in the SharePoint Server farm where SharePoint Workflow Manager was installed. 3. Open the SharePoint Management Shell as an administrator by right-clicking the **SharePoint Management Shell** and choosing **Run as administrator**. These factors translate into four scenarios. Each scenario configures a SharePoi Register-SPWorkflowService -SPSite "https://myserver/mysitecollection" -WorkflowHostUri "https://workflow.example.com:12290" ``` -5. Log on to each server in the SharePoint Server farm. +5. Sign-in to each server in the SharePoint Server farm. Each server in the SharePoint Server farm must have the Workflow Manager Client installed. > [!NOTE]- > When you install Workflow Manager on a server it automatically installs the Workflow Manager Client on that server. You will still have to install the Workflow Manager Client on any additional servers. For example, if you have a farm that contains five servers and you install Workflow Manager on one of those servers you will still need to install the Workflow Manager Client on the four additional servers. + > When you install SharePoint Workflow Manager on a server it automatically installs the Workflow Manager Client on that server. You will still have to install the SharePoint Workflow Manager Client on any additional servers. For example, if you have a farm that contains five servers and you install Workflow Manager on one of those servers you will still need to install the Workflow Manager Client on the four additional servers. -6. Install the Workflow Manager Client on each server in the SharePoint farm. - - Download and install the Workflow Manager Client here: [https://go.microsoft.com/fwlink/p/?LinkID=268376](https://go.microsoft.com/fwlink/p/?LinkID=268376) +6. Install the SharePoint Workflow Manager Client on each server in the SharePoint farm. - **To configure Workflow Manager on a server that is NOT part of the SharePoint Server farm and on which communication takes place by using HTTP** +**To configure SharePoint Workflow Manager on a server that is NOT part of the SharePoint Server farm and on which communication takes place by using HTTP** -1. Log on to each server in the SharePoint Server farm. +1. Sign-in to each server in the SharePoint Server farm. -2. Install the Workflow Manager Client on each server in the SharePoint farm. +2. Install the SharePoint Workflow Manager Client on each server in the SharePoint farm. - Before you can run the workflow pairing cmdlet, you must install Workflow Manager Client on each of the servers in the SharePoint farm. + Before you can run the workflow pairing cmdlet, you must install SharePoint Workflow Manager Client on each of the servers in the SharePoint farm. - Download and install the Workflow Manager Client here: [https://go.microsoft.com/fwlink/p/?LinkID=268376](https://go.microsoft.com/fwlink/p/?LinkID=268376) - -3. Open the SharePoint Management Shell as an administrator by right-clicking the **SharePoint 2013 Management Shell** command and choosing **Run as administrator**. +3. Open the SharePoint Management Shell as an administrator by right-clicking the **SharePoint Management Shell** command and choosing **Run as administrator**. 4. Run the **Register-SPWorkflowService** cmdlet. The cmdlet should be run only once and can be run from any of the servers in the SharePoint farm. These factors translate into four scenarios. Each scenario configures a SharePoi ``` > [!IMPORTANT]-> You must install the Workflow Manager Client on each server in the SharePoint farm before you run the pairing cmdlet. +> You must install the SharePoint Workflow Manager Client on each server in the SharePoint farm before you run the pairing cmdlet. - **To configure Workflow Manager on a server that is NOT part of the SharePoint Server farm and on which communication takes place by using HTTPS** +**To configure SharePoint Workflow Manager on a server that is NOT part of the SharePoint Server farm and on which communication takes place by using HTTPS** -1. Determine whether you need to install Workflow Manager certificates in SharePoint 2013. - - Under some circumstances, you have to obtain and install Workflow Manager certificates. If your installation requires that you obtain and install these certificates, you must complete that step before continuing. To learn whether you need to install certificates, and for instructions, see [Install Workflow Manager certificates in SharePoint Server](install-workflow-manager-certificates-in-sharepoint-server.md). +1. Determine whether you need to install SharePoint Workflow Manager certificates in SharePoint Server. -2. Log on to each server in the SharePoint Server farm. + Under some circumstances, you have to obtain and install SharePoint Workflow Manager certificates. If your installation requires that you obtain and install these certificates, you must complete that step before continuing. To learn whether you need to install certificates, and for instructions, see [Install Workflow Manager certificates in SharePoint Server](install-workflow-manager-certificates-in-sharepoint-server.md). -3. Install the Workflow Manager Client on each server in the SharePoint farm. +2. Sign-in to each server in the SharePoint Server farm. - Before you can run the workflow pairing cmdlet, you must install Workflow Manager Client on each of the servers in the SharePoint farm. +3. Install the SharePoint Workflow Manager Client on each server in the SharePoint farm. - Download and install the Workflow Manager Client here: [https://go.microsoft.com/fwlink/p/?LinkID=268376](https://go.microsoft.com/fwlink/p/?LinkID=268376) + Before you can run the workflow pairing cmdlet, you must install SharePoint Workflow Manager Client on each of the servers in the SharePoint farm. 4. Open the SharePoint Management Shell as an administrator. This is accomplished by right-clicking the **SharePoint Management Shell** command and choosing **Run as administrator**. These factors translate into four scenarios. Each scenario configures a SharePoi ``` > [!IMPORTANT]-> You must install the Workflow Manager Client on each server in the SharePoint farm before you run the pairing cmdlet. - +> You must install the SharePoint Workflow Manager Client on each server in the SharePoint farm before you run the pairing cmdlet. ++## Upgrade existing Microsoft Workflow Manager ++In order to update Microsoft Workflow Manager to SharePoint Workflow Manager, SharePoint Workflow Manager cannot be placed on top of Microsoft Workflow Manager. Installing this build requires first uninstalling any prior versions of Workflow Manager (Client) and Service Bus. ++You can upgrade to SharePoint Workflow Manager from any version of Microsoft Workflow Manager. ++Follow the steps below to uninstall Microsoft Workflow Manager and install SharePoint Workflow ++1. Open Workflow Manager Configuration Wizard. +2. Select **Leave Workflow Manager Farm**. +3. Confirm the subsequent steps until the end. + > [!NOTE] + >Each database used by Workflow Manager and Service Bus will need to be specified when rejoining the farm with SharePoint Workflow Manager. For example, the SQL Server instance and database name for the Workflow Manager farm management database and the Service Bus farm management database. ++4. Uninstall Microsoft Workflow Manager, Workflow Manager Client, Service Bus for Windows Server, and Windows Fabric if they're installed. You can uninstall them from the Control Panel. If Windows Fabric is installed, ensure you install Azure Service Fabric after uninstalling Windows Fabric. +5. If the folder *%ProgramFiles%\Workflow Manager\1.0* already exists, you must manually remove it for the next steps to succeed. +6. Install SharePoint Workflow Manager and SharePoint Workflow Manager Client. +7. If there is more than one server in your Workflow Manager farm, repeat the previous steps on all farm servers. +8. Run the Workflow Manager Configuration Wizard and rejoin the previous farm with the databases you noted in the previous steps on all servers in your Workflow Manager farm. + > [!NOTE] + >There is no need to delete the existing Workflow Service Application Proxy, and there is no need to re-register SPWorkflowService. ++9. Rerun the Workflow Manager Configuration Wizard, select **Upgrade Workflow Manager Farm**, and confirm subsequent steps until the end. + > [!NOTE] + >You only need to run this step once on any server in the Workflow Manager farm. ++10. Install SharePoint Workflow Management Client on each server in the SharePoint Server farm after uninstalling any previous versions. + ## Validate the installation <a name="section6"> </a> -Use these steps to validate that you have successfully installed and configured the required components. +Follow these steps to validate that you have successfully installed and configured the required components. **To validate the installation** The user who deploys and runs a workflow must be added to the User Profile servi You can determine which ports SharePoint Server and Workflow Manager are using for both HTTP and HTTPS by using IIS Manager as shown in the figure. -**Figure: Use IIS Manager to view the ports used by Workflow Manager** +**Figure: Use IIS Manager to view the ports used by SharePoint Workflow Manager**  -Workflow Manager communicates by using TCP/IP or Named Pipes. Make sure that the appropriate communication protocol is enabled on the SQL Server instance that hosts the Workflow Manager databases. +Sharepoint Workflow Manager communicates by using TCP/IP or Named Pipes. Ensure that the appropriate communication protocol is enabled on the SQL Server instance that hosts the SharePoint Workflow Manager databases. The SQL Browser Service must be running on the SQL Server instance that hosts the Workflow Manager databases. |
SharePoint | Cloud Hybrid Search Faq | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/hybrid/cloud-hybrid-search-faq.md | Quite frequently, we receive questions regarding Cloud hybrid search service app ***Is there an automated wizard that can help configure hybrid in my environment?*** -Yes, you can leverage the Hybrid picker on the <a href="https://go.microsoft.com/fwlink/?linkid=2185077" target="_blank">**More features** page of the SharePoint admin center</a> for hybrid configurations. This wizard automates certain configuration steps required to connect on-premises SharePoint Server environment with SharePoint in Microsoft 365. [Read more about the Hybrid picker](./hybrid-picker-in-the-sharepoint-online-admin-center.md). +Yes, you can leverage the Hybrid Configuration Wizard on the <a href="https://go.microsoft.com/fwlink/?linkid=2185077" target="_blank">**More features** page of the SharePoint admin center</a> for hybrid configurations. This wizard automates certain configuration steps required to connect on-premises SharePoint Server environment with SharePoint in Microsoft 365. [Read more about the Hybrid Configuration Wizard](hybrid-configuration-wizard-in-the-sharepoint-online-admin-center.md#hybrid-configuration-wizard-in-the-sharepoint-admin-center) -***Can I leverage SharePoint Hybrid picker to perform a clean-up of hybrid environment or deactivate the hybrid features that was activated by picker?*** +***Can I leverage the SharePoint Hybrid Configuration Wizard to perform a clean-up of my hybrid environment or deactivate hybrid features that were activated by the wizard?*** -The Hybrid picker automates certain configuration steps to configure hybrid between on-premises SharePoint Server with SharePoint in Microsoft 365. This is not designed to undo the changes once the wizard completes. The Hybrid picker creates a Server-to-Server (S2S)/OAuth trust between the SharePoint in Microsoft 365 and SharePoint on-premises farm. After this is configured, re-running the wizard does not clean up the trust. You can refer to the documentation at [Hybrid picker in the SharePoint admin center](./hybrid-picker-in-the-sharepoint-online-admin-center.md#sharepoint-hybrid-features-offered-in-the-hybrid-picker). +The Hybrid Configuration Wizard automates certain configuration steps to configure hybrid between on-premises SharePoint Server with SharePoint in Microsoft 365. This is not designed to undo the changes once the wizard completes. The Hybrid Configuration Wizard creates a Server-to-Server (S2S)/OAuth trust between the SharePoint in Microsoft 365 and SharePoint on-premises farm. After this is configured, re-running the wizard does not clean up the trust. You can refer to the documentation at [Hybrid Configuration Wizard in the SharePoint admin center](hybrid-configuration-wizard-in-the-sharepoint-online-admin-center.md#hybrid-configuration-wizard-in-the-sharepoint-admin-center). > [!IMPORTANT]-> If the Hybrid picker is run a second time with an enabled feature unchecked, this will not cause the feature to be uninstalled. Any additional selections will be installed and previously installed features will remain. +> If the Hybrid Configuration Wizard is run a second time with an enabled feature unchecked, this will not cause the feature to be uninstalled. Any additional selections will be installed and previously installed features will remain. ***I plan to configure Cloud hybrid search with high availability (HA) topologies. Is there a script available to configure the same?*** -If you plan to configure Cloud hybrid search with HA topologies in SharePoint Server, you can configure it with Hybrid picker. Hybrid picker has automated certain configuration steps needed to connect your on-premises SharePoint Server environment with SharePoint in Microsoft 365 for Cloud hybrid search. [Learn more](./configure-cloud-hybrid-searchroadmap.md). +If you plan to configure Cloud hybrid search with HA topologies in SharePoint Server, you can configure it with the Hybrid Configuration Wizard. The Hybrid Configuration Wizard has automated certain configuration steps needed to connect your on-premises SharePoint Server environment with SharePoint in Microsoft 365 for Cloud hybrid search. [Learn more](./configure-cloud-hybrid-searchroadmap.md). ***What is hybrid federated search and how is it different from Cloud hybrid search?*** This question primarily revolves around the following use cases: - You have a SharePoint Server farm that already has provider-hosted add-ins and/or leverages workflow manager. -Hybrid features/Cloud search service application can be implemented on same SharePoint farm as mentioned above. When you try to establish a S2S trust via the Cloud SSA onboarding script or Hybrid picker, the authentication realm of the on-premises Farm is updated to match the Microsoft 365 organization context id. Within the script, we set it using [Set-SPAuthenticationRealm](/powershell/module/sharepoint-server/set-spauthenticationrealm). Once the authentication realm is changed, existing SharePoint Add-ins fail to authenticate; users will get an HTTP 401 when they are redirected to the add-ins. You can read more about the problem as well and fix in the article [Provider-hosted add-ins stop working and HTTP 401 error after you configure SharePoint farm hybrid features](/sharepoint/support/administration/provider-hosted-add-ins-stop-working-and-http-401-error-after-configure-farm-hybrid-features). +Hybrid features/Cloud search service application can be implemented on the same SharePoint farm as mentioned above. When you try to establish a S2S trust via the Cloud SSA onboarding script or Hybrid Configuration Wizard, the authentication realm of the on-premises Farm is updated to match the Microsoft 365 organization context id. Within the script, we set it using [Set-SPAuthenticationRealm](/powershell/module/sharepoint-server/set-spauthenticationrealm). Once the authentication realm is changed, existing SharePoint Add-ins fail to authenticate; users will get an HTTP 401 when they are redirected to the add-ins. You can read more about the problem as well and fix in the article [Provider-hosted add-ins stop working and HTTP 401 error after you configure SharePoint farm hybrid features](/sharepoint/support/administration/provider-hosted-add-ins-stop-working-and-http-401-error-after-configure-farm-hybrid-features). > [!NOTE]-> If you configure hybrid using Hybrid picker from the <a href="https://go.microsoft.com/fwlink/?linkid=2185077" target="_blank">**More features** page of the SharePoint admin center</a>, then the wizard takes care of the fix. +> If you configure hybrid using the Hybrid Configuration Wizard from the <a href="https://go.microsoft.com/fwlink/?linkid=2185077" target="_blank">**More features** page of the SharePoint admin center</a>, then the wizard takes care of the fix. ***What are the out-of-box Cloud hybrid search service application crawl limits? Also, can I request additional index quota for my tenant?*** |
SharePoint | Configure Cloud Hybrid Searchroadmap | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/hybrid/configure-cloud-hybrid-searchroadmap.md | To complete the configuration steps you'll need these items: - The search architecture plan you made for cloud hybrid search. -- If you'll use the [Hybrid picker in the SharePoint admin center](hybrid-picker-in-the-sharepoint-online-admin-center.md) wizard to help you configure, ensure that the application farm that hosts the SharePoint Server Central Administration website has [.NET 4.6.3](https://www.microsoft.com/download/details.aspx?id=53321) installed.+- If you'll use the [Hybrid Configuration Wizard in the SharePoint admin center](hybrid-configuration-wizard-in-the-sharepoint-online-admin-center.md#hybrid-configuration-wizard-in-the-sharepoint-admin-center) to help you configure, ensure that the application farm that hosts the SharePoint Server Central Administration website has [.NET 4.6.2 or higher](https://dotnet.microsoft.com/download/dotnet-framework/net462) installed. - If you'll use the **CreateCloudSSA.ps1** and **Onboard-CloudHybridSearch.ps1** Microsoft PowerShell scripts to help you configure, find them in the [Microsoft Download Center](https://go.microsoft.com/fwlink/?LinkId=717902). You'll also need the [Microsoft Online Services Sign-In Assistant for IT Professionals RTW](https://go.microsoft.com/fwlink/?LinkID=286152) and the [Azure Active Directory Module for Windows PowerShell](https://www.powershellgallery.com/packages/MSOnline/1.1.183.8). If you already completed step 1 when you configured a different hybrid solution, |Step <br/> |Description <br/> | |:--|:--| |**1. [Configure Microsoft 365 for SharePoint hybrid](./configure-office-365-for-sharepoint-hybrid.md)** <br/> |Configure your Microsoft 365 organization for a hybrid environment, including registering your domain, configuring UPN suffixes, and synchronizing your on-premises user accounts with Microsoft 365. <br/> |-|**2. [Create a cloud Search service application in SharePoint Server](configure-cloud-hybrid-searchroadmap.md#BKMK_CreateCloudSSA)** <br/> |Run the Hybrid Picker wizard on the application farm that hosts the SharePoint ServerCentral Administration website. <br/> Alternatively, run the **CreateCloudSSA.ps1** PowerShellscript <br/> | -|**3. [Connect your cloud Search service application to your Microsoft 365 organization](configure-cloud-hybrid-searchroadmap.md#BKMK_ConnectCloudSSAToO365)** <br/> |If you used the Hybrid Picker wizard to create a cloud Search service application, skip this step. The Hybrid Picker automatically connected your environments. <br/> Otherwise, run the **Onboard-CloudHybridSearch.ps1** PowerShell script to onboard your cloud SSA and Microsoft 365 organization to cloud hybrid search. The script sets up the cloud SSA to interact with the Microsoft 365 organization and also sets up server-to-server authentication. <br/> | +|**2. [Create a cloud Search service application in SharePoint Server](configure-cloud-hybrid-searchroadmap.md#BKMK_CreateCloudSSA)** <br/> |Run the Hybrid Configuration Wizard on the application farm that hosts the SharePoint Server Central Administration website. <br/> Alternatively, run the **CreateCloudSSA.ps1** PowerShell script. <br/> | +|**3. [Connect your cloud Search service application to your Microsoft 365 organization](configure-cloud-hybrid-searchroadmap.md#BKMK_ConnectCloudSSAToO365)** <br/> |If you used the Hybrid Configuration Wizard to create a cloud Search service application, skip this step. The Hybrid Configuration Wizard automatically connected your environments. <br/> Otherwise, run the **Onboard-CloudHybridSearch.ps1** PowerShell script to onboard your cloud SSA and Microsoft 365 organization to cloud hybrid search. The script sets up the cloud SSA to interact with the Microsoft 365 organization and also sets up server-to-server authentication. <br/> | |**4. [Set up search architecture in SharePoint Server for cloud hybrid search](configure-cloud-hybrid-searchroadmap.md#BKMK_SetupSearchArch)** <br/> |This step is optional. If you planned a search architecture that's different from the default one, set up the planned search architecture. <br/> | |**5. [Create a content source for cloud hybrid search to crawl](configure-cloud-hybrid-searchroadmap.md#BKMK_CreateOnPremContentSource)** <br/> |We recommend adding a small file share first, you can add more on-premises content later. <br/> | |**6. [Set up a separate Search Center in Office 365 to validate hybrid search results](configure-cloud-hybrid-searchroadmap.md#BKMK_SetupValidationSearchCenter)** <br/> |Keep the existing search experience unchanged by setting up a separate Search Center in Office 365 so you can validate and tune the new search experience there. <br/> | The cloud SSA lets you crawl and add metadata from on-premises content to the se > [!NOTE] > If your organization restricts computers from connecting to the internet, you need to allow access to the endpoints (FQDNs) that cloud hybrid search uses. Include the endpoints in your outbound allow lists. The endpoints are listed in the SharePoint in Microsoft 365 section of the article [Microsoft 365 URLs and IP address ranges](/office365/enterprise/urls-and-ip-address-ranges) and are marked for use with Hybrid Search. -Use the Hybrid Picker to connect your SharePoint Server and Microsoft 365 environments and create the cloud Search service application. +Use the Hybrid Configuration Wizard to connect your SharePoint Server and Microsoft 365 environments and create the cloud Search service application. On the application server that hosts the SharePoint Server Central Administration website: On the application server that hosts the SharePoint Server Central Administratio - Application Administrator - Cloud Application Administrator -3. Navigate to [https://go.microsoft.com/fwlink/?linkid=867176](https://go.microsoft.com/fwlink/?linkid=867176) to download, install, and start the Hybrid Picker wizard. +3. Navigate to [https://go.microsoft.com/fwlink/?linkid=867176](https://go.microsoft.com/fwlink/?linkid=867176) to download, install, and start the Hybrid Configuration Wizard. -4. Follow the prompts in the Hybrid Picker and select the hybrid search feature. +4. Follow the prompts in the Hybrid Configuration Wizard and select the hybrid search feature. -The Hybrid Picker lets you choose between a cloud SSA with the default search architecture on the application server that hosts the SharePoint Server Central Administration website, or a cloud SSA with a search architecture on **two** application servers (supports [high availability](../search/plan-enterprise-search-architecture.md#BKMK_HiAvail)) +The Hybrid Configuration Wizard lets you choose between a cloud SSA with the default search architecture on the application server that hosts the SharePoint Server Central Administration website, or a cloud SSA with a search architecture on **two** application servers (supports [high availability](../search/plan-enterprise-search-architecture.md#BKMK_HiAvail)). -The Hybrid Picker saves you time because it also connects the cloud SSA to your Microsoft 365 organization (step 3). +The Hybrid Configuration Wizard saves you time because it also connects the cloud SSA to your Microsoft 365 organization (step 3). ### Alternative methods for creating a cloud Search service application To create a cloud SSA by running the **CreateCloudSSA.ps1** PowerShell script, f > [!NOTE] > When you installed SharePoint Server, the user account from which you ran the installation was granted the appropriate permissions to run Windows PowerShell cmdlets. -On the application server that hosts the SharePoint ServerCentral Administration website, follow these steps: +On the application server that hosts the SharePoint Server Central Administration website, follow these steps: 1. Make sure you're using the same user account as when you installed SharePoint Server. This account is granted the appropriate permissions to run Window Powershell cmdlets. If you want to make your own PowerShell script for creating a cloud SSA, first s <a name="BKMK_ConnectCloudSSAToO365"> </a> > [!NOTE]-> If you used the Hybrid Picker to create a cloud Search service application, then you can skip this step. +> If you used the Hybrid Configuration Wizard to create a cloud Search service application, then you can skip this step. This section guides you how to onboard your cloud SSA and Microsoft 365 organization to cloud hybrid search and covers: This section guides you how to onboard your cloud SSA and Microsoft 365 organiza - **Configuring server-to-server authentication** - Server-to-server authentication allows servers to access and request resources from one another on behalf of users. -On the application server that hosts the SharePoint ServerCentral Administration website, follow these steps: +On the application server that hosts the SharePoint Server Central Administration website, follow these steps: 1. Ensure that the date and time of the server is synchronized with the other servers in the SharePoint Server farm. |
SharePoint | Configure Hybrid Onedrive For Business | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/hybrid/configure-hybrid-onedrive-for-business.md | To configure hybrid OneDrive, you must be both a SharePoint Server farm administ 3. Click **Go to Hybrid Picker Download Page**. -4. On the SharePoint in Microsoft 365 Hybrid Picker page, select **click here**. +4. On the SharePoint in Microsoft 365 Hybrid Configuration Wizard page, select **click here**. 5. Accept the security prompts to install and run the wizard. -6. On the **SharePoint Hybrid Picker** page, select **Next**. +6. On the **SharePoint Hybrid Configuration Wizard** page, select **Next**. 7. On the **Credentials** page, verify your on-premises credentials and enter your global admin credentials. Select **Validate credentials**, and then select **Next**. |
SharePoint | Configure Hybrid Sharepoint Taxonomy And Hybrid Content Types | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/hybrid/configure-hybrid-sharepoint-taxonomy-and-hybrid-content-types.md | description: "In this article, we look at how to configure hybrid SharePoint tax In this article, we look at how to configure hybrid SharePoint taxonomy and hybrid content types. -Hybrid SharePoint taxonomy allows you to have a shared taxonomy between SharePoint Server and SharePoint in Microsoft 365. Hybrid content types allows you to have a shared set of content types between SharePoint Server and SharePoint in Microsoft 365. +Hybrid SharePoint taxonomy allows you to have a shared taxonomy between SharePoint Server and SharePoint in Microsoft 365. Hybrid content types allow you to have a shared set of content types between SharePoint Server and SharePoint in Microsoft 365. Before you follow the procedures in this article, be sure to read [Plan hybrid SharePoint taxonomy and hybrid content types](plan-hybrid-sharepoint-taxonomy-and-hybrid-content-types.md). This feature is available in SharePoint Server 2013 and SharePoint Server 2016 w - Hybrid taxonomy requires the November 2016 public update or later. -- Hybrid content types requires the June 2017 public update or later.+- Hybrid content types require the June 2017 public update or later. The functionality and configuration procedures are the same for both versions of SharePoint Server. This video shows a walkthrough of configuring hybrid taxonomy and hybrid content ## Migrate your taxonomy from SharePoint Server -If you have an existing taxonomy in SharePoint Server, the best practice is to copy any term groups you want to be part of the shared taxonomy to SharePoint in Microsoft 365 before you configure hybrid SharePoint taxonomy. You can migrate additional taxonomy groups from SharePoint Server to SharePoint in Microsoft 365 to add to the shared taxonomy later, but if you do you may need to run the configuration wizard again to include them in the shared taxonomy. +If you have an existing taxonomy in SharePoint Server, the best practice is to copy any term groups you want to be part of the shared taxonomy to SharePoint in Microsoft 365 before you configure hybrid SharePoint taxonomy. You can migrate more taxonomy groups from SharePoint Server to SharePoint in Microsoft 365 to add to the shared taxonomy later, but if you do, you may need to run the Hybrid Configuration Wizard again to include them in the shared taxonomy. -The migration process copies taxonomy groups from SharePoint Server to SharePoint in Microsoft 365. This is done by using the [Copy-SPTaxonomyGroups](/powershell/module/sharepoint-server/Copy-SPTaxonomyGroups?view=sharepoint-ps&preserve-view=true) PowerShell cmdlet. +The migration process copies taxonomy groups from SharePoint Server to SharePoint in Microsoft 365 by using the [Copy-SPTaxonomyGroups](/powershell/module/sharepoint-server/Copy-SPTaxonomyGroups?view=sharepoint-ps&preserve-view=true) PowerShell cmdlet. **Active Directory groups** -While the copy process preserves most user information associated with term sets - such as owner and stakeholders - note, that the copy process does not work with Active Directory groups. If you use Active Directory groups in your term sets, there are two options for copying your taxonomy groups: +While the copy process preserves most user information associated with term sets - such as owner and stakeholders - note, that the copy process doesn't work with Active Directory groups. If you use Active Directory groups in your term sets, there are two options for copying your taxonomy groups: -- You can replace the Active Directory groups with individual users within your taxonomy groups. The individual users will be copied when you copy your taxonomy groups.+- You can replace the Active Directory groups with individual users within your taxonomy groups. The individual users are copied when you copy your taxonomy groups. -- You can copy your taxonomy groups with the Active Directory groups in place. You will see a PowerShell warning and the Active Directory group assignments will be lost if you proceed. You can then assign a Microsoft 365 group in place of the Active Directory group after you've copied the taxonomy groups.+- You can copy your taxonomy groups with the Active Directory groups in place. You'll see a PowerShell warning and the Active Directory group assignments are lost if you proceed. You can then assign a Microsoft 365 group in place of the Active Directory group after you've copied the taxonomy groups. **Copying taxonomy groups** $credential = Get-Credential Copy-SPTaxonomyGroups -LocalTermStoreName "Managed Metadata Service" -LocalSiteUrl "https://sharepoint" -RemoteSiteUrl "https://contoso.sharepoint.com" -GroupNames "Engineering","Marketing" -Credential $credential ``` -Note that you can also simply run Copy-SPTaxonomyGroups and you will be prompted for the needed parameters. +You can also run Copy-SPTaxonomyGroups and you'll be prompted for the needed parameters. **Copying content types** If you're planning to use hybrid content types, you can copy your SharePoint Ser Copy-SPContentTypes -LocalSiteUrl http://localsite/ -LocalTermStoreName "managed metadata service application proxy" -RemoteSiteUrl https://contoso.sharepoint.com/ -ContentTypeNames @("ContentTypeA", "ContentTypeB") -Credential $credential ``` -The content types will be copied into https://contoso.sharepoint.com/sites/contentTypeHub. If this site does not exist, it will be created for you and the Site Collection Feature Content Type Syndication Hub will be enabled. The site URL is hard coded and cannot be changed. +The content types are copied into https://contoso.sharepoint.com/sites/contentTypeHub. If this site doesn't exist, it's created for you, and the Site Collection Feature Content Type Syndication Hub is enabled. The site URL is hard coded and can't be changed. ## Configure hybrid SharePoint taxonomy -Configuration of hybrid SharePoint taxonomy is done using the Hybrid Picker in the SharePoint admin center. The Hybrid Picker has a number of prerequisites. Be sure to read [Hybrid picker in the SharePoint admin center](hybrid-picker-in-the-sharepoint-online-admin-center.md) before you follow the procedures in this section. +Configuration of hybrid SharePoint taxonomy is done using the Hybrid Configuration Wizard in the SharePoint admin center. The Hybrid Configuration Wizard has many prerequisites. Be sure to read [Hybrid Configuration Wizard in the SharePoint admin center](hybrid-configuration-wizard-in-the-sharepoint-online-admin-center.md#hybrid-configuration-wizard-in-the-sharepoint-admin-center) before you follow the procedures in this section. We also recommend that you back up your term store before you proceed. For taxonomy replication to work properly, the account that runs the SharePoint 3. Add the timer service account to the **Term Store Administrators** box, and then select **Save**. - **Configure hybrid SharePoint taxonomy using the Hybrid Picker** + **Configure hybrid SharePoint taxonomy using the Hybrid Configuration Wizard** -The next step is to configure hybrid SharePoint taxonomy by running the Hybrid Picker in the SharePoint admin center. +The next step is to configure hybrid SharePoint taxonomy by running the Hybrid Configuration Wizard in the SharePoint admin center. **To configure hybrid SharePoint taxonomy** -1. Log on to a server in your SharePoint Server farm as the farm administrator. +1. Sign in a server in your SharePoint Server farm as the farm administrator. 2. From your SharePoint Server computer, open a web browser. Like other timer jobs in SharePoint in Microsoft 365, you can configure the Taxo If at any time you want to stop taxonomy replication between SharePoint in Microsoft 365 and SharePoint Server, you can do so by using PowerShell. -The [Stop-SPTaxonomyReplication](/powershell/module/sharepoint-server/Stop-SPTaxonomyReplication?view=sharepoint-ps&preserve-view=true) cmdlet will stop taxonomy replication. For example: +The [Stop-SPTaxonomyReplication](/powershell/module/sharepoint-server/Stop-SPTaxonomyReplication?view=sharepoint-ps&preserve-view=true) cmdlet stops taxonomy replication. For example: ``` $credential = Get-Credential $credential = Get-Credential Stop-SPTaxonomyReplication -Credential $credential ``` -The [Stop-SPContentTypeReplication](/powershell/module/sharepoint-server/?view=sharepoint-ps&preserve-view=true) cmdlet will stop content type replication: +The [Stop-SPContentTypeReplication](/powershell/module/sharepoint-server/?view=sharepoint-ps&preserve-view=true) cmdlet stops content type replication: ``` Stop-SPContentTypeReplication ``` -If you wish to reenable taxonomy replication again, you must run the Hybrid Picker again. +If you wish to reenable taxonomy replication again, you must run the Hybrid Configuration Wizard again. -If you simply want to reconfigure which taxonomy groups you are replicating, there's no need to stop replication. You can just run the hybrid picker again and specify the new taxonomy groups that you want to replicate. +If you simply want to reconfigure which taxonomy groups you're replicating, there's no need to stop replication. You can just run the Hybrid Configuration Wizard again and specify the new taxonomy groups that you want to replicate. ## See also |
SharePoint | Configure Hybrid Sites Featuresroadmap | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/hybrid/configure-hybrid-sites-featuresroadmap.md | This article provides a roadmap for configuring [hybrid sites features](sharepoi |1. [Configure Microsoft 365 for SharePoint in Microsoft 365 hybrid](configure-office-365-for-sharepoint-hybrid.md) <br/> |Configure your Microsoft 365 for enterprises organization for a hybrid environment, including registering your domain, configuring UPN suffixes, and synchronizing your user accounts. <br/> | |2. [Set up SharePoint in Microsoft 365 services for hybrid environments](set-up-sharepoint-services-for-hybrid-environments.md) <br/> |Configure the needed SharePoint in Microsoft 365 services for hybrid search, including User Profiles, MySites, and the Application Management service. <br/> | |**3. (SharePoint Server 2013 only) [Install the September PU for SharePoint Server 2013](/officeupdates/sharepoint-updates)** <br/> |Install the September 2015 PU or higher for SharePoint Server 2013. (We recommend installing the latest PU.) <br/> |-|3. [Run Hybrid Picker](run-hybrid-picker.md) <br/> |Configure hybrid sites features by running the Hybrid Picker in Microsoft 365. <br/> | +|3. [Run Hybrid Configuration Wizard](run-hybrid-picker.md) <br/> |Configure hybrid sites features by running the Hybrid Configuration Wizard in Microsoft 365. <br/> | |4. Quick test <br/> | Check to make sure hybrid sites features are working: <br/> Log in to a SharePoint Server as a regular user. (Be sure you're a member of the correct audience if you used audiences.) <br/> Select the Follow link at the top of the page. <br/> You should see a small pop-up under **Follow** letting you know that you're following the site. Select this pop-up and note that it navigates to your personal site, and the list of sites you're following in SharePoint in Microsoft 365. <br/> | ## The extensible hybrid app launcher |
SharePoint | Configure Server To Server Authentication | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/hybrid/configure-server-to-server-authentication.md | description: Learn how to build a server-to server trust between SharePoint Serv This article is part of a roadmap of procedures for configuring SharePoint hybrid solutions. Be sure you're [following a roadmap](configuration-roadmaps.md) when you do the procedures in this article. > [!NOTE]-> We recommend using the [SharePoint Hybrid Picker](hybrid-picker-in-the-sharepoint-online-admin-center.md) to establish the Server-to-Server authentication between SharePoint Server and SharePoint in Microsoft 365. If you are unable to use the Hybrid Picker for any reason, follow the steps in this article to enable server-to-server authentication. +> We recommend using the [SharePoint Hybrid Configuration Wizard](hybrid-configuration-wizard-in-the-sharepoint-online-admin-center.md#hybrid-configuration-wizard-in-the-sharepoint-admin-center) to establish the Server-to-Server authentication between SharePoint Server and SharePoint in Microsoft 365. If you are unable to use the Hybrid Configuration Wizard for any reason, follow the steps in this article to enable server-to-server authentication. ## Configure server-to-server authentication |
SharePoint | Explore Sharepoint Server Hybrid | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/hybrid/explore-sharepoint-server-hybrid.md | When you're done exploring, [plan your hybrid deployment](plan-sharepoint-server |[SharePoint hybrid sites and search](sharepoint-hybrid-sites-and-search.md) <br/> |Learn about the available hybrid features related to sites and search that can help create a cohesive user experience between SharePoint Server and SharePoint in Microsoft 365. <br/> | |[Learn about cloud hybrid search for SharePoint](./learn-about-cloud-hybrid-search-for-sharepoint.md) <br/> |Learn about cloud hybrid search, its advantages, and what search experiences are available for your users. <br/> | |[Learn about hybrid federated search for SharePoint](learn-about-hybrid-federated-search-for-sharepoint.md) <br/> |Learn about the different scenarios available for hybrid federated search and what search experiences they enable for your users. <br/> |-|[Hybrid picker in the SharePoint admin center](hybrid-picker-in-the-sharepoint-online-admin-center.md) <br/> |Learn about the hybrid picker configuration wizard and which hybrid scenarios it enables. <br/> | +|[Hybrid Configuration Wizard in the SharePoint admin center](hybrid-configuration-wizard-in-the-sharepoint-online-admin-center.md#hybrid-configuration-wizard-in-the-sharepoint-admin-center) <br/> |Learn about the Hybrid Configuration Wizard and which hybrid scenarios it enables. <br/> | ## Related topics |
SharePoint | Hardware And Software Requirements For Sharepoint Hybrid | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/hybrid/hardware-and-software-requirements-for-sharepoint-hybrid.md | This article describes the prerequisites that are required to deploy a SharePoin ## Certificate requirements <a name="CertReq"> </a> -The default STS certificate in the SharePoint farm is used by the hybrid picker to establish the token signing trust when configuring hybrid workloads. Using the inbuilt STS certificate is the recommended approach when configuring hybrid workloads. If however, you intend to use a publicly signed certificate instead of the inbuilt STS one then you must replace the inbuilt certificate with your own following the provided guidance. +The default STS certificate in the SharePoint farm is used by the Hybrid Configuration Wizard to establish the token signing trust when configuring hybrid workloads. Using the inbuilt STS certificate is the recommended approach when configuring hybrid workloads. If however, you intend to use a publicly signed certificate instead of the inbuilt STS one then you must replace the inbuilt certificate with your own following the provided guidance. For more information, see [Replace the STS certificate](plan-server-to-server-authentication-m365.md). |
SharePoint | Hybrid Configuration Wizard In The Sharepoint Online Admin Center | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/hybrid/hybrid-configuration-wizard-in-the-sharepoint-online-admin-center.md | + + Title: Hybrid Configuration Wizard in the SharePoint admin center ++++ Last updated : 3/9/2023+audience: ITPro +f1.keywords: +- CSH +++ms.localizationpriority: medium ++- Ent_O365_Hybrid +- IT_Sharepoint_Server +- IT_SharePoint_Hybrid_Top +- Strat_SP_gtc +- M365-collaboration +- SPO_Content ++ms.assetid: dcac4cbf-7840-470a-9712-3b968c4f06d0 +description: Learn how to use the Hybrid Configuration Wizard in the SharePoint admin center. ++++# Hybrid Configuration Wizard in the SharePoint admin center +++## What is the Hybrid Configuration Wizard? ++Hybrid Configuration Wizard is a wizard that can be downloaded to your SharePoint Server from Microsoft 365. The wizard helps automate certain configuration steps needed to connect your on-premises SharePoint Server environment with SharePoint in Microsoft 365. The Hybrid Configuration Wizard is your assistant, designed to do some of the work for you. ++Use the Hybrid Configuration Wizard to redirect OneDrive to Microsoft 365, leverage hybrid site features or app launcher, and add some extra integration between on-premises SharePoint Server and an extranet site made in Microsoft 365. Hybrid Configuration Wizard also creates a Server-to-Server (S2S)/OAuth connection for your [SharePoint Hybrid features](sharepoint-hybrid-sites-and-search.md). ++## Using the Hybrid Configuration Wizard ++First, you need to ensure you meet the prerequisites in your SharePoint Server on-premises farm, then you can run the Hybrid Configuration Wizard. ++ **Prerequisites to run the Hybrid Configuration Wizard** ++The Hybrid Configuration Wizard requires the [.NET Framework 4.6.2](https://dotnet.microsoft.com/download/dotnet-framework/net462) in order to run. ++To run the Hybrid Configuration Wizard, you must be: ++- A member of the Farm Administrators group. ++- A service application administrator (Full Control) for the User Profile Service. ++- A Microsoft 365 Global Admin, either with or without multi-factor authentication (MFA) enabled for the account. ++- Signed in to Microsoft 365 and SharePoint Server from a server in your SharePoint Server farm. ++- Able to launch the Hybrid Configuration Wizard as a Farm Admin with elevated permissions. ++> [!IMPORTANT] +> The Hybrid Configuration Wizard must be launched from an on-premises server with SharePoint Server 2013, SharePoint Server 2016, SharePoint Server 2019, or SharePoint Server Subscription Edition installed. Launch it in the environment you want to use for your SharePoint hybrid. ++## SharePoint Hybrid features offered in the Hybrid Configuration Wizard ++Use the Hybrid Configuration Wizard to configure, or assist with the configuration of, hybrids that connect Microsoft 365 and your on-premises SharePoint environment. ++The Hybrid Configuration Wizard helps with or completes the setup of these hybrid features: ++- **[Hybrid OneDrive](plan-hybrid-onedrive-for-business.md)** - Choosing this option will redirect on-premises My Sites/OneDrive sites to SharePoint in Microsoft 365 and OneDrive. After the wizard completes, any click of the OneDrive link from on-premises redirects to OneDrive in the cloud. Once your redirection is complete, the users can begin to migrate any files to their online OneDrive. This option also sets up hybrid user profiles. When users click to view a profile, they'll be redirected to the profile in Microsoft 365. ++- **[Hybrid Sites Features](sharepoint-hybrid-sites-and-search.md)** - Choosing this option sets up hybrid sites features, a suite of site integration features, and OneDrive redirection. Selecting this option configures hybrid OneDrive and hybrid user profiles, hybrid site following, and the hybrid app launcher. ++- **[Hybrid App Launcher](the-extensible-hybrid-app-launcher.md)** - This hybrid feature further integrates Microsoft 365 with your on-premises SharePoint Server farm by placing tiles like Office 365 Delve and Video (and custom Microsoft 365 tiles you may have) on the on-premises SharePoint Server App Launcher. This option also sets up hybrid OneDrive with user profile redirection, and sites features. ++- **[Business-to-business (B2B) extranet sites](../../SharePointOnline/create-b2b-extranet.md)** - Choosing this option installs extra features you can integrate with an extranet site you create in Microsoft 365. With Microsoft 365 extranet, partners can connect directly to a members-only site in Microsoft 365 without access to the corporate on-premises environment or any other Microsoft 365 site. Choosing this option sets up OneDrive and user profile redirection, sites features, and hybrid app launcher. ++- **[Hybrid Taxonomy](plan-hybrid-sharepoint-taxonomy-and-hybrid-content-types.md)** - This feature allows a centralized taxonomy that's readable and writable in the Microsoft 365 Cloud, to be used as a read-only copy within the premises. This feature includes Hybrid Content type (June 2017 PU required) which replicates the published content types in Microsoft 365 to on-premises. Choosing this option sets up OneDrive and user profile redirection, sites features, and hybrid app launcher. ++- **[Hybrid self-service site creation](hybrid-self-service-site-creation.md)** - This feature redirects the default self-service site creation page in SharePoint Server 2013, SharePoint Server 2016, or SharePoint Server 2019 (/_layouts/15/scsignup.aspx) to the SharePoint in Microsoft 365 Group Creation page. This setting can be configured independently for each web application in your farm. It helps your users create their sites in SharePoint in Microsoft 365 instead of SharePoint Server. ++- **[Cloud hybrid search](./learn-about-cloud-hybrid-search-for-sharepoint.md)** - Choosing this option creates a cloud Search service application in SharePoint Server and connects it to your Microsoft 365 organization. Implementing this option means you've performed one of the steps needed to set up cloud hybrid search; you must do the rest of the steps yourself (see the [roadmap](configure-cloud-hybrid-searchroadmap.md)). This option doesn't include setting up of other hybrid features. ++> [!TIP] +> If the Hybrid Configuration Wizard is run a second time with an enabled feature unchecked, this setting won't cause the feature to be uninstalled. Any additional selections will be installed and previously installed features will remain. ++For all options, the Hybrid Configuration Wizard configures a server-to-server trust between your SharePoint Server farm and Microsoft 365. ++The Hybrid Configuration Wizard doesn't uninstall features. If you run the Hybrid Configuration Wizard and deselect a feature that you previously installed, it remains installed. ++To get started configuring hybrid features for your environment, choose from: ++- [Configure hybrid OneDrive - roadmap](configure-hybrid-onedrive-for-businessroadmap.md) ++- [Configure hybrid sites features - roadmap](configure-hybrid-sites-featuresroadmap.md) ++- [Configure cloud hybrid search - roadmap](configure-cloud-hybrid-searchroadmap.md) ++- [Configure hybrid SharePoint taxonomy and hybrid content types](configure-hybrid-sharepoint-taxonomy-and-hybrid-content-types.md) ++## Hybrid Configuration Wizard Prerequisite Checking ++While running the Hybrid Configuration Wizard, the basic SharePoint farm settings are checked which would otherwise block the setup of essential hybrid building-blocks (such as OAuth/S2S Trust). The importance of settings' check is why you should launch the Hybrid Configuration Wizard from a server that will be part of your SharePoint hybrid. Some of the settings that are detected and checked while the configuration is run, include whether the: ++- SharePoint Server farm exists ++- Account is a farm administrator ++- SharePoint farm is a version that can function in a hybrid configuration ++- AppMangementServiceInstance is online ++- AppMangementServiceApplication is online ++- AppMangementServiceApplicationProxy is online ++- UserProfileApplicationProxy is online ++- The SPO365LinkSettings cmdlet (used to set MySiteHostURL) is accessible on the server ++The results of this testing can be viewed as a report if any prerequisite isn't met. If all prerequisites are met, you'll see green check-marks beside all the prerequisites and can continue your hybrid configuration. ++## Authentication realm update ++As part of hybrid configuration, the Hybrid Configuration Wizard updates the on-premises farm's authentication realm to match the Microsoft 365 organization context ID. After the authentication realm is changed, existing SharePoint in Microsoft 365 add-ins fail to authenticate. The Hybrid Configuration Wizard attempts to fix this issue automatically. If the Hybrid Configuration Wizard isn't able to fix this issue or if you choose to fix it manually, follow the steps in [Fix the HTTP 401 error with provider-hosted add-ins and issues with workflow and cross farm trust scenarios in SharePoint in Microsoft 365](https://support.microsoft.com/help/4010011). ++## See also ++#### Other Resources ++[You receive the error "Value cannot be null. Parameter name: My site URL or team site URL from Discovery Service is null or empty" when you use the SharePoint Hybrid Configuration Wizard](https://support.microsoft.com/kb/3204761) |
SharePoint | Hybrid Picker In The Sharepoint Online Admin Center | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/hybrid/hybrid-picker-in-the-sharepoint-online-admin-center.md | - Title: Hybrid picker in the SharePoint admin center---- Previously updated : 12/5/2017-- CSH----- Ent_O365_Hybrid-- IT_Sharepoint_Server-- IT_SharePoint_Hybrid_Top-- Strat_SP_gtc-- M365-collaboration-- SPO_Content- -description: Learn how to use the Hybrid Picker wizard in the SharePoint admin center. ----# Hybrid picker in the SharePoint admin center ---## What is the Hybrid Picker? --Hybrid Picker is a wizard that can be downloaded to your SharePoint Server from Microsoft 365. The wizard helps automate certain configuration steps needed to connect your on-premises SharePoint Server environment with SharePoint in Microsoft 365. The Hybrid Picker wizard is your assistant, designed to do some of the work for you. --Use the Hybrid Picker wizard to redirect OneDrive to Microsoft 365, leverage hybrid site features or app launcher, and add some extra integration between on-premises SharePoint Server and an extranet site made in Microsoft 365. Hybrid Picker also creates a Server-to-Server (S2S)/OAuth connection for your [SharePoint Hybrid features](sharepoint-hybrid-sites-and-search.md). --## Using the Hybrid Picker --First, you need to make sure you meet the prerequisites in your SharePoint Server on-premises farm, then you can run the Hybrid Picker wizard. -- **Prerequisites to run the Picker** --The Picker requires the [.NET Framework 4.6.2](https://www.microsoft.com/download/details.aspx?id=53321) in order to run. --The following are the account requirements to run the Hybrid Picker. You must be: --- A member of the Farm Administrators group.--- A service application administrator (Full Control) for the User Profile Service.--- a Microsoft 365 Global Admin, either with or without multi-factor authentication (MFA) enabled for the account.--- Logged into Microsoft 365 and SharePoint Server from a server in your SharePoint Server farm.--- Able to launch the Hybrid Picker as a Farm Admin with elevated permissions.--> [!IMPORTANT] -> The Hybrid Picker wizard must be launched from an on-premises server with SharePoint Server 2013, SharePoint Server 2016, or SharePoint Server 2019 installed. Launch it in the environment you want to use for your SharePoint hybrid. --## SharePoint hybrid features offered in the Hybrid Picker --Use the Hybrid Picker to either configure, or assist with the configuration of, hybrids that connect Microsoft 365 and your on-premises SharePoint environment. --The Hybrid picker helps with or completes the setup of these hybrid features: --- **[Hybrid OneDrive](plan-hybrid-onedrive-for-business.md)** - Choosing this option will redirect on-premises My Sites/OneDrive sites to SharePoint in Microsoft 365 and OneDrive. After the wizard completes, any click of the OneDrive link from on-premises redirects to OneDrive in the cloud. Your redirection is complete and users can begin to migrate any files to their online OneDrive. This option also sets up hybrid user profiles. When users click to view a profile, they will be redirected to the profile in Microsoft 365. --- **[Hybrid Sites Features](sharepoint-hybrid-sites-and-search.md)** - Choosing this option sets up hybrid sites features, a suite of site integration features, as well as OneDrive redirection. Selecting this option configures hybrid OneDrive and hybrid user profiles, hybrid site following, and the hybrid app launcher. --- **[Hybrid App Launcher](the-extensible-hybrid-app-launcher.md)** - This hybrid feature further integrates Microsoft 365 with your on-premises SharePoint Server farm by placing tiles like Office 365 Delve and Video (as well as custom Microsoft 365 tiles you may have) on the on-premises SharePoint Server App Launcher. This option also sets up hybrid OneDrive with user profile redirection, and sites features. --- **[Business-to-business (B2B) extranet sites](../../SharePointOnline/create-b2b-extranet.md)** - Choosing this option will install extra features you can integrate with an extranet site you create in Microsoft 365. With Microsoft 365 extranet, partners can connect directly to a members-only site in Microsoft 365 without access to the corporate on-premises environment or any other Microsoft 365 site. Choosing this option sets up OneDrive and user profile redirection, sites features, and hybrid app launcher. --- **[Hybrid Taxonomy](plan-hybrid-sharepoint-taxonomy-and-hybrid-content-types.md)** - This feature allows a centralized taxonomy that's readable and writable in the Microsoft 365 Cloud, to be used as a read-only copy on-premises. This feature includes Hybrid Content type (June 2017 PU required) which will replicate the published content types in Microsoft 365 to on-premises. Choosing this option sets up OneDrive and user profile redirection, sites features, and hybrid app launcher. --- **[Hybrid self-service site creation](hybrid-self-service-site-creation.md)** - This feature redirects the default self-service site creation page in SharePoint Server 2013, SharePoint Server 2016, or SharePoint Server 2019 (/_layouts/15/scsignup.aspx) to the SharePoint in Microsoft 365 Group Creation page. This setting can be configured independently for each web application in your farm. It helps your users create their sites in SharePoint in Microsoft 365 instead of SharePoint Server. --- **[Cloud hybrid search](./learn-about-cloud-hybrid-search-for-sharepoint.md)** - Choosing this option creates a cloud Search service application in SharePoint Server and connects the cloud Search service application to your Microsoft 365 organization. This is one of the steps needed to set up cloud hybrid search, you must do the rest of the steps yourself (see the [roadmap](configure-cloud-hybrid-searchroadmap.md)). This option doesn't include set-up of other hybrid features.--> [!TIP] -> If the Hybrid Picker is run a second time with an enabled feature unchecked, this will not cause the feature to be uninstalled. Any additional selections will be installed and previously installed features will remain. --For all options, the hybrid picker configures a server-to-server trust between your SharePoint Server farm and Microsoft 365. --Note that the hybrid picker does not uninstall features. If you run the hybrid picker and deselect a feature that you previously installed, it will remain installed. --To get started configuring hybrid features for your environment, choose from the following: --- [Configure hybrid OneDrive - roadmap](configure-hybrid-onedrive-for-businessroadmap.md)--- [Configure hybrid sites features - roadmap](configure-hybrid-sites-featuresroadmap.md)--- [Configure cloud hybrid search - roadmap](configure-cloud-hybrid-searchroadmap.md)--- [Configure hybrid SharePoint taxonomy and hybrid content types](configure-hybrid-sharepoint-taxonomy-and-hybrid-content-types.md)--## Hybrid Picker Prerequisite Checking --While running the Hybrid Picker, the wizard will check basic SharePoint farm settings that would otherwise block setup of essential hybrid building-blocks (such as OAuth/S2S Trust). This is why you should launch the Hybrid Picker from a server that will be part of your SharePoint hybrid. Some of the settings that are detected and checked while the configuration is run, include whether the: --- SharePoint Server farm exists--- Account is a farm administrator--- SharePoint farm is a version that can function in a hybrid configuration--- AppMangementServiceInstance is online--- AppMangementServiceApplication is online--- AppMangementServiceApplicationProxy is online--- UserProfileApplicationProxy is online--- The SPO365LinkSettings cmdlet (used to set the MySiteHostURL) is accessible on the server --The results of this testing can be viewed as a report if any prerequisite isn't met. If all prerequisites are met you will see green check-marks beside all the prerequisites, and will be able to continue your hybrid configuration. --## Authentication realm update --As part of hybrid configuration, the hybrid picker updates the on-premises farm's authentication realm to match the Microsoft 365 organization context ID. After the authentication realm is changed, existing SharePoint in Microsoft 365 add-ins fail to authenticate. The hybrid picker will attempt to fix this issue automatically. If the hybrid picker is not able to fix this issue or if you choose to fix it manually, follow the steps in [Fix the HTTP 401 error with provider-hosted add-ins and issues with workflow and cross farm trust scenarios in SharePoint in Microsoft 365](https://support.microsoft.com/help/4010011). --## See also --#### Other Resources --[You receive the error "Value cannot be null. Parameter name: My site URL or team site URL from Discovery Service is null or empty" when you use the SharePoint Hybrid Picker](https://support.microsoft.com/kb/3204761) |
SharePoint | Hybrid Self Service Site Creation | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/hybrid/hybrid-self-service-site-creation.md | This setting can be configured independently for each web application in your fa Hybrid self-service site creation is available in SharePoint Server 2013 with the March 2017 PU. <br> Hybrid self-service site creation is available in SharePoint 2016 with November 2017 PU. -## Configure hybrid self-service site creation using the Hybrid Picker +## Configure hybrid self-service site creation using the Hybrid Configuration Wizard -Configuring hybrid self-service site creation is done by using the hybrid picker in the SharePoint admin center. +Configuring hybrid self-service site creation is done by using the Hybrid Configuration Wizard in the SharePoint admin center. > [!NOTE]-> If you've previously configured other hybrid features with the hybrid picker, you can go directly to the SharePoint Central Administration website to manage hybrid self-service site creation. In this case, the hybrid connection has been made and there's no need to run the hybrid picker again. +> If you've previously configured other hybrid features with the Hybrid Configuration Wizard, you can go directly to the SharePoint Central Administration website to manage hybrid self-service site creation. In this case, the hybrid connection has been made and there's no need to run the Hybrid Configuration Wizard again. **To configure hybrid self-service site creation** Configuring hybrid self-service site creation is done by using the hybrid picker 7. When prompted, select the web application with which you want to use hybrid self-service site creation. -When the hybrid picker wizard completes, hybrid self-service site creation will be enabled for the web application that you selected. +When the Hybrid Configuration Wizard completes, hybrid self-service site creation will be enabled for the web application that you selected. ## Manage hybrid self-service site creation |
SharePoint | Plan Hybrid Sharepoint Taxonomy And Hybrid Content Types | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/hybrid/plan-hybrid-sharepoint-taxonomy-and-hybrid-content-types.md | -description: "SharePoint hybrid taxonomy enables you to have a single taxonomy that spans SharePoint Server and SharePoint in Microsoft 365. This gives you a single, consistent taxonomy no matter where your sites are located." +description: "SharePoint hybrid taxonomy enables you to have a single taxonomy that spans SharePoint Server and SharePoint in Microsoft 365. This single taxonomy gives you a single, consistent taxonomy no matter where your sites are located." # Plan hybrid SharePoint in Microsoft 365 taxonomy and hybrid content types [!INCLUDE[appliesto-2013-2016-2019-SUB-SPO-md](../includes/appliesto-2013-2016-2019-SUB-SPO-md.md)] -SharePoint hybrid taxonomy enables you to have a single taxonomy that spans SharePoint Server and SharePoint in Microsoft 365. This gives you a single, consistent taxonomy no matter where your sites are located. +SharePoint hybrid taxonomy enables you to have a single taxonomy that spans SharePoint Server and SharePoint in Microsoft 365. This single taxonomy gives you a single, consistent taxonomy no matter where your sites are located. You can choose which term groups are shared between SharePoint Server and SharePoint in Microsoft 365 and which are on-premises only or online only. Hybrid SharePoint taxonomy and hybrid content types are available in SharePoint - Hybrid taxonomy requires the November 2016 public update or later. -- Hybrid content types requires the June 2017 public update or later.+- Hybrid content types require the June 2017 public update or later. -Configuration of both features uses the Hybrid Picker in the <a href="https://go.microsoft.com/fwlink/?linkid=2185219" target="_blank">SharePoint admin center</a>, which also has a number of prerequisites. Be sure to read [Hybrid picker in the SharePoint admin center](hybrid-picker-in-the-sharepoint-online-admin-center.md) as you plan your hybrid SharePoint taxonomy rollout. +Configuration of both features uses the Hybrid Configuration Wizard in the <a href="https://go.microsoft.com/fwlink/?linkid=2185219" target="_blank">SharePoint admin center</a>, which also has many prerequisites. Be sure to read [Hybrid picker in the SharePoint admin center](hybrid-configuration-wizard-in-the-sharepoint-online-admin-center.md#hybrid-configuration-wizard-in-the-sharepoint-admin-center) as you plan your hybrid SharePoint taxonomy rollout. The functionality and configuration procedures are the same for both versions of SharePoint Server. -As with all hybrid scenarios, hybrid SharePoint taxonomy and hybrid content types both rely on your [user accounts being synchronized between SharePoint Server and SharePoint in Microsoft 365](/office365/enterprise/office-365-integration), though users whose accounts are not synchronized can still use the replicated and local term sets on-premises. +As with all hybrid scenarios, hybrid SharePoint taxonomy and hybrid content types both rely on your [user accounts being synchronized between SharePoint Server and SharePoint in Microsoft 365](/office365/enterprise/office-365-integration), though users whose accounts aren't synchronized can still use the replicated and local term sets on-premises. ## How hybrid SharePoint taxonomy works Hybrid SharePoint taxonomy works by replicating changes that you make to your taxonomy in SharePoint in Microsoft 365 to your term store in SharePoint Server. Replication is done at the term group level. Groups that are replicated via hybrid SharePoint taxonomy are set to read-only in SharePoint Server and can only be updated in SharePoint in Microsoft 365. (A term store administrator can still update the SharePoint Server groups, but such updates will be overwritten during the next replication.) -You choose the groups that you want to share across SharePoint Server and SharePoint in Microsoft 365. System and special groups (the System, Search, SearchDirectories, and People groups) cannot be replicated, but any other groups that you create can be. (Be sure you're not reusing terms between groups that you replicate and groups that you don't replicate.) +You choose the groups that you want to share across SharePoint Server and SharePoint in Microsoft 365. System and special groups (the System, Search, SearchDirectories, and People groups) can't be replicated, but any other groups that you create can be. (Be sure you're not reusing terms between groups that you replicate and groups that you don't replicate.) The Taxonomy Groups Replication SharePoint Server timer job polls SharePoint in Microsoft 365 for taxonomy changes on a daily basis and replicates them to the SharePoint Server taxonomy store. This timer job performs a daily update of changes and a weekly full replication. You can reschedule the timer job to meet your needs or run it manually when you want to force an update. **On-premises taxonomy** -If you already have a taxonomy in SharePoint Server, you can copy it to SharePoint in Microsoft 365 by using PowerShell. This allows you to create your master taxonomy from your existing SharePoint Server and SharePoint in Microsoft 365 taxonomies, while maintaining the IDs of the terms, term sets, and term groups in those taxonomies. +If you already have a taxonomy in SharePoint Server, you can copy it to SharePoint in Microsoft 365 by using PowerShell. This taxonomy - once copied into SharePoint in Microsoft 365 - allows you to create your master taxonomy from your existing SharePoint Server and SharePoint in Microsoft 365 taxonomies, while maintaining the IDs of the terms, term sets, and term groups in those taxonomies. -We recommend that you copy your taxonomy to SharePoint in Microsoft 365 before you set up hybrid SharePoint taxonomy. You can do so at a later time, but you'll have to rerun the Hybrid Picker configuration wizard in order to turn on replication for those groups. +We recommend that you copy your taxonomy to SharePoint in Microsoft 365 before you set up hybrid SharePoint taxonomy. You can do so at a later time, but you'll have to rerun the Hybrid Configuration Wizard in order to turn on replication for those groups. **Local term sets** -You can continue to work with local term sets in both locations. They remain local and are not affected by hybrid SharePoint taxonomy. These local site-specific terms cannot be replicated. +You can continue to work with local term sets in both locations. They remain local and aren't affected by hybrid SharePoint taxonomy. These local site-specific terms can't be replicated. ## How hybrid content types work -If you already have content types in SharePoint Server, you can copy them to SharePoint in Microsoft 365 by using PowerShell. This allows you to create your master content types list from your existing SharePoint Server and SharePoint in Microsoft 365 content types. You control which content types are shared across SharePoint in Microsoft 365 and SharePoint Server. +If you already have content types in SharePoint Server, you can copy them to SharePoint in Microsoft 365 by using PowerShell. These content types - once copied into SharePoint in Microsoft 365 - allows you to create your master content types list from your existing SharePoint Server and SharePoint in Microsoft 365 content types. You control which content types are shared across SharePoint in Microsoft 365 and SharePoint Server. We recommend that you copy your content types to SharePoint in Microsoft 365 before you set up hybrid content types. ## Get set up -To get started configuring hybrid SharePoint taxonomy and hybrid content types, be sure you've reviewed the [prerequisites for the Hybrid Picker](hybrid-picker-in-the-sharepoint-online-admin-center.md), and then read [Configure hybrid SharePoint taxonomy and hybrid content types](configure-hybrid-sharepoint-taxonomy-and-hybrid-content-types.md). +To get started configuring hybrid SharePoint taxonomy and hybrid content types, be sure you've reviewed the [prerequisites for the Hybrid Configuration Wizard](hybrid-configuration-wizard-in-the-sharepoint-online-admin-center.md#hybrid-configuration-wizard-in-the-sharepoint-admin-center), and then read [Configure hybrid SharePoint taxonomy and hybrid content types](configure-hybrid-sharepoint-taxonomy-and-hybrid-content-types.md). ## See also |
SharePoint | Removing Sharepoint Hybrid Scenarios | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/hybrid/removing-sharepoint-hybrid-scenarios.md | See [Manage hybrid self-service site creation](./hybrid-self-service-site-creati ## Removing the Azure Access Control Service Application Proxy and SharePoint in Microsoft 365 Application Principal Management Service Application Proxy -The final step to removing hybrid is to delete the **Azure Access Control Service Application Proxy** and **SharePoint Application Principal Management Service Application Proxy** created by the hybrid picker. +The final step to removing hybrid is to delete the **Azure Access Control Service Application Proxy** and **SharePoint Application Principal Management Service Application Proxy** created by the Hybrid Configuration Wizard. 1. In the **Central Administration** website, select **Application Management**. 2. In the **Application Management** page, select **Manage service applications**. |
SharePoint | Run Hybrid Picker | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/hybrid/run-hybrid-picker.md | Title: "Run Hybrid Picker" + Title: "Run Hybrid Configuration Wizard" -description: "Learn to run Hybrid Picker in Microsoft 365 for enterprises." +description: "Learn to run Hybrid Configuration Wizard in Microsoft 365 for enterprises." -# Run Hybrid Picker +# Run Hybrid Configuration Wizard [!INCLUDE[appliesto-2013-2016-2019-SUB-SPO-md](../includes/appliesto-2013-2016-2019-SUB-SPO-md.md)] **This article is part of a roadmap of procedures for configuring SharePoint hybrid solutions. Be sure you're [following a roadmap](configuration-roadmaps.md) when you do the procedure in this article. ** -Hybrid Picker is located in Microsoft 365 for enterprises, and you can use it to help you configure certain hybrid scenarios between Microsoft 365 and SharePoint Server. +Hybrid Configuration Wizard is located in Microsoft 365 for enterprises, and you can use it to help you configure certain hybrid scenarios between Microsoft 365 and SharePoint Server. > [!NOTE]-> If you're using a pop-up blocker with your browser, be sure to turn it off before running the hybrid picker. +> If you're using a pop-up blocker with your browser, be sure to turn it off before running the Hybrid Configuration Wizard. - **To run Hybrid Picker** + **To run Hybrid Configuration Wizard** 1. Log in to the console of a SharePoint Server farm server as a farm admin. Hybrid Picker is located in Microsoft 365 for enterprises, and you can use it to 3. Navigate to [https://go.microsoft.com/fwlink/?linkid=867176](https://go.microsoft.com/fwlink/?linkid=867176). -4. To configure your hybrid features, follow the prompts in Hybrid Picker. - +4. To configure your hybrid features, follow the prompts in Hybrid Configuration Wizard. |
SharePoint | Software Requirements For Sharepoint Servers For Sharepoint Server Subscription Edition | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/install/software-requirements-for-sharepoint-servers-for-sharepoint-server-subscription-edition.md | The SharePoint Server Subscription Edition prerequisite installer (`prerequisite 3. [Visual C++ Redistributable Package for Visual Studio 2015-2019](https://go.microsoft.com/fwlink/?LinkId=2130438) + > [!NOTE] + > SharePoint Server Subscription Edition will require the Visual C++ 2015-2022 Redistributable (x64) as a software prerequisite starting with SharePoint Server Subscription Edition Version 23H1. This new software prerequisite replaces the Visual C++ Redistributable Package for Visual Studio 2015-2019. This new software prerequisite will not be installed by the prerequisiteinstaller.exe tool, but will be installed by the SharePoint Server Subscription Edition Version 23H1 feature update if it isn't already installed. To download and install it separately, see [Visual C++ 2015-2022 Redistributable (x64)](https://go.microsoft.com/fwlink/?LinkId=2224881). + ### Prerequisite installer operation and command-line options You can run `prerequisiteinstaller.exe` with no parameters or at a command prompt with the following optional parameters. When you run `prerequisiteinstaller.exe`, you might be asked to restart the server one or more times during the software installation process. If you're running it at a command prompt, you should continue the prerequisite installation by running `prerequisiteinstaller.exe` with the **/continue** parameter after restarting. |
SharePoint | Configure Amsi Integration | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/security-for-sharepoint-server/configure-amsi-integration.md | description: "Learn to secure environments and respond to associated threats fro # Configure AMSI integration with SharePoint Server ## Introduction Before enabling AMSI integration, check the following prerequisites on each Shar - Windows Server 2016 or higher - SharePoint Server Subscription Edition Version 22H2 or higher+- SharePoint Server 2019 build 16.0.10396.20000 or higher (KB 5002358: March 14, 2023 security update for SharePoint Server 2019) - Microsoft Defender with AV engine version at 1.1.18300.4 or higher (alternatively, a compatible AMSI-capable third-party antivirus/antimalware provider) ## Activate/Deactivate AMSI for SharePoint Server |
SharePoint | Default Timer Jobs In Sharepoint Server 2019 | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/technical-reference/default-timer-jobs-in-sharepoint-server-2019.md | The following table lists the default timer jobs for SharePoint Server 2019. | Health Statistics Updating | | 1 Minute | | High Write Volume Sites Document Changed Anti-virus Processing | | Disabled | | Hold Processing and Reporting | This job generates reports about items on hold and removes items from holds that are pending release. | Daily |-| Hybrid Auditing ODL Error Log Upload Job | Upload event IDs and timestamps from ODL error logs to Microsoft to monitor the health and stability of the SharePoint Hybrid Auditing Feature. This job only uploads data if you have turned on the SharePoint Hybrid Auditing feature in the Hybrid Picker ΓÇô if Hybrid Auditing is not configured this timer job will do nothing. | Disabled | +| Hybrid Auditing ODL Error Log Upload Job | Upload event IDs and timestamps from ODL error logs to Microsoft to monitor the health and stability of the SharePoint Hybrid Auditing Feature. This job only uploads data if you have turned on the SharePoint Hybrid Auditing feature in the Hybrid Configuration Wizard ΓÇô if Hybrid Auditing is not configured this timer job will do nothing. | Disabled | | Identity column maintenance job | Checks and reseeds identity column values. | Weekly | | Immediate Alerts | Sends out immediate and scheduled alerts. | 1 Minute | | Indexing Schedule Manager on \<server\> | | 5 Minutes | |
SharePoint | Deploy Updates For Sharepoint Server 2016 | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/upgrade-and-update/deploy-updates-for-sharepoint-server-2016.md | Title: "Deploy software updates for SharePoint Server 2016 and 2019" + Title: "Deploy software updates for SharePoint Server 2016, 2019, and Subscription Edition" ms.assetid: f484f5f2-35bb-4d70-bf56-dd1c4c287c72 description: "Learn how to prepare for, download, install, and configure software updates and patches for SharePoint Server 2016." -# Deploy software updates for SharePoint Server 2016 and 2019 +# Deploy software updates for SharePoint Server 2016, 2019, and Subscription Edition -Microsoft periodically releases software updates for SharePoint Server 2016 and 2019. The following articles provide information about the software update process for SharePoint Server 2016 and 2019. +Microsoft periodically releases software updates for SharePoint Server 2016, 2019 and Subscription Edition. The following articles provide information about the software update process for SharePoint Server 2016, 2019 and Subscription Edition. ++> [!IMPORTANT] +> Microsoft is changing how software updates for SharePoint Server Subscription Edition are packaged beginning with the March 2023 public update, which introduces SharePoint Server Subscription Edition Version 23H1. In this software update, Microsoft will no longer release separate core and language pack software updates each month. Instead, Microsoft will release a single software update each month that will contain all of the changes that previously would have been included in those two separate updates. Going forward, customers will only need to install this single software update each month to be fully up to date with the latest security fixes, bug fixes, and new feature experiences. ++> [!NOTE] +> Microsoft will continue to release separate core and language pack software updates for SharePoint Server 2016 and SharePoint Server 2019. Customers will need to continue installing the latest version of the core and language pack software updates each month to ensure theyΓÇÖre fully up to date with the latest security fixes, bug fixes, and new feature experiences. -## Articles about software updates for SharePoint Server 2016 and 2019 +## Articles about software updates for SharePoint Server 2016, 2019, and Subscription Edition |**Content**|**Description**| |:--|:--|-|[Software updates overview for SharePoint Server 2016](software-updates-overview.md) <br/> |Provides an overview of the software update process for SharePoint Server 2016. <br/> | -|[Install a software update for SharePoint Server 2016](install-a-software-update.md) <br/> |Learn how to install a software update on servers in a SharePoint farm. <br/> | +|[Software updates overview for SharePoint Server 2016, 2019 and Subscription Edition](software-updates-overview.md) <br/> |Provides an overview of the software update process for SharePoint Server 2016, 2019, and Subscription Edition. <br/> | +|[Install a software update for SharePoint Server 2016, 2019 and Subscription Edition](install-a-software-update.md) <br/> |Learn how to install a software update on servers in a SharePoint farm. <br/> | |[Video demo of Zero Downtime Patching in SharePoint Server 2016](video-demo-of-zero-downtime-patching-in-sharepoint-server-2016.md) <br/> |Learn how to patch a software update on servers in a SharePoint farm. <br/> | -|[SharePoint Server 2016 zero downtime patching steps](sharepoint-server-2016-zero-downtime-patching-steps.md) <br/> |Learn the steps to patch a software update on servers in a SharePoint farm. <br/> | -|[Video: How to enable Remote Windows PowerShell to use with SharePoint Server](video-how-to-enable-remote-windows-powershell-to-use-with-sharepoint-server.md) <br/> |Learn how to enable remote Powershell to use with servers in a SharePoint farm. <br/> | +|[SharePoint Server zero downtime patching steps](sharepoint-server-2016-zero-downtime-patching-steps.md) <br/> |Learn the steps to patch a software update on servers in a SharePoint farm. <br/> | +|[Video: How to enable Remote Windows PowerShell to use with SharePoint Server](video-how-to-enable-remote-windows-powershell-to-use-with-sharepoint-server.md) <br/> |Learn how to enable remote PowerShell to use with servers in a SharePoint farm. <br/> | +++ ->[!NOTE] -> The articles above reference SharePoint Server 2016 but the same process is applicable to SharePoint Server 2019. |
SharePoint | Install A Software Update | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/upgrade-and-update/install-a-software-update.md | description: "Install a software update to perform a build-to-build upgrade on s Before you begin the software update process, review the following information about permissions, hardware requirements, software requirements, and update processes. -- [Account permissions and security settings in SharePoint 2016](../install/account-permissions-and-security-settings-in-sharepoint-server-2016.md)+- [Account permissions and security settings in SharePoint Servers](../install/account-permissions-and-security-settings-in-sharepoint-server-2016.md) - [Hardware and software requirements for SharePoint 2016](../install/hardware-and-software-requirements.md) -- [Software updates overview for SharePoint 2016](./software-updates-overview.md)+- [Software updates overview for SharePoint Server 2016, 2019, and Subscription Edition](./software-updates-overview.md) -- [Prepare to deploy software updates for SharePoint 2016](./deploy-updates-for-sharepoint-server-2016.md)+- [Prepare to deploy software updates for SharePoint Server 2016, 2019, and Subscription Edition](./deploy-updates-for-sharepoint-server-2016.md) >[!NOTE]->While the steps in this article refer to SharePoint Server 2016, they are applicable to SharePoint Foundation 2013, SharePoint Server 2013, and SharePoint Server 2019 unless otherwise noted. +>While the steps in this article refer to SharePoint Server 2016, they are applicable to SharePoint Foundation 2013, SharePoint Server 2013, SharePoint Server 2019, and SharePoint Server Subscription Edition unless otherwise noted. To perform the procedures in this article, you must have the following memberships and roles: Before you install an update, verify that the following conditions are satisfied - All databases are active and operating properly. -Do not start the update if any of the preceding conditions are not satisfied. Resolve all issues before you continue. +Don't start the update if any of the preceding conditions aren't satisfied. Resolve all issues before you continue. -SharePoint Server 2016 can handle certain upgrade failures after the patching phase finishes. However, if the build-to-build upgrade fails, you might have to restore from a backup. Therefore, make sure that you perform a full backup before you start the update process. After the restore is complete, you can resume the update. Completed tasks do not run again. For more information, see the following resources: +SharePoint Server 2016, 2019, and Subscription Edition can handle certain upgrade failures after the patching phase finishes. However, if the build-to-build upgrade fails, you might have to restore from a backup. Therefore, make sure that you perform a full backup before you start the update process. After the restore is complete, you can resume the update. Completed tasks don't run again. For more information, see the following resources: - [Test and troubleshoot an upgrade to SharePoint 2016](./test-and-troubleshoot-an-upgrade.md) ## Determine the update strategy <a name="verifystrategy"> </a> -Before you start to deploy a software update, verify that the update strategy that you plan to use is optimal for your SharePoint Server 2016 environment. There are several factors, such as downtime reduction, cost, and complexity that determine the strategy to use to deploy a software update. For more information about how the database-attach process works, see the diagrams in [Overview of the upgrade process from SharePoint 2013 to SharePoint Server 2016](./overview-of-the-upgrade-process.md). +Before you start to deploy a software update, verify that the update strategy that you plan to use is optimal for your SharePoint Server 2016, 2019, or Subscription Edition environment. There are several factors, such as downtime reduction, cost, and complexity that determine the strategy to use to deploy a software update. ++For more information about how the database-attach process works, see the diagrams in [Overview of the upgrade process from SharePoint 2013 to SharePoint Server 2016](./overview-of-the-upgrade-process.md), [Overview of the upgrade process to SharePoint Server 2019](overview-of-the-upgrade-process-2019.md), and [Overview of the upgrade process to SharePoint Server Subscription Edition](overview-of-the-upgrade-process-subscription-edition.md). > [!NOTE] > Certain links in this article go to content that is about version-to-version upgrade rather than build-to-build upgrade. However, the general process is similar for the two types of upgrade. For example, the database upgrade phase is essentially the same for build-to-build upgrade and version-to-version upgrade. Before you start to deploy a software update, verify that the update strategy th ## Monitor installation progress <a name="monitorprogress"> </a> -Monitor the process that deploys updates to verify that the update is proceeding as planned. There might be issues that block the update or that result in an updated farm that has elements that do not work as expected. Pay extra attention to database synchronization and customizations. +Monitor the process that deploys updates to verify that the update is proceeding as planned. There might be issues that block the update or that result in an updated farm that has elements that don't work as expected. Pay extra attention to database synchronization and customizations. We recommend that you use the **Upgrade and Migration** page in Central Administration as the primary tool to view product and patch installation status, data status, and update status in real time. The following illustration shows the farm topology that is used as an example fo  -When you are ready to continue, perform only one of the following procedures in this article to install the update: +When you're ready to continue, perform only one of the following procedures in this article to install the update: - Use the in-place method without backward compatibility When you are ready to continue, perform only one of the following procedures in ## Use the in-place method without backward compatibility <a name="usinginplace"> </a> -In this scenario you disable incoming requests to the front-end web servers, thus effectively shutting down the entire farm. Then you install the update on all the farm servers. This strategy combines the update and the build-to-build upgrade phase that is described in the [Software updates overview for SharePoint Server 2016](./software-updates-overview-for-sharepoint-server-2013.md#updateprocess) section of [Overview of the upgrade process from SharePoint 2013 to SharePoint Server 2016](./overview-of-the-upgrade-process.md). +In this scenario you disable incoming requests to the front-end web servers, thus effectively shutting down the entire farm. Then you install the update on all the farm servers. This strategy combines the update and the build-to-build upgrade phase that is described in the [Software updates overview for SharePoint Server 2016](/sharepoint/upgrade-and-update/software-updates-overview#software-update-process) section of [Overview of the upgrade process from SharePoint 2013 to SharePoint Server 2016](./overview-of-the-upgrade-process.md). The following illustration shows the steps that are required to install the update on the farm. You can use the illustration as a guide as you go through the steps in the procedure that follows ("To install an update without backward compatibility"). The following illustration shows the steps that are required to install the upda ### To install an update without backward compatibility -1. Notify users that the farm will not be available while you are installing the update. +1. Notify users that the farm won't be available while you're installing the update. 2. Remove all web servers (WEB-1 to WEB-4) from rotation in the load balancer, or pause the load balancer to stop incoming requests to the servers. 3. Run the update executable file to install the update on the application server that hosts Central Administration (APP-1). -4. Run the update executable file to install the update on all other application servers that host Search components (APP-2). To do this, perform the procedure [Host Search components](#HostSearch) which appears later in this article, and then return to the next step in this procedure. Do not run the SharePoint Products Configuration Wizard on these servers at this time. +4. Run the update executable file to install the update on all other application servers that host Search components (APP-2). To do this, perform the procedure [Host Search components](#HostSearch) which appears later in this article, and then return to the next step in this procedure. Don't run the SharePoint Products Configuration Wizard on these servers at this time. 5. Review the upgrade log files to verify that all the application servers were updated successfully. The following illustration shows the steps that are required to install the upda 9. Review the upgrade log files to verify that all the web servers were updated successfully. -10. Run the SharePoint Products Configuration Wizard on the Central Administration server (APP-1). This will upgrade the configuration database and upgrade each content database. For information about how to run the wizard, see [Install SharePoint Server 2016 across multiple servers](../install/multiple-servers-for-a-three-tier-farm.md#CreateConfigure) in the article [Install SharePoint 2013 across multiple servers for a three-tier farm](../install/multiple-servers-for-a-three-tier-farm.md). +10. Run the SharePoint Products Configuration Wizard on the Central Administration server (APP-1). This upgrades the configuration database and upgrade each content database. ++ For information about how to run the wizard, see [Install SharePoint Server across multiple servers](/SharePoint/install/install-sharepoint-server-2016-across-multiple-servers) for SharePoint Server 2016, 2019, or Subscription Edition. See [Install SharePoint 2013 across multiple servers for a three-tier farm](../install/multiple-servers-for-a-three-tier-farm.md) for SharePoint 2013. 11. Run the SharePoint Products Configuration Wizard on the other application servers. 12. Run the SharePoint Products Configuration Wizard on the first web server (WEB-1). - >[!NOTE] - >Run the configuration wizard to ensure that if an update fails for a specific server, the error is not propagated to the other web servers. For example, a failed update for one server could make the update fail for one or more site collections. + > [!NOTE] + > Run the configuration wizard to ensure that if an update fails for a specific server, the error is not propagated to the other web servers. For example, a failed update for one server could make the update fail for one or more site collections. 13. Repeat the preceding step for each remaining web server. The following illustration shows the steps that are required to install the upda 15. Add the web servers (WEB-1 to WEB-4) to the rotation in the load balancer, or start the load balancer to enable incoming requests to the servers. -16. Notify users that the farm is available. You are finished installing the update and using this article. +16. Notify users that the farm is available. You're finished installing the update and using this article. ## Use the in-place method with backward compatibility <a name="inplacewithbackcompatibility"> </a> -This scenario takes advantage of the backward compatibility of SharePoint and the deferred upgrade feature to reduce the farm downtime that is required to deploy a software update. However, downtime is not completely eliminated. The sites and services will not be available while the database content is being upgraded. +This scenario takes advantage of the backward compatibility of SharePoint and the deferred upgrade feature to reduce the farm downtime that is required to deploy a software update. However, downtime isn't eliminated. The sites and services won't be available while the database content is being upgraded. This update scenario uses two phases to install the update on farm servers. These phases are as follows: This update scenario uses two phases to install the update on farm servers. Thes >[!IMPORTANT] >During the update phase, the farm can continue to be in production with minimal downtime. However, during the build-to-build upgrade phase, the farm will be unavailable. If users attempt to access content while the farm is upgrading, the result could be failed upgrades or excessive slowdowns in the upgrade process because of resource contention and locking. Such an attempt is unsupported and untested. -For more information, see the [Software updates overview for SharePoint Server 2016](./software-updates-overview.md) section in [Overview of the upgrade process from SharePoint 2013 to SharePoint Server 2016](./verify-upgrade-for-databases.md). +For more information, see the following: +- [Software updates overview for SharePoint Server 2016, 2019, and Subscription Edition](./software-updates-overview.md) +- [Overview of the upgrade process from SharePoint 2013 to SharePoint Server 2016](./verify-upgrade-for-databases.md) +- [Verify database upgrades in SharePoint Server 2019](./verify-upgrade-for-databases-2019.md) +- [Verify database upgrades in SharePoint Server Subscription Edition](./verify-upgrade-for-databases-subscription-edition.md) ### Update phase The following illustration shows the steps that are required to install the upda 1. Remove half of the web servers (WEB-1 and WEB-2) from rotation in the load balancer, or pause the load balancer to stop incoming requests to the servers. -2. On each web server that is out of the load-balancing rotation (WEB-1 and WEB-2), run the executable file to install the update. Do not run the SharePoint Products Configuration Wizard on these servers. Verify that these web servers were updated successfully by reviewing the upgrade log files. +2. On each web server that is out of the load-balancing rotation (WEB-1 and WEB-2), run the executable file to install the update. Don't run the SharePoint Products Configuration Wizard on these servers. Verify that these web servers were updated successfully by reviewing the upgrade log files. The upgrade log file and the upgrade error log file are located at %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\16\LOGS. Upgrade log file names are in the following format: Upgrade-_YYYYMMDD-HHMMSS-SSS_.log, where _YYYYMMDD_ is the date and _HHMMSS-SSS_ is the time (hours in 24-hour clock format, minutes, seconds, and milliseconds). The upgrade error log file combines all errors and warnings in a shorter file that is named Upgrade- _YYYYMMDD-HHMMSS-SSS_-error.log. The following illustration shows the steps that are required to install the upda 4. Add the updated web servers (WEB-1 and WEB-2) back into the load-balancing rotation. -5. On each web server that is out of the load-balancing rotation, run the executable file to install the update. Do not run the SharePoint Products Configuration Wizard on these servers at this time. Verify that both of the web servers were updated successfully by reviewing the upgrade log files. +5. On each web server that is out of the load-balancing rotation, run the executable file to install the update. Don't run the SharePoint Products Configuration Wizard on these servers at this time. Verify that both of the web servers were updated successfully by reviewing the upgrade log files. 6. Add the updated web servers (WEB-3 and WEB-4) back to the load-balancing rotation. -7. Install the update on all application servers that host Search components (APP-1 and APP-2). To do this, perform the procedure [Install a software update for SharePoint Server 2016](#install-a-software-update-on-servers-that-host-search-components) which appears later in this article, and then return to the next step in this procedure. Do not run the SharePoint Products Configuration Wizard at this time. +7. Install the update on all application servers that host Search components (APP-1 and APP-2). To do this, perform the procedure [Install a software update for SharePoint Server 2016](#install-a-software-update-on-servers-that-host-search-components) which appears later in this article, and then return to the next step in this procedure. Don't run the SharePoint Products Configuration Wizard at this time. -8. If your farm has additional application servers that do not host Search components, run the update executable file to install the update on these servers. Do not run the SharePoint Products Configuration Wizard on these servers at this time. +8. If your farm has additional application servers that don't host Search components, run the update executable file to install the update on these servers. Don't run the SharePoint Products Configuration Wizard on these servers at this time. 9. Review the upgrade log files to verify that these application servers were updated successfully. -At this point in the process, the databases and other components such as settings, features, and site-level data must still be upgraded because the SharePoint Products Configuration Wizard was not run on any of the farm servers. However, the farm should be capable of running in backward compatibility mode. +At this point in the process, the databases and other components such as settings, features, and site-level data must still be upgraded because the SharePoint Products Configuration Wizard wasn't run on any of the farm servers. However, the farm should be capable of running in backward compatibility mode. ### Upgrade phase -The following illustration shows the steps that upgrade the farm servers to finish the patching process. During this process, the sites that are being upgraded will not be available to users. +The following illustration shows the steps that upgrade the farm servers to finish the patching process. During this process, the sites that are being upgraded won't be available to users.  The following procedure shows all the steps to upgrade the farm. You can upgrade - Services - If the software update contains updates to services that must be applied, you can upgrade the service, and then resume operating the farm (step 8 in the following procedure) until it is possible to take a longer farm outage to complete the content and farm upgrade. + If the software update contains updates to services that must be applied, you can upgrade the service, and then resume operating the farm (step 8 in the following procedure) until it's possible to take a longer farm outage to complete the content and farm upgrade. - Content databases You can take a short farm outage to upgrade only a few content databases (steps 3 and 4 in the following procedure) each time and then resume farm operation (step 8 in the following procedure). You can repeat the process over successive outage windows until you upgrade all content and the farm servers are ready to be upgraded. - You can also upgrade individual content databases in parallel for a very small number of content databases at the same time. However, do not attempt to upgrade too many content databases in parallel because it will slow down the overall upgrade process and extend the outage time. We recommend that you do not upgrade more than two content databases on the same SQL Server volume at a time. Start the upgrade for each content database that will occur in parallel several minutes apart to prevent lock contention as the upgrade process starts. In addition, limit the number of content databases that you upgrade on a single web server or application server. Each additional upgrade process will consume a relatively large amount of resources. The typical number of content databases that you can upgrade per web server or application server is four databases. However, be sure not to exceed the number of databases that are being upgraded per SQL Server volume, no matter which web server or application server originates the upgrade. + You can also upgrade individual content databases in parallel for a very small number of content databases at the same time. However, don't attempt to upgrade too many content databases in parallel because it slows down the overall upgrade process and extends the outage time. We recommend that you don't upgrade more than two content databases on the same SQL Server volume at a time. Start the upgrade for each content database that will occur in parallel several minutes apart to prevent lock contention as the upgrade process starts. In addition, limit the number of content databases that you upgrade on a single web server or application server. Each additional upgrade process consumes a relatively large number of resources. The typical number of content databases that you can upgrade per web server or application server is four databases. However, be sure not to exceed the number of databases that are being upgraded per SQL Server volume, no matter which web server or application server originates the upgrade. #### To upgrade the farm The following procedure shows all the steps to upgrade the farm. You can upgrade 2. Upgrade specific services, as needed. - Some updates might also require you to run additional PowerShell cmdlets to upgrade specific service applications. Notes for a software update might indicate that you have to upgrade a specific service so that it will continue to operate after patching. This applies to a service that cannot operate in backward compatibility mode, for example. + Some updates might also require you to run additional PowerShell cmdlets to upgrade specific service applications. Notes for a software update might indicate that you have to upgrade a specific service so that it will continue to operate after patching. This applies to a service that can't operate in backward compatibility mode, for example. You can create a short offline period to upgrade the service without having to upgrade the complete farm. The additional PowerShell cmdlets to upgrade specific service applications should be in the notes if this is required. 3. (Optional) Use the PowerShell **Upgrade-SPContentDatabase** cmdlet to upgrade each content database. For more information, see [Upgrade-SPContentDatabase](/powershell/module/sharepoint-server/Upgrade-SPContentDatabase?view=sharepoint-ps&preserve-view=true). - This is an optional step, but it will help ensure that all content databases are upgraded first. It has the advantage of enabling some parallelism to reduce the outage time. If it is not performed, all remaining non-upgraded content databases will be upgraded serially when you run the SharePoint Products Configuration Wizard to upgrade the farm servers. + This is an optional step, but it helps ensure that all content databases are upgraded first. It has the advantage of enabling some parallelism to reduce the outage time. If it isn't performed, all remaining non-upgraded content databases will be upgraded serially when you run the SharePoint Products Configuration Wizard to upgrade the farm servers. >[!IMPORTANT] >Run the **Upgrade-SPContentDatabase** cmdlet for each database. You can run this cmdlet from any of the upgraded web servers or application servers. Note that the content for each database will be unavailable while this process is running on that database. The following procedure shows all the steps to upgrade the farm. You can upgrade 6. Run the SharePoint Products Configuration Wizard or PSConfig (as in step 4 of this procedure) on the web servers (WEB-1 to WEB-4). -7. Verify update completion and success. For more information, see [Verify database upgrades in SharePoint 2013](./verify-upgrade.md). +7. Verify update completion and success. + + For more information, see [Verify database upgrades in SharePoint 2013](./verify-upgrade.md), [Verify database upgrades in SharePoint Server 2016](/sharepoint/upgrade-and-update/verify-upgrade-for-databases), [Verify database upgrades in SharePoint Server 2019](/sharepoint/upgrade-and-update/verify-upgrade-for-databases-2019), and [Verify database upgrades in SharePoint Server Subscription Edition](/sharepoint/upgrade-and-update/verify-upgrade-for-databases-subscription-edition) . 8. Add the upgraded web servers (WEB-1 to WEB-4) back into rotation in the load balancer. - You are finished installing the update and using this article. + You're finished installing the update and using this article. ## Use the database-attach method for high availability of existing content <a name="databaseattach"> </a> To ensure high availability for existing content, this scenario uses read-only databases on the existing farm. You install the update on a new farm and route user traffic to the new farm after updates are complete. -The following illustration shows the sequence of steps to follow to install the update on a new farm by using the database attach method. For more information, see [Upgrade content databases from SharePoint 2013 to SharePoint Server 2016](./upgrade-content-databases.md). +The following illustration shows the sequence of steps to follow to install the update on a new farm by using the database attach method. ++For more information, see [Upgrade content databases from SharePoint 2013 to SharePoint Server 2016](./upgrade-content-databases.md), [Upgrade databases from SharePoint 2016 to SharePoint Server 2019](/sharepoint/upgrade-and-update/upgrade-databases-2019), and [Upgrade databases from SharePoint Server 2019 and SharePoint Server 2016 to SharePoint Server Subscription Edition](/sharepoint/upgrade-and-update/upgrade-databases-subscription-edition).  Use the preceding illustration as a guide to follow the recommended steps in the ### To install the update by using the database-attach method -1. Create a new farm where you will install the software update. This farm does not require front-end web servers. For more info, see [Create the SharePoint 2016 farm for a database attach upgrade](./create-the-sharepoint-server-2016-farm-for-a-database-attach-upgrade.md). +1. Create a new farm where you'll install the software update. This farm doesn't require front-end web servers. + + For more info, see [Create the SharePoint 2016 farm for a database attach upgrade](./create-the-sharepoint-server-2016-farm-for-a-database-attach-upgrade.md), [Create the SharePoint Server 2019 farm for a database attach upgrade](/sharepoint/upgrade-and-update/create-the-sharepoint-server-2019-farm-for-a-database-attach-upgrade), and [Create the SharePoint Server Subscription Edition farm for a database attach upgrade](/sharepoint/upgrade-and-update/create-the-sharepoint-server-subscription-edition-farm-for-a-database-attach-upgrade). > [!NOTE] > If the original farm uses a database mirror, configure mirroring after you deploy the software update on the new farm. Use the preceding illustration as a guide to follow the recommended steps in the 3. Configure the service application databases on the existing farm so that they are in a read-only state. This prevents unexpected changes to service applications. - >[!NOTE] - >Steps 4 through 14 do not apply to SharePoint Foundation 2013, SharePoint Server 2016, and SharePoint Server 2019. + > [!NOTE] + > Steps 4 through 13 do not apply to SharePoint Foundation 2013, SharePoint Server 2016, SharePoint Server 2019, and SharePoint Server Subscription Edition. -4. If you are patching the User Profile Service service application database, you must export the User Profile Synchronization Service encryption key from the old database and then import the key to the new database. This key is also known as the Microsoft Identity Integration Server (MIIS) key, the Synchronization Service encryption key, and the Forefront Identity Manager 2010 (FIM 2010) key. If you do not export and then import the key correctly, the Synchronization Service will not start. To export the encryption key, complete these steps: +4. If you're patching the User Profile Service service application database, you must export the User Profile Synchronization Service encryption key from the old database, and then import the key to the new database. This key is also known as the Microsoft Identity Integration Server (MIIS) key, the Synchronization Service encryption key, and the Forefront Identity Manager 2010 (FIM 2010) key. If you don't export and then import the key correctly, the Synchronization Service won't start. To export the encryption key, complete these steps: - 1. Use farm administrator credentials to log on to the computer that contains the old User Profile Service service application database. + 1. Use farm administrator credentials to sign in to the computer that contains the old User Profile Service service application database. 2. Open the Command Prompt window, and then change to the following folder: Use the preceding illustration as a guide to follow the recommended steps in the 6. To import the encryption key, perform these steps: - 1. Use farm administrator credentials to log on to the computer that contains the new User Profile Service service application database. + 1. Use farm administrator credentials to sign in to the computer that contains the new User Profile Service service application database. - 2. Attempt to start the User Profile Synchronization service. Because you have not yet imported the encryption key, the service will not start. Confirm that the service did not start by using the ULS log or by making sure that the status of the service is **Stopped**. + 2. Attempt to start the User Profile Synchronization service. Because you haven't yet imported the encryption key, the service won't start. Confirm that the service didn't start by using the ULS log or by making sure that the status of the service is **Stopped**. 3. Open the Command Prompt window, and then change to the following folder: Use the preceding illustration as a guide to follow the recommended steps in the 13. Verify update completion and success. For more information, see [Verify database upgrades in SharePoint 2016](./verify-upgrade-for-databases.md). - You are finished installing the update and using this article. + You're finished installing the update and using this article. ## Install a software update on servers that host Search components <a name="HostSearch"> </a> -Perform the procedures in this section only when they are pointed to from other procedures in this article. This includes the following procedures which are in this section: +Perform the procedures in this section only when they're pointed to from other procedures in this article. This includes the following procedures that are in this section: - Update servers that host Search components during farm downtime Perform the procedures in this section only when they are pointed to from other 4. On each server in availability group 1, run the update executable file to install the update. -5. On each server in availability group 2, stop the Search-related Windows services in the same order that was prescribed for stopping them for availability group 1. Again, it is important to verify that each service is stopped before you stop the next service. +5. On each server in availability group 2, stop the Search-related Windows services in the same order that was prescribed for stopping them for availability group 1. Again, it's important to verify that each service is stopped before you stop the next service. 6. On each server in availability group 1, start the Search-related Windows services in the following order: Perform the procedures in this section only when they are pointed to from other ### Determine server availability groups for update with minimal downtime -1. Start a SharePoint 2016 Management Shell on any server in the farm. +1. Start a SharePoint Management Shell on any server in the farm. 2. Determine the primary Search administration component and the server that hosts the component by typing the following commands at the PowerShell command prompt: Perform the procedures in this section only when they are pointed to from other - The set must contain one or more, but not all, of the index components for each index partition. - - The set must contain a Search administration component that is not the primary component that was identified in step 2 in this procedure. + - The set must contain a Search administration component that isn't the primary component that was identified in step 2 in this procedure. 4. Determine the set of servers in availability group 2. This set must contain all remaining servers that host Search components, including the server that hosts the primary Search administration component that was identified in step 2 of this procedure. Perform the procedures in this section only when they are pointed to from other Prior to restarting a server from running a software update or Configuration Wizard, you must stop Distributed Cache to prevent unallocated cache fractions. Follow the process outlined [here](../administration/manage-the-distributed-cache-service.md#perform-a-graceful-shutdown-of-the-distributed-cache-service-by-using-a-powershell-script) to gracefully shut down Distributed Cache. >[!IMPORTANT]-> Do not use `Stop-SPDistributedCacheServiceInstance -Graceful` as this will terminate Distributed Cache prior to the cache being transferred to another server in the farm. +> Do not use `Stop-SPDistributedCacheServiceInstance -Graceful` for SharePoint Server 2013, SharePoint Server 2016, and SharePoint Server 2019 as this will terminate Distributed Cache prior to the cache being transferred to another server in the farm. But `Stop-SPDistributedCacheServiceInstance -Graceful` can be used for SharePoint Server Subscription Edition. -### Troubleshoot software updates on servers that host Search componenets +### Troubleshoot software updates on servers that host Search components -- **Issue:** After an update you may no longer have proper registry key or file system permissions.+- **Issue:** After an update, you may no longer have proper registry key or file system permissions. - **Resolution:** Run the following command: |
SharePoint | Software Updates Overview | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/upgrade-and-update/software-updates-overview.md | Title: "Software updates overview for SharePoint Server 2016 and 2019" + Title: "Software updates overview for SharePoint Server 2016, 2019, and Subscription Edition" ms.assetid: 4cbe141a-095f-4c09-82f4-dec8af16c590 description: "Learn how to deploy a software update to a SharePoint Server 2016 or 2019 farm." -# Software updates overview for SharePoint Server 2016 and 2019 +# Software updates overview for SharePoint Server 2016, 2019, and Subscription Edition -Administrators update SharePoint Server 2016 or SharePoint Server 2019 to deploy or update assemblies that provide functionality and to upgrade databases. A successful update follows a methodical approach that minimizes interruptions in service. Review information in this article to learn about the process before you begin the update process. +Administrators update SharePoint Server 2016, 2019, or Subscription Edition to deploy or update assemblies that provide functionality and to upgrade databases. A successful update follows a methodical approach that minimizes interruptions in service. Review information in this article to learn about the process before you begin the update process. > [!NOTE]-> This article applies to both SharePoint Server 2016 and SharePoint Server 2019. +> This article applies to SharePoint Server 2016, 2019, and Subscription Edition. ## Before you begin software updates <a name="begin"> </a> Before you begin the software update process, review the following information about permissions, hardware requirements, and software requirements. -- [Account permissions and security settings in SharePoint Server 2016](../install/account-permissions-and-security-settings-in-sharepoint-server-2016.md)+- [Account permissions and security settings in SharePoint Server 2016, 2019, and Subscription Edition](../install/account-permissions-and-security-settings-in-sharepoint-server-2016.md) - [Hardware and software requirements for SharePoint Server 2016](../install/hardware-and-software-requirements.md) -Information in this article is for all IT professionals who maintain SharePoint Server 2016. However, specific instructions to install a software update are intended for IT professionals who have to deploy software updates on a farm of servers that host SharePoint Server 2016. +Information in this article is for all IT professionals who maintain SharePoint Server 2016, 2019, or Subscription Edition. However, specific instructions to install a software update are intended for IT professionals who have to deploy software updates on a farm of servers that host SharePoint Server 2016, 2019, or Subscription Edition. Information in this article applies to the following products: Information in this article applies to the following products: - SharePoint Server 2019 - SharePoint Server 2019 Language Packs++- SharePoint Server Subscription Edition ++- SharePoint Server Subscription Edition Language Packs > [!NOTE]-> The process that installs software updates in stand-alone environments of SharePoint Server 2016 or 2019 is a simpler process than the process that installs software updates in a server farm and does not require all the steps that are required for a server farm. +> The process that installs software updates in stand-alone environments of SharePoint Server 2016, 2019, or Subscription Edition is a simpler process than the process that installs software updates in a server farm and does not require all the steps that are required for a server farm. Microsoft releases Public Updates each month. The first update is known as the language independent update. This update will often include both feature and security fixes. It is also known as the 'sts-x-none' patch. The second type of patch is the language dependent patch. This patch covers all language packs, including English installations. This patch is required to fully update the farm, although may not be released every month. This patch is also known as the 'wssloc' patch. +> [!NOTE] +> From March 2023 PU, Microsoft will release a single ΓÇ£uberΓÇ¥ patch for SharePoint Server Subscription Edition that contains all of the fixes that previously would have been released in those separate 'sts-x-none' and 'wssloc' patches. + > [!IMPORTANT] > If a language dependent patch isn't available for a given month, update to the latest previously available language dependent patch. For example, if applying the July 2019 Public Update for SharePoint Server 2016, install the language independent update for July 2019 and the language dependent patch from April 2019. If you do not install the language dependent patch, you may encounter missing or incorrect functionality. ## Software update terminology <a name="terms"> </a> -To understand how to implement software updates in SharePoint Server 2016, it is important to understand the terminology for the core components. +To understand how to implement software updates in SharePoint Server 2016, 2019, and Subscription Edition, it is important to understand the terminology for the core components. |**Term** <br/> |**Definition** <br/> |**Comment** <br/> | |:--|:--|:--| |**Public Update (PU)** <br/> |A PU is a rollup update that contains all previous critical on-demand hotfixes to date. Additionally, a PU contains fixes for issues that meet the hotfix acceptance criteria. These criteria may include the availability of a workaround, the effect on the customer, the reproducibility of the problem, the complexity of the code that must be changed, or other reasons. <br/> || |**patch** <br/> |A compiled, executable installer file that contains updates to one or more products. Examples of packages are the executable (.exe) files that you download to install a service pack, public update (PU), or hotfix. Packages are also known as MSI files. <br/> || |**software update** <br/> |A software update is any update, update rollup, service pack, feature pack, critical update, security update, or hotfix that is used to improve or to fix a software product that is released by Microsoft Corporation. <br/> ||-|**upgrade** <br/> |Process by which you change an environment to use a newer version of software. You can upgrade to a minor release, such as an update or patch, or to a major release. An upgrade to a minor release is called a build-to-build upgrade. An upgrade to a major release is called a version-to-version upgrade. <br/> |In SharePoint Server 2016, for build-to-build upgrades, you can use either in-place or database-attach methods. For version-to-version upgrade, only database-attach is supported. For more information about version-to-version upgrade, see [Overview of the upgrade process to SharePoint Server 2016](overview-of-the-upgrade-process.md). For an overview of the steps for in-place and database-attach upgrade for build-to-build upgrades, see [Install a software update for SharePoint Server 2016](install-a-software-update.md) <br/> | +|**upgrade** <br/> |Process by which you change an environment to use a newer version of software. You can upgrade to a minor release, such as an update or patch, or to a major release. An upgrade to a minor release is called a build-to-build upgrade. An upgrade to a major release is called a version-to-version upgrade. <br/> |In SharePoint Server 2016, for build-to-build upgrades, you can use either in-place or database-attach methods. For version-to-version upgrade, only database-attach is supported. For more information about version-to-version upgrade, see [Overview of the upgrade process to SharePoint Server 2016](overview-of-the-upgrade-process.md), [Overview of the upgrade process to SharePoint Server 2019](overview-of-the-upgrade-process-2019.md) and [Overview of the upgrade process to SharePoint Server Subscription Edition](overview-of-the-upgrade-process-subscription-edition.md). For an overview of the steps for in-place and database-attach upgrade for build-to-build upgrades, see [Install a software update for SharePoint Server 2016, 2019, and Subscription Edition](install-a-software-update.md) <br/> | For a complete list of terminology about software updates, see [Description of the standard terminology that is used to describe Microsoft software updates](/troubleshoot/windows-client/deployment/standard-terminology-software-updates). ## Software update features <a name="Improvements"> </a> -SharePoint Server 2016 has features that facilitate the end-to-end software update experience. Some of these features are as follows: +SharePoint Server 2016, 2019, and Subscription Edition has features that facilitate the end-to-end software update experience. Some of these features are as follows: - Backward compatibility between an updated services farm and non-updated content farm. SharePoint Server 2016 has features that facilitate the end-to-end software upda ## Software update process <a name="updateprocess"> </a> -The process that deploys updates in a SharePoint Server 2016 environment is a two-phase process: patching and build-to-build upgrade. +The process that deploys updates in a SharePoint Server 2016, 2019, and Subscription Edition environment is a two-phase process: patching and build-to-build upgrade. Each phase has specific steps and results. It is possible to postpone the build-to-build upgrade phase. The patch phase involves running the update on each SharePoint Server in the far > [!NOTE] > No specific order of installation in a farm is required. -The patch phase has two steps, the patch deployment step and the binaries deployment step. During the patch deployment step, new binary files are copied to the server running SharePoint Server 2016. Services that use files that the patch has to replace are temporarily stopped. Stopping services reduces the requirement to restart the server to replace files that are being used. However, in some instances you have to restart the server. +The patch phase has two steps, the patch deployment step and the binaries deployment step. During the patch deployment step, new binary files are copied to the server running SharePoint Server 2016, 2019, or Subscription Edition. Services that use files that the patch has to replace are temporarily stopped. Stopping services reduces the requirement to restart the server to replace files that are being used. However, in some instances you have to restart the server. -The second step in the patch phase is the binaries deployment step. In this step, the installer copies support dynamic link library (.dll) files to the appropriate directories on the server that is running SharePoint Server 2016. This step ensures that all the web applications are running the correct version of the binary files and will function correctly after the update is installed. The update phase is complete after the binaries deployment step. +The second step in the patch phase is the binaries deployment step. In this step, the installer copies support dynamic link library (.dll) files to the appropriate directories on the server that is running SharePoint Server 2016, 2019, or Subscription Edition. This step ensures that all the web applications are running the correct version of the binary files and will function correctly after the update is installed. The update phase is complete after the binaries deployment step. The next and final phase to deploy software updates is the build-to-build upgrade phase. This phase modifies database schemas, updates objects in the farm, and updates site collections. After you finish the patch phase, you must complete the update installation by s <a name="updatestrategy"> </a> > [!NOTE]-> The information in this section is valid if you farm is not in a high availability (HA) environment. If you have an HA environment, follow the instructions at [SharePoint Server 2016 zero downtime patching steps](./sharepoint-server-2016-zero-downtime-patching-steps.md). +> The information in this section is valid if you farm is not in a high availability (HA) environment. If you have an HA environment, follow the instructions at [SharePoint Server zero downtime patching steps](./sharepoint-server-2016-zero-downtime-patching-steps.md). The update strategy that you select is based primarily on one of the following factors: In terms of downtime reduction, the following options, ordered from most to leas ## Software update deployment cycle <a name="updatecycle"> </a> -The cycle that is used for upgrading SharePoint Server 2016 farms and servers also applies to deploying software updates, which are a subset of an upgrade phase. We recommend that you use the update cycle in the following illustration as a guide to deploy software updates. +The cycle that is used for upgrading SharePoint Server 2016, 2019, or Subscription Edition farms and servers also applies to deploying software updates, which are a subset of an upgrade phase. We recommend that you use the update cycle in the following illustration as a guide to deploy software updates.  During this phase of the cycle, you learn about requirements to install the upda #### Requirements and prerequisites -First, ensure that the system can be provisioned as a farm server. For more information, see [Hardware and software requirements for SharePoint Server 2016](../install/hardware-and-software-requirements.md). Ensure that any server that you plan to update is running the same version of the operating system as the other farm servers. This includes updates, service packs, and security hotfixes. +First, ensure that the system can be provisioned as a farm server. For more information, see [Hardware and software requirements for SharePoint Server 2016](../install/hardware-and-software-requirements.md), [Hardware and software requirements for SharePoint Server 2019](/sharepoint/install/hardware-and-software-requirements-2019), and [System requirements for SharePoint Server Subscription Edition](/sharepoint/install/system-requirements-for-sharepoint-subscription-edition). ++Ensure that any server that you plan to update is running the same version of the operating system as the other farm servers. This includes updates, service packs, and security hotfixes. #### Update strategy Determine the strategy that you want to use to update the farm. Depending on you - Database-attach -For more information about the update strategy to use, see [Install a software update for SharePoint Server 2016](install-a-software-update.md) +For more information about the update strategy to use, see [Install a software update for SharePoint Server 2016, 2019, and Subscription Edition](install-a-software-update.md) #### Downtime reduction |
SharePoint | New And Improved Features In Sharepoint Server Subscription Edition 22H2 Release | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/what-s-new/new-and-improved-features-in-sharepoint-server-subscription-edition-22h2-release.md | description: "Learn about the new features and updates to existing features in S [!INCLUDE[appliesto-xxx-xxx-xxx-SUB-xxx-md](../includes/appliesto-xxx-xxx-xxx-SUB-xxx-md.md)] -Learn about the new features and updates introduced in the SharePoint Server Subscription Edition Version 22H2 feature. +Learn about the new features and updates introduced in the SharePoint Server Subscription Edition Version 22H2 feature update. ## Summary of the features The following table provides a summary of the new features introduced in the SharePoint Server Subscription Edition Version 22H2 feature update. -|**Feature**|**Release rings**|**More information**| +|**Feature**|**Release ring**|**More information**| |:--|:--|:--| |**Feature release rings** <br/> |Standard release <br/> |For more information, see [Feature release rings](#feature-release-rings). <br/> | |**AMSI integration** <br/> |Standard release <br/> |For more information, see [AMSI integration](#amsi-integration). <br/> | |
SharePoint | New And Improved Features In Sharepoint Server Subscription Edition 23H1 Release | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/what-s-new/new-and-improved-features-in-sharepoint-server-subscription-edition-23h1-release.md | + + Title: "New and improved features in SharePoint Server Subscription Edition Version 23H1" +++++audience: ITPro +f1.keywords: +- NOCSH +++ms.localizationpriority: high ++- IT_Sharepoint_Server +- IT_Sharepoint_Server_Top +- Strat_SP_server ++description: "Learn about the new features and updates to existing features in SharePoint Server Subscription Edition Version 23H1." +++# New and improved features in SharePoint Server Subscription Edition Version 23H1 +++Learn about the new features and updates introduced in the SharePoint Server Subscription Edition Version 23H1 feature update. ++## List of new features and updates to existing features ++The following table provides the list of new features and updates to existing features in SharePoint Server Subscription Edition. ++|**Feature**|**Release ring**|**More information**| +|:--|:--|:--| +|**Copy and move improvement in modern document library** <br/> |Standard release <br/> |For more information, see [Copy and move improvement in modern document library](/sharepoint/what-s-new/new-and-improved-features-in-sharepoint-server-subscription-edition-22h2-release#copy-and-move-improvement-in-modern-document-library).<br/> <br/>This was part of *Early release* in the Version 22H2 feature update.| +|**Bulk editing in modern lists** <br/> |Standard release <br/> |For more information, see [Bulk editing in modern lists](/sharepoint/what-s-new/new-and-improved-features-in-sharepoint-server-subscription-edition-22h2-release#bulk-editing-in-modern-lists). <br/> <br/> This was part of *Early release* in the Version 22H2 feature update.| +|**Column formatting enhancement** <br/> |Standard release <br/> |For more information, see [Column formatting enhancement](/sharepoint/what-s-new/new-and-improved-features-in-sharepoint-server-subscription-edition-22h2-release#column-formatting-enhancement). <br/> <br/> This was part of *Early release* in the Version 22H2 feature update.| +|**Button web part** <br/> |Standard release <br/> |For more information, see [Button web part](/sharepoint/what-s-new/new-and-improved-features-in-sharepoint-server-subscription-edition-22h2-release#button-web-part). <br/> <br/> This was part of *Early release* in the Version 22H2 feature update.| +|**Choose the default site language in the modern self-service site creation pane** <br/> |Standard release <br/> |For more information, see [Choose the default site language in the modern self-service site creation pane](/sharepoint/what-s-new/new-and-improved-features-in-sharepoint-server-subscription-edition-22h2-release#choose-the-default-site-language-in-the-modern-self-service-site-creation-pane). <br/> <br/> This was part of *Early release* in the Version 22H2 feature update.| +|**New SharePoint RESTful ListData.svc implementation** <br/> |Standard release <br/> |For more information, see [New SharePoint RESTful ListData.svc implementation](/sharepoint/what-s-new/new-and-improved-features-in-sharepoint-server-subscription-edition-22h2-release#new-sharepoint-restful-listdatasvc-implementation). <br/> <br/> This was part of *Early release* in the Version 22H2 feature update.| +|**Unified "uber" patches** <br/> |Standard release <br/> |For more information, see [Unified "uber" patches](#unified-uber-patches). <br/> | +|**Support for SharePoint Framework (SPFx) version 1.5.1** <br/> |Standard release <br/> |For more information, see [Support for SharePoint Framework (SPFx) version 1.5.1](#sfsf). <br/> | +|**New PowerShell cmdlets for variations feature** <br/> |Standard release <br/> |For more information, see [New PowerShell cmdlets for variations feature](#new-powershell-cmdlets-for-variations-feature). <br/> | +|**SharePoint Server recompiled with Visual C++ 2022** <br/> |Standard release <br/> |For more information, see [SharePoint Server recompiled with Visual C++ 2022](#ssrwv). <br/> | +|**Private key management in certificate management** <br/> |Early release <br/> |For more information, see [Private key management in certificate management](#private-key-management-in-certificate-management). <br/> | +|**Support for wildcard host header bindings** <br/> |Early release <br/> |For more information, see [Support for wildcard host header bindings](#support-for-wildcard-host-header-bindings). <br/> | +|**Expanded usage of modern sharing dialog** <br/> |Early release <br/> |For more information, see [Expanded usage of modern sharing dialog](#expanded-usage-of-modern-sharing-dialog). <br/> | +|**Column totals in modern list views** <br/> |Early release <br/> |For more information, see [Column totals in modern list views](#column-totals-in-modern-list-views). <br/> | +|**Enhanced Quick Chart web part** <br/> |Early release <br/> |For more information, see [Enhanced Quick Chart web part](#enhanced-quick-chart-web-part). <br/> | +|**Improved file picker** <br/> |Early release <br/> |For more information, see [Improved file picker](#improved-file-picker). <br/> | ++## Detailed description of features ++This section provides detailed descriptions of the new and updated features in SharePoint Server Subscription Edition Version 23H1. ++> [!NOTE] +> Features previously introduced in the SharePoint Server Subscription Edition Version 22H2 feature update will not be described here. See [New and improved features in SharePoint Server Subscription Edition Version 22H2](/sharepoint/what-s-new/new-and-improved-features-in-sharepoint-server-subscription-edition-22h2-release) for descriptions of those features. ++### Unified "uber" patches ++Up until now, Microsoft would release two separate public updates each month for SharePoint Server 2016, SharePoint Server 2019, and SharePoint Server Subscription Edition. The first public update was called the **STS** or **core** update and contained all of the language-independent file updates. The second public update was called the **WSSLOC** or **language pack** update and contained all of the language-dependent file updates. Both public updates were required to be installed to fully update a SharePoint farm, although a new language-dependent WSSLOC public update may not have been released every month. ++Some SharePoint customers were confused by the need to download and install two separate updates to fully update their SharePoint farm each month. They may mistakenly only download and install one of those updates, which could lead to unexpected behavior in their SharePoint farms due to mismatched updates. ++To simplify the process of updating your SharePoint Server farm, Microsoft will now only release a single update each month for SharePoint Server Subscription Edition, starting with the March 2023 public update. This single "uber" update combines all of the fixes that would have previously been released in separate STS and WSSLOC updates. ++The single uber updates are cumulative, so you only need to install the latest uber update to be fully up to date with all of the latest fixes for SharePoint Server Subscription Edition. It isnΓÇÖt necessary to install any of the previous STS or WSSLOC updates before installing the uber update. No additional STS or WSSLOC updates will be released after the February 2023 public updates. ++Customers should remember to run the SharePoint upgrade actions in their farm after installing a new update to complete the patching and upgrade process. For more information, see [Upgrade to SharePoint Server Subscription Edition](/sharepoint/upgrade-and-update/upgrade-to-sharepoint-server-subscription-edition). ++For more information, see [Software updates overview for SharePoint Server 2016, 2019, and Subscription Edition](/SharePoint/upgrade-and-update/software-updates-overview?branch=pr-en-us-4897), and [Install a software update for SharePoint Server](/SharePoint/upgrade-and-update/install-a-software-update?branch=pr-en-us-4897). ++<a name="sfsf"> </a> +### Support for SharePoint Framework (SPFx) version 1.5.1 ++Previous versions of SharePoint Server Subscription Edition supported SharePoint Framework (SPFx) version 1.4.1. To expand the customization scenarios that SharePoint Server Subscription Edition supports, the 23H1 feature update adds support for SharePoint Framework (SPFx) version 1.5.1. ++This is one step on our long-term journey to improve and expand the capabilities of SharePoint Framework in SharePoint Server Subscription Edition. +For more information about SharePoint Framework version 1.5.1, see [SharePoint Framework v1.5.1 release notes](/sharepoint/dev/spfx/release-1.5.1). ++### New PowerShell cmdlets for variations feature ++Previous versions of SharePoint Server included an `stsadm.exe -o variationsfixuptool` command to configure the variations feature of SharePoint. However, the `stsadm.exe` command line tool was removed in SharePoint Server Subscription Edition with no PowerShell cmdlets provided to replace this variations functionality. +SharePoint Server Subscription Edition Version 23H1 introduces four new PowerShell cmdlets that replaces the functionality of the `stsadm.exe -o variationsfixuptool` command. ++Those cmdlets are: ++ - `Deploy-SPVariation -Identity <SPWebPipeBind> [-Recurse] [-Label <String>]` + - `Repair-SPVariation -Identity <SPWebPipeBind> [-Recurse] [-Label <String>]` + - `Test-SPVariation -Identity <SPWebPipeBind> [-Recurse] [-Label <String>]` + - `Get-SPVariationJob -Identity <SPWebPipeBind>` ++For more information, see [Cmdlet reference for SharePoint Server](/powershell/module/sharepoint-server/). ++<a name="ssrwv"> </a> +### SharePoint Server recompiled with Visual C++ 2022 ++Previous versions of SharePoint Server Subscription Edition were compiled with the Visual C++ 2019 compiler for unmanaged code. The SharePoint Prerequisite Installer that comes with the SharePoint Server Subscription Edition installed the Visual C++ Redistributable Package for Visual Studio 2015-2019 to support the binaries compiled with that compiler. ++To ensure SharePoint Server can take advantage of the latest capabilities and fixes in the Visual C++ libraries, Microsoft has recompiled SharePoint Server Subscription Edition Version 23H1 with the Visual C++ 2022 compiler. The Version 23H1 feature update will automatically install the Visual C++ Redistributable Package for Visual Studio 2015-2022 to support the binaries recompiled with this compiler. + +### Private key management in certificate management + +SharePoint Server Subscription Edition introduced a new certificate management feature that allows SharePoint farm administrators to directly manage the deployment and lifecycle of SSL/TLS certificates in their SharePoint Server farms. The certificate management feature would apply a standard set of permissions to the private keys of these certificates regardless of their use cases. ++To better support least privileges scenarios and minimize the permissions given to these private keys, SharePoint Server Subscription Edition Version 23H1 applies more granular and sophisticated permission management for these private keys. The permissions are based on the certificate assignments and will be dynamically updated when the certificate assignments change. ++For example, if a certificate is assigned to perform client certificate authentication to an SMTP server, SharePoint ensures the process thatΓÇÖs connecting to the SMTP server has the necessary permissions to use the private key of that certificate. If a certificate is no longer assigned to perform client certificate authentication to an SMTP server, SharePoint removes permissions for that process so it no longer has access to the private key of that certificate. ++APIs have been added to the *Microsoft.SharePoint.Administration.CertificateManagement.SPServerCertificate* class to allow third party integration with this functionality. + +### Support for wildcard host header bindings + +Previous versions of SharePoint Server Subscription Edition support host header bindings that would allow multiple SharePoint web applications to share the same TCP port. However, SharePoint Server only supported explicit host header bindings such as "sharepoint.example.com". Sometimes customers may want to support multiple host-named site collections across multiple web applications, all using the same TCP port. ++SharePoint Server Subscription Edition Version 23H1 adds support for specifying a wildcard host header binding for a web application. This allows you to specify different wildcard bindings across multiple web applications that can share the same TCP port such as `*.external.example.com` and `*.internal.example.com`. You can then provision host-named site collections in the first web application using the `*.external.example.com` DNS naming scheme (such as `site1.external.example.com`, `site2.external.example.com`, etc.) and other host-named site collections in the second web application using the `*.internal.example.com` DNS naming scheme (such as `site1.internal.example.com`, `site2.internal.example.com`, etc.). + +### Expanded usage of modern sharing dialog + +In previous releases of SharePoint Server Subscription Edition, using sharing functionality in lists, document libraries, pages, or site contents would trigger the classic sharing dialog, even when using the modern view in a modern Team site or Communication site. ++To provide a more intuitive sharing experience, these sharing entry points have been updated to use SharePointΓÇÖs modern sharing dialog. The modern sharing dialog is also a more accessible experience. ++### Column totals in modern list views + +SharePoint Server Subscription Edition Version 23H1 adds support for displaying column totals in modern list views just like in classic list views. This option can be enabled in the **save view** feature. + +### Enhanced Quick Chart web part + +Previous versions of SharePoint Server Subscription Edition allowed users to manually enter data in the Quick Chart modern web part to render charts on modern pages. However, users were unable to connect the Quick Chart web part to a list or library within the site to consume its data. ++SharePoint Server Subscription Edition Version 23H1 enhances the Quick Chart modern web part by adding a **Get data from a list or library on this site** option. Users can now configure the Quick Chart web part to consume data from a list or library within the site. ++For more information, see [Use the Quick Chart web part](https://support.microsoft.com/office/use-the-quick-chart-web-part-bcfee244-2408-400b-a9bd-4eca61aead51). + +### Improved file picker + +SharePoint Server Subscription Edition Version 23H1 improves the modern file picker used by the Quick Links and File Viewer web parts. The Quick Links web part file picker can now support more file types such as PDF, TXT, MP4, M4V, MP3, OGG, and WAV. The File Viewer web part file picker can now support PDF files. |
SharePoint | What S Deprecated Or Removed From Sharepoint Server 2019 | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/what-s-new/what-s-deprecated-or-removed-from-SharePoint-Server-2019.md | The aggregated newsfeed feature (available at newsfeed.aspx and typically access ### Custom Help -To ensure that users receive highly relevant help content, we are moving from away from our legacy on-premises SharePoint help engine, which is based on help collections being installed in the on-prem farm. The new SharePoint help system is now rendered in the cloud and will have updated, synchronized content with Microsoft 365. Custom help based on the legacy SharePoint help engine will remain supported, but deprecated, for the SharePoint Server 2019 release. +To ensure that users receive highly relevant help content, we are moving from away from our legacy on-premises SharePoint help engine, which is based on help collections being installed in the on-premises farm. The new SharePoint help system is now rendered in the cloud and will have updated, synchronized content with Microsoft 365. Custom help based on the legacy SharePoint help engine will remain supported, but deprecated, for the SharePoint Server 2019 release. ### Groove.exe (Previous OneDrive for Business sync app) As announced by the Windows Server team, Microsoft is [deprecating](/windows-ser ### Multi-Tenancy -As Microsoft continues to innovate in SharePoint, an increasing amount of SharePoint multi-tenancy capabilities are taking dependencies on cloud technologies that aren't available in on-premises environments. The cost and complexity of providing an on-premises alternative has become prohibitive, so we will no longer support multi-tenancy in the SharePoint Server 2019 release. Existing SharePoint Server customers who depend on multi-tenancy are recommended to explore migrating to SharePoint in Microsoft 365. Other options include migrating to a non-multi-tenancy farm configuration or remaining with SharePoint Server 2016. +As Microsoft continues to innovate in SharePoint, an increasing number of SharePoint multi-tenancy capabilities are taking dependencies on cloud technologies that aren't available in on-premises environments. The cost and complexity of providing an on-premises alternative has become prohibitive, so we will no longer support multi-tenancy in the SharePoint Server 2019 release. Existing SharePoint Server customers who depend on multi-tenancy are recommended to explore migrating to SharePoint in Microsoft 365. Other options include migrating to a non-multi-tenancy farm configuration or remaining with SharePoint Server 2016. ### PDF Viewer (SharePoint Server 2019 Preview) SharePoint Server 2019 Preview included a built-in PDF viewer which allowed Shar Since the feature was first introduced in SharePoint, Microsoft BI strategy has shifted away from heavy integration to a standalone BI solution, Power BI, to give customers a flexible, optional integration with SharePoint along with standalone capabilities. Both [Power BI.com](https://powerbi.com/) and [Power BI Report Server](https://powerbi.microsoft.com/report-server/) offer the option to host and view Excel Workbooks with PowerPivot models today and is the preferred method for customers going forward to host and use their Excel Workbooks with PowerPivot models, or simply to migrate to PBIX files using the migration option in Power BI Desktop for Excel Workbooks. -### SharePoint Workflow Manager (SharePoint Server 2019 Preview) --Microsoft announced that SharePoint Server 2019 Preview would support a new workflow management application called SharePoint Workflow Manager to run SharePoint Server 2013 workflows. However, the SharePoint Workflow Manager application was canceled before its final release. The RTM release of SharePoint Server 2019 supports [Service Bus 1.1](https://support.microsoft.com/help/4077554/add-support-for-tls-1-1-and-tls-1-2-on-service-bus-for-windows-server) and [Microsoft Workflow Manager 1.0 CU5](https://support.microsoft.com/help/4055730/description-of-the-cumulative-update-5-for-workflow-manager-1-0) to run SharePoint Server 2013 workflows. For more information, see [Install and configure workflow in SharePoint Server](../governance/install-and-configure-workflow-for-sharepoint-server.md). - ### Tags and Notes The Tags and Notes feature has been removed from SharePoint Server 2019. This means that users cannot create new tags and notes or access any existing ones. Verify that you meet all of the following minimum requirements. Export-SPTagsAndNotesData -Site <http://site.contoso.com> -FilePath <tagsandnotes.zip> ``` -Where : +Where: - `<http://site.contoso.com>` is the URL to an existing SharePoint root site where you want to export the tags and notes from. |
SharePoint | What S Deprecated Or Removed From Sharepoint Server Subscription Edition | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/what-s-new/what-s-deprecated-or-removed-from-SharePoint-Server-Subscription-Edition.md | Different customers may have different interpretations of terms such as "depreca ## Deprecated features + - InfoPath Forms Services + + - Microsoft Workflow Manager + + - SharePoint 2010 workflows + + - SharePoint Designer 2013 - Internet Explorer 11 Different customers may have different interpretations of terms such as "depreca The following features and functionality have been deprecated or removed in SharePoint Server Subscription Edition. +### InfoPath Forms Services ++InfoPath Forms Services are deprecated but will remain supported for the SharePoint Server Subscription Edition release until July 14, 2026. After that date, InfoPath Forms Services will no longer be supported. Microsoft recommends exploring Power Apps as a potential alternative to InfoPath forms. ++### Microsoft Workflow Manager +Microsoft has released SharePoint Workflow Manager as the new workflow engine to power the SharePoint 2013 Workflow platform for SharePoint Server and replace Microsoft Workflow Manager. We recommend that all customers using SharePoint 2013 workflows upgrade to SharePoint Workflow Manager as soon as theyΓÇÖre able to. Microsoft will focus all future investments and maintenance on SharePoint Workflow Manger rather than Microsoft Workflow Manager, including providing support beyond the year 2026. For more information, see [Install and configure workflow for SharePoint Server](/sharepoint/governance/install-and-configure-workflow-for-sharepoint-server). + ### SharePoint 2010 workflows SharePoint 2010 workflows are deprecated but will remain supported for the SharePoint Server Subscription Edition release until July 14, 2026. After that date, SharePoint 2010 workflows will no longer be supported. Microsoft recommends exploring [SharePoint 2013 workflows](/sharepoint/dev/general-development/creating-a-workflow-by-using-sharepoint-designer-and-the-sharepoint-wo#:~:text=%20Creating%20a%20workflow%20by%20using%20SharePoint%20Designer,for%20many...%204%20See%20also.%20%20More%20) or [Power Automate](https://flow.microsoft.com/) as potential alternatives to SharePoint 2010 workflows. +### SharePoint Designer 2013 ++SharePoint Designer 2013 is deprecated but will remain supported with SharePoint Server Subscription Edition until July 14, 2026. After that date, SharePoint Designer 2013 will no longer be supported. Customers will be able to continue using Visual Studio to create and edit their SharePoint 2013 workflows after that date. + ### Internet Explorer 11 -Internet Explorer 11 is only supported in the SharePoint Central Administration site. Internet Explorer 11 is not supported in Team sites, OneDrive personal sites, or any other types of SharePoint content sites. Microsoft recommends exploring Microsoft Edge as the replacement for Internet Explorer 11. +Internet Explorer 11 is only supported in the SharePoint Central Administration site. Internet Explorer 11 isn't supported in Team sites, OneDrive personal sites, or any other types of SharePoint content sites. Microsoft recommends exploring Microsoft Edge as the replacement for Internet Explorer 11. ### Access Services 2010 Access Services 2013 has been removed and is no longer supported by Microsoft in ### Classic authentication mode for content web applications -Classic authentication mode has been removed and is no longer supported by Microsoft for content web applications in SharePoint Server Subscription Edition. Content web applications will now only support claims authentication mode. The Central Administration web application will continue to use and support classic authentication mode. +Classic authentication mode has been removed and is no longer supported by Microsoft for content web applications in SharePoint Server Subscription Edition. Content web applications will now only support claims authentication mode. The Central Administration web application continues to use and support classic authentication mode. ### Groove sync app support |