+ Title: "Microsoft Syntex Advanced Management (Preview) overview"

+audience: Admin

+f1.keywords:

+- NOCSH

+ms.localizationpriority: normal

+search.appverid:

+- MET150

+description: "Learn about Microsoft Syntex Advanced Management and how you can use it in your organization."

+# Microsoft Syntex Advanced Management (Preview) overview

+<!

+>

+Microsoft Syntex Advanced Management is a Microsoft 365 add-on that provides a suite of features that can help you:

+- Manage and govern SharePoint and OneDrive

+- Enhance Microsoft 365 secure collaboration capabilities

+<!

+Articles that cover features that use Syntex Advanced Management are designated with [!INCLUDE[Advanced Management](includes/advanced-management.md)] at the top.

+>

+## Management and governance

+Data access governance reports help you discover sites that contain potentially overshared or sensitive content. You can use these reports to assess and apply appropriate security and compliance policies. For details, see [Data access governance reports](data-access-governance-reports.md).

+You can limit OneDrive access to members of a specific security group if you want to allow only certain users to have access. Even if other users outside of these security groups are licensed for OneDrive, they won't have access to their own OneDrive or any shared OneDrive content. For details, see [Limit OneDrive access by security group](limit-access.md).

+You can review and export the most recent site-related actions you made in the SharePoint admin center in the last 30 days by using the recent actions panel. Site property changes like site name, site creation and deletion, site URL, sharing settings, and storage quota are listed as actions in the panel. Note that changes made to organization-level settings, and changes made by other admins are not shown in the panel. For details, see [Review recent SharePoint site actions](recent-actions-panel.md).

+## Secure collaboration

+With Azure Active Directory authentication context, you can enforce more stringent access conditions when users access SharePoint sites that have a sensitivity label applied. Authentication contexts are used with sensitivity labels to connect Azure AD conditional access policies to labeled sites. For details, see [Manage site access based on sensitivity label](authentication-context-example.md).

+When SharePoint is enabled for sensitivity labels, you can configure a default label for document libraries. Then, any new files uploaded to that library, or existing files edited in the library will have that label applied if they don't already have a sensitivity label, or they have a sensitivity label but with lower priority. For details, see [Configure a default sensitivity label for a SharePoint document library](/microsoft-365/compliance/sensitivity-labels-sharepoint-default-label).

+You can restrict the access of a SharePoint site and its content only to the members of Microsoft 365 group connected to the site. Users who are not in the Microsoft 365 group won't have access even if they previously had site access permissions to a file. For details, see [Restricted Access Control for SharePoint sites](restricted-access-control.md).

+ Title: "Review recent SharePoint site actions"

+recommendations: true

+audience: admin

+f1.keywords:

+- NOCSH

+ms.localizationpriority: medium

+description: "Learn how to review recent actions in SharePoint admin center."

+# Review recent SharePoint site actions

+> [!NOTE]

+> This feature is currently in private preview. If you would like to participate in the preview, contact your Microsoft account manager.

+With the recent actions panel, you can make changes to SharePoint site properties and review your most recent 30 actions in the [SharePoint admin center](/sharepoint/get-started-new-admin-center).

+Changes to site properties like site name, site deletion and storage quota, show as recent actions. The panel shows the previous and current values of site properties, which can be useful when tracking changes.

+The recent actions panel only shows changes you made in the last 30 days. Changes made by other admins and organization-level changes won't show in the panel.

+You can also download a .csv file of all your changes made in the last 30 days.

+## View recent actions of a site

+1. In the SharePoint admin center, expand **Sites** and select **Active sites**.

+2. Select **Your recent actions**. The recent actions panel appears on the right and lists your most recent 30 actions made within the last 30 days.

+3. Select **Export** to download the list as a .csv file.

+4. Select **View site details** to open the site info panel. From here, you can make changes to site properties like site name, site address, hub association, and aliases.

+## Bulk site edits

+Bulk edits are listed as one action item in the recent actions panel. Select a bulk action item to see a list of sites affected by a bulk edit. Bulk edits show as separate items in the .csv file. The bulk edit column lets you quickly filter which changes were part of a bulk edit.

+HereΓÇÖs an example of how bulk edits are grouped as one action in the recent actions panel:

+You deleted 4 SharePoint sites on May 21 at 6:15 PM. The bulk edit will show as one item named Deleted 4 sites on the recent actions panel. Select the Deleted 4 sites action and the list of deleted SharePoint sites appears.

+> [!NOTE]

+> This feature is currently in private preview. If you would like to participate in the preview, contact your Microsoft account manager.

+1. On a server that hosts a content processing component in the Search service application, check whether the format of the file type is supported by a built-in format handler or a third-party filter-based format handler (iFilter). Built-in format handlers are those that SharePoint Server has by default. See [View information about file formats that can be parsed](add-or-remove-a-file-type-from-the-search-index.md#ViewInformationFileFormats).

+- `https://webAppUrl`, which is for crawling the Default Zone URL specified for the existing Web Application(s)

+- `sps3s://myWebAppUrl`, which is for crawling user profiles

+However, if you are deploying "People Search", we recommend that you create a separate content source for the start address `sps3s://myWebAppUrl` and run a crawl for that content source first. The reason for the crawl execution is that after it finishes, the search system generates a list to standardize people's names. This is so that when a person's name has different forms in one set of search results, all results for that person are displayed in a single group (known as a **result block**). For example, for the search query "Anne Weiler", all documents authored by Anne Weiler or A. Weiler or alias AnneW can be displayed in a result block that is labeled "Documents by Anne Weiler". Similarly, all documents authored by any of those identities can be displayed under the heading "Anne Weiler" in the refinement panel if "Author" is one of the categories there.

+ - Create a content source that is only for crawling user profiles (the profile store). You might give that content source a name such as People. In the new content source, in the **Start Addresses** section, type `sps3s:// myWebAppUrl`, where `myWebAppUrl` is the URL of the My Site host.

+ - Delete the start address `sps3s://myWebAppUrl` from the preconfigured content source **Local SharePoint sites**.

+| Default | Public URL | Authentication provider |

+| Default |`https://contoso` | Windows authentication: NTLM |

+| Extranet | `https://fabrikam` | Forms-based authentication |

+| Intranet | `http://fabrikam` | Windows authentication: NTLM |

+Now, say that you crawl the default zone, `https://contoso`. When users perform queries from `https://contoso/searchresults.aspx`, URLs of results from WebApp1 will all be relative to `https://contoso`, and therefore will be of the form `https://contoso/ _path_/ _result_.aspx`.

+Similarly, when queries originate from the Extranet zoneΓÇöin this case, `https://fabrikam/searchresults.aspxΓÇöresults` from WebApp1 will all be relative to `https://fabrikam`, and therefore will be of the form `https://fabrikam/ _path_/ _result_.aspx`.

+However, now instead say that you crawl a non-default zone such as the Intranet zone, `http://fabrikam`. In this case, for queries from any zone, URLs of results from WebApp1 will always be relative to the non-default zone that was crawled. That is, a query from `https://contoso/searchresults.aspx`, `https://fabrikam/searchresults.aspx`, or `http://fabrikam/searchresults.aspx` will yield search-result URLs that begin with the non-default zone that was crawled, and therefore will be of the form h`ttp://fabrikam/ _path_/ _result_.aspx`. This setting can cause unexpected or problematic behavior such as:

+- The results from WebApp1 will use HTTP, but users might be searching from the Extranet zone at `https://fabrikam/searchresults.aspx`. This search operation by the users might have security implications because the results will not use secure sockets layer (SSL) encryption.

+The ability of a user or group to perform various activities on a site is determined by the permission level that you assign. If you add or remove users individually for site permissions, or if you use a SharePoint Server group to specify site permissions and you change the membership of the group, the crawler must perform a "security-only crawl", which updates all affected items in the search index to reflect the change. Similarly, adding or updating web application policy with different users or SharePoint Server groups will trigger a crawl of all content covered by that policy. This increases crawl load and can reduce search-results freshness. Therefore, to specify site permissions, it is best to use Active Directory Domain Services (AD DS) groups, because these groups don't require the crawler to update the affected items in the search index.

+| To address this potential performance bottleneck | Implement this solution |

+> Pausing a crawl has the disadvantage that references to crawl components can remain in the `MSSCrawlComponentsState` table in the search administration database. This can cause a problem if you want to remove any crawl components (say, because you want to remove a server that hosts those components from the farm). However, when you stop a crawl, references to crawl components in the `MSSCrawlComponentsState` table are deleted. Therefore, if you want to remove crawl components, it is better to stop crawls than to pause crawls.

+To confirm that no crawls are in progress, on the `_Search_service_application_name_: Manage Content Sources` page, make sure that the value in the **Status** field for each content source is either **Idle** or **Paused**. (When a crawl is completed, or when you stop a crawl, the value in the **Status** field for the content source will change to **Idle**.)

+ For more information, see [Start, pause, resume, or stop a crawl in SharePoint Server](start-pause-resume-or-stop-a-crawl.md). When the crawl is complete, on the `_Search_service_application_name_: Manage Content Sources` page, the value in the **Status** column for the content source will be **Idle**. (To update the **Status** column, refresh the Manage Content Sources page by clicking **Refresh**.)

+If possible, keep your most important content in SharePoint, and crawl and index as much premium content as possible. If you can't crawl and index the content, consider federating results from other sources into your local search results.

+It's important to know what content to crawl and include in the search index, but it's also important to know what content **not** to crawl. For example, you don't want to crawl and index backup file shares. You should also establish routines for archiving obsolete content, deleting low-quality content and encourage users to add expiration dates to announcements.

+By organizing SharePoint content in **natural hierarchies**, you not only make it's easier for users to understand where they can find and file their content, but you also make it easier for the search system to rank the content and return search results that better match the user's intent.

+URLs and other metadata of files, such as file names, are analyzed linguistically by the search system. If you use natural language for URLs and for metadata, the search system can more easily understand what information is in the site or file and give it an appropriate ranking in the results. It's much easier for the search system (and users) to understand a URL and file name like http://sales/Europe/presentations/phones.ppt than it's to make sense of http://slseur/p_phones.ppt.

+To provide the right search results for people, it's also important that My Sites and user profile data is entered so that this information can be used as metadata by the search system.

+- If possible, keep content in different languages on different sites. If the search system can't detect the language of a particular content item, it assumes that it is in the language of the site where it's stored.

+We recommend that you only specify a small number (four-five) of authoritative pages. If you specify lots of authoritative pages, it's difficult to predict the effects on the ranking of search results.

+- **The SSA Search Administration database could be backed up independently**. The SSA Search Administration database is backed up independently using conventional SQL Server backup approaches and used on the DR farm to create an SSA using Microsoft PowerShell. This restores the search configuration but not the indexes. A full crawl is needed to populate the search indexes and complete the recovery.

+- **A full SSA backup and restore**. A full SSA backup and restore is performed using Microsoft PowerShell or using the SharePoint Central Administration website interface. This backs up the SSA databases and search indexes, which enables them to be restored on the DR farm to populate the SSA on that farm.

+The Site Administration pages in SharePoint Server provide options that support a flexible configuration of the search experience. The new configuration options for sites and site collections mean that site administrators can make search configuration changes that previously could only be made by farm or search administrators. The next screen capture shows the two locations where you can configure search optionsΓÇöunder **Site Collection Administration** or under **Search**.

+To restore a SharePoint Server Search service application, the backup must have completed successfully, and if backups are taken frequently, then the ID of the specific backup to be restored is needed. This ID can be easily obtained in several ways. The simplest is to open the **Backup and Restore History** page on the production farm where the backup was taken and enter the **Backup Directory Location**. This provides a list of all the entries in the backup and restore manifest file (psbrtoc.xml). In the following screenshot, a backup ID of {149fc816-8927-4a32-9437-6e05c2869ab7} can be easily seen.

+- [Back up and restore a search service application in SharePoint 2013 using VSS](/sharepoint/dev/general-development/how-to-back-up-and-restore-a-search-service-application-in-sharepoint-using).

+| Virtual machine A (on physical application server X) `myserver1.example.com` | Virtual machine B (on physical application server X) `myserver2.example.com` | Virtual machine C (on physical application server Y) `myserver3.example.com` | Virtual machine D (on physical application server Y) `myserver4.example.com` |

+| :- | :- | :-- | :- |

+3. Specify the new servers you want to add search components to, start a search service instance (ssi) on these servers and create references to the search service instances. In this procedure we have used the example host names `myserver< *n* >` for the servers as listed in the **Target search topology** table. At the Windows PowerShell command prompt, type the following command(s):

+By default, the Refinement Web Part is used on all search vertical pages (results.aspx, peopleresults.aspx, conversationresults.aspx, videoresults.aspx). The Web Part filters search results from a Search Results Web Part into categories to help users narrow search results to help them find what they are looking for. By changing properties in the Refinement Web Part you can do the following:

+- Change the Web Part or page where the search results should be displayedΓÇöfor example, a custom Search Results Web Part or a custom search results page.

+- Turn off query suggestions and people suggestions. For more information about query suggestions, see [Manage query suggestions in SharePoint Server](manage-query-suggestions.md).

+[How to change the text that is displayed in the Search Box Web Part in SharePoint Server 2013](/archive/blogs/tothesharepoint/how-to-change-the-text-that-is-displayed-in-the-search-box-web-part-in-sharepoint-server-2013)

+The Search Results Web Part uses a query that is specified in the Web Part to display search results. By default, the query defined in this Web Part uses the query variable {searchboxquery}. The query variable is a placeholder for a value. When a query is run, the placeholder is replaced with a value. For example, when a user types the search phrase *yellow* in the Search Box Web Part, the {searchboxquery} variable in the Search Results Web Part will resolve to search all items that contain the phrase *yellow*.

+By changing the properties and query in the Search Results Web Part you can do the following:

+ Select when the search results returned by the Search Results Web Part appear on the web page. The default option is **Async option: Issue query from the browser**. Queries will be issued from the end-users browser after the complete page is received (asynchronous). If you select the synchronous option, **Sync option: Issue query from the server**, queries are issued from the server, and the search results are included in the page response that is sent back from SharePoint (synchronous). Synchronous loading makes search vulnerable to cross-site request forgery attacks and you should **only** choose this option after carefully considering whether this vulnerability can be exploited, learn more.

+[Blog series: How to change the way search results are displayed in SharePoint Server 2013](/archive/blogs/tothesharepoint/how-to-change-the-way-search-results-are-displayed-in-sharepoint-server-2013)

+description: "Specify whether a SharePoint Server crawler will crawl a site if there's a problem with the site's Secure Sockets Layer (SSL) certificate."

+When a crawler requests a connection to crawl a site, the system generates a warning if there's a problem with the site's SSL certificate. By default, the crawler doesn't crawl the site when this happens. For security reasons, we strongly recommend that you don't change this default crawler behavior unless you have sufficient reason to do so.

+An SSL certificate problem can occur due to the following reasons:

+- The certificate isn't signed by a trusted authority.

+- The name in the certificate doesn't match the site name.

+However, if you're only crawling internal sites, you might expect SSL warnings in certain cases. For example, you might know that some site names and certificate names are mismatched for legitimate reasons, such as if the organization changed a server name or site name, or if the organization is using a single certificate for multiple sites. In such cases, it might be safe to change the default crawler behavior and thus ignore SSL certificate warnings.

+Use the following procedure to specify whether the crawler will crawl sites in the event of SSL certificate warnings. The setting applies to all content sources in all Search service applications in a farm. After you change this setting, you must recrawl all affected sites so that the appropriate content is in the search index.

+2. In Central Administration, in the Quick Launch, select **General Application Settings**.

+3. On the General Application Settings page, in the **Search** section, select **Farm Search Administration**.

+ - If you don't want the crawler to crawl a site when there's an SSL certificate warning, make sure that the **Ignore SSL certificate name warnings** check box is cleared. For security reasons, the check box is cleared by default.

+ - If you want the crawler to crawl a site even if there's an SSL certificate warning, make sure that the **Ignore SSL certificate name warnings** check box is selected.

+6. Select **OK**.

+ - In the **Request acknowledgment time (in seconds)** text box, type the number of seconds that you want the crawler to wait for a content repository to respond to a connection attempt. The default value is 60 seconds.

+Before you begin this operation, you must have in place:

+The following table shows what type of custom extraction dictionaries you can create and how the dictionary entries are matched with content in the search index, which dictionary name you should use when you deploy the dictionary and which managed property will contain the extracted entities.

+And then there are acronyms. Acronyms are especially popular in organizations, but when we search for information, this can be challenging. For example, if we want to see the Monthly Sales Report, we'll most likely search for it by using the terms *Monthly Sales Report*. But, the people who create this report might use the acronym *MSR*. So, when we search for *Monthly Sales Report*, no search results are returned.

+

+In the classic search experience of SharePoint Server, we can easily create and upload a thesaurus that contains synonyms for search phrases and acronyms. In this article, we'll use a simple example to show how to do this.

+When you search for *coffee*, the Word document is returned.

+When you search for *cup of joe*, the PowerPoint document is returned.

+For both documents to be returned when you search for either *coffee* or *cup of joe*, we can create a thesaurus.

+2. In the text editor, enter the columns of our thesaurus: *Key*, *Synonym*, and *Language*.

+4. On a new line in the text editor, enter a term or a phrase, a synonym for that term or phrase and a two letter language code. Use commas to separate the phrases, for example *Coffee,Cup of Joe,en* .

+5. Repeat step 3, but switch the order of *Key* and *Synonym*.

+To verify that your thesaurus is working the way that you want it to, search for phrases from the thesaurus. In this example scenario, two files were returned for both "coffee" and "cup of joe."

+An easy way to help users search for information in SharePoint Server is to create *query suggestions*. Query suggestions are words that appear under the search box as users type a query.

+

+ 

+

+

+[Customize query suggestions in SharePoint search](../../SharePointOnline/manage-query-suggestions.md)

+ 

+The AMSI integration functionality is designed to prevent malicious web requests from reaching SharePoint endpoints. For example, to exploit a security vulnerability in a SharePoint endpoint before the official fix for the security vulnerability has been installed.

+When an AMSI-capable antivirus or anti-malware solution is integrated with SharePoint Server, it can examine `HTTP` and `HTTPS` requests made to the server and prevent dangerous requests from being processed by SharePoint Server. Any AMSI-capable antivirus or anti-malware program that is installed on the server performs the scan as soon as the server starts to process the request.

+The purpose of AMSI integration isn't to replace existing antivirus/anti-malware defenses already installed on the server; it's to provide an additional layer of protection from malicious web requests made to SharePoint endpoints. Customers should still deploy SharePoint-compatible antivirus solutions on their servers to prevent their users from uploading or downloading files with viruses.

+4. On the **SharePoint Server Antimalware Scanning** screen, click **Activate** to turn on AMSI integration, or click **Deactivate** to turn off AMSI integration.

+[SQL Vulnerability Assessment](/sql/relational-databases/security/sql-vulnerability-assessment)

+- Ensure that you don't have too many items at the same level of hierarchy in the document libraries, because the time that is required to process items in the views increases.

+- Use the **AddToCurrentScopeOnly** method to assign Limited Access membership in a SharePoint group. The key element in this principle is to redesign the architecture so that scope membership doesn't cause Access Control List (ACL) recalculation at the parent document library and web. For additional information about scope changes, Issue 3: Use fine-grained permissions by scope structure changes (2010 only).

+When working with fine-grained permissions, it's easy to unintentionally encounter limits that prevent permissions from resolving. This section describes some of these limits and best practices on how to set them to allow permissions to resolve correctly.

+There's a built-in limit of 50,000 scopes per list or document library. After 50,000 scopes are reached addition of new scopes in a given list or document library is prohibited.

+- Don't create a system with many uniquely permissioned objects below an object that has many scopes.

+ - Administrators group on the server on which you're running the PowerShell cmdlets.

+ > If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For more information about PowerShell permissions, see [Add-SPShellAdmin](/powershell/module/sharepoint-server/Add-SPShellAdmin?view=sharepoint-ps&preserve-view=true).

+- See the following resource for information about how to upgrade databases: [Upgrade SQL Server](/sql/database-engine/install-windows/upgrade-sql-server).

+description: "Learn about the default timer jobs in SharePoint Server 2019."