Updates from: 03/18/2021 04:34:12
Service Microsoft Docs article Related commit history on GitHub Change details
SharePoint Differences Classic Modern Search https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointOnline/differences-classic-modern-search.md
You use the SharePoint admin center to manage classic search and the Microsoft 3
- Company name extraction (to be deprecated as of November 15th, 2019) - The modern search experience only shows results from the default result source. If you change the default [result source](manage-result-sources.md), both search experiences are impacted.-- Depending on the search scenario, some Microsoft Search features might not work if the [classic global Search Center URL](https://docs.microsoft.com/sharepoint/specify-default-search-center) is not set to "yourcompanyname.sharepoint.com/search/pages". Ensure that the Search Center site collection exists, that its URL is set to "yourcompanyname.sharepoint.com/search/pages", and that all users have read access to it.
+- Depending on the search scenario, some Microsoft Search features might not work if the [classic global Search Center URL](https://docs.microsoft.com/sharepoint/specify-default-search-center) is not set to point to the URL of the default classic Search Center. Depending on your tenant, this URL is "yourcompanyname.sharepoint.com/search" or "yourcompanyname.sharepoint.com/search/pages". Furthermore, ensure that the Search Center site collection exists and that all users have read access to it.
- If you temporarily [remove a search result](remove-search-results.md), the result is removed in both search experiences. - The classic search experience lets admins define **promoted results** to help users find important content, while the Microsoft Search experience uses **bookmarks** to achieve the same. When you [create a promoted result](../SharePointServer/search/manage-query-rules.md) at the organization level, users might also see it on the **All** tab on the Microsoft Search results page if they searched across the whole organization. For example, when users search from the search box on a hub site, they're only searching in the sites associated with the hub and therefore they don't see any promoted results even if they are on the **All** tab. But when users search from the SharePoint start page, they might see promoted results on the **All** tab. If you have defined both a promoted result and a bookmark for the same content (same URL), only the bookmark will appear on the **All** tab.
SharePoint Manage Search Schema https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointOnline/manage-search-schema.md
For more info about Delve, see [Office Delve for Office 365 admins](https://go.m
> Not all options are available in SharePoint in Microsoft 365. Refinable Managed Properties cannot be created. Instead use the existing Refinable Managed Properties, e.g. RefinableString00 or RefinableInt00. Searching "Refinable" will show all of the usable Refinable Managed Properties available. In SharePoint in Microsoft 365, when you create a new managed property, it will have some limitations. For example, the property can only be of type **Text** or **Yes/No**, and it can't be refinable or sortable.+
+> [!IMPORTANT]
+> Consider using only letters and digits in managed property names. Although it is possible to create custom managed properties with special characters (such as hyphens, dots, and underscores), many of those characters act as operator characters in the query syntax. For example, a hyphen means negation. Such property names have to be enclosed in double quotation marks when used in queries. Many tools and applications that create queries donΓÇÖt handle this correctly, and therefore it is better to use only letters and digits in managed property names.
If you need a property of a different type, or one that has different characteristics than what is available, follow the steps under [Create a managed property by renaming an existing one](manage-search-schema.md#__ref341260321).
SharePoint Search Limits https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointOnline/search-limits.md
The following table lists the limits for SharePoint search.
|Parsed content size <br/> |2 million characters <br/> |Boundary <br/> |Search stops parsing an item after it has parsed up to 2 million characters of content from it, including the item's attachments. The actual amount of parsed characters can be lower than this limit because search uses a maximum of 30 seconds on parsing a single item and its attachments. When search stops parsing an item, the item is marked as partially processed. Any unparsed content isn't processed and therefore isn't indexed. <br/> | |Characters processed by the word breaker <br/> |1,000,000 <br/> |Boundary <br/> |Search breaks content into individual words (tokens). The word breaker produces tokens from the first 1,000,000 characters of a single item, including the item's attachments. <br/> The actual amount of tokens can be lower than this limit because search uses a maximum of 30 seconds on word breaking. Any remaining content isn't processed. <br/> | |Indexed managed property size <br/> |512 KB per managed property that is set to either "searchable" or "queryable" <br/> |Boundary <br/> ||
-|Retrievable managed property size <br/> |16 KB per managed property <br/> |Boundary <br/> ||
+|Retrievable managed property size <br/> |64 KB per managed property <br/> |Boundary <br/> ||
|Sortable and refinable managed property size <br/> |16 KB per managed property <br/> |Boundary <br/> || |Token size <br/> |Variable - the size depends on the word breaker, and the word-breaker is language-dependent. <br/> |Boundary <br/> |Search can index tokens of any length but the word breaker that is used to produce tokens can limit the token length. Word breakers are language-aware components that break content into single words (tokens). <br/> || |Unique indexed tokens per managed property <br/> |10,000 <br/> |Boundary <br/> |This is the maximum number of unique tokens that can be added to the search index per managed property. If the limit is exceeded, the index will contain the first 10,000 tokens from the managed property and the file will be marked as partially processed by setting the IsPartiallyProcessed property to true. <br/> ||
SharePoint View Search Usage Reports https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointOnline/view-search-usage-reports.md
description: "View usage reports and search reports and see how often your users
# View search usage reports >[!NOTE]
->Beginning on January 11, 2021, we'll be retiring classic tenant-wide search usage reports in SharePoint Online. After this change, you will be able to discover site collection search usage data through the classic site collection usage reports under the **Site** > **Site Settings** > **Site collection Administration** > **Search Reports** where you can access and download usage data for the last 31 days and past 12 months. For administrators of Microsoft Search you can access the tenant usage analytics reports through the Microsoft 365 admin center under **Settings** > **Search and Intelligence** > **Insights**.
+>Starting in the fourth quarter of 2021, we'll be retiring classic tenant-wide search usage reports in SharePoint Online. After this change, you will be able to discover site collection search usage data through the classic site collection usage reports under the **Site** > **Site Settings** > **Site collection Administration** > **Search Reports** where you can access and download usage data for the last 31 days and past 12 months. For administrators of Microsoft Search you can access the tenant usage analytics reports through the Microsoft 365 admin center under **Settings** > **Search and Intelligence** > **Insights**.
If you're a SharePoint admin in your organization, you're probably asked questions about search usage, such as:
This article describes how you can use search reports in the SharePoint admin ce
[Microsoft 365 Reports in the Admin Center - SharePoint site usage](/office365/admin/activity-reports/sharepoint-site-usage) [Microsoft 365 Reports in the Admin Center - SharePoint activity](/office365/admin/activity-reports/sharepoint-activity)-
SharePoint Hardware And Software Requirements 0 https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointServer/install/hardware-and-software-requirements-0.md
Minimum requirements for a database server in a farm:
- One of the following:
+ - The 64-bit edition of SQL Server 2014 (requires May 2014 cumulative update for SharePoint Server 2013).
+
- The 64-bit edition of Microsoft SQL Server 2012. - The 64-bit edition of SQL Server 2008 R2 Service Pack 1
Certain prerequisites are installed by the prerequisite installer with specific
The prerequisite installer creates log files at %TEMP%\prerequisiteinstaller.\<date\>.\<time\>.log. You can check these log files for specific details about all changes the installer makes to the target computer. -
SharePoint Install Or Uninstall Language Packs 0 https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointServer/install/install-or-uninstall-language-packs-0.md
Last updated 7/24/2018
audience: ITPro f1.keywords: - NOCSH-+ ms.prod: sharepoint-server-itpro localization_priority: Normal
Language packs are not bundled into multilingual installation packages. You must
> [!IMPORTANT] > You cannot change an existing site, site collection, or web page from one language to another by applying different language-specific site templates. After you use a language-specific site template for a site or a site collection, the site or site collection always displays content in the language of the original site template. For example, SharePoint can render the same site in multiple languages based on the preferred language of the userΓÇÖs web browser. But for this to work, the SharePoint language pack that matches the userΓÇÖs preferred language must be installed on each server in the SharePoint farm.
-Although a site owner specifies a language ID for a site, some user interface elements such as error messages, notifications, and dialoges do not display in the language that was specified. This is because SharePoint Server relies on several supporting technologies ΓÇö for example, the Microsoft .NET Framework, Microsoft Windows Workflow Foundation, Microsoft ASP.NET, and SQL Server ΓÇö some of which are localized into only a limited number of languages. If a user interface element is generated by any of the supporting technologies that are not localized into the language that the site owner specified for the site, the user interface element appears in English. For example, if a site owner creates a site in Hebrew, and the .NET Framework component displays a notification message, the notification message will not display in Hebrew because the .NET Framework is not localized into Hebrew. This situation can occur when sites are created in any language except the following: Chinese, French, German, Italian, Japanese, Korean, and Spanish.
+Although a site owner specifies a language ID for a site, some user interface elements such as error messages, notifications, and dialogs do not display in the language that was specified. This is because SharePoint Server relies on several supporting technologies ΓÇö for example, the Microsoft .NET Framework, Microsoft Windows Workflow Foundation, Microsoft ASP.NET, and SQL Server ΓÇö some of which are localized into only a limited number of languages. If a user interface element is generated by any of the supporting technologies that are not localized into the language that the site owner specified for the site, the user interface element appears in English. For example, if a site owner creates a site in Hebrew, and the .NET Framework component displays a notification message, the notification message will not display in Hebrew because the .NET Framework is not localized into Hebrew. This situation can occur when sites are created in any language except the following: Chinese, French, German, Italian, Japanese, Korean, and Spanish.
Each language pack that you install creates a folder at %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\16\TEMPLATE\LAYOUTS\Locale_ID that contains language-specific data. In each locale_ID folder, you must have only one HTML error file that contains the error information that is used when a file cannot be found. Anytime a file cannot be found for any site in that language, this file will be used. You can specify the file to use by setting the **FileNotFoundPage()** for each web application.
Folders for the language-specific components are identified by the language tag
SharePoint Servers 2016 and 2019 support the following languages:
-|**Language**|**Language tag**|**LCID**
+|Language|Language tag|LCID|
|:--|:--|:--|:-- Arabic <br/>|ar-sa <br/> | 1025 <br/> Azerbaijani <br/> |az-latn-az <br/> |1068 <br/>
Chinese (Simplified) <br/> |zh-cn <br/> |2052 <br/>
Chinese (Traditional) <br/> |zh-tw <br/> |1028 <br/>|| Croatian <br/> |hr-hr <br/> |1050 <br/>|| Czech <br/> |cs-cz <br/> |1029 <br/>||
-Danish <br/> |da-dk <br/> |1026 <br/>||
+Danish <br/> |da-dk <br/> |1030 <br/>||
Dari <br/> |prs-af <br/> |1164 <br/>|| Dutch <br/> |nl-nl <br/> |1043 <br/>|| English <br/> |en-us <br/> |1033 <br/>||
SharePoint Default Crawled File Name Extensions And Parsed File Types https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/live/SharePoint/SharePointServer/technical-reference/default-crawled-file-name-extensions-and-parsed-file-types.md
The following table shows all the file formats that SharePoint Server has built-
||||| |:--|:--|:--|:--| |**File format** <br/> |**Format ID** <br/> |**File name extension** <br/> |**File name extension listed on the Manage File Types page by default** <br/> |
-|Email message <br/> |eml <br/> |.eml <br/> |Yes <br/> | Not supported with SharePoint in Microsoft 365.
+|Email message <br/> |eml <br/> |.eml <br/> |Yes <br/> |
|Email message <br/> |nws <br/> |.nws <br/> |Yes <br/> | |HTML <br/> |html <br/> |.ascx <br/> |Yes <br/> | |HTML <br/> |html <br/> |.asp <br/> |Yes <br/> |
The following table shows all the file formats that SharePoint Server has built-
|HTML <br/> |html <br/> |.htx <br/> |No <br/> | |HTML <br/> |html <br/> |.jhtml <br/> |No <br/> | |HTML <br/> |html <br/> |.stm <br/> |No <br/> |
-|MHTML document <br/> |mhtml <br/> |.mht <br/> |Yes <br/> | Not supported with SharePoint in Microsoft 365.
+|MHTML document <br/> |mhtml <br/> |.mht <br/> |Yes <br/> |
|MHTML document <br/> |mhtml <br/> |.mhtml <br/> |Yes <br/> | |Microsoft Excel <br/> |xlb <br/> |.xlb <br/> |No <br/> | |Microsoft Excel <br/> |xlc <br/> |.xlc <br/> |No <br/> |