From 00952f226040affd30f47471d084e463076632ef Mon Sep 17 00:00:00 2001 From: Akash Ravi Date: Wed, 27 Nov 2024 09:36:17 -0800 Subject: [PATCH 01/14] Update manage-access-agents-in-sharepoint.md Added notes about using permissions, service plan details, and site owner controls. --- .../manage-access-agents-in-sharepoint.md | 25 ++++++++++++++----- 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/SharePoint/SharePointOnline/manage-access-agents-in-sharepoint.md b/SharePoint/SharePointOnline/manage-access-agents-in-sharepoint.md index 7ffb49591c..91162827e6 100644 --- a/SharePoint/SharePointOnline/manage-access-agents-in-sharepoint.md +++ b/SharePoint/SharePointOnline/manage-access-agents-in-sharepoint.md @@ -32,10 +32,18 @@ Agents in SharePoint, powered by AI, help users quickly find information and ins ## Manage who can access the agents +### Leverage file permissions on the agent file + +As agents in SharePoint are represented as [.agent files](https://support.microsoft.com/office/create-and-edit-an-agent-d16c6ca1-a8e3-4096-af49-67e1cfdddd42#where-agent-file), permissions on the *.agent* file govern who can access or edit the agent. Only users who are able to create or access files on a SharePoint site can create or access agents. + +### Control user access through licensing + Currently, users with a [Microsoft 365 Copilot license](/copilot/microsoft-365/microsoft-365-copilot-licensing) can use the agents. You can use the [Microsoft 365 Copilot setup guide](https://admin.microsoft.com/Adminportal/Home?Q=learndocs#/modernonboarding/microsoft365copilotsetupguide) in the Microsoft 365 admin center to assign the required licenses to users. For more information, see [Assign licenses to users in the Microsoft 365 admin center](/microsoft-365/admin/manage/assign-licenses-to-users) and [Microsoft 365 Copilot requirements](/copilot/microsoft-365/microsoft-365-copilot-requirements). +Admins can choose to leverage the service plans under the Copilot license to specifically allow or block users from using Copilot experiences on SharePoint. Under the [license details page for Microsoft 365 Copilot](https://admin.microsoft.com/Adminportal/Home?#/licensedetailpage/639dec6b-bb19-468b-871c-c5c441c4b0cb) on the Microsoft 365 admin center, admins can turn *'Microsoft 365 Copilot for SharePoint'* on or off on a per-user basis. For example, a user could be allowed to use Microsoft 365 Copilot on Teams but not use any agents on SharePoint alone. Please note that this will also disable Copilots on OneDrive and the SharePoint page authoring Copilot for that user.  + > [!NOTE] -> From December 1, 2024, to June 30, 2025, enterprise tenants with 50 or more Microsoft 365 Copilot licenses will receive 10,000 free Agents in SharePoint queries for unlicensed users every month as a trial. Users with a role SharePoint administrators or higher can [check the trial promotion status](/powershell/module/sharepoint-online/get-spocopilotpromooptinstatus) and [set trial promotion](/powershell/module/sharepoint-online/set-spocopilotpromooptinstatus) using PowerShell cmdlets. Please see terms of trial usage [here](/legal/microsoft-365/in-app-trials-terms-of-service). +> From December 1, 2024, to June 30, 2025, enterprise tenants with 50 or more Microsoft 365 Copilot licenses will receive 10,000 free Agents in SharePoint queries for unlicensed users every month as a trial. Users with a role of SharePoint administrator or higher can [check the trial promotion status](/powershell/module/sharepoint-online/get-spocopilotpromooptinstatus) and [set trial promotion](/powershell/module/sharepoint-online/set-spocopilotpromooptinstatus) using PowerShell cmdlets. Please see the terms of trial usage [here](/legal/microsoft-365/in-app-trials-terms-of-service).  ## Manage what information a user can access through the agents @@ -47,7 +55,7 @@ Agents in SharePoint use SharePoint sites, pages, and document libraries as know - Control access to a site that isn't associated with a group using [site permissions](/sharepoint/site-permissions). - Control access with access governance policies available in the SharePoint admin center and PowerShell. -Learn more about using SharePoint built-in features to control access [here](/sharepoint/sharepoint-copilot-best-practices#step-2---prevent-oversharing-and-control-access-with-sharepoint-and-onedrive). +Learn more about using SharePoint's built-in features to control access [here](/sharepoint/sharepoint-copilot-best-practices#step-2---prevent-oversharing-and-control-access-with-sharepoint-and-onedrive). ### With SharePoint Advanced Management @@ -57,12 +65,17 @@ Learn more about more features to prevent oversharing, control access, and enhan ### With Microsoft Purview Data Loss Prevention (DLP) You can prevent selected files from being used by agents by using sensitivity labels along with [Microsoft Purview Data Loss Prevention (DLP)](/purview/dlp-learn-about-dlp). You [do this](/purview/dlp-create-deploy-policy#scenario-2-block-sharing-of-sensitive-items-via-sharepoint-and-onedrive-in-microsoft-365-with-external-users) by creating a DLP custom policy with the **Content contains** > **Sensitivity labels** condition to exclude items from being processed. Identified items are available in the citations of the response, but the content of the item isn't used in the response. -We don’t yet support adding a sensitivity label directly to the [.agent file](https://support.microsoft.com/office/create-and-edit-an-agent-d16c6ca1-a8e3-4096-af49-67e1cfdddd42#where-agent-file). If you want to govern your *.agent* file with DLP, instead of using the Sensitivity labels as the condition, you can use conditions based on the *.agent* extension. We'll support the ability of adding a sensitivity label directly to a *.agent* file in the future. +We don’t yet support adding a sensitivity label directly to the [.agent file](https://support.microsoft.com/office/create-and-edit-an-agent-d16c6ca1-a8e3-4096-af49-67e1cfdddd42#where-agent-file). If you want to govern your *.agent* file with DLP, instead of using the sensitivity labels as the condition, you can use conditions based on the *.agent* extension. We'll support the ability of adding a sensitivity label directly to a *.agent* file in the future. + +## Manage where agents are available in SharePoint + +### Site owner controls + +Agents created in SharePoint are not automatically listed or published anywhere. Users can manually navigate to *.agent* files to use them just like how they would discover or use Word or Excel files. Site owners can choose to designate specific agents from their sites as 'approved' ones. These agents would be guaranteed to show up on the picker for that particular site, and users can differentiate them from the ones that are recommended to them. Learn more [here](https://support.microsoft.com/en-us/office/manage-agents-in-sharepoint-bcab837a-835c-4a1a-8ad4-d53a353c369f). -## Manage where agents are available in SharePoint with restricted content discovery +### Turn agents off on sites with restricted content discovery -You as a SharePoint Admin can turn off all agent-related features on individual sites with the [restricted content discovery](/sharepoint/restricted-access-control). Once a site is flagged with restricted content discovery, users can't see the Copilot icon on the upper right of the site. Therefore, they don’t have access to use the ready-made agent, create new agents, or add content from that site to any other agents. The restricted content discovery policy leaves site access unchanged but prevents the site's content from being surfaced in Microsoft 365 Copilot or organization-wide Search for all users. -You as a SharePoint Admin can turn off all agent-related features on individual sites with the [restricted content discovery](/sharepoint/restricted-access-control). Once a site is flagged with restricted content discovery, users can't see the Copilot icon on the upper right of the site. Therefore, they don’t have access to use the ready-made agent, create new agents, or add content from that site to any other agents. The restricted content discovery policy leaves site access unchanged but prevents the site's content from being surfaced in Microsoft 365 Copilot or organization-wide Search for all users. +You as a SharePoint Admin can turn off all agent-related features on individual sites with the [restricted content discovery](/sharepoint/restricted-access-control). Once a site is flagged with restricted content discovery, users can't see the Copilot icon on the upper right of the site. Therefore, they don’t have access to use the ready-made agent, create new agents, or add content from that site to any other agents. The restricted content discovery policy leaves site access unchanged but prevents the site's content from being surfaced in Microsoft 365 Copilot or organization-wide Search for all users.  ## More resources From 1cfbe0ff8216708472ea87c8b43af2eded3fe8e4 Mon Sep 17 00:00:00 2001 From: Akash Ravi Date: Wed, 27 Nov 2024 09:46:30 -0800 Subject: [PATCH 02/14] Update manage-access-agents-in-sharepoint.md Fixed RCD link --- .../SharePointOnline/manage-access-agents-in-sharepoint.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/SharePoint/SharePointOnline/manage-access-agents-in-sharepoint.md b/SharePoint/SharePointOnline/manage-access-agents-in-sharepoint.md index 91162827e6..48a747753d 100644 --- a/SharePoint/SharePointOnline/manage-access-agents-in-sharepoint.md +++ b/SharePoint/SharePointOnline/manage-access-agents-in-sharepoint.md @@ -75,7 +75,7 @@ Agents created in SharePoint are not automatically listed or published anywhere. ### Turn agents off on sites with restricted content discovery -You as a SharePoint Admin can turn off all agent-related features on individual sites with the [restricted content discovery](/sharepoint/restricted-access-control). Once a site is flagged with restricted content discovery, users can't see the Copilot icon on the upper right of the site. Therefore, they don’t have access to use the ready-made agent, create new agents, or add content from that site to any other agents. The restricted content discovery policy leaves site access unchanged but prevents the site's content from being surfaced in Microsoft 365 Copilot or organization-wide Search for all users.  +You as a SharePoint Admin can turn off all agent-related features on individual sites with the [restricted content discovery](/sharepoint/restricted-content-discovery). Once a site is flagged with restricted content discovery, users can't see the Copilot icon on the upper right of the site. Therefore, they don’t have access to use the ready-made agent, create new agents, or add content from that site to any other agents. The restricted content discovery policy leaves site access unchanged but prevents the site's content from being surfaced in Microsoft 365 Copilot or organization-wide Search for all users.  ## More resources From 0f6eb766411b40c8d3ca0562dbcd465c98213132 Mon Sep 17 00:00:00 2001 From: Akash Ravi Date: Wed, 27 Nov 2024 10:02:00 -0800 Subject: [PATCH 03/14] Update manage-access-agents-in-sharepoint.md based on acrolinx comments --- .../manage-access-agents-in-sharepoint.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/SharePoint/SharePointOnline/manage-access-agents-in-sharepoint.md b/SharePoint/SharePointOnline/manage-access-agents-in-sharepoint.md index 48a747753d..63d0859e61 100644 --- a/SharePoint/SharePointOnline/manage-access-agents-in-sharepoint.md +++ b/SharePoint/SharePointOnline/manage-access-agents-in-sharepoint.md @@ -32,7 +32,7 @@ Agents in SharePoint, powered by AI, help users quickly find information and ins ## Manage who can access the agents -### Leverage file permissions on the agent file +### Use file permissions on the agent file As agents in SharePoint are represented as [.agent files](https://support.microsoft.com/office/create-and-edit-an-agent-d16c6ca1-a8e3-4096-af49-67e1cfdddd42#where-agent-file), permissions on the *.agent* file govern who can access or edit the agent. Only users who are able to create or access files on a SharePoint site can create or access agents. @@ -40,7 +40,7 @@ As agents in SharePoint are represented as [.agent files](https://support.micros Currently, users with a [Microsoft 365 Copilot license](/copilot/microsoft-365/microsoft-365-copilot-licensing) can use the agents. You can use the [Microsoft 365 Copilot setup guide](https://admin.microsoft.com/Adminportal/Home?Q=learndocs#/modernonboarding/microsoft365copilotsetupguide) in the Microsoft 365 admin center to assign the required licenses to users. For more information, see [Assign licenses to users in the Microsoft 365 admin center](/microsoft-365/admin/manage/assign-licenses-to-users) and [Microsoft 365 Copilot requirements](/copilot/microsoft-365/microsoft-365-copilot-requirements). -Admins can choose to leverage the service plans under the Copilot license to specifically allow or block users from using Copilot experiences on SharePoint. Under the [license details page for Microsoft 365 Copilot](https://admin.microsoft.com/Adminportal/Home?#/licensedetailpage/639dec6b-bb19-468b-871c-c5c441c4b0cb) on the Microsoft 365 admin center, admins can turn *'Microsoft 365 Copilot for SharePoint'* on or off on a per-user basis. For example, a user could be allowed to use Microsoft 365 Copilot on Teams but not use any agents on SharePoint alone. Please note that this will also disable Copilots on OneDrive and the SharePoint page authoring Copilot for that user.  +Admins can choose to edit the service plans under the Copilot license to specifically allow or block users from using Copilot experiences on SharePoint. Under the [license details page for Microsoft 365 Copilot](https://admin.microsoft.com/Adminportal/Home?#/licensedetailpage/639dec6b-bb19-468b-871c-c5c441c4b0cb) on the Microsoft 365 admin center, admins can turn *'Microsoft 365 Copilot for SharePoint'* on or off on a per-user basis. For example, a user could be allowed to use Microsoft 365 Copilot on Teams but not use any agents on SharePoint alone. Note that this will also disable Copilots on OneDrive and the SharePoint page authoring Copilot for that user.  > [!NOTE] > From December 1, 2024, to June 30, 2025, enterprise tenants with 50 or more Microsoft 365 Copilot licenses will receive 10,000 free Agents in SharePoint queries for unlicensed users every month as a trial. Users with a role of SharePoint administrator or higher can [check the trial promotion status](/powershell/module/sharepoint-online/get-spocopilotpromooptinstatus) and [set trial promotion](/powershell/module/sharepoint-online/set-spocopilotpromooptinstatus) using PowerShell cmdlets. Please see the terms of trial usage [here](/legal/microsoft-365/in-app-trials-terms-of-service).  @@ -71,11 +71,11 @@ We don’t yet support adding a sensitivity label directly to the [.agent file]( ### Site owner controls -Agents created in SharePoint are not automatically listed or published anywhere. Users can manually navigate to *.agent* files to use them just like how they would discover or use Word or Excel files. Site owners can choose to designate specific agents from their sites as 'approved' ones. These agents would be guaranteed to show up on the picker for that particular site, and users can differentiate them from the ones that are recommended to them. Learn more [here](https://support.microsoft.com/en-us/office/manage-agents-in-sharepoint-bcab837a-835c-4a1a-8ad4-d53a353c369f). +Agents created in SharePoint aren't automatically listed or published anywhere. Users can manually navigate to *.agent* files to use them just like how they would discover or use Word or Excel files. Site owners can choose to designate specific agents from their sites as 'approved' ones. These agents would be guaranteed to show up on the picker for that particular site, and users can differentiate them from the ones that are recommended to them. Learn more [here](https://support.microsoft.com/en-us/office/manage-agents-in-sharepoint-bcab837a-835c-4a1a-8ad4-d53a353c369f). -### Turn agents off on sites with restricted content discovery +### Turn off agents on sites with restricted content discovery -You as a SharePoint Admin can turn off all agent-related features on individual sites with the [restricted content discovery](/sharepoint/restricted-content-discovery). Once a site is flagged with restricted content discovery, users can't see the Copilot icon on the upper right of the site. Therefore, they don’t have access to use the ready-made agent, create new agents, or add content from that site to any other agents. The restricted content discovery policy leaves site access unchanged but prevents the site's content from being surfaced in Microsoft 365 Copilot or organization-wide Search for all users.  +You as a SharePoint Admin can turn off all agent-related features on individual sites with the [restricted content discovery](/sharepoint/restricted-content-discovery). Once a site is flagged with restricted content discovery, users can't see the Copilot icon on the upper right of the site. Therefore, they don’t have access to use the ready-made agent, create new agents, or add content from that site to any other agents. The restricted content discovery policy leaves site access unchanged but prevents the site's content from being surfaced in Microsoft 365 Copilot or organization-wide search for all users.  ## More resources From 3ce544dd7c2f6982bd728866ed413b767a7c2611 Mon Sep 17 00:00:00 2001 From: Rui Hu <7605757+maggierui@users.noreply.github.com> Date: Mon, 2 Dec 2024 10:05:09 -0500 Subject: [PATCH 04/14] broken links row 1 and row 2 --- ...sharepoint-server-2013-in-a-three-tier-farm.md | 15 ++++++++------- ...software-requirements-for-sharepoint-hybrid.md | 10 +++++----- 2 files changed, 13 insertions(+), 12 deletions(-) diff --git a/SharePoint/SharePointServer/administration/configure-sharepoint-server-2013-in-a-three-tier-farm.md b/SharePoint/SharePointServer/administration/configure-sharepoint-server-2013-in-a-three-tier-farm.md index 63af4e2f0a..dabba531d8 100644 --- a/SharePoint/SharePointServer/administration/configure-sharepoint-server-2013-in-a-three-tier-farm.md +++ b/SharePoint/SharePointServer/administration/configure-sharepoint-server-2013-in-a-three-tier-farm.md @@ -1,10 +1,10 @@ --- title: "Test Lab Guide Configure SharePoint Server 2013 in a three-tier farm" ms.reviewer: -ms.author: serdars -author: SerdarSoysal -manager: serdars -ms.date: 7/10/2017 +ms.author: ruihu +author: maggierui +manager: jtremper +ms.date: 12/2/2024 audience: ITPro f1.keywords: - NOCSH @@ -49,10 +49,11 @@ For information about how to configure this test lab in Hyper-V, see [Hosting th ## See also -#### Concepts +### Concepts [Install SharePoint Server 2016 across multiple servers](../install/install-sharepoint-server-2016-across-multiple-servers.md) -#### Other Resources -[Test Lab Guides](https://go.microsoft.com/fwlink/p/?LinkId=202817) +### Other Resources + +[Test Lab Guides](/sharepoint/administration/test-lab-guides) diff --git a/SharePoint/SharePointServer/hybrid/hardware-and-software-requirements-for-sharepoint-hybrid.md b/SharePoint/SharePointServer/hybrid/hardware-and-software-requirements-for-sharepoint-hybrid.md index 459fd8bc29..bc8985d1df 100644 --- a/SharePoint/SharePointServer/hybrid/hardware-and-software-requirements-for-sharepoint-hybrid.md +++ b/SharePoint/SharePointServer/hybrid/hardware-and-software-requirements-for-sharepoint-hybrid.md @@ -1,10 +1,10 @@ --- title: "Hardware and software requirements for SharePoint hybrid" ms.reviewer: -ms.author: serdars -author: SerdarSoysal -manager: serdars -ms.date: 2/5/2018 +ms.author: ruihu +author: maggierui +manager: jtremper +ms.date: 12/2/2024 audience: ITPro f1.keywords: - NOCSH @@ -91,7 +91,7 @@ The following table lists the currently supported reverse proxy devices for Shar |:-----|:-----|:-----| |Windows Server 2012 R2 with Web Application Proxy (WA-P)
|[Configure Web Application Proxy for a hybrid environment](configure-web-application-proxy-for-a-hybrid-environment.md)
|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.
> [!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. Earlier versions of Windows don't support Web Application Proxy | |Forefront Threat Management Gateway (TMG) 2010
|[Configure Forefront TMG for a hybrid environment](configure-forefront-tmg-for-a-hybrid-environment.md)
|Forefront TMG 2010 is a comprehensive, secure, web gateway solution that provides secure reverse proxy functionality.
Note that 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 Forefront TMG 2010](/lifecycle/products/?alpha=Forefront+Threat+Management+Gateway+2010&Filter=FilterNO). | -|F5 BIG-IP
|[Enabling SharePoint 2013 Hybrid Search with the BIG-IP](https://devcentral.f5.com/articles/enabling-sharepoint-2013-hybrid-search-with-the-big-ip)
|This is external content that's managed by F5 Networks.
| +|F5 BIG-IP
|[Enabling SharePoint 2013 Hybrid Search with the BIG-IP](https://community.f5.com/kb/technicalarticles/enabling-sharepoint-2013-hybrid-search-with-the-big-ip/282467)
|This is external content that's managed by F5 Networks.
| #### General reverse proxy requirements From 49fca75eabf28c7f3d64dd3d1ee6d203067f8d39 Mon Sep 17 00:00:00 2001 From: Rui Hu <7605757+maggierui@users.noreply.github.com> Date: Mon, 2 Dec 2024 10:07:44 -0500 Subject: [PATCH 05/14] hardware software for sharepoint hybrid acrolinx --- ...and-software-requirements-for-sharepoint-hybrid.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/SharePoint/SharePointServer/hybrid/hardware-and-software-requirements-for-sharepoint-hybrid.md b/SharePoint/SharePointServer/hybrid/hardware-and-software-requirements-for-sharepoint-hybrid.md index bc8985d1df..c600ae17b5 100644 --- a/SharePoint/SharePointServer/hybrid/hardware-and-software-requirements-for-sharepoint-hybrid.md +++ b/SharePoint/SharePointServer/hybrid/hardware-and-software-requirements-for-sharepoint-hybrid.md @@ -19,7 +19,7 @@ ms.collection: - SPO_Content ms.assetid: 43e52f2f-2586-451d-814d-edf43f3459ab -description: "Learn what prerequisites you'll need to configure hybrid for SharePoint Server." +description: "Learn what prerequisites you need to configure hybrid for SharePoint Server." --- # Hardware and software requirements for SharePoint hybrid @@ -32,7 +32,7 @@ This article describes the prerequisites that are required to deploy a SharePoin - An operational, on-premises Active Directory Directory Services (AD DS) domain. -- An operational SharePoint Server farm. Services must be running on the local farm - farms with federated services are not supported. For more information about setting up a farm, see [Install SharePoint Server](../install/install.md). +- An operational SharePoint Server farm. Services must be running on the local farm - farms with federated services aren't supported. For more information about setting up a farm, see [Install SharePoint Server](../install/install.md). - A [properly configured Microsoft 365 organization](configure-office-365-for-sharepoint-hybrid.md) that is provisioned with SharePoint in Microsoft 365 with one of the following subscription plans: E1 supports [Display hybrid federated search results in SharePoint Server](display-hybrid-federated-search-results-in-sharepoint-server.md) only, E3, or E4. @@ -44,6 +44,7 @@ The default STS certificate in the SharePoint farm is used by the Hybrid Configu For more information, see [Replace the STS certificate](plan-server-to-server-authentication-m365.md). ## Inbound connectivity requirements + The following hybrid solutions require inbound connectivity from Microsoft 365 to SharePoint Server: @@ -69,7 +70,7 @@ Inbound connectivity requires the following: ### Certificate requirements -This section describes the certificates you'll need to configure a inbound connectivity from Microsoft 365 to SharePoint Server. +This section describes the certificates you need to configure an inbound connectivity from Microsoft 365 to SharePoint Server. #### About the Secure Channel SSL certificate @@ -77,7 +78,7 @@ This certificate provides authentication and encryption between the reverse prox #### About the on-premises SharePoint SSL certificate -If you'll configure your primary web application to use SSL (which is the web application on the on-premises SharePoint farm that's configured for hybrid), you'll have to bind an SSL certificate to the primary web application. +If you configure your primary web application to use SSL (which is the web application on the on-premises SharePoint farm that's configured for hybrid), you have to bind an SSL certificate to the primary web application. If this web application already exists and is configured for SSL, you're ready to go. Otherwise you have to either obtain or create one for this purpose. For production environments, this certificate should be issued by a public certification authority (CA). For test and development environments, it can be a self-signed certificate. @@ -90,7 +91,7 @@ The following table lists the currently supported reverse proxy devices for Shar |**Supported reverse proxy devices**|**Configuration article**|**More information**| |:-----|:-----|:-----| |Windows Server 2012 R2 with Web Application Proxy (WA-P)
|[Configure Web Application Proxy for a hybrid environment](configure-web-application-proxy-for-a-hybrid-environment.md)
|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.
> [!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. Earlier versions of Windows don't support Web Application Proxy | -|Forefront Threat Management Gateway (TMG) 2010
|[Configure Forefront TMG for a hybrid environment](configure-forefront-tmg-for-a-hybrid-environment.md)
|Forefront TMG 2010 is a comprehensive, secure, web gateway solution that provides secure reverse proxy functionality.
Note that 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 Forefront TMG 2010](/lifecycle/products/?alpha=Forefront+Threat+Management+Gateway+2010&Filter=FilterNO). | +|Forefront Threat Management Gateway (TMG) 2010
|[Configure Forefront TMG for a hybrid environment](configure-forefront-tmg-for-a-hybrid-environment.md)
|Forefront TMG 2010 is a comprehensive, secure, web gateway solution that provides secure reverse proxy functionality.
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 Forefront TMG 2010](/lifecycle/products/?alpha=Forefront+Threat+Management+Gateway+2010&Filter=FilterNO). | |F5 BIG-IP
|[Enabling SharePoint 2013 Hybrid Search with the BIG-IP](https://community.f5.com/kb/technicalarticles/enabling-sharepoint-2013-hybrid-search-with-the-big-ip/282467)
|This is external content that's managed by F5 Networks.
| #### General reverse proxy requirements From dab53477667480e894bc20675ebdde2da1acf0bb Mon Sep 17 00:00:00 2001 From: Rui Hu <7605757+maggierui@users.noreply.github.com> Date: Mon, 2 Dec 2024 10:14:39 -0500 Subject: [PATCH 06/14] removed reference to the broken link which is ireplacable. --- ...nfigure-sharepoint-server-2013-in-a-three-tier-farm.md | 6 ++---- .../administration/performancepoint-services-overview.md | 8 ++++---- 2 files changed, 6 insertions(+), 8 deletions(-) diff --git a/SharePoint/SharePointServer/administration/configure-sharepoint-server-2013-in-a-three-tier-farm.md b/SharePoint/SharePointServer/administration/configure-sharepoint-server-2013-in-a-three-tier-farm.md index dabba531d8..2714e7b122 100644 --- a/SharePoint/SharePointServer/administration/configure-sharepoint-server-2013-in-a-three-tier-farm.md +++ b/SharePoint/SharePointServer/administration/configure-sharepoint-server-2013-in-a-three-tier-farm.md @@ -19,9 +19,7 @@ description: "Learn how to install and configure SharePoint Server 2013 on multi [!INCLUDE[appliesto-2013-xxx-xxx-xxx-xxx-md](../includes/appliesto-2013-xxx-xxx-xxx-xxx-md.md)] -This document is the [Test Lab Guide](https://go.microsoft.com/fwlink/p/?LinkId=202817) version of the procedures that are described in [Install SharePoint Server 2016 across multiple servers](../install/install-sharepoint-server-2016-across-multiple-servers.md). - -This document contains instructions [for](https://go.microsoft.com/fwlink/p/?LinkId=202817) the following: +This document contains instructions [for](https://go.microsoft.com/fwlink/p/?LinkId=202817): 1. Configuring the Base Configuration test lab. @@ -37,7 +35,7 @@ This document contains instructions [for](https://go.microsoft.com/fwlink/p/?Lin 7. Demonstrating the facilities of the default Contoso team site on WFE1. -**Watch the configure SharePoint Server 2013 in a three-tier farm test lab guide overview video** +**Watch the "Configure SharePoint Server 2013 in a three-tier farm test lab guide overview" video** > [!VIDEO https://www.microsoft.com/videoplayer/embed/47259e75-5973-4296-8d2a-e86c64efe5a2?autoplay=false] diff --git a/SharePoint/SharePointServer/administration/performancepoint-services-overview.md b/SharePoint/SharePointServer/administration/performancepoint-services-overview.md index 724efe51b2..36063beeb3 100644 --- a/SharePoint/SharePointServer/administration/performancepoint-services-overview.md +++ b/SharePoint/SharePointServer/administration/performancepoint-services-overview.md @@ -1,10 +1,10 @@ --- -ms.date: 03/19/2018 +ms.date: 12/02/2024 title: "PerformancePoint Services in SharePoint Server overview" ms.reviewer: -ms.author: serdars -author: SerdarSoysal -manager: serdars +ms.author: ruihu +author: maggierui +manager: jtremper audience: ITPro f1.keywords: - NOCSH From 38b05e291e7df57b5d66cf41963f9930ef728a5a Mon Sep 17 00:00:00 2001 From: Rui Hu <7605757+maggierui@users.noreply.github.com> Date: Mon, 2 Dec 2024 10:23:34 -0500 Subject: [PATCH 07/14] remove or replace broken links --- .../administration/performancepoint-services-overview.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/SharePoint/SharePointServer/administration/performancepoint-services-overview.md b/SharePoint/SharePointServer/administration/performancepoint-services-overview.md index 36063beeb3..857b1dcae1 100644 --- a/SharePoint/SharePointServer/administration/performancepoint-services-overview.md +++ b/SharePoint/SharePointServer/administration/performancepoint-services-overview.md @@ -29,8 +29,6 @@ To configure PerformancePoint Services in SharePoint Server, see [Configure Perf To learn about how to use PerformancePoint Services, see the following resources: - [PerformancePoint Services and Dashboard Designer compiled help file (CHM)](https://www.microsoft.com/download/details.aspx?id=55772). - -- [PerformancePoint Services Dashboard Creation SuperFlow](https://go.microsoft.com/fwlink/p/?LinkId=226357) > [!NOTE] > PerformancePoint Services has been removed from SharePoint Server Subscription Edition. We recommend to explore Microsoft [Power BI](https://powerbi.microsoft.com/) as an alternative to PerformancePoint Services. @@ -40,5 +38,5 @@ To learn about how to use PerformancePoint Services, see the following resources ## See also -[PerformancePoint Services IT Configuration SuperFlow](https://go.microsoft.com/fwlink/p/?LinkId=226358) +[Configure PerformancePoint Services](/SharePoint/administration/configure-performancepoint-services) From 088fc1f9bd2a6cbd860cfd2d694c82407a9ede80 Mon Sep 17 00:00:00 2001 From: Rui Hu <7605757+maggierui@users.noreply.github.com> Date: Mon, 2 Dec 2024 10:24:44 -0500 Subject: [PATCH 08/14] line 22 configure 2013 in 3 tirer farm --- .../configure-sharepoint-server-2013-in-a-three-tier-farm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/SharePoint/SharePointServer/administration/configure-sharepoint-server-2013-in-a-three-tier-farm.md b/SharePoint/SharePointServer/administration/configure-sharepoint-server-2013-in-a-three-tier-farm.md index 2714e7b122..b7233908ee 100644 --- a/SharePoint/SharePointServer/administration/configure-sharepoint-server-2013-in-a-three-tier-farm.md +++ b/SharePoint/SharePointServer/administration/configure-sharepoint-server-2013-in-a-three-tier-farm.md @@ -19,7 +19,7 @@ description: "Learn how to install and configure SharePoint Server 2013 on multi [!INCLUDE[appliesto-2013-xxx-xxx-xxx-xxx-md](../includes/appliesto-2013-xxx-xxx-xxx-xxx-md.md)] -This document contains instructions [for](https://go.microsoft.com/fwlink/p/?LinkId=202817): +This document contains instructions for: 1. Configuring the Base Configuration test lab. From 87fcfb4318727cdca45afb87c42b6692c829717c Mon Sep 17 00:00:00 2001 From: Rui Hu <7605757+maggierui@users.noreply.github.com> Date: Mon, 2 Dec 2024 10:29:19 -0500 Subject: [PATCH 09/14] import list to product list cross site publishing --- .../administration/configure-cross-site-publishing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/SharePoint/SharePointServer/administration/configure-cross-site-publishing.md b/SharePoint/SharePointServer/administration/configure-cross-site-publishing.md index e527fe16d7..b8bbafff26 100644 --- a/SharePoint/SharePointServer/administration/configure-cross-site-publishing.md +++ b/SharePoint/SharePointServer/administration/configure-cross-site-publishing.md @@ -104,7 +104,7 @@ For information about how to create site content types and site columns, see the - [Create a managed metadata column](https://office.microsoft.com/office365-sharepoint-online-enterprise-help/create-a-managed-metadata-column-HA102832524.aspx?CTT=1) -If you have large amounts of data in external business systems — for example, an ERP system — consider importing this data into one or more SharePoint lists. SharePoint Server does not have a solution for importing list content. However, you can develop custom import tools — for example, by using Microsoft PowerShell. For a set of example Microsoft PowerShell scripts that you can use to import list content for cross-site publishing, see [Import list content to Products list for SharePoint 2013 Preview](https://gallery.technet.microsoft.com/Import-list-content-to-f735d7fb). The example scripts import content only to a site collection that was created by using the Product Catalog Site Collection template. +If you have large amounts of data in external business systems — for example, an ERP system — consider importing this data into one or more SharePoint lists. SharePoint Server does not have a solution for importing list content. However, you can develop custom import tools — for example, by using Microsoft PowerShell. For a set of example Microsoft PowerShell scripts that you can use to import list content for cross-site publishing, see [Import list content into the Product Catalog Site Collection in SharePoint Server](/sharepoint/administration/stage-2-import-list-content-into-the-product-catalog-site-collection). The example scripts import content only to a site collection that was created by using the Product Catalog Site Collection template. ### Share a library or list as a catalog From 91839f9b9cde416f01a640f3044e3c1f96d7e117 Mon Sep 17 00:00:00 2001 From: Rui Hu <7605757+maggierui@users.noreply.github.com> Date: Mon, 2 Dec 2024 10:43:39 -0500 Subject: [PATCH 10/14] update author and date --- .../administration/configure-cross-site-publishing.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/SharePoint/SharePointServer/administration/configure-cross-site-publishing.md b/SharePoint/SharePointServer/administration/configure-cross-site-publishing.md index b8bbafff26..74670e62f7 100644 --- a/SharePoint/SharePointServer/administration/configure-cross-site-publishing.md +++ b/SharePoint/SharePointServer/administration/configure-cross-site-publishing.md @@ -1,10 +1,10 @@ --- title: "Configure cross-site publishing in SharePoint Server" ms.reviewer: -ms.author: serdars -author: SerdarSoysal -manager: serdars -ms.date: 7/18/2017 +ms.author: ruihu +author: maggierui +manager: jtremper +ms.date: 12/2/2024 audience: ITPro f1.keywords: - NOCSH From 0bf76e05217087e04475f08fa4cea3f1e15c0905 Mon Sep 17 00:00:00 2001 From: Rui Hu <7605757+maggierui@users.noreply.github.com> Date: Mon, 2 Dec 2024 10:56:50 -0500 Subject: [PATCH 11/14] demonstrate forms based claims broken links replaced --- ...emonstrate-forms-based-claims-authentication.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/SharePoint/SharePointServer/administration/demonstrate-forms-based-claims-authentication.md b/SharePoint/SharePointServer/administration/demonstrate-forms-based-claims-authentication.md index 185e399de7..9ae673a105 100644 --- a/SharePoint/SharePointServer/administration/demonstrate-forms-based-claims-authentication.md +++ b/SharePoint/SharePointServer/administration/demonstrate-forms-based-claims-authentication.md @@ -1,10 +1,10 @@ --- title: "Test Lab Guide Demonstrate forms-based claims authentication for SharePoint Server 2013" ms.reviewer: -ms.author: serdars -author: SerdarSoysal -manager: serdars -ms.date: 7/10/2017 +ms.author: ruihu +author: maggierui +manager: jtremper +ms.date: 12/02/2024 audience: ITPro f1.keywords: - NOCSH @@ -19,9 +19,9 @@ description: "Learn how to configure and demonstrate form-based authentication f [!INCLUDE[appliesto-2013-xxx-xxx-xxx-xxx-md](../includes/appliesto-2013-xxx-xxx-xxx-xxx-md.md)] -This document is the [Test Lab Guide](https://go.microsoft.com/fwlink/p/?LinkId=202817) version of the configuration described in [Configure forms-based authentication for a claims-based web application in SharePoint Server](/previous-versions/office/sharepoint-server-2010/ee806890(v=office.14)). +This document is the [Test Lab Guide](https://www.microsoft.com/download/details.aspx?id=34684) version of the configuration described in [Configure forms-based authentication for a claims-based web application in SharePoint Server](/previous-versions/office/sharepoint-server-2010/ee806890(v=office.14)). -This document contains instructions for the following: +This document contains instructions for: 1. Setting up the SharePoint Server 2013 three-tier farm test lab. @@ -42,5 +42,5 @@ This document contains instructions for the following: [Configure forms-based authentication for a claims-based web application in SharePoint Server](/previous-versions/office/sharepoint-server-2010/ee806890(v=office.14)) -[Test Lab Guides](https://go.microsoft.com/fwlink/p/?LinkId=202817) +[Test Lab Guides](https://www.microsoft.com/download/details.aspx?id=34684) From 11fa1300fa60e076eacfa246803ee65739cfe1c2 Mon Sep 17 00:00:00 2001 From: Rui Hu <7605757+maggierui@users.noreply.github.com> Date: Mon, 2 Dec 2024 11:07:54 -0500 Subject: [PATCH 12/14] viva engage multiple viva networks --- ...le-viva-engage-networks-into-sharepoint-server.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/SharePoint/SharePointServer/administration/integrate-multiple-viva-engage-networks-into-sharepoint-server.md b/SharePoint/SharePointServer/administration/integrate-multiple-viva-engage-networks-into-sharepoint-server.md index 3b7e8237de..8604ac77a4 100644 --- a/SharePoint/SharePointServer/administration/integrate-multiple-viva-engage-networks-into-sharepoint-server.md +++ b/SharePoint/SharePointServer/administration/integrate-multiple-viva-engage-networks-into-sharepoint-server.md @@ -1,10 +1,10 @@ --- title: "Integrate multiple Viva Engage networks into SharePoint Server" ms.reviewer: -ms.author: serdars -author: SerdarSoysal -manager: serdars -ms.date: 9/7/2018 +ms.author: ruihu +author: maggierui +manager: jtremper +ms.date: 12/02/2024 audience: ITPro f1.keywords: - NOCSH @@ -22,7 +22,7 @@ description: "Learn how to integrate multiple active Viva Engage networks togeth This scenario describes the prerequisites and recommended steps to integrate multiple active Viva Engage networks together with your SharePoint Server environment. > [!NOTE] -> Multiple active Viva Engage networks on one account are no longer supported after October 26, 2018. For more info, see [FAQ: Consolidating multiple Viva Engage networks](/viva/engage/configure-your-viva-engage-network/faq-consolidate-multiple-viva-engage-networks). +> Multiple active Viva Engage networks on one account are no longer supported after October 26, 2018. For more info, see [Network migration - Consolidate multiple Viva Engage networks](/viva/engage/configure-your-viva-engage-network/consolidate-multiple-networks). ## Scenario prerequisites @@ -43,7 +43,7 @@ For example, say Contoso.com is an international company with subsidiaries in lo > [!CAUTION] > When you do a network merge, the data in all subsidiary networks is permanently deleted. -For more information about administering Viva Engage, see [Viva Engage - Admin help](/viva-engage/). +For more information about administering Viva Engage, see [Viva Engage - Admin help](/viva/engage/overview). ## Step 1: Merge multiple Viva Engage networks From bacad844e3ba6775788bd29dd1e3556cc6a9b0a0 Mon Sep 17 00:00:00 2001 From: Rui Hu <7605757+maggierui@users.noreply.github.com> Date: Mon, 2 Dec 2024 11:11:09 -0500 Subject: [PATCH 13/14] acrolinx --- ...te-multiple-viva-engage-networks-into-sharepoint-server.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/SharePoint/SharePointServer/administration/integrate-multiple-viva-engage-networks-into-sharepoint-server.md b/SharePoint/SharePointServer/administration/integrate-multiple-viva-engage-networks-into-sharepoint-server.md index 8604ac77a4..32203ee462 100644 --- a/SharePoint/SharePointServer/administration/integrate-multiple-viva-engage-networks-into-sharepoint-server.md +++ b/SharePoint/SharePointServer/administration/integrate-multiple-viva-engage-networks-into-sharepoint-server.md @@ -38,7 +38,7 @@ For this scenario, we assume that: When you integrate an email domain that has an existing Viva Engage network into a larger parent network, it's called a network merge. A network merge is a valid option when an organization has multiple business units or subsidiaries that want to take advantage of the collaboration and administrative features of Viva Engage but that don't share a common email domain. -For example, say Contoso.com is an international company with subsidiaries in locations around the world. Each subsidiary has different product lines to serve the unique needs of customers in the area. Employee email addresses reflect the name of their subsidiary, like @contoso-europe.com and @contoso-asia.com. In a network merge, all subsidiary domains merge into the parent Viva Engage network, @contoso.com, and users who have subsidiary email addresses would be routed to the parent Viva Engage network when they sign in. +For example, say Contoso.com is an international company with subsidiaries in locations around the world. Each subsidiary has different product lines to serve the unique needs of customers in the area. User email addresses reflect the name of their subsidiary, like @contoso-europe.com and @contoso-asia.com. In a network merge, all subsidiary domains merge into the parent Viva Engage network, @contoso.com, and users who have subsidiary email addresses would be routed to the parent Viva Engage network when they sign in. > [!CAUTION] > When you do a network merge, the data in all subsidiary networks is permanently deleted. @@ -49,7 +49,7 @@ For more information about administering Viva Engage, see [Viva Engage - Admin h Merging Viva Engage networks merges the users, but not the data. Before doing the merge, tell users whose networks will be merged with the parent network the date, time, and effects of the merge. Additionally, share the reasons for the merge, highlight the benefits, and provide instructions for archiving private message data, notes, files, and so on. Let users know that all data in the child networks will be permanently deleted. -When you are ready to merge networks: +When you're ready to merge networks: - Follow the directions in [Combine multiple Viva Engage networks](/viva/engage/configure-your-viva-engage-network/consolidate-multiple-viva-engage-networks). From 488ae89d7a91f6c4a16ce3a7abe4e21748ddb563 Mon Sep 17 00:00:00 2001 From: Stacyrch140 <102548089+Stacyrch140@users.noreply.github.com> Date: Mon, 2 Dec 2024 11:26:26 -0500 Subject: [PATCH 14/14] pencil edit --- .../administration/configure-cross-site-publishing.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/SharePoint/SharePointServer/administration/configure-cross-site-publishing.md b/SharePoint/SharePointServer/administration/configure-cross-site-publishing.md index 74670e62f7..a4c6a347ca 100644 --- a/SharePoint/SharePointServer/administration/configure-cross-site-publishing.md +++ b/SharePoint/SharePointServer/administration/configure-cross-site-publishing.md @@ -130,7 +130,7 @@ By default, anonymous access is enabled when you share a library or list as a ca 4. On the **Catalog Settings** page, in the **Catalog Sharing** section, select the **Enable this library as a catalog** check box. -5. In the **Anonymous Access** section, if you want don't want anonymous users to view and search this content, click **Disable anonymous access**. +5. In the **Anonymous Access** section, if you don't want anonymous users to view and search this content, click **Disable anonymous access**. 6. In the **Catalog Item URL Fields** section, in the **Available fields** box, select up to five fields that uniquely identify an item in the library or list, and then click **Add**. @@ -264,4 +264,4 @@ Some actions — for example, doing search schema management to enable refiners #### Concepts -[Automatically created managed properties in SharePoint Server](../technical-reference/automatically-created-managed-properties-in-sharepoint.md) \ No newline at end of file +[Automatically created managed properties in SharePoint Server](../technical-reference/automatically-created-managed-properties-in-sharepoint.md)