| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| SharePoint | About Display Templates | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/about-display-templates.md | By default, display templates have a set of property mappings in them that were 2. In the different lists below the check box, enter the managed property to use for that field in the Item Display Template. - If you enter multiple managed property names in a list, separate the managed properties by using semicolon. When displaying content, SharePoint will use the first property that is not empty. + If you enter multiple managed property names in a list, separate the managed properties by using semicolon. When displaying content, SharePoint will use the first property that isn't empty. For more information, see: |
| SharePoint | Onedrive Site Access Restriction | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/onedrive-site-access-restriction.md | To enable site access restriction for your organization in SharePoint admin cent 1. Expand **Policies** and select **Access control**. 1. Select **Site access restriction**.-1. Select **Allow access restriction** and then select **Save**.:::image type="content" source="media/rac-spac/1-RAC-SPAC-dashboard.png" alt-text="screenshot of site access restriction in sharepoint admin center dashboard." lightbox="media/rac-spac/1-RAC-SPAC-dashboard.png"::: +1. Select **Allow access restriction** and then select **Save**. ++ :::image type="content" source="media/rac-spac/1-rac-spac-dashboard-feb-2024.png" alt-text="screenshot of site access restriction in sharepoint admin center dashboard." lightbox="media/rac-spac/1-rac-spac-dashboard-feb-2024.png"::: To enable site access restriction for your organization using PowerShell, run the following command: |
| SharePoint | Restricted Access Control | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/restricted-access-control.md | Previously updated : 01/19/2024 Last updated : 02/06/2024 Title: "Restrict SharePoint site access with Microsoft 365 groups and Entra security groups" +- ContentEngagementFY24 search.appverid: description: "Learn how to restrict access to SharePoint sites to members of a Microsoft 365 or Entra security group." Restricting site access via group membership can minimize the risk of oversharin The site access restriction policy requires [Microsoft Syntex - SharePoint Advanced Management](advanced-management.md). -## Enable site access restriction for your organization +## Enable site-level access restriction for your organization You must enable site-level access restriction for your organization before you can configure it for individual sites. To enable site-level access restriction for your organization in SharePoint admi 1. Expand **Policies** and select **Access control**. 2. Select **Site-level access restriction**.-3. Select **Allow access restriction** and then select **Save**.:::image type="content" source="media/rac-spac/restricted-access-control-site-level-restriction-page.png" alt-text="screenshot of site access restriction in sharepoint admin center dashboard." lightbox="media/rac-spac/restricted-access-control-site-level-restriction-page.png"::: +3. Select **Allow access restriction** and then select **Save**. ++ :::image type="content" source="media/rac-spac/1-RAC-SPAC-dashboard-feb-2024.png" alt-text="screenshot of site access restriction in sharepoint admin center dashboard." lightbox="media/rac-spac/1-RAC-SPAC-dashboard-feb-2024.png"::: To enable site-level access restriction for your organization using PowerShell, run the following command: Set-SPOSite -Identity <siteurl> -RestrictedAccessControl $false ## Restrict site access to non-group connected sites -You can restrict access to non-group connected sites by specifying [Entra security groups](/azure/active-directory/fundamentals/how-to-manage-groups) or Microsoft 365 groups that contain the people who should be allowed access to the site. You can configure up to 10 Entra security groups or Microsoft 365 groups. Once the policy is applied, users in the specified security group who have site access permissions are granted access to the site and its content. You can use [dynamic security groups](/azure/active-directory/enterprise-users/groups-create-rule) if you want to base group membership on user properties. +You can restrict access to non-group connected sites by specifying [Entra security groups](/azure/active-directory/fundamentals/how-to-manage-groups) or Microsoft 365 groups that contain the people who should be allowed access to the site. You can configure up to 10 Entra security groups or Microsoft 365 groups. Once the policy is applied, users in the specified group who have site access permissions are granted access to the site and its content. You can use [dynamic security groups](/azure/active-directory/enterprise-users/groups-create-rule) if you want to base group membership on user properties. To manage site access to a non-group connected site: |
| SharePoint | Accessibility Guidelines | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/accessibility-guidelines.md | Users who don't use a mouse can use a keyboard to navigate the user interface an ## SharePoint Server conformance statement -The following SharePoint Server 2016, SharePoint Server 2019, and SharePoint Server Subscription Edition conformance statement, VPAT, and EN 301 549 reports are available at [Microsoft Accessibility Conformance Reports](https://cloudblogs.microsoft.com/industry-blog/government/2018/09/11/accessibility-conformance-reports/) You can download the WCAG Conformance Statement and the Section 508 VPAT for SharePoint Server 2016, click the provided link and search for SharePoint Server 2016, SharePoint Server 2019, or SharePoint Server Subscription Edition. +The following SharePoint Server 2016, SharePoint Server 2019, and SharePoint Server Subscription Edition conformance statement, VPAT, and EN 301 549 reports are available at [Microsoft Accessibility Conformance Reports](https://cloudblogs.microsoft.com/industry-blog/government/2018/09/11/accessibility-conformance-reports/) You can download the WCAG Conformance Statement and the Section 508 VPAT for SharePoint Server 2016, select the provided link and search for SharePoint Server 2016, SharePoint Server 2019, or SharePoint Server Subscription Edition. ## Accessibility features in SharePoint Server |
| SharePoint | Add A Content Database | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/administration/add-a-content-database.md | You can use the procedures that are described in this article to create a new co 6. On the **Add Content Database** page: - - Specify a web application for the new database. + - Specify a web application for the new database. - - Specify a database server to host the new database. + - Specify a database server to host the new database. - - Specify the authentication method that the new database will use and supply an account name and password, if they are necessary. + - Specify the authentication method that the new database will use and supply an account name and password, if they're necessary. - > [!IMPORTANT] - > The account name and password must already exist as a SQL Server login. + > [!IMPORTANT] + > The account name and password must already exist as a SQL Server login. - - Specify the name of the failover database server, if one exists. + - Specify the name of the failover database server, if one exists. - - Specify the number of top-level sites that can be created before a warning is issued. By default, this is 2,000. + - Specify the number of top-level sites that can be created before a warning is issued. By default, this is 2,000. - - Specify the total number of top-level sites that can be created in the database. By default, this is 5,000. + - Specify the total number of top-level sites that can be created in the database. By default, this is 5,000. 7. Click **OK**. You can use the procedures that are described in this article to create a new co 1. Verify that you have the following memberships: - - **securityadmin** fixed server role on the SQL Server instance. + - **securityadmin** fixed server role on the SQL Server instance. - - **db_owner** fixed database role on all databases that are to be updated. + - **db_owner** fixed database role on all databases that are to be updated. - - Administrators group on the server on which you are running the PowerShell cmdlets. + - Administrators group on the server on which you are running the PowerShell cmdlets. - An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets. + An administrator can use the **Add-SPShellAdmin** cmdlet to grant permissions to use SharePoint Server cmdlets. - > [!NOTE] - > If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin?view=sharepoint-ps&preserve-view=true). + > [!NOTE] + > If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin?view=sharepoint-ps&preserve-view=true). 2. Open **SharePoint Management Shell**. 3. At the PowerShell command prompt, type the following command: - ```PowerShell - New-SPContentDatabase -Name <ContentDbName> -WebApplication <WebApplicationName> - ``` + ```PowerShell + New-SPContentDatabase -Name <ContentDbName> -WebApplication <WebApplicationName> + ``` -Where: + Where: - - _\<ContentDbName\>_ is the name of the content database to create. + - _\<ContentDbName\>_ is the name of the content database to create. - - _\<WebApplicationName\>_ is the name of the web application to which the new database is attached. + - _\<WebApplicationName\>_ is the name of the web application to which the new database is attached. -For more information, see [New-SPContentDatabase](/powershell/module/sharepoint-server/New-SPContentDatabase?view=sharepoint-ps&preserve-view=true). + For more information, see [New-SPContentDatabase](/powershell/module/sharepoint-server/New-SPContentDatabase?view=sharepoint-ps&preserve-view=true). > [!NOTE] > To attach an existing content database to a web application, use the Microsoft PowerShell cmdlet **Mount-SPContentDatabase**. For more information, see [Mount-SPContentDatabase](/powershell/module/sharepoint-server/Mount-SPContentDatabase?view=sharepoint-ps&preserve-view=true). |