Updates from: 06/02/2022 01:30:24
Service Microsoft Docs article Related commit history on GitHub Change details
SharePoint Allow Or Prevent Custom Script https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/allow-or-prevent-custom-script.md
Title: "Allow or prevent custom script"
+ Title: Allow or prevent custom script
search.appverid:
- BSA160 - MET150 ms.assetid: 1f2c515f-5d7e-448a-9fd7-835da935584f
-description: "Learn how global and SharePoint admins can change the custom script setting for SharePoint sites in the organization."
+description: Learn how global and SharePoint admins can change the custom script setting for SharePoint sites in the organization.
# Allow or prevent custom script
To allow custom script on a particular site (previously called "site collection"
```PowerShell Set-SPOSite <SiteURL> -DenyAddAndCustomizePages 0 ```
- or by means of the PnP.PowerShell cmdlet [Set-PnPSite](/powershell/module/sharepoint-pnp/set-pnpsite)
+ or by means of the PnP.PowerShell cmdlet [Set-PnPSite](https://pnp.github.io/powershell/cmdlets/Set-PnPSite.html)
```PowerShell Set-PnPSite <SiteURL> -NoScriptSite $false
SharePoint Change Management Template https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/change-management-template.md
search.appverid: - SPO160 - MET150
-description: "Provision and customize the Workplace transformation site"
+description: Provision and customize the Workplace transformation site
# Overview of the Workplace transformation site
Learn how to customize web parts and content that will appear on certain pages o
![Image of the button web part on the Community page](media/hybrid-news-templates.png)
-Edit the [Button web part](https://support.microsoft.com/office/use-the-button-web-part-d2e37c48-11e8-45b9-8d9e-abdaa97c2a7a#:~:text=%20Add%20the%20Button%20web%20part%20%201,pane%20on%20the%20right,%20enter%20your...%20More) on bottom of the **Community** page to give users an opportunity to engage and acknowledge others. Connect the Button web part to a [Microsoft Form](https://support.microsoft.com/office/create-a-form-with-microsoft-forms-4ffb64cc-7d5d-402f-b82e-b1d49418fd9d.) where users can submit nominations. Then, use the pre-populated news post templates in **Settings > Site contents** to publish news.
+Edit the [Button web part](https://support.microsoft.com/office/use-the-button-web-part-d2e37c48-11e8-45b9-8d9e-abdaa97c2a7a#:~:text=%20Add%20the%20Button%20web%20part%20%201,pane%20on%20the%20right,%20enter%20your...%20More) on bottom of the **Community** page to give users an opportunity to engage and acknowledge others. Connect the Button web part to a [Microsoft Form](https://support.microsoft.com/office/create-a-form-with-microsoft-forms-4ffb64cc-7d5d-402f-b82e-b1d49418fd9d) where users can submit nominations. Then, use the pre-populated news post templates in **Settings > Site contents** to publish news.
<br> #### Edit the change management checklist
SharePoint Crawl Site Content https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/crawl-site-content.md
Title: "Manually request crawling and reindexing of a site, a library or a list"
+ Title: Manually request crawling and reindexing of a site, a library or a list
search.appverid:
- SPO160 - MET150 ms.assetid: 9afa977d-39de-4321-b4ca-8c7c7e6d264e
-description: "Manually request crawling and full reindexing of a site by clicking the Reindex site button. All of the site content is marked as changed and will be picked up during the next crawl and reindexed."
+description: Manually request crawling and full reindexing of a site by clicking the Reindex site button. All of the site content is marked as changed and will be picked up during the next crawl and reindexed.
# Manually request crawling and reindexing of a site, a library or a list
SharePoint Create Customize Content Type https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/create-customize-content-type.md
Title: "Create or customize a content type"
+ Title: Create or customize a content type
search.appverid:
- M365-collaboration
-description: "Learn how to create or customize a content type in the SharePoint admin center."
+description: Learn how to create or customize a content type in the SharePoint admin center.
# Create or customize a content type
SharePoint Disable Auto Modernization Classic Home Pages https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/disable-auto-modernization-classic-home-pages.md
search.appverid: - SPO160 - MET150
-description: "Learn about the automatic modernization of classic home pages, and how to disable this if you want."
+description: Learn about the automatic modernization of classic home pages, and how to disable this if you want.
# Classic home page modernization
When users first experience the change, theyΓÇÖll see a walkthrough that highlig
![Classic-to-modern upgrade experience](media/classictomodernnewGIF.gif)
-For more training, download the [classic to modern walkthrough](https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/raw/live/SharePoint/SharePointOnline/media/modernize-classic-home-page-walkthrough.pdf).
+For more training, download the [classic to modern walkthrough](https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/raw/public/SharePoint/SharePointOnline/media/modernize-classic-home-page-walkthrough.pdf).
## How to prevent specific sites from being updated
For more help in transitioning to modern, refer to the following resources:
- [Transform classic pages to modern pages](/sharepoint/dev/transform/modernize-userinterface-site-pages) -- [Enable the communication site experience on classic team sites](modernize-classic-team-site.md)
+- [Enable the communication site experience on classic team sites](modernize-classic-team-site.md)
SharePoint Support For Organization Fonts In Powerpoint For The Web https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/support-for-organization-fonts-in-powerpoint-for-the-web.md
Organization fonts allow customers to create a brand for their organizations and
## How does this work? The following diagram outlines the key steps in making our solution work:
+ :::image type="content" source="media/companyadmin.png" alt-text="image of Admin user profiles":::
1. Organization administrator uploads their fonts to their organization's SharePoint site using the **SharePoint Online Management Shell.** 2. SharePoint stores the assets in a [public Office 365 Content Delivery Network.](/microsoft-365/enterprise/use-microsoft-365-cdn-with-spo?view=o365-worldwide&preserve-view=true)
The following diagram outlines the key steps in making our solution work:
> [!NOTE] > You cannot customize the permissions of font organization asset libraries as the fonts are hosted in a public CDN. When uploaded, font asset libraries are available across your entire tenant. Currently, sub-group permissioning of font asset libraries are not supported.
-2. Ensure the site permissions for **Everyone except external user** are set to **Read** or **Edit.**
+2. Ensure that your administrator account has **Full control** permissions to the SharePoint site you are using for your Organization Asset Libraries.
+
+ :::image type="content" source="media/fullcontrol.png" alt-text="Full Control image":::
+
+3. Ensure the site permissions for **Everyone except external user** are set to **Read** or **Edit.**
:::image type="content" source="media/sitepermissions.png" alt-text="image of sitepermissions" lightbox="media/sitepermissions.png":::
- :::image type="content" source="media/userpermissions.png" alt-text="image of userpermissions":::
+ :::image type="content" source="media/userpermission.png" alt-text="image of userpermissions":::
-3. Navigate to your siteΓÇÖs home page. From the **New** dropdown menu, select **Create a Document Library** and name your new font library.
+4. Navigate to your siteΓÇÖs home page. From the **New** dropdown menu, select **Create a Document Library** and name your new font library.
:::image type="content" source="media/new-dropdown.png" alt-text="New drop-down option" lightbox="media/new-dropdown.png"::: :::image type="content" source="media/createdocumentlibrary.png" alt-text="Create and name your font library" lightbox="media/createdocumentlibrary.png":::
-4. [Download the latest version of the SharePoint Online Management Shell.](https://go.microsoft.com/fwlink/p/?LinkId=255251)
-5. [Connect your SharePoint Management Shell with your administrator username and password.](/powershell/sharepoint/sharepoint-online/connect-sharepoint-online)
-6. Using the **SharePoint Online Management Shell**, run the following command to designate the library as custom fonts asset library.
+5. [Download the latest version of the SharePoint Online Management Shell.](https://go.microsoft.com/fwlink/p/?LinkId=255251)
+6. [Connect your SharePoint Management Shell with your administrator username and password.](/powershell/sharepoint/sharepoint-online/connect-sharepoint-online)
+7. Using the **SharePoint Online Management Shell**, run the following command to designate the library as custom fonts asset library.
`Add-SPOOrgAssetsLibrary -LibraryUrl <New Document Library SharePoint URL> -OrgAssetType OfficeFontLibrary -CdnType Public`
The following diagram outlines the key steps in making our solution work:
> - Only include the direct path of your font library. The trailing `/AllItems.aspx` should not be included in your Library URL. > - Font asset libraries must be designated with `ΓÇôCdnType Public`.
-7. Using the **SharePoint Online Management Shell**, run the following command to upload your custom font(s) to the document library location.
+8. Using the **SharePoint Online Management Shell**, run the following command to upload your custom font(s) to the document library location.
`Set-SPOCustomFontCatalog -FontFolder <Local Font Folder Location> -LibraryUrl <Document Library SharePoint URL>`
The following diagram outlines the key steps in making our solution work:
`Set-SPOCustomFontCatalog -FontFolder ΓÇ£C:\ProgramData\Fonts" -LibraryUrl https://contosofonts.sharepoint.com/FontLibrary` > [!NOTE]
- > Your font folder should be the directory holding all your font files and should not include any non-font files.
+ > - Your font folder should be the directory holding all your font files and should not include any non-font files.
+ > - You may be re-prompted to enter your credentials at this step.
Allow 24-hours for the Sharepoint servers to update and for the users in your organization to see their organization fonts when using the **Font** dropdown menu in PowerPoint for the web.
+ :::image type="content" source="media/font_dropdown.png" alt-text="t":::
+ ## Important notes on features and its release ### Feature notes
SharePoint Performance Testing https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/performance-testing.md
Title: "Performance testing for SharePoint Server 2013"
+ Title: Performance testing for SharePoint Server 2013
ms.prod: sharepoint-server-itpro
ms.localizationpriority: medium ms.assetid: fe3d1a2a-6147-4d10-8d88-cba86ee2f436
-description: "Learn about how to plan and execute performance testing of a SharePoint Server 2013 environment."
+description: Learn about how to plan and execute performance testing of a SharePoint Server 2013 environment.
# Performance testing for SharePoint Server 2013
SharePoint Plan For Sql Server Always On And Microsoft Azure Disaster Recovery https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/plan-for-sql-server-always-on-and-microsoft-azure-disaster-recovery.md
Title: "Plan for SQL Server Always On and Microsoft Azure for SharePoint Server Disaster Recovery"
+ Title: Plan for SQL Server Always On and Microsoft Azure for SharePoint Server Disaster Recovery
- Strat_SP_server ms.assetid: be987a18-9a54-4925-8d78-e0798f4d2901
-description: "Use SQL Server 2014 and SQL Server Always On Availability Groups and Microsoft Azure to create a hybrid disaster-recovery environment for your on-premises SharePoint Server farm. This article describes how to design and implement this solution."
+description: Use SQL Server 2014 and SQL Server Always On Availability Groups and Microsoft Azure to create a hybrid disaster-recovery environment for your on-premises SharePoint Server farm. This article describes how to design and implement this solution.
# Plan for SQL Server Always On and Microsoft Azure for SharePoint Server Disaster Recovery
Use the configurations in the following table when you deploy SQL Server for the
|**Component**|**Settings**| |:--|:--| |Port <br/> |Block UDP port 1434. <br/> We recommend that you block TCP port 1433, and assign the port that is used by the default instance to a different port. However, this is not mandatory. <br/> Make sure that the port number that is to be assigned to the default instance is not in the registered ports. Refer to [Service Name and Transport Protocol Port Number Registry](https://go.microsoft.com/fwlink/?LinkID=626877) to avoid using the registered port. <br/> Ensure that you follow the security guidance in [Configure SQL Server security for SharePoint Server](../security-for-sharepoint-server/configure-sql-server-security-for-sharepoint-environments.md). <br/> Firewall Rules: Create new Inbound rules for the non-default port used by the SQL Server instance. <br/> Hide instance: Hide the SQL Server instance from client computers. <br/> |
-|Lock pages in memory <br/> |Grant the SQL Server service account permissions to lock pages in memory. For more information, see [Enable the Lock Pages in Memory Option (Windows)](/sql/database-engine/configure-windows/enable-the-lock-pages-in-memory-option-windows) and [Server Memory Server Configuration Options](/sql/database-engine/configure-windows/server-memory-server-configuration-options?view=sql-server-2017). <br/> |
+|Lock pages in memory <br/> |Grant the SQL Server service account permissions to lock pages in memory. For more information, see [Enable the Lock Pages in Memory Option (Windows)](/sql/database-engine/configure-windows/enable-the-lock-pages-in-memory-option-windows) and [Server Memory Server Configuration Options](/sql/database-engine/configure-windows/server-memory-server-configuration-options?view=sql-server-2017&preserve-view=true). <br/> |
|Disable Auto-create statistics <br/> |**Do not** enable auto-create statistics on SQL Server. This is not supported for SharePoint Server. For more information, see [Best practices for SQL Server in a SharePoint Server farm](best-practices-for-sql-server-in-a-sharepoint-server-farm.md). <br/> | |Set Max Degree of Parallelism <br/> |Set the max degree of parallelism (MAXDOP) to 1 in SQL Server instances that host SharePoint Server databases. <br/> **Note:** SharePoint Server installation on SQL Server will fail by design unless the installer account has permission to change it. <br/> For more information, see [Best practices for SQL Server in a SharePoint Server farm](best-practices-for-sql-server-in-a-sharepoint-server-farm.md). <br/> | |Trace Flags <br/> |Add the trace flags 1222 (return resources and types of locks participating in a deadlock) and 3226 (suppress log backup entries in the SQL error log). <br/> DBCC TRACEON (1222,-1) <br/> DBCC TRACEON (3226,-1) <br/> | |SQLAgent Job History <br/> |Make sure that SQLAgent has these settings, (Jobhistory_max_rows = 50000 and Jobhistory_max_rows_per_job = 10000). <br/> |
-|Minimum memory <br/> |Min Memory = 512 Mb. (However, this is based on our test configuration and may not apply to your SQL Server installation so you should calculate your requirement.) For more information, see [Server Memory Server Configuration Options](/sql/database-engine/configure-windows/server-memory-server-configuration-options?view=sql-server-2017) and [Configure the min memory per query Server Configuration Option](/sql/database-engine/configure-windows/server-memory-server-configuration-options?view=sql-server-2017). <br/> |
-|Maximum memory <br/> |Set the maximum memory limit for SQL Server based on the following formula: <br/> Total Server RAM (GB) - 4 GB = [max server memory] <br/> For more information, see [Server Memory Server Configuration Options](/sql/database-engine/configure-windows/server-memory-server-configuration-options?view=sql-server-2017). <br/> |
+|Minimum memory <br/> |Min Memory = 512 Mb. (However, this is based on our test configuration and may not apply to your SQL Server installation so you should calculate your requirement.) For more information, see [Server Memory Server Configuration Options](/sql/database-engine/configure-windows/server-memory-server-configuration-options?view=sql-server-2017&preserve-view=true) and [Configure the min memory per query Server Configuration Option](/sql/database-engine/configure-windows/server-memory-server-configuration-options?view=sql-server-2017&preserve-view=true). <br/> |
+|Maximum memory <br/> |Set the maximum memory limit for SQL Server based on the following formula: <br/> Total Server RAM (GB) - 4 GB = [max server memory] <br/> For more information, see [Server Memory Server Configuration Options](/sql/database-engine/configure-windows/server-memory-server-configuration-options?view=sql-server-2017&preserve-view=true). <br/> |
|DNS aliases <br/> |We recommend that you create DNS aliases for all SQL Server instances. This helps to simplify maintenance, such as to make it easier to move databases to another server. For example, the SharePoint farm in the Azure disaster recovery datacenter, connects directly to the SQL Server instance names. You should create a DNS alias rather than configure the farm with the instance names directly. <br/> **Note:** The client alias and DNS alias should match to ensure clients which don't use SQL client aliases can also contact SQL servers. <br/> For more information, see [Best practices for SQL Server in a SharePoint Server farm](best-practices-for-sql-server-in-a-sharepoint-server-farm.md). <br/> | |Database collation <br/> |Latin1_General_Cl_AS_KS_WS <br/> The SQL Server database collation must be configured for case-insensitive, accent-sensitive, kana-sensitive, and width-sensitive. This is to ensure file name uniqueness consistent with the Windows operating system. <br/> |
Each SQL Server instance that is part of an Always On Availability Group must al
For more information about prerequisites, restrictions, recommendations, and general usage for availability groups, see: -- [Prerequisites, Restrictions, and Recommendations for AlwaysOn Availability Groups (SQL Server)]( /sql/database-engine/availability-groups/windows/prereqs-restrictions-recommendations-always-on-availability?view=sql-server-2017)
+- [Prerequisites, Restrictions, and Recommendations for AlwaysOn Availability Groups (SQL Server)]( /sql/database-engine/availability-groups/windows/prereqs-restrictions-recommendations-always-on-availability?view=sql-server-2017&preserve-view=true)
-- [AlwaysOn Availability Groups (SQL Server)](/sql/database-engine/availability-groups/windows/always-on-availability-groups-sql-server?view=sql-server-2017)
+- [AlwaysOn Availability Groups (SQL Server)](/sql/database-engine/availability-groups/windows/always-on-availability-groups-sql-server?view=sql-server-2017&preserve-view=true)
The next figure (Figure 4) shows the Availability Group replica infrastructure that we used for the SharePoint databases.
Like SharePoint Server, it is easier to design the architecture up front, rather
### Availability group commit modes and failover types
-It is important to understand how commit modes affect the different types of failover for each Availability Group configuration because this will affect farm recovery. The following table is from the SQL Server documentation. This table summarizes which forms of failover are supported under different availability and failover modes. For each pairing, the effective availability mode and failover mode is determined by the intersection of the modes of the primary replica plus the modes of one or more secondary replicas. For more information, see [Failover and Failover Modes (AlwaysOn Availability Groups)](/sql/database-engine/availability-groups/windows/failover-and-failover-modes-always-on-availability-groups?view=sql-server-2017).
+It is important to understand how commit modes affect the different types of failover for each Availability Group configuration because this will affect farm recovery. The following table is from the SQL Server documentation. This table summarizes which forms of failover are supported under different availability and failover modes. For each pairing, the effective availability mode and failover mode is determined by the intersection of the modes of the primary replica plus the modes of one or more secondary replicas. For more information, see [Failover and Failover Modes (AlwaysOn Availability Groups)](/sql/database-engine/availability-groups/windows/failover-and-failover-modes-always-on-availability-groups?view=sql-server-2017&preserve-view=true).
|**Failover type**|**Synchronous-commit mode with automatic-failover mode**|**Synchronous-commit mode with manual-failover mode**|**Asynchronous-commit mode**| |:--|:--|:--|:--|
The following table lists the key infrastructure components for this disaster re
|**Infrastructure component**|**Notes**| |:--|:--| |Domain controller <br/> |For our on-premises test environment we deployed a domain controller and created the corp.adventureworks.com domain. If you decide to run a proof of concept disaster recovery scenario you can use your organization's domain name. <br/> **Note:** After we configured the domain, we also provisioned all of the VMs we'd be using for the farm and patched the OS to the same level. This made things more manageable than taking a piecemeal approach. <br/> |
-|Windows Server 2012 R2 and Windows Server 2016 failover clustering <br/> |Windows Server 2012 R2 or Windows Server 2016 on each farm server configured according to best practices (Windows Server and SharePoint Server). For more information, see [Windows Server Failover Clustering (WSFC) with SQL Server](/sql/sql-server/failover-clusters/windows/windows-server-failover-clustering-wsfc-with-sql-server?view=sql-server-2017). <br/> Every server that will be a cluster node must have the Failover Cluster feature and the Failover Cluster Management MMC installed. <br/> A file share for the WSFC Quorum. As a best practice this should be configured in a third site that can be accessed by the on-premises site and the recovery site. <br/> Document and stick to a consistent naming convention for the cluster. <br/> |
-|SQL Server database configuration and Always On Availability Groups <br/> |SQL Server 2014 or SQL Server 2016 configured according to SharePoint requirements and the best practices identified in "Dependencies, prerequisites and best practices". <br/> Databases use full recovery model. For more information, see [Recovery Models (SQL Server)](/sql/relational-databases/backup-restore/recovery-models-sql-server?view=sql-server-2017). <br/> SQL Server instance names. (We used the Default instance name, which is supported in this design across all the cluster nodes). <br/> The same file paths for the database and log file locations for each SQL Server instance. We used the following drive layouts, (System (L:\) for SQL databases and SharePoint databases), (User (S:\) for tempdb databases and log files), and (Local disk (T:\) for SharePoint SQL backups). <br/> Document and stick to a consistent naming convention for the Availability Groups, the replicas, and the listeners. <br/> |
+|Windows Server 2012 R2 and Windows Server 2016 failover clustering <br/> |Windows Server 2012 R2 or Windows Server 2016 on each farm server configured according to best practices (Windows Server and SharePoint Server). For more information, see [Windows Server Failover Clustering (WSFC) with SQL Server](/sql/sql-server/failover-clusters/windows/windows-server-failover-clustering-wsfc-with-sql-server?view=sql-server-2017&preserve-view=true). <br/> Every server that will be a cluster node must have the Failover Cluster feature and the Failover Cluster Management MMC installed. <br/> A file share for the WSFC Quorum. As a best practice this should be configured in a third site that can be accessed by the on-premises site and the recovery site. <br/> Document and stick to a consistent naming convention for the cluster. <br/> |
+|SQL Server database configuration and Always On Availability Groups <br/> |SQL Server 2014 or SQL Server 2016 configured according to SharePoint requirements and the best practices identified in "Dependencies, prerequisites and best practices". <br/> Databases use full recovery model. For more information, see [Recovery Models (SQL Server)](/sql/relational-databases/backup-restore/recovery-models-sql-server?view=sql-server-2017&preserve-view=true). <br/> SQL Server instance names. (We used the Default instance name, which is supported in this design across all the cluster nodes). <br/> The same file paths for the database and log file locations for each SQL Server instance. We used the following drive layouts, (System (L:\) for SQL databases and SharePoint databases), (User (S:\) for tempdb databases and log files), and (Local disk (T:\) for SharePoint SQL backups). <br/> Document and stick to a consistent naming convention for the Availability Groups, the replicas, and the listeners. <br/> |
|Networking <br/> |Cluster nodes - Three static IP Cluster IP addresses (two for the on-premises farm and one for the recovery farm). <br/> Availability Group Listeners - A static IP addresses for each listener. (Our test farm used four listeners.) <br/> | |Microsoft Azure gateway server <br/> |A server in Azure that provides the endpoint for the VPN gateway connection from the on-premises farm. It is configured with the Active Directory Domain Services (AD DS) and DNS Services roles and is designated as a global catalog server for the test domain (corp.adventureworks.com). <br/> When there is a disaster this server can become the primary domain controller. <br/> | |VPN gateway <br/> |A site-to-site VPN or ExpressRoute configured between the primary datacenter and the Windows Azure Subscription where the disaster recovery farm will be configured. <br/> For more information, see [Create a VNet with a Site-to-Site connection using the classic portal (classic)](/azure/vpn-gateway/vpn-gateway-howto-site-to-site-classic-portal) and [Create and modify an ExpressRoute circuit using PowerShell (classic)](/azure/expressroute/expressroute-howto-circuit-classic). <br/> |
The next table provides more information about the steps in Build phase 1.
|:--|:--| |1. Configure a two-node WSFC cluster <br/> |Use the Windows Server article, [Create a Failover Cluster](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn505754(v=ws.11)) to create a two-node cluster. For Windows Server 2016 information, see [Failover Clustering in Windows Server 2016](/windows-server/failover-clustering/failover-clustering-overview). <br/> | |2. Configure a file share witness <br/> |The preferred configuration for WSFC in a SharePoint environment is to use a file share witness and a node majority. Both cluster nodes in the on-premises farm have a quorum vote. The cluster node in the recovery farm doesn't have a vote. <br/> For more information, see [Configure and Manage the Quorum in a Windows Server 2012 Failover Cluster](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj612870(v=ws.11)). For Windows Server 2016, see [Deploy a Cloud Witness for a Failover Cluster](/windows-server/failover-clustering/failover-clustering-overview). <br/> Use the following Microsoft PowerShell cmdlet to configure a file share and node majority Quorum: <br/> `Set-ClusterQuorum -NodeAndFileShareMajority "\\fileserver\share"` <br/> Use the following PowerShell cmdlet to assign votes: <br/> `(Get-ClusterNode {CLUSTERNODENAME}).NodeWeight=1` <br/> Use the following PowerShell syntax to configure a Cloud Witness: <br/> `Set-ClusterQuorum -CloudWitness -AccountName <StorageAccountName> -AccessKey <StorageAccountAccessKey>` <br/> |
-|3. Install SQL Server on each Windows cluster node <br/> |Install SQL Server on both Windows Server cluster nodes. Note the following: <br/> **Do not** run the SQL Server setup program for a failover cluster. These nodes are not part of a SQL Failover Cluster Instance (FCI) Cluster. <br/> Make sure that the SQL Server data paths are exactly the same for each instance. <br/> For more information, see [Install SQL Server 2014 from the Installation Wizard (Setup)](/sql/database-engine/install-windows/install-sql-server-from-the-installation-wizard-setup?viewFallbackFrom=sql-server-2014) or [Install SQL Server 2014 from the Command Prompt](/sql/database-engine/install-windows/install-sql-server-from-the-command-prompt?viewFallbackFrom=sql-server-2014). Also, see [Install SQL Server from the Installation Wizard (Setup)](/sql/database-engine/install-windows/install-sql-server-from-the-installation-wizard-setup?view=sql-server-2017). <br/> |
-|4. Enable SQL Server Always On <br/> |Use the guidance in [Enable and Disable AlwaysOn Availability Groups (SQL Server)](/sql/database-engine/availability-groups/windows/enable-and-disable-always-on-availability-groups-sql-server?viewFallbackFrom=sql-server-2014) to enable Always On. Use theSQL Server2016 guidance in [Enable and Disable Always On Availability Groups (SQL Server)](/sql/database-engine/availability-groups/windows/enable-and-disable-always-on-availability-groups-sql-server?view=sql-server-2017). <br/> The database grouping section after this table shows how you can logically group SharePoint databases and map them to different availability groups to meet your disaster recovery requirements as well as your high availability requirements. <br/> |
+|3. Install SQL Server on each Windows cluster node <br/> |Install SQL Server on both Windows Server cluster nodes. Note the following: <br/> **Do not** run the SQL Server setup program for a failover cluster. These nodes are not part of a SQL Failover Cluster Instance (FCI) Cluster. <br/> Make sure that the SQL Server data paths are exactly the same for each instance. <br/> For more information, see [Install SQL Server 2014 from the Installation Wizard (Setup)](/sql/database-engine/install-windows/install-sql-server-from-the-installation-wizard-setup?viewFallbackFrom=sql-server-2014&preserve-view=true) or [Install SQL Server 2014 from the Command Prompt](/sql/database-engine/install-windows/install-sql-server-from-the-command-prompt?viewFallbackFrom=sql-server-2014). Also, see [Install SQL Server from the Installation Wizard (Setup)](/sql/database-engine/install-windows/install-sql-server-from-the-installation-wizard-setup?view=sql-server-2017&preserve-view=true). <br/> |
+|4. Enable SQL Server Always On <br/> |Use the guidance in [Enable and Disable AlwaysOn Availability Groups (SQL Server)](/sql/database-engine/availability-groups/windows/enable-and-disable-always-on-availability-groups-sql-server?viewFallbackFrom=sql-server-2014&preserve-view=true) to enable Always On. Use theSQL Server2016 guidance in [Enable and Disable Always On Availability Groups (SQL Server)](/sql/database-engine/availability-groups/windows/enable-and-disable-always-on-availability-groups-sql-server?view=sql-server-2017&preserve-view=true). <br/> The database grouping section after this table shows how you can logically group SharePoint databases and map them to different availability groups to meet your disaster recovery requirements as well as your high availability requirements. <br/> |
|5. Configure farm account security <br/> |Configure the appropriate permissions in each SQL Server instance for the SharePoint setup user administrator account. This account must be a member of the **db_owner** role and assigned to the **securityadmin** and **dbcreator** SQL Server security roles during setup and configuration. <br/> For more information, see [Configure SQL Server security for SharePoint Server](../security-for-sharepoint-server/configure-sql-server-security-for-sharepoint-environments.md) and [Account permissions and security settings in SharePoint Server 2016](../install/account-permissions-and-security-settings-in-sharepoint-server-2016.md). <br/> |
-|6. Create availability groups, Always On Endpoints, and Availability Group Listeners <br/> |Create the availability groups for synchronous-commit mode for high availability. (It is common practice to configure the availability groups logically for the logical failover of databases). After you create the Always On Endpoints, create Availability Group listeners to enable client connectivity to each availability group. <br/> **Note:** You can create the availability groups with temporary database names so SharePoint can use the listeners when the farm is configured. This is so the database connection strings point to the appropriate DNS entries created by the listeners. This saves you having to reconfigure the listeners later. <br/> For more information, see [Configure SQL Server AlwaysOn Availability Groups for SharePoint Server](configure-an-alwayson-availability-group.md). <br/> For information, see [Create a Database Mirroring Endpoint for AlwaysOn Availability Groups (SQL Server PowerShell)](/sql/database-engine/availability-groups/windows/database-mirroring-always-on-availability-groups-powershell?viewFallbackFrom=sql-server-2014). For SQL Server 2016 information, see [Database Mirroring - Always On Availability Groups- PowerShell](/sql/database-engine/availability-groups/windows/database-mirroring-always-on-availability-groups-powershell?view=sql-server-2017). <br/> For information, see [Availability Group Listeners, Client Connectivity, and Application Failover (SQL Server)](https://go.microsoft.com/fwlink/?LinkID=626903&amp;clcid=0x409). For SQL Server 2016 information, see [Listeners, Client Connectivity, Application Failover](/sql/database-engine/availability-groups/windows/listeners-client-connectivity-application-failover?view=sql-server-2017). <br/> **Note:** If you create the Availability Group Listeners using SQL Server Management Studio, you have to add an IP address for the disaster recovery subnet for each listener. This is not required if you provision Availability Group Listeners using the SQL Server `New-SqlAvailabilityGroupListener` PowerShell cmdlet. The recovery farm will reference the SQL instances through DNS host (A) entries and not the Availability Group listeners. For more information, see [New-SqlAvailabilityGroupListener](/powershell/module/sqlps/New-SqlAvailabilityGroupListener?view=sqlserver-ps). <br/> |
+|6. Create availability groups, Always On Endpoints, and Availability Group Listeners <br/> |Create the availability groups for synchronous-commit mode for high availability. (It is common practice to configure the availability groups logically for the logical failover of databases). After you create the Always On Endpoints, create Availability Group listeners to enable client connectivity to each availability group. <br/> **Note:** You can create the availability groups with temporary database names so SharePoint can use the listeners when the farm is configured. This is so the database connection strings point to the appropriate DNS entries created by the listeners. This saves you having to reconfigure the listeners later. <br/> For more information, see [Configure SQL Server AlwaysOn Availability Groups for SharePoint Server](configure-an-alwayson-availability-group.md). <br/> For information, see [Create a Database Mirroring Endpoint for AlwaysOn Availability Groups (SQL Server PowerShell)](/sql/database-engine/availability-groups/windows/database-mirroring-always-on-availability-groups-powershell?viewFallbackFrom=sql-server-2014). For SQL Server 2016 information, see [Database Mirroring - Always On Availability Groups- PowerShell](/sql/database-engine/availability-groups/windows/database-mirroring-always-on-availability-groups-powershell?view=sql-server-2017&preserve-view=true). <br/> For SQL Server 2016 information, see [Listeners, Client Connectivity, Application Failover](/sql/database-engine/availability-groups/windows/listeners-client-connectivity-application-failover?view=sql-server-2017&preserve-view=true). <br/> **Note:** If you create the Availability Group Listeners using SQL Server Management Studio, you have to add an IP address for the disaster recovery subnet for each listener. This is not required if you provision Availability Group Listeners using the SQL Server `New-SqlAvailabilityGroupListener` PowerShell cmdlet. The recovery farm will reference the SQL instances through DNS host (A) entries and not the Availability Group listeners. For more information, see [New-SqlAvailabilityGroupListener](/powershell/module/sqlps/New-SqlAvailabilityGroupListener?view=sqlserver-ps&preserve-view=true). <br/> |
#### Database grouping for disaster recovery
The next table provides more information about the steps in Build phase 2.
|2. Install prerequisites and binaries <br/> |For more information, see [Install prerequisites for SharePoint Server from a network share](../install/install-prerequisites-from-network-share.md). <br/> | |3. Configure Farm SMTP Settings, Web Apps, and Site Collections <br/> |Use the `New-SPWebApplication` cmdlet to create Web Applications and use the `New-SPSite` cmdlet to create Site Collections. <br/> | |4. Configure Service Applications <br/> |Use the Service Application cmdlets in [Index of Windows PowerShell cmdlets for SharePoint Server 2016](/powershell/module/sharepoint-server/?view=sharepoint-ps&preserve-view=true) to configure service applications. <br/> |
-|5. Add the on-premises production farm databases to availability groups and synchronize the replicas <br/> |When you finish configuring the farm, add the farm databases to the appropriate availability groups. Use these PowerShell cmdlets to add the databases and verify that they've been added to the availability group you specify, `Add-DatabasetoAvailabilityGroup` and `Get-AvailabilityGroupStatus` <br/> **Important:** Make sure that you enable the full recovery model on all databases that are to be added to an availability group before you add them. <br/> After you add the farm configuration database to an availability group you must restart all the servers in the farm to ensure farm stability. <br/> Synchronize the availability group replicas. For more information, see [Select Initial Data Synchronization Page (AlwaysOn Availability Group Wizards)](/sql/database-engine/availability-groups/windows/select-initial-data-synchronization-page-always-on-availability-group-wizards?view=sql-server-2017). <br/> |
+|5. Add the on-premises production farm databases to availability groups and synchronize the replicas <br/> |When you finish configuring the farm, add the farm databases to the appropriate availability groups. Use these PowerShell cmdlets to add the databases and verify that they've been added to the availability group you specify, `Add-DatabasetoAvailabilityGroup` and `Get-AvailabilityGroupStatus` <br/> **Important:** Make sure that you enable the full recovery model on all databases that are to be added to an availability group before you add them. <br/> After you add the farm configuration database to an availability group you must restart all the servers in the farm to ensure farm stability. <br/> Synchronize the availability group replicas. For more information, see [Select Initial Data Synchronization Page (AlwaysOn Availability Group Wizards)](/sql/database-engine/availability-groups/windows/select-initial-data-synchronization-page-always-on-availability-group-wizards?view=sql-server-2017&preserve-view=true). <br/> |
### Build phase 3 <a name="Bp3"> </a>
The next table provides more information about the steps in Build phase 3.
|**Step**|**Notes and guidance**| |:--|:--| |1. Add two nodes to the Azure disaster recovery datacenter which will stretch the on-premises WSFC cluster <br/> |Configure these settings on the server that will be the new cluster node; Install the Windows Failover clustering feature, test the cluster, and then remove the quorum vote from the new node. <br/> Open the Windows PowerShell command line as an Administrator and run the following cmdlet to install the Windows Failover clustering feature and management tools: `Install-WindowsFeature -Name Failover-Clustering -IncludeManagementTools` <br/> Test the cluster with the following cmdlet: `Test-Cluster` <br/> Remove the Quorum vote from the server with the following commands: `(Get-ClusterNode {CLUSTERNODENAME}).NodeWeight=0` <br/> For more information, see [Configure and Manage the Quorum in a Windows Server 2012 Failover Cluster](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj612870(v=ws.11)). For Windows Server 2016 information, see [Deploy a Cloud Witness for a Failover Cluster](/windows-server/failover-clustering/deploy-cloud-witness). <br/> **Note:** If you use the same architecture as our test environment, you'll have to perform these configuration steps on both the SQL Server instances in the recovery environment. <br/> |
-|2. Install the SQL Server instances <br/> |Install SQL Server on both nodes. Ensure that the data paths are exactly the same for each SQL instance and that the configurations are identical, for example, port configurations, database collation, and so on. For more information, see [Install SQL Server 2012 from the Installation Wizard (Setup)](/sql/database-engine/install-windows/install-sql-server-from-the-installation-wizard-setup?viewFallbackFrom=sql-server-2014). Also, see [Install SQL Server from the Installation Wizard (Setup)](/sql/database-engine/install-windows/install-sql-server-from-the-installation-wizard-setup?view=sql-server-2017). <br/> |
-|3. Enable SQL Server Always On Availability Groups <br/> |Use SQL Server Configuration Manager to enable SQL Server Always On Availability Groups. For more information, see [Enable and Disable AlwaysOn Availability Groups (SQL Server)](/sql/database-engine/availability-groups/windows/enable-and-disable-always-on-availability-groups-sql-server?viewFallbackFrom=sql-server-2014). For SQL Server 2016 guidance, see [Enable and Disable Always On Availability Groups (SQL Server)](/sql/database-engine/availability-groups/windows/enable-and-disable-always-on-availability-groups-sql-server?view=sql-server-2017). <br/> Refer to the table in [Build phase 1](#Bp1) for examples of the logical grouping of SharePoint Server 2016 databases to availability groups. <br/> |
+|2. Install the SQL Server instances <br/> |Install SQL Server on both nodes. Ensure that the data paths are exactly the same for each SQL instance and that the configurations are identical, for example, port configurations, database collation, and so on. For more information, see [Install SQL Server 2012 from the Installation Wizard (Setup)](/sql/database-engine/install-windows/install-sql-server-from-the-installation-wizard-setup?viewFallbackFrom=sql-server-2014). Also, see [Install SQL Server from the Installation Wizard (Setup)](/sql/database-engine/install-windows/install-sql-server-from-the-installation-wizard-setup?view=sql-server-2017&preserve-view=true). <br/> |
+|3. Enable SQL Server Always On Availability Groups <br/> |Use SQL Server Configuration Manager to enable SQL Server Always On Availability Groups. For more information, see [Enable and Disable AlwaysOn Availability Groups (SQL Server)](/sql/database-engine/availability-groups/windows/enable-and-disable-always-on-availability-groups-sql-server?viewFallbackFrom=sql-server-2014). For SQL Server 2016 guidance, see [Enable and Disable Always On Availability Groups (SQL Server)](/sql/database-engine/availability-groups/windows/enable-and-disable-always-on-availability-groups-sql-server?view=sql-server-2017&preserve-view=true). <br/> Refer to the table in [Build phase 1](#Bp1) for examples of the logical grouping of SharePoint Server 2016 databases to availability groups. <br/> |
|4. Configure farm account security <br/> |Configure the appropriate permissions in each SQL Server instance for the SharePoint setup user administrator account. This account must be a member of the **db_owner** role and assigned to the **securityadmin** and **dbcreator** SQL Server security roles during setup and configuration. <br/> For more information, see [Configure SQL Server security for SharePoint Server](../security-for-sharepoint-server/configure-sql-server-security-for-sharepoint-environments.md), [Account permissions and security settings in SharePoint Server 2016](../install/account-permissions-and-security-settings-in-sharepoint-server-2016.md), and [Account permissions and security settings in SharePoint 2013](../install/account-permissions-and-security-settings-in-sharepoint-2013.md) <br/> | ### Build phase 4
The next table provides more information about the steps in Build phase 4.
|1. Create build scripts <br/> |We recommend that you develop a set of build scripts to install SharePoint Server. These scripts can also be used to build out the recovery farm (and future SharePoint farms). Because the recovery farm will have service applications that are identical to those in the on-premises farm, it's a best practice to use identical service application and database names. Scripting reduces configuration errors and ensures consistency in farm configuration. <br/> **Note:** Service applications reference their databases by the database name, unlike the Content databases which also have a database ID that's stored in the SharePoint configuration database. <br/> There are several examples of scripted SharePoint installations that use PowerShell. For example, [SharePointDsc](https://github.com/PowerShell/SharePointDSC) or [AutoSPInstaller](https://github.com/brianlallet. Create Web applications, site collections, and service applications. Finally, set the SharePoint App domain and prefix. <br/> | |2. Install the prerequisites and binaries <br/> |For more information, see [Install prerequisites for SharePoint Server from a network share](../install/install-prerequisites-from-network-share.md). <br/> | |3. Configure farm SMTP settings, Web Applications, and Site Collections <br/> |Use the `New-SPWebApplication` cmdlet to create Web Applications and use the `New-SPSite` cmdlet to create Site Collections. <br/> |
-|4. Configure Service Applications <br/> |Use the Service Application cmdlets in [Index of Windows PowerShell cmdlets for SharePoint Server 2016](/powershell/module/sharepoint-server/?view=sharepoint-ps&preserve-view=true) to configure service applications. <br/> **Note:** Service Applications are created in the disaster recovery farm, with the exact same name as the primary farm. Ensure the database names are also named exactly the same as the primary farm, as the database will be referenced by the Service Applications in the disaster recovery farm, where the service application databases will eventually be created as replicas. As part of the process, the databases in the disaster recovery farm will be restored from the primary replicas, when the asynchronous replicas are added to the SQL Availability Group. <br/> The content databases in the disaster recovery farm can be removed from the SharePoint configuration as the primary farm content databases will have a read-only replica available in the disaster recovery SQL Server instance. <br/> Use the SharePoint 2016 Management Shell to run the following PowerShell cmdlet to dismount any content databases from the disaster recovery farm `Remove-SPContentDatabase`. <br/> If any additional content databases exist on the SQL Server instances in the disaster recovery farm, delete all of them. You can use any of these methods, [DROP DATABASE (Transact-SQL)](/sql/t-sql/statements/drop-database-transact-sql), [Database.Drop Method ()](/dotnet/api/microsoft.sqlserver.management.smo.database.drop), or [Delete a Database](/sql/relational-databases/databases/delete-a-database?view=sql-server-2017). <br/> |
+|4. Configure Service Applications <br/> |Use the Service Application cmdlets in [Index of Windows PowerShell cmdlets for SharePoint Server 2016](/powershell/module/sharepoint-server/?view=sharepoint-ps&preserve-view=true) to configure service applications. <br/> **Note:** Service Applications are created in the disaster recovery farm, with the exact same name as the primary farm. Ensure the database names are also named exactly the same as the primary farm, as the database will be referenced by the Service Applications in the disaster recovery farm, where the service application databases will eventually be created as replicas. As part of the process, the databases in the disaster recovery farm will be restored from the primary replicas, when the asynchronous replicas are added to the SQL Availability Group. <br/> The content databases in the disaster recovery farm can be removed from the SharePoint configuration as the primary farm content databases will have a read-only replica available in the disaster recovery SQL Server instance. <br/> Use the SharePoint 2016 Management Shell to run the following PowerShell cmdlet to dismount any content databases from the disaster recovery farm `Remove-SPContentDatabase`. <br/> If any additional content databases exist on the SQL Server instances in the disaster recovery farm, delete all of them. You can use any of these methods, [DROP DATABASE (Transact-SQL)](/sql/t-sql/statements/drop-database-transact-sql), [Database.Drop Method ()](/dotnet/api/microsoft.sqlserver.management.smo.database.drop), or [Delete a Database](/sql/relational-databases/databases/delete-a-database?view=sql-server-2017&preserve-view=true). <br/> |
|5. Shut down the farm <br/> |Shut down the farm after you finish configuring SharePoint. Now you can create asynchronous replicas for the databases on the on-premises farm. <br/> | ### Build phase 5
The next table provides more information about the steps in Build phase 5.
|**Step**|**Notes and guidance**| |:--|:--| |1. Verify that the SQL instance can access the database and backup shares. <br/> |Each node in an availability group must have access to a common backup location. This is required for the initial database seeding during the process of adding replicas to the availability group. <br/> The SQL Server account must have access to the common backup location. <br/> |
-|2. Create a SQL Server endpoint and grant connect permissions to the endpoint. <br/> |You must create a logon on the disaster recovery SQL Server instance in order to create a secondary replica and join the databases to the Availability Groups. For more information, see [Set Up Login Accounts for Database Mirroring or AlwaysOn Availability Groups (SQL Server)](/sql/database-engine/database-mirroring/set-up-login-accounts-database-mirroring-always-on-availability?viewFallbackFrom=sql-server-2014) and [Set Up Login Accounts - Database Mirroring Always On Availability](/sql/database-engine/database-mirroring/set-up-login-accounts-database-mirroring-always-on-availability?view=sql-server-2017). <br/> A SQL Server endpoint is required on the primary replica so the SQL instance can send log buffers to the secondary replicas. Use the process in [Create a Database Mirroring Endpoint for AlwaysOn Availability Groups (SQL Server PowerShell)](/sql/database-engine/availability-groups/windows/database-mirroring-always-on-availability-groups-powershell?viewFallbackFrom=sql-server-2014) and [Database Mirroring - Always On Availability Groups- PowerShell](/sql/database-engine/availability-groups/windows/database-mirroring-always-on-availability-groups-powershell?view=sql-server-2017) to create the endpoint. <br/> You must give the service account on the primary SQL Server instance access to the endpoint in order to transfer log buffers to the disaster recovery instances. Connect permission is required. <br/> For more information, see [GRANT Endpoint Permissions (Transact-SQL)](/sql/t-sql/statements/grant-endpoint-permissions-transact-sql). <br/> |
-|3. Create secondary replicas of the user content and service application databases in the recovery farm instance. <br/> |Each Availability Group requires a secondary replica in the disaster recovery farm. You must be connected to the SQL instance that is hosting the primary replica before you can create the secondary replica. <br/> For more information, see [Add a Secondary Replica to an Availability Group (SQL Server)](/sql/database-engine/availability-groups/windows/add-a-secondary-replica-to-an-availability-group-sql-server?view=sql-server-2017). <br/> |
-|4. Ensure that the replicas in the recovery farm are configured for Read-Only access. <br/> |The availability replicas in the DR SL Server instances are configured as readable secondary replicas. The disaster recovery farm will access the service application and content databases in read-only mode. This is because the recovery farm is already referencing the service application database names. This reduces the Recovery Time Objective (RTO) when we failover to the DR environment. <br/> **Note:** If this is not configured correctly, you may experience errors in the recovery environment. <br/> For more information, see [Configure Read-Only Routing for an Availability Group (SQL Server)](/sql/database-engine/availability-groups/windows/configure-read-only-routing-for-an-availability-group-sql-server?view=sql-server-2017) and [Configure Read-Only Access on an Availability Replica (SQL Server)](/sql/database-engine/availability-groups/windows/configure-read-only-access-on-an-availability-replica-sql-server?view=sql-server-2017). <br/> |
+|2. Create a SQL Server endpoint and grant connect permissions to the endpoint. <br/> |You must create a logon on the disaster recovery SQL Server instance in order to create a secondary replica and join the databases to the Availability Groups. For more information, see [Set Up Login Accounts for Database Mirroring or AlwaysOn Availability Groups (SQL Server)](/sql/database-engine/database-mirroring/set-up-login-accounts-database-mirroring-always-on-availability?viewFallbackFrom=sql-server-2014) and [Set Up Login Accounts - Database Mirroring Always On Availability](/sql/database-engine/database-mirroring/set-up-login-accounts-database-mirroring-always-on-availability?view=sql-server-2017&preserve-view=true). <br/> A SQL Server endpoint is required on the primary replica so the SQL instance can send log buffers to the secondary replicas. Use the process in [Create a Database Mirroring Endpoint for AlwaysOn Availability Groups (SQL Server PowerShell)](/sql/database-engine/availability-groups/windows/database-mirroring-always-on-availability-groups-powershell?viewFallbackFrom=sql-server-2014) and [Database Mirroring - Always On Availability Groups- PowerShell](/sql/database-engine/availability-groups/windows/database-mirroring-always-on-availability-groups-powershell?view=sql-server-2017&preserve-view=true) to create the endpoint. <br/> You must give the service account on the primary SQL Server instance access to the endpoint in order to transfer log buffers to the disaster recovery instances. Connect permission is required. <br/> For more information, see [GRANT Endpoint Permissions (Transact-SQL)](/sql/t-sql/statements/grant-endpoint-permissions-transact-sql). <br/> |
+|3. Create secondary replicas of the user content and service application databases in the recovery farm instance. <br/> |Each Availability Group requires a secondary replica in the disaster recovery farm. You must be connected to the SQL instance that is hosting the primary replica before you can create the secondary replica. <br/> For more information, see [Add a Secondary Replica to an Availability Group (SQL Server)](/sql/database-engine/availability-groups/windows/add-a-secondary-replica-to-an-availability-group-sql-server?view=sql-server-2017&preserve-view=true). <br/> |
+|4. Ensure that the replicas in the recovery farm are configured for Read-Only access. <br/> |The availability replicas in the DR SL Server instances are configured as readable secondary replicas. The disaster recovery farm will access the service application and content databases in read-only mode. This is because the recovery farm is already referencing the service application database names. This reduces the Recovery Time Objective (RTO) when we failover to the DR environment. <br/> **Note:** If this is not configured correctly, you may experience errors in the recovery environment. <br/> For more information, see [Configure Read-Only Routing for an Availability Group (SQL Server)](/sql/database-engine/availability-groups/windows/configure-read-only-routing-for-an-availability-group-sql-server?view=sql-server-2017&preserve-view=true) and [Configure Read-Only Access on an Availability Replica (SQL Server)](/sql/database-engine/availability-groups/windows/configure-read-only-access-on-an-availability-replica-sql-server?view=sql-server-2017&preserve-view=true). <br/> |
|5. Copy logons from the primary SQL Server instance to the secondary SQL Server instances. <br/> |You have to copy SQL logons and passwords from the primary instance to the secondary instances. SQL Server copies only the content of an availability group database. Logons and passwords are not copied from one instance to another. <br/> For more information, see [How to transfer logins and passwords between instances of SQL Server](/troubleshoot/sql/security/transfer-logins-passwords-between-instances) and [Troubleshoot Orphaned Users (SQL Server)](/sql/sql-server/failover-clusters/troubleshoot-orphaned-users-sql-server). <br/> | ### Build phase 6
Perform a failover of the cluster and the availability groups by using the Power
9. Perform this operation for each Availability Group.
-For more information, see [Perform a Planned Manual Failover of an Availability Group (SQL Server)](/sql/database-engine/availability-groups/windows/perform-a-planned-manual-failover-of-an-availability-group-sql-server?view=sql-server-2017).
+For more information, see [Perform a Planned Manual Failover of an Availability Group (SQL Server)](/sql/database-engine/availability-groups/windows/perform-a-planned-manual-failover-of-an-availability-group-sql-server?view=sql-server-2017&preserve-view=true).
**Failover step 3**
As a final note, you have to review and validate your plan for falling back to t
|**Item**|**Notes**| |:--|:--|
-|Azure subscriptions and storage accounts <br/> |At a minimum, you will need one subscription to create the Azure recovery farm. After you have a subscription, you can create up to 100 uniquely named storage accounts. As in the case of other Azure services, there are standard and premium storage accounts. For more information, see [Introduction to Microsoft Azure Storage](https://go.microsoft.com/fwlink/?LinkID=626892&amp;clcid=0x409). <br/> |
+|Azure subscriptions and storage accounts <br/> |At a minimum, you will need one subscription to create the Azure recovery farm. After you have a subscription, you can create up to 100 uniquely named storage accounts. As in the case of other Azure services, there are standard and premium storage accounts. For more information, see [Introduction to Microsoft Azure Storage](/azure/storage/common/storage-introduction). <br/> |
|Cloud services <br/> |When you create the server for the VPN gateway, a cloud service gets created for the virtual machine. At this point, you have to determine how many cloud services you want to have for the recovery farm. You obviously don't want a cloud service for every server in the farm; but should you use one or several? There are good arguments for both options. By grouping virtual machines into separate cloud services, you can work with several servers as a single unit. In our test farm, we used four cloud services. The first was for the VPN gateway and then one for each of the following tiers: front end web servers, application servers, and the database servers. For more information, see [Should I Choose Cloud Services?](/azure/cloud-services/cloud-services-choose-me). <br/> | |Networking <br/> |Virtual networks are important in this disaster recovery scenario. For more information, see [Virtual Network documentation](/en-gb/azure/virtual-network/). <br/> | |PowerShell <br/> |PowerShell Azure cmdlets can help you automate tasks in your virtual environment. For more information, see [Windows Azure PowerShell Cmdlets (v2.2.2)](https://azure.microsoft.com/blog/windows-azure-powershell-cmdlets-v2-2-2/). <br/> |
As a final note, you have to review and validate your plan for falling back to t
[What workloads can you protect with Azure Site Recovery?](/azure/site-recovery/site-recovery-workload)
-[Replicate a multi-tier SharePoint application for disaster recovery using Azure Site Recovery](/azure/site-recovery/site-recovery-sharepoint)
+[Replicate a multi-tier SharePoint application for disaster recovery using Azure Site Recovery](/azure/site-recovery/site-recovery-sharepoint)
SharePoint Sharepoint 2013 Dev Test Environments In Azure https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/sharepoint-2013-dev-test-environments-in-azure.md
Title: "SharePoint 2013 dev/test environments in Azure"
+ Title: SharePoint 2013 dev/test environments in Azure
- IT_Sharepoint_Server - IT_Sharepoint_Server_Top ms.assetid: 9cf0367c-ed53-4f14-9864-4ab984e40819
-description: "Create a basic or high-availability SharePoint dev/test farm in Microsoft Azure."
+description: Create a basic or high-availability SharePoint dev/test farm in Microsoft Azure.
# SharePoint 2013 dev/test environments in Azure
Modify the **azuredeploy.parameters.json** file as needed for your basic SharePo
- The virtual machine size of the SharePoint server (spVMSize).
-For the virtual machine sizes, you must specify a size in the [DS or GS series of virtual machines](https://azure.microsoft.com/documentation/articles/virtual-machines-windows-sizes/).
+For the virtual machine sizes, you must specify a size in the [DS or GS series of virtual machines](/azure/virtual-machines/sizes).
> [!NOTE] > Although you can specify the passwords for the various accounts in the azuredeploy. parameters.json file, this is not recommended for security reasons because the passwords are recorded in a text file that anyone with access to the file can easily see.
Modify the **azuredeploy.parameters.json** file as needed for your high-availabi
- The Windows Server AD domain name (domainName).
-For the virtual machine sizes, you must specify a size in the [DS or GS series of virtual machines](https://azure.microsoft.com/documentation/articles/virtual-machines-windows-sizes/).
+For the virtual machine sizes, you must specify a size in the [DS or GS series of virtual machines](/azure/cloud-services/cloud-services-sizes-specs).
> [!NOTE] > Although you can specify the passwords for the various accounts in the azuredeploy. parameters.json file, this is not recommended for security reasons because the passwords are recorded in a text file that anyone with access to the file can easily see.
This can take some time to complete.
## Manage the SharePoint 2013 dev/test farms <a name="powershell"> </a>
-You can administer the servers of these farms through [Remote Desktop connections](https://azure.microsoft.com/documentation/articles/virtual-machines-windows-connect-logon/).
+You can administer the servers of these farms through [Remote Desktop connections](/azure/virtual-machines/windows/connect-logon).
From the Central Administration SharePoint site, you can configure My sites, SharePoint applications, and other functionality. For more information, see [Configure SharePoint 2013](../install/configure.md).
See the instructions in [SharePoint Server 2016 dev/test environment in Azure](.
[Technical diagrams for SharePoint Server](../technical-reference/technical-diagrams.md)
-[SharePoint Server 2016 dev/test environment in Azure](./sharepoint-server-2016-dev-test-environment-in-azure.md)
+[SharePoint Server 2016 dev/test environment in Azure](./sharepoint-server-2016-dev-test-environment-in-azure.md)
SharePoint Stage 3 How To Enable A List As A Catalog https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/stage-3-how-to-enable-a-list-as-a-catalog.md
Title: "Stage 3 How to enable a list as a catalog in SharePoint Server"
+ Title: Stage 3 How to enable a list as a catalog in SharePoint Server
ms.prod: sharepoint-server-itpro
ms.localizationpriority: medium ms.assetid: 9a7d541e-8db7-48b3-8c5a-6173f7358763
-description: "Learn how to enable a list as a catalog in SharePoint Server 2016."
+description: Learn how to enable a list as a catalog in SharePoint Server 2016.
# Stage 3: How to enable a list as a catalog in SharePoint Server
In the following screenshot, notice that the structure in the **Product Hierarch
![Contoso Product Hierarchy](../media/OTCSP_ContosoProductHierarchy.PNG)
-The terms from the **Product Hierarchy** term set will also be used to create a friendly URL for our category pages on the publishing site (the Contoso website). For example, the URL to the page displaying camcorders is *http://www.contoso/cameras/camcorders* , and the URL to the page displaying camera accessories is *http://www.contoso/cameras/camera-accessories* .
+The terms from the **Product Hierarchy** term set will also be used to create a friendly URL for our category pages on the publishing site (the Contoso website). For example, the URL to the page displaying camcorders is *`http://www.contoso/cameras/camcorders`*, and the URL to the page displaying camera accessories is *`http://www.contoso/cameras/camera-accessories`*.
![Contoso Friendly URL](../media/OTCSP_ContosoFriendlyURL.PNG)
SharePoint Storage And Sql Server Capacity Planning And Configuration https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/storage-and-sql-server-capacity-planning-and-configuration.md
Title: "Storage and SQL Server capacity planning and configuration (SharePoint Server)"
+ Title: Storage and SQL Server capacity planning and configuration (SharePoint Server)
- Strat_SP_server ms.assetid: a96075c6-d315-40a8-a739-49b91c61978f
-description: "Learn how to plan and configure the storage and database tier for SQL Server in SharePoint Server."
+description: Learn how to plan and configure the storage and database tier for SQL Server in SharePoint Server.
# Storage and SQL Server capacity planning and configuration (SharePoint Server)
We recommend that for SharePoint Server Subscription Edition, 2019, or 2016 you
- SQL Server 2014 with Service Pack 1 (SP1) (SharePoint Server 2016 only)
-For more information about the benefits of these versions, see [Features Supported by the Editions of SQL Server 2014](https://go.microsoft.com/fwlink/?LinkID=808793&amp;clcid=0x409), [Editions and supported features of SQL Server 2016](/sql/sql-server/editions-and-components-of-sql-server-2016), [Editions and supported features of SQL Server 2017](/sql/sql-server/editions-and-components-of-sql-server-2017), and [https://docs.microsoft.com/sql/sql-server/editions-and-components-of-sql-server-version-15?view=sql-server-ver15](/sql/sql-server/editions-and-components-of-sql-server-version-15?view=sql-server-ver15&preserve-view=true)).
+For more information about the benefits of these versions, see [Features Supported by the Editions of SQL Server 2014](/sql/sql-server/sql-server-2014-release-notes?view=sql-server-2016&preserve-view=true), [Editions and supported features of SQL Server 2016](/sql/sql-server/editions-and-components-of-sql-server-2016), [Editions and supported features of SQL Server 2017](/sql/sql-server/editions-and-components-of-sql-server-2017), and [https://docs.microsoft.com/sql/sql-server/editions-and-components-of-sql-server-version-15?view=sql-server-ver15](/sql/sql-server/editions-and-components-of-sql-server-version-15?view=sql-server-ver15&preserve-view=true)).
-We recommend that for SharePoint Server 2013 you consider running your environment on the Enterprise Edition of SQL Server 2008 R2 with Service Pack 1 (SP1), SQL Server 2012, or SQL Server 2014 to take advantage of the other performance, availability, security, and management capabilities that these versions provide. For more information about the benefits of SQL Server 2008 R2 with SP1, SQL Server 2012, and SQL Server 2014 Enterprise Edition, see [Features Supported by the Editions of SQL Server 2014](https://go.microsoft.com/fwlink/?LinkID=808793&amp;clcid=0x409), [Features Supported by the Editions of SQL Server 2012](/previous-versions/sql/sql-server-2012/cc645993(v=sql.110)), and [Features Supported by the Editions of SQL Server 2008 R2](/previous-versions/sql/sql-server-2008-r2/cc645993(v=sql.105)).
+We recommend that for SharePoint Server 2013 you consider running your environment on the Enterprise Edition of SQL Server 2008 R2 with Service Pack 1 (SP1), SQL Server 2012, or SQL Server 2014 to take advantage of the other performance, availability, security, and management capabilities that these versions provide. For more information about the benefits of SQL Server 2008 R2 with SP1, SQL Server 2012, and SQL Server 2014 Enterprise Edition, see [Features Supported by the Editions of SQL Server 2014](/sql/sql-server/sql-server-2014-release-notes?view=sql-server-2016&preserve-view=true), [Features Supported by the Editions of SQL Server 2012](/previous-versions/sql/sql-server-2012/cc645993(v=sql.110)), and [Features Supported by the Editions of SQL Server 2008 R2](/previous-versions/sql/sql-server-2008-r2/cc645993(v=sql.105)).
In particular, you should consider your need for the following features:
SharePoint Understanding Multi Tenancy https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/understanding-multi-tenancy.md
Title: "Understanding multi-tenancy in SharePoint Server 2013"
+ Title: Understanding multi-tenancy in SharePoint Server 2013
- IT_Sharepoint_Server_Top ms.assetid: 3f03113d-627a-4cd2-adbd-2945bdee9a4b
-description: "Learn about the multi-tenancy feature and the underlying components and services related to multi-tenancy in SharePoint Server."
+description: Learn about the multi-tenancy feature and the underlying components and services related to multi-tenancy in SharePoint Server.
# Understanding multi-tenancy in SharePoint Server 2013
A SharePoint 2013 web application is composed of an Internet Information Service
#### Host-named site collection
-Host-named site collections enable you to assign a unique DNS name to site collections. For example, you can address them as http://TeamA.contoso.com and http://TeamB.fabrikam.com. This lets you deploy many sites that use unique DNS names in the same web application. It also enables service providers to scale an environment to many customers. If you do not use host-named site collections, the SharePoint web application will contain many path-based site collections that share the same host name (DNS name). For example, Team A would have a site collection at http://contoso.com/sites/teamA and Team B would have a site collection at http://fabrikam.com/sites/teamB.
+Host-named site collections enable you to assign a unique DNS name to site collections. For example, you can address them as `http://TeamA.contoso.com` and `http://TeamB.fabrikam.com`. This lets you deploy many sites that use unique DNS names in the same web application. It also enables service providers to scale an environment to many customers. If you do not use host-named site collections, the SharePoint web application will contain many path-based site collections that share the same host name (DNS name). For example, Team A would have a site collection at http://contoso.com/sites/teamA and Team B would have a site collection at http://fabrikam.com/sites/teamB.
Host Named Site Collections are fundamentally the only way to scale for multi-tenancy environments, and provide ultimate flexibility with respect to the URL namespace used. If using path-based sites with multi-tenancy the software boundary for managed paths will be reached extremely quickly.
For additional information about how to plan for host-named site collections for
#### Service groups (proxy groups)
-A *service group* , also known as *proxy group* , is a group of service applications that are selected for use by a web application.
+A *service group*, also known as *proxy group*, is a group of service applications that are selected for use by a web application.
By default, all service applications are included in the default group unless another group is specified at the time that the service application is created. You can add and remove service applications from the default group at any time. When you create a web application, you can select the default group, or you can create a custom group of services. You create a custom group of services by selecting only the service applications that you want the web application to use.
function RemoveSiteSubTenantProperty([string]$url, [string]$theKey)
#### Concepts
-[General guidance for hosters in SharePoint Server 2013](general-guidance-for-hosters-in-sharepoint-server-2013.md)
+[General guidance for hosters in SharePoint Server 2013](general-guidance-for-hosters-in-sharepoint-server-2013.md)
SharePoint Update A Web Application Url And Iis Bindings https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/update-a-web-application-url-and-iis-bindings.md
Title: "Update a web application URL and IIS bindings for SharePoint Server"
+ Title: Update a web application URL and IIS bindings for SharePoint Server
- IT_Sharepoint_Server - IT_Sharepoint_Server_Top ms.assetid: 41d83364-afc7-4b3c-81f2-faef0f140f89
-description: "Learn how to update a web application and IIS bindings for SharePoint Server."
+description: Learn how to update a web application and IIS bindings for SharePoint Server.
# Update a web application URL and IIS bindings for SharePoint Server
SharePoint Delete Odfb Lists https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/delete-odfb-lists.md
description: "Learn about deleting OneDrive experience settings."
The recommended way to delete all Microsoft OneDrive experience settings and information is to remove the user's OneDrive site, after reassigning any retained files to other users.
-An admin can delete these lists by using [PowerShell Script](/powershell/scripting/powershell-scripting?view=powershell-6) and [SharePoint Client-Side Object Model (CSOM)](/sharepoint/dev/sp-add-ins/complete-basic-operations-using-sharepoint-client-library-code) commands. All of the needed CSOM assemblies are included in the SharePointPnPPowerShellOnline Microsoft PowerShell module.
+An admin can delete these lists by using [PowerShell Script](/powershell/module/microsoft.powershell.core/about/about_scripts?view=powershell-7.2&preserve-view=true) and [SharePoint Client-Side Object Model (CSOM)](/sharepoint/dev/sp-add-ins/complete-basic-operations-using-sharepoint-client-library-code) commands. All of the needed CSOM assemblies are included in the SharePointPnPPowerShellOnline Microsoft PowerShell module.
You can adapt the script included in this article to meet the your needs. For example, you can extract the information for user1@contoso.com as follows:
SharePoint Application Management And Governance In Sharepoint https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/governance/application-management-and-governance-in-sharepoint.md
Title: "Application management and governance in SharePoint"
+ Title: Application management and governance in SharePoint
- Strat_SP_gtc ms.assetid: f8efdfaf-8ef6-445c-9fb9-8845667e478b
-description: "Learn how to govern applications for SharePoint by creating a customization policy and understanding the app model, branding, and life-cycle management."
+description: Learn how to govern applications for SharePoint by creating a customization policy and understanding the app model, branding, and life-cycle management.
# Application management and governance in SharePoint
Determine the types of customizations you want to allow and how to manage them.
- **Specific policies regarding each potential type of customization** What types of customizations do you allow?
- For more information about kinds of customizations and their potential risks, see the Customizations table later in this article. For more information about processes for managing customizations, see the white paper [SharePoint Products and Technologies customization policy](https://go.microsoft.com/fwlink/p/?linkid=92311). Most of this content still applies to SharePoint Server 2016.
+ For more information about kinds of customizations and their potential risks, see the Customizations table later in this article. Most of this content still applies to SharePoint Server 2016.
- **Policies around using the App Catalog and SharePoint Store** Which apps for SharePoint do you want to make available to your organization? Can users purchase apps directly? See [Solutions or apps for SharePoint?](application-management-and-governance-in-sharepoint.md#SolutionsApps) later in this article for more information.
SharePoint Ediscovery And In Place Holds In Sharepoint Server https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/governance/ediscovery-and-in-place-holds-in-sharepoint-server.md
Title: "eDiscovery and in-place holds in SharePoint Server"
+ Title: eDiscovery and in-place holds in SharePoint Server
ms.prod: sharepoint-server-itpro
ms.localizationpriority: medium ms.assetid: d6a85e37-4a3c-4c89-913c-563bb9c8a013
-description: "Learn about eDiscovery across SharePoint Server 2016 and Exchange Server 2016, or SharePoint Server 2013 and Exchange Server 2013, and the eDiscovery Center, eDiscovery cases, in-place holds, and exports."
+description: Learn about eDiscovery across SharePoint Server 2016 and Exchange Server 2016, or SharePoint Server 2013 and Exchange Server 2013, and the eDiscovery Center, eDiscovery cases, in-place holds, and exports.
# eDiscovery and in-place holds in SharePoint Server
As the Search system crawls content, it creates a search index. The search index
SharePoint Server 2013 introduced the concept of an in-place hold. When you apply an in-place hold to a site, content in the site remains in its original location. Users can still work with the content, but a copy of the content as it was at the time that you initiated the hold is preserved. Additionally, if an in-place hold is applied to a site, any new content that's created or added to the site after it was put on hold will be discoverable, and will be preserved if it's deleted. Also, users don't have to know that their content is on hold. > [!IMPORTANT]
-> If SharePoint Server runs on a server that uses Alternate Access Mapping (AAM), host-named site collections, or SSL termination format, then users will not be able to edit web pages in a site that has an in-place hold applied. To allow users to edit pages in sites that are on hold, you need to disable loopback checking as described in Method 2 of [KB article 896861](https://go.microsoft.com/fwlink/p/?LinkId=272340).
+> If SharePoint Server runs on a server that uses Alternate Access Mapping (AAM), host-named site collections, or SSL termination format, then users will not be able to edit web pages in a site that has an in-place hold applied. To allow users to edit pages in sites that are on hold, you need to disable loopback checking as described in Method 2 of `KB article 896861`.
An in-place hold is applied at the level of a site. When a hold is placed on a SharePoint site, a preservation hold library is created, if one doesn't already exist. The preservation hold library is only visible to site collection administrators so most users can't view it. The search crawler also has special permissions to crawl content in the preservation hold library.
SharePoint How To Use The Managed Solutions Gallery https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/governance/how-to-use-the-managed-solutions-gallery.md
Title: "How to use the Managed Solutions Gallery"
+ Title: How to use the Managed Solutions Gallery
If you want to govern the activation of code-based sandbox solutions, you can ut
After an administrator uploads a solution to the Managed Solutions Gallery, site collection administrators can add and activate the solution using existing processes. Code-based sandbox solutions that are not in the Managed Solutions Gallery can't be activated by site collection administrators within the web application. > [!IMPORTANT]
-> When an InfoPath form that contains custom code is published in a web application with a Managed Solutions Gallery, the form no longer renders in a browser. It also creates a category of sandbox solution that cannot be approved using the Managed Solutions Gallery, so publishing fails and the form can no longer be rendered by InfoPath Forms Services. For additional information, see [InfoPath Forms Containing Code Fail to Activate when using the Managed Solutions Gallery](https://support.microsoft.com/kb/3192603).
+> When an InfoPath form that contains custom code is published in a web application with a Managed Solutions Gallery, the form no longer renders in a browser. It also creates a category of sandbox solution that cannot be approved using the Managed Solutions Gallery, so publishing fails and the form can no longer be rendered by InfoPath Forms Services.
## Overview
SharePoint Add-ins are self-contained extensions of SharePoint websites that you
[Disable-SPUserSolutionAllowList](/powershell/module/sharepoint-server/Disable-SPUserSolutionAllowList?view=sharepoint-ps&preserve-view=true)
-[Get-SPUserSolutionAllowList](/powershell/module/sharepoint-server/Get-SPUserSolutionAllowList?view=sharepoint-ps&preserve-view=true)
+[Get-SPUserSolutionAllowList](/powershell/module/sharepoint-server/Get-SPUserSolutionAllowList?view=sharepoint-ps&preserve-view=true)
SharePoint Cloud Hybrid Search Faq https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/hybrid/cloud-hybrid-search-faq.md
Title: "Cloud hybrid search service (Cloud SSA) FAQ"
+ Title: Cloud hybrid search service (Cloud SSA) FAQ
ms.prod: sharepoint-server-itpro
ms.localizationpriority: medium
-description: "Cloud hybrid search service (Cloud SSA) FAQ"
+description: Cloud hybrid search service (Cloud SSA) FAQ
# Cloud hybrid search service (Cloud SSA) FAQ
SharePoint Server Search Crawler:Azure Plugin ayg2m High AzureServiceProxy::Subm
If Cloud search service application is hosted in a SharePoint Server 2013 environment, the uls tag tracking the error would be `amnz2` and `amoeu`.
-You need to request an increase in the available quota to fix the issue. To increase the maximum items that can be indexed beyond 20 million, you need to contact Microsoft Support via the [Microsoft 365 admin center](/office365/admin/contact-support-for-business-products?tabs=online&view=o365-worldwide).
+You need to request an increase in the available quota to fix the issue. To increase the maximum items that can be indexed beyond 20 million, you need to contact Microsoft Support via the [Microsoft 365 admin center](/office365/admin/contact-support-for-business-products?tabs=online&view=o365-worldwide&preserve-view=true).
***My Microsoft 365 organization is configured for hybrid. Can I query for only on-premises items that have been crawled using Cloud hybrid search service application?***
Cloud search service application always communicates with endpoints using port 4
3. <https://login.windows.net/common/oauth2/authorize>
-4. <https://sts.windows.net/*>
+4. `https://sts.windows.net/*`
5. [https://login.microsoftonline.com](https://login.microsoftonline.com/)
SharePoint Configure A Reverse Proxy Device For Sharepoint Server Hybrid https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/hybrid/configure-a-reverse-proxy-device-for-sharepoint-server-hybrid.md
Title: "Configure a reverse proxy device for SharePoint Server hybrid"
+ Title: Configure a reverse proxy device for SharePoint Server hybrid
- SPO_Content ms.localizationpriority: medium ms.assetid: 1780ec27-19f8-4d77-b787-8abc23921258-
-description: "Learn about supported reverse proxy devices for SharePoint Server hybrid deployments."
+description: Learn about supported reverse proxy devices for SharePoint Server hybrid deployments.
# Configure a reverse proxy device for SharePoint Server hybrid
The table below lists the currently supported reverse proxy devices for SharePoi
|Azure Application Proxy|[Enable remote access to SharePoint in Microsoft 365 with Azure AD Application Proxy](/azure/active-directory/manage-apps/application-proxy-integrate-with-sharepoint-server)|Azure Application Proxy is an Azure service that allows remote access to services within your network without opening firewall ports from the Internet to your service.| |Windows Server 2012 R2 with Web Application Proxy (WA-P) <br/> |[Configure Web Application Proxy for a hybrid environment](configure-web-application-proxy-for-a-hybrid-environment.md) <br/> |Web Application Proxy (WA-P) is a Remote Access service in Windows Server 2012 R2 that publishes web applications that users can interact with from many devices. <br/> > [!IMPORTANT]> To use Web Application Proxy as a reverse proxy device in a hybrid SharePoint Server environment, you must also deploy AD FS in Windows Server 2012 R2. | |Forefront Threat Management Gateway (TMG) 2010 <br/> |[Configure Forefront TMG for a hybrid environment](configure-forefront-tmg-for-a-hybrid-environment.md) <br/> |Forefront TMG 2010 is a comprehensive, secure, web gateway solution that provides secure reverse proxy functionality. <br/> > [!NOTE]> Forefront TMG 2010 is no longer sold by Microsoft but will be supported through 4/14/2020. For more information, see [Microsoft Support Lifecycle information for TMG 2010](https://support.microsoft.com/lifecycle/default.aspx?LN=en-us&amp;p1=14873&amp;x=13&amp;y=9). |
-|F5 BIG-IP <br/> |[Enabling SharePoint 2013 Hybrid Search with the BIG-IP](https://devcentral.f5.com/articles/enabling-sharepoint-2013-hybrid-search-with-the-big-ip) <br/> |External content managed by F5 Networks. <br/> |
+|F5 BIG-IP <br/> |[Enabling SharePoint 2013 Hybrid Search with the BIG-IP](https://community.f5.com/t5/technical-articles/enabling-sharepoint-2013-hybrid-search-with-the-big-ip/ta-p/282467) <br/> |External content managed by F5 Networks. <br/> |
|Citrix NetScaler <br/> |[Citrix NetScaler and Microsoft SharePoint 2013 Hybrid Deployment Guide](https://www.citrix.com/content/dam/citrix/en_us/documents/products-solutions/deployment-guide-netscaler-office-365-en.pdf) <br/> |External content managed by Citrix. <br/> | ## See also
SharePoint Configure Cloud Hybrid Searchroadmap https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/hybrid/configure-cloud-hybrid-searchroadmap.md
Title: "Configure cloud hybrid search - roadmap"
+ Title: Configure cloud hybrid search - roadmap
- SPO_Content ms.assetid: 0bba350d-ec33-43db-a873-930559c78dee
-description: "Learn how to configure cloud hybrid search for SharePoint Server by setting up a cloud Search service application in your SharePoint Server environment and connecting it to your search index in Office 365."
+description: Learn how to configure cloud hybrid search for SharePoint Server by setting up a cloud Search service application in your SharePoint Server environment and connecting it to your search index in Office 365.
# Configure cloud hybrid search - roadmap
You might find this guidance useful:
After setting up and validating the planned search experiences, you might want to clear your search index in Office 365 for metadata from the on-premises content you've used during this work. This works differently from what you might be familiar with from SharePoint Server.
-In the SharePoint Central Administration website you can use the option "Index reset" for an SSA to remove all content from the search index. This option does not work for cloud hybrid search because there is no direct communication between the cloud SSA in SharePoint Server and the search index in Office 365. If you only want to remove some on-premises metadata, remove that on-premises content source, or create a crawl rule that doesn't crawl the URL of a file. If you need to remove all metadata from on-premises content from the search index in Office 365, open a ticket with [Microsoft Support](https://support.microsoft.com/assistedsupportproducts).
+In the SharePoint Central Administration website you can use the option "Index reset" for an SSA to remove all content from the search index. This option does not work for cloud hybrid search because there is no direct communication between the cloud SSA in SharePoint Server and the search index in Office 365. If you only want to remove some on-premises metadata, remove that on-premises content source, or create a crawl rule that doesn't crawl the URL of a file. If you need to remove all metadata from on-premises content from the search index in Office 365, open a ticket with [Microsoft Support](https://support.microsoft.com/).
## Proxy Considerations <a name="BKMK_SearchProxy"> </a>
SharePoint Configure Inbound Connectivity https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/hybrid/configure-inbound-connectivity.md
Title: "Configure connectivity from Microsoft 365 to SharePoint Server"
+ Title: Configure connectivity from Microsoft 365 to SharePoint Server
- SPO_Content ms.assetid: 91274b73-f7be-4066-a4ab-ec30af30016e
-description: "Learn how to configure inbound connectivity for SharePoint hybrid."
+description: Learn how to configure inbound connectivity for SharePoint hybrid.
# Configure connectivity from Microsoft 365 to SharePoint Server
New-SPSite 'https://spexternal.adventureworks.com' -HostHeaderWebApplication 'ht
Where: -- https://spexternal.adventureworks.com is the URL of the host-named site collection. This URL must be identical to the External URL.
+- `https://spexternal.adventureworks.com` is the URL of the host-named site collection. This URL must be identical to the External URL.
- https://sharepoint is the web application that the site collection is created in.