Updates from: 04/19/2022 07:31:59
Service Microsoft Docs article Related commit history on GitHub Change details
SharePoint Branding Sharepoint Online Sites Modern Experience https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/branding-sharepoint-online-sites-modern-experience.md
Below is a summary of the differences between branding a site in the classic exp
| Classic experience | Modern experience | |:--|:--| |Unresponsive, OOB themes that you can customize|Responsive themes that look great on any device and can be customized to match your brand|
-|Use custom master pages and CSS that are ignored in the modern experience|Use the [SharePoint Framework](/sharepoint/dev/spfx/sharepoint-framework-overview) to add header and footer, customize theme colors, etc.|
+|Use custom master pages and CSS that are ignored in the modern experience|Use the [SharePoint Framework](/sharepoint/dev/spfx/sharepoint-framework-overview) to add headers and footers. Site templates and tenant settings offer some custom options|
## Before you begin
SharePoint Crawl Site Content https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/crawl-site-content.md
Title: "Manually request crawling and re-indexing 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 re-indexing 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 re-indexed."
+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 re-indexing of a site, a library or a list
+# Manually request crawling and reindexing of a site, a library or a list
-In SharePoint, content is automatically crawled based on a defined crawl schedule. The crawler picks up content that has changed since the last crawl and updates the index. You will want to manually request crawling and full re-indexing of a site, a document library, or a list after a schema change has occurred.
+In SharePoint, content is automatically crawled based on a defined crawl schedule. The crawler picks up content that has changed since the last crawl and updates the index. You will want to manually request crawling and full reindexing of a site, a document library, or a list after a schema change has occurred.
> [!CAUTION]
-> Re-indexing a site can cause a massive load on the search system. Don't re-index your site unless you've made changes that require all items to be re-indexed.
+> Reindexing a site can cause a massive load on the search system. Don't reindex your site unless you've made changes that require all items to be reindexed.
-## Re-index after changing managed properties
+## Reindex after changing managed properties
<a name="__top"> </a> When people search for content on your SharePoint sites, what's in your search index decides what they'll find. The search index contains information from all documents and pages on your site. The search index is built up by crawling the content on your SharePoint site. The crawler picks up content and metadata from the documents in the form of crawled properties. To get the content and metadata from the documents into the search index, the crawled properties must be mapped to managed properties. Only managed properties are kept in the index. This means that users can only search on managed properties.
-When you have changed a managed property, or when you have changed the mapping of crawled and managed properties, the site must be re-crawled before your changes will be reflected in the search index. Because your changes are made in the search schema, and not to the actual site, the crawler will not automatically re-index the site. To make sure that your changes are crawled and fully re-indexed, you must request a re-indexing of the site. The site content will be re-crawled and re-indexed so that you can start using the managed properties in queries, query rules and display templates.
+When you've changed a managed property, or when you've changed the mapping of crawled and managed properties, the site must be recrawled before your changes will be reflected in the search index. Because your changes are made in the search schema, and not to the actual site, the crawler won't automatically reindex the site. To make sure that your changes are crawled and fully reindexed, you must request a reindexing of the site. The site content will be recrawled and reindexed so that you can start using the managed properties in queries, query rules and display templates.
-You can also choose to only re-index a document library or a list. When you have changed a managed property that's used in a library or list, or changed the mapping of crawled and managed properties, you can specifically request a re-indexing of that library or list only. All of the content in that library or list is marked as changed, and the content is picked up during the next scheduled crawl and re-indexed.
+You can also choose to only reindex a document library or a list. When you've changed a managed property that's used in a library or list, or changed the mapping of crawled and managed properties, you can specifically request a reindexing of that library or list only. All of the content in that library or list is marked as changed, and the content is picked up during the next scheduled crawl and reindexed.
Learn more about search and crawled and managed properties in [Manage the search schema in SharePoint](manage-search-schema.md). See also: [Enable content on a site to be searchable](make-site-content-searchable.md)
-## Re-index a site
+## Reindex a site
<a name="__top"> </a> 1. On the site, select **Settings** ![Settings icon.](media/a47a06c3-83fb-46b2-9c52-d1bad63e3e60.png), and then select **Site settings**. If you don't see **Site settings**, select **Site information**, and then select **View all site settings**.
See also: [Enable content on a site to be searchable](make-site-content-searchab
3. In the **Reindex site** section, click **Reindex site**.
-4. A warning appears, click **Reindex site** again to confirm. The content will be re-indexed during the next scheduled crawl.
+4. A warning appears, click **Reindex site** again to confirm. The content will be reindexed during the next scheduled crawl.
-## Re-index a document library or a list
+## Reindex a document library or a list
<a name="__top"> </a>
-1. On the site, go to the list or library that you want to re-index.
+1. On the site, go to the list or library that you want to reindex.
2. In the ribbon, click the **Library** tab or the **List** tab.
See also: [Enable content on a site to be searchable](make-site-content-searchab
1. On the Settings page, under **General Settings**, choose **Advanced settings**.
-2. Scroll down to **Reindex Document Library** or **Reindex List**, and click the button. The content will be re-indexed during the next scheduled crawl.
-
-## See also
-[Get-PnPSearchCrawlLog](/powershell/module/sharepoint-pnp/get-pnpsearchcrawllog)
+2. Scroll down to **Reindex Document Library** or **Reindex List**, and click the button. The content will be reindexed during the next scheduled crawl.
+
SharePoint Information Architecture Modern Experience https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/information-architecture-modern-experience.md
Information architecture for your organization will be the most effective by col
**Departmental business owners** ΓÇô Departmental business owners represent large areas of the organization, like human resources, marketing, and engineering. Departmental business owners work with organizational intranet owners to ensure their area of the business is well-represented in global and hub navigation. Organizational intranet owners should be included early in the planning stage to ensure business and user needs are met.
-**IT Admins** ΓÇô IT admins partner with organizational intranet owners and departmental business owners to implement high level navigational structure like implementing the [start page](https://support.microsoft.com/office/discover-content-with-the-sharepoint-start-page-6b85097a-87e0-4611-a29a-dfd49b1a1220) and [hubs](./create-hub-site.md). IT admins also help implement certain governance policies around [site creation and usage](./sites-usage-guidelines.md). IT admins are involved in planning, implementing, and maintaining information architecture as the business changes and scales.
-Hub owners ΓÇô Hub owners manage hub-level content, branding, permissions, and navigational elements for hub in your organizationΓÇÖs intranet. Hub owners partner with departmental business owners and IT admins to [plan](./planning-hub-sites.md), create, and manage hubs throughout the lifecycle of your organizationΓÇÖs intranet architecture.
+**IT Admins** ΓÇô IT admins partner with organizational intranet owners and departmental business owners to implement high level navigational structure like implementing the [start page](https://support.microsoft.com/office/discover-content-with-the-sharepoint-start-page-6b85097a-87e0-4611-a29a-dfd49b1a1220) and [hubs](./create-hub-site.md). IT admins also help implement certain governance policies around [site creation and usage](./sites-usage-guidelines.md). IT admins are involved in planning, implementing, and maintaining information architecture as the business changes and scales.
+
+**Hub owners** ΓÇô Hub owners manage hub-level content, branding, permissions, and navigational elements for hubs in your organizationΓÇÖs intranet. Hub owners partner with departmental business owners and IT admins to [plan](./planning-hub-sites.md), create, and manage hubs throughout the lifecycle of your organizationΓÇÖs intranet architecture.
**Site owners** ΓÇô Site owners manage site-level content, branding, permissions, and navigation. Depending on the needs of the business and users, site owners can [associate their sites to hubs](https://support.microsoft.com/office/associate-a-sharepoint-site-with-a-hub-site-ae0009fd-af04-4d3d-917d-88edb43efc05) if the hub owner allows.
Search leverages your information architecture investments to help users find co
You can help users discover content and improve search outcomes by leveraging several features in search, including acronyms, bookmarks, Q&A, floor plans, and locations. For more info, see [Make content easy to find](/microsoftsearch/make-content-easy-to-find) and [Search experiences in SharePoint](./get-started-with-modern-search-experience.md).
-[**Next: learn about SharePoint information architecture principles**](information-architecture-principles.md)
+[**Next: learn about SharePoint information architecture principles**](information-architecture-principles.md)
SharePoint Manage Loop Components https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/manage-loop-components.md
You'll need the latest version of SharePoint PowerShell module to enable or disa
|Experience|SharePoint organization properties|Notes| |:|:|:-| |**All Microsoft 365 experiences** powered by Fluid Framework|`IsFluidEnabled` (boolean)|This core property controls all other experiences powered by Fluid Framework. Setting it to `False` will effectively disable all experiences (everything in this table) in the organization powered by Fluid Framework.|
-|Loop components in Teams|n/a|there is no setting for disabling only Loop components in Teams at this time, you must use the core property above.|
-|Microsoft Whiteboard on OneDrive|`IsWBFluidEnabled` (boolean) |only applies when `IsFluidEnabled` is `True`|
-|Microsoft OneNote collaborative Meeting notes|`IsCollabMeetingNotesEnabled` (boolean)|only applies when `IsFluidEnabled` is `True`|
+|Loop components in Teams|n/a|There is no setting for disabling only Loop components in Teams at this time, you must use the core property above.|
+|Microsoft Whiteboard on OneDrive|`IsWBFluidEnabled` (boolean) |Only applies when `IsFluidEnabled` is `True`|
+|Microsoft OneNote collaborative Meeting notes|`IsCollabMeetingNotesEnabled` (boolean)|Only applies when `IsFluidEnabled` is `True`|
To check your tenant's default file permissions 1. Go to the [Microsoft 365 admin center](https://admin.microsoft.com).
To check if the Fluid Framework is enabled, run `Get-SPOTenant` without any argu
To enable the Fluid Framework, run `Set-SPOTenant -IsFluidEnabled $true`. The change will take a short time to apply across your organization.
-The feature will be available on Teams Windows Desktop, Mac, iOS, Android. When enabled, users will see a new option for inserting Loop components in the message compose experience for these clients.
+The feature will be available on Teams Windows Desktop, Mac, iOS, Android, and web. When enabled, users will see a new option for inserting Loop components in the message compose experience for these clients.
To disable Fluid Framework, run `Set-SPOTenant -IsFluidEnabled $false`. The change will take a short time to apply across your organization.
+## eDiscovery
+
+Loop components, Whiteboard on OneDrive, and OneNote collaborative Meeting Notes are discoverable but have limited eDiscovery workflow support. Currently, these files are stored in the creatorΓÇÖs OneDrive for Business and are available for search and collection in both core and advanced eDiscovery. However, they do not render in preview and the export format for review is not consumable by existing tools. To view the exported content, upload them to any OneDrive for Business.
+
+Microsoft is working on an offline consumable export format. In the meantime, if this workaround for review flows is not sufficient for your organizationΓÇÖs needs, you can temporarily disable these experiences as outlined in the [Settings management](#settings-management) section.
+ ## Related topics [Overview of Loop components in Teams](/microsoftteams/live-components-in-teams)
SharePoint Teams Connected Sites https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/teams-connected-sites.md
These are the basic parts of Teams and SharePoint and how they relate to each ot
- **Team** ΓÇô A team is a place in Teams where you can invite others to collaborate. Each team is connected to one or more SharePoint sites. These sites are where the team's files are stored. -- **Channel** ΓÇô A channel is a location in a team where you can collaborate with others on a specific thing. A team can have multiple channels for different purposes. For example, you might have a team for marketing with different channels for different products or events. There are three types of channels in Teams: *standard* and *private*.
+- **Channel** ΓÇô A channel is a location in a team where you can collaborate with others on a specific thing. A team can have multiple channels for different purposes. For example, you might have a team for marketing with different channels for different products or events. There are three types of channels in Teams: *standard*, *private*, and *shared*.
- **Standard channel** ΓÇô A standard channel is a channel that all members of a team have access to. Each team comes with a standard channel called "General." Team owners and members can add additional standard channels.
These are the basic parts of Teams and SharePoint and how they relate to each ot
- **[Shared channels](/MicrosoftTeams/shared-channels)** ΓÇô A shared channel is a channel that you can add anyone to, even if theyΓÇÖre not a member of the team. It is used for broader collaboration with people outside the team. Each shared channel has its own SharePoint site for file storage. Only members of the shared channel can access this site. -- **Channel site** - The SharePoint site that is created when you create a private channel in a team. Only owners and members of the private channel have access to this site.
+- **Channel site** - The SharePoint site that is created when you create a private or shared channel in a team. Only owners and members of the private or shared channel have access to this site.
- **Public team** - A public team is a team that anyone in the organization can join. Public teams do not require a team owner to invite someone to the team. -- **Private team** - A private team is a team that a person can only join when invited by a team owner. Both public teams and private teams offer the same channel types - standard and private.
+- **Private team** - A private team is a team that a person can only join when invited by a team owner. Both public teams and private teams offer the same channel types - standard, private, and shared.
- **Azure AD** - Azure AD is the directory service where Microsoft 365 user accounts are stored. (You can manage these accounts from Microsoft 365 as well.) Microsoft 365 groups are also stored in Azure AD. Azure AD allows administrators to manage users and groups and to apply business rules to user accounts, such as requiring multi-factor authentication.
Teams and SharePoint are connected in the following scenarios:
- When you create a new team from scratch, a new SharePoint site is created and connected to the team. - When you create a new team from an existing Microsoft 365 group, the team is connected to the SharePoint site associated with the group. - When you add Teams to an existing SharePoint site, that site is connected to the new team.-- When you create a new private channel, a new SharePoint site is created and connected to that channel.
+- When you create a new private or shared channel, a new SharePoint site is created and connected to that channel.
-In Teams, the Files tab on each standard channel is connected to a folder in the parent siteΓÇÖs default document library. The Files tab on each private channel is connected to the default document library in the corresponding channel site. Whenever you add or update a file on the Files tab, you are accessing the SharePoint site.
+In Teams, the Files tab on each standard channel is connected to a folder in the parent siteΓÇÖs default document library. The Files tab on each private and shared channel is connected to the default document library in the corresponding channel site. Whenever you add or update a file on the Files tab, you are accessing the SharePoint site.
## Example of a team with multiple channel types
The standard channels display as folders in the parent site. The private channel
## Teams-connected sites and channel types
-Teams-connected sites are a specialized type of SharePoint site that's been optimized for a Teams connection. These include the parent site that is created when you create the team, and any channel sites that are created when you create a private channel.
+Teams-connected sites are a specialized type of SharePoint site that's been optimized for a Teams connection. These include the parent site that is created when you create the team, and any channel sites that are created when you create a private or shared channel.
This table describes how site, file, and folder sharing work for each type of channel in Teams.
SharePoint What S Deprecated Or Removed From Sharepoint Server 2019 https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointServer/what-s-new/what-s-deprecated-or-removed-from-SharePoint-Server-2019.md
The previous OneDrive sync app will remain supported, but deprecated, for the Sh
As we announced in the Microsoft 365 blog, InfoPath Services is a deprecated feature and customers are advised to explore alternatives for this feature. InfoPath Services will remain supported, but deprecated, for the SharePoint Server 2019 release.
-There will not be a new InfoPath client shipped with this release. Microsoft will ensure that the InfoPath 2013 client will work with SharePoint Server 2019 for the remainder of the client support lifecycle (2026). InfoPath 2013 client will not be supported beyond that timeframe.
+There will not be a new InfoPath client shipped with this release. Microsoft will ensure that the InfoPath 2013 client will work with SharePoint Server 2019 for the remainder of the [client support lifecycle](/lifecycle/products/infopath-2013) (2026). InfoPath 2013 clients will not be supported beyond that timeframe.
### Lists Web Service