SharePoint Search Administration

SharePoint Search is the engine that indexes content from SharePoint sites, OneDrive, and external sources, and returns relevant results to users. It is built on the SharePoint Search service application, which consists of a crawl component, content processing, index, query processing, and analytics. The search system is essential for users to find documents, list items, pages, and people across the organization. Without proper administration, search can become slow, incomplete, or return irrelevant results.

The search process follows a pipeline:

For SharePoint Online, administration is via SharePoint Admin Center or PowerShell. Key PowerShell cmdlets:

# Get search configuration
Get-SPEnterpriseSearchServiceApplication
Get-SPEnterpriseSearchCrawlContentSource
Get-SPEnterpriseSearchCrawlRule
Get-SPEnterpriseSearchMetadataManagedProperty
Get-SPEnterpriseSearchQueryRule
Get-SPEnterpriseSearchResultSource

# Create a new content source
New-SPEnterpriseSearchCrawlContentSource -Name "My Content Source" -Type SharePoint -StartAddress "https://contoso.sharepoint.com/sites/mysite" -SearchApplication $ssa

# Start a full crawl
Start-SPEnterpriseSearchCrawlContentSource -Identity "My Content Source" -FullCrawl

# Create a managed property
New-SPEnterpriseSearchMetadataManagedProperty -Name "CustomProperty" -Type Text -SearchApplication $ssa

# Map crawled property to managed property
New-SPEnterpriseSearchMetadataMapping -SearchApplication $ssa -ManagedProperty "CustomProperty" -CrawledProperty "MyCrawledProperty"

# Create a query rule
New-SPEnterpriseSearchQueryRule -SearchApplication $ssa -QueryRuleName "Promote Sales" -QueryCondition "sales" -IsAdvanced $true -RuleType 1 -Context "SPSite" -ContextValue "https://contoso.sharepoint.com/sites/sales"

For verification, use:

# Check crawl status
Get-SPEnterpriseSearchCrawlContentSource | Select Name, CrawlStatus, CrawlCompletedTime

# Test search query
$query = New-SPEnterpriseSearchQuery -SearchApplication $ssa -QueryText "test"
$result = $query.Execute()
$result | Select Title, Path, Rank

Security trimming is the process of filtering search results based on the user's permissions. SharePoint Search achieves this by storing the ACL (access control list) for each item in the index. When a query is executed, the search engine retrieves the ACL of the user and compares it to the ACL of each candidate result. Only items where the user has at least read access are returned. This happens at query time, not crawl time, so changes to permissions are reflected immediately without recrawling. However, if an item's ACL changes and the item is not recrawled, the old ACL remains in the index, which could cause over-trimming (user doesn't see item they should) or under-trimming (user sees item they shouldn't). To avoid under-trimming, SharePoint Online uses a security update mechanism that updates ACLs in the index without a full recrawl. For on-premises, incremental crawls pick up ACL changes.

Managed properties are the backbone of search customization. Each managed property has attributes: - Type: Text, Integer, Decimal, DateTime, YesNo, etc. - Searchable: The property's value is included in full-text search. - Retrievable: The property's value can be returned in search results. - Sortable: Results can be sorted by this property. - Refinable: Users can filter results by this property using refiners. - Multivalued: The property can have multiple values (e.g., multiple authors). - Queryable: The property can be used in search queries (e.g., author:"John").

Crawled properties are automatically discovered during crawl. They have names like ows_MyField for SharePoint list columns. You map crawled properties to managed properties. Up to 20 crawled properties can be mapped to one managed property. The mapping can include a custom processing instruction (e.g., combine values, extract substring).

Query rules allow you to promote specific results when certain conditions are met. Conditions can be based on:

Actions include: - Promote results: Add specific URLs to the top of results. - Add result block: Display a block of results from a predefined query (e.g., show all documents from the Sales library). - Change ranking: Boost or demote results based on a property. - Change query: Modify the query (e.g., add a filter).

Query rules are evaluated in order of priority (0-100, lower number = higher priority). They can be active or inactive. You can also set a start and end date for time-bound promotions.

Result sources define the scope of a search query. They can point to:

You can create custom result sources with specific provider URLs or query transforms. For example, a result source that searches only the Sales site collection:

{?{searchTerms} site:https://contoso.sharepoint.com/sites/sales}

Search verticals are tabs on the search results page that limit results to a specific result source. Out-of-the-box verticals: All, People, Conversations, Videos. You can create custom verticals (e.g., Contracts, Policies). Each vertical is associated with a result source and can have its own display template.

A global law firm with 10,000 users across 50 offices uses SharePoint Online for document management. Each client matter is a separate site with unique permissions. The firm needs search to return only documents the user has access to (security trimming). They configure continuous crawl every 5 minutes to keep index fresh. However, they notice that when a new associate joins a matter, it takes up to 5 minutes for documents to appear in search. To reduce this, they set continuous crawl to 1 minute, but Microsoft throttles at 1 minute minimum. They also create a query rule that promotes the most recent documents in the user's primary practice area. The search administrator regularly reviews crawl logs for access denied errors, which often indicate permission misconfigurations. They also use managed properties like 'ClientMatterID' to allow users to refine by client.

A university with 50,000 students and staff runs SharePoint on-premises for administrative systems and SharePoint Online for student collaboration. They need a unified search experience. They configure a cloud hybrid search: on-premises content is crawled by the cloud search service application (CSSA) and indexed in Office 365. The on-premises farm has 10 million items, so they create 2 index partitions with 2 replicas each. They set incremental crawl every 15 minutes and full crawl weekly. They create a result source in SharePoint Online that queries the on-premises index via the cloud hybrid search endpoint. They also create query rules that boost results from the online environment for current student content. A common issue is that on-premises content may not appear if the hybrid connection fails; they monitor the hybrid search topology using PowerShell.

A retail company with 5,000 employees uses SharePoint Online for product catalogs, sales playbooks, and training materials. They want a search vertical for 'Products' that only searches the product catalog site. They create a result source with query transform: {?{searchTerms} site:https://tenant.sharepoint.com/sites/products}. Then they create a search vertical in the Search Center site and assign the result source. They also create a managed property 'ProductCategory' and map it to a crawled property from a list column. Users can refine by category. To ensure new products appear quickly, they configure continuous crawl for the product site. They also set up a query rule that promotes top-selling products when users search for a category. The search team regularly reviews analytics to see which queries return zero results and adds synonyms for common misspellings.