Quick reference for SharePoint Online search index limits. Scroll down for index freshness timelines, query construction limits, and search schema capacity by component.
| Limit | Value | Notes |
|---|---|---|
| Maximum search query length | 2,048 characters | Applies across all search surfaces (classic, modern, API) |
| Maximum results returned per query | 500 items | Regardless of the number of matching documents; use paging for programmatic access |
| Index freshness after content change | ~15 minutes (target) | Not a hard SLA; see freshness table below |
| Maximum promoted results (best bets) per site collection | 1,000 | Configured in search settings per site collection |
| Maximum result sources per site collection | 50 | Includes both tenant-level and site-level sources counting toward the site collection total |
| Maximum managed properties per tenant | 50,000 | Includes auto-created and custom-defined properties |
| Maximum search query suggestions displayed | 20 | Shown as type-ahead in the modern search box |
Values sourced from Microsoft's SharePoint Online service limits documentation. Limits are subject to change; verify at Microsoft Learn before making capacity decisions.
How Does SharePoint Online Search Keep Content Fresh?
SharePoint Online uses a continuous crawl model rather than the scheduled full-crawl approach used by SharePoint Server. When a document is saved, uploaded, or modified, a change notification is queued and the item is re-indexed in the background. In most cases the updated version is searchable within 15 minutes.
Index freshness varies by content type and operation. The table below summarises typical timelines across different scenarios.
| Content event | Typical time to reflect in search | Notes |
|---|---|---|
| New or modified document | ~15 minutes | After the save or upload operation completes |
| Newly created site collection | 1-4 hours | First crawl of a new site takes longer than incremental updates |
| Deleted document or item | ~15 minutes | Deleted items may continue to appear in search results until the next crawl removes them from the index |
| Permission change on a file or site | Up to 24 hours | Security trimming relies on a separate cache that refreshes independently of the content index |
| New managed metadata term published | ~15 minutes | After the term is published in the Term Store; unpublished terms are not indexed |
| Bulk upload (large batch) | Variable; may exceed 1 hour | High-volume operations are queued and processed progressively; partial results may appear while the batch is still indexing |
The security trimming delay is the one most likely to cause visible confusion. An admin who removes a user's access to a file may find that the file still appears in that user's search results for up to 24 hours. The user cannot open the file (access is denied at retrieval time), but it will appear in the result set until the security trim cache expires and refreshes.
Query Construction and Result Set Limits
SharePoint search supports the Keyword Query Language (KQL) for constructing queries programmatically. The limits below apply to all KQL queries, whether issued via the search box, a search web part, or the Search REST API.
| Query component | Limit | Notes |
|---|---|---|
| Total query string length | 2,048 characters | Includes the full KQL expression |
| Maximum rows in a single response | 500 | Set via the rowLimit parameter; requesting more than 500 returns 500 |
| Start row offset (for paging) | Up to the total result count | Used with the startRow parameter to page through results beyond the first 500 |
| Maximum number of refiners per query | 20 | Refiners specified in the Refiners query parameter |
| Maximum sort properties per query | 1 (with relevance as default secondary) | Only one property can be specified as the primary sort order in SharePoint search |
To retrieve more than 500 results via the REST API or PnP PowerShell, use startRow to page through the full result set in batches of up to 500. Increment startRow by 500 on each subsequent request until the returned result count is less than the batch size, which indicates the last page.
Search Schema Limits: Managed and Crawled Properties
SharePoint's search schema maps content metadata to indexed managed properties. When SharePoint discovers a new column or metadata field during a crawl, it creates a crawled property. Admins can then map crawled properties to managed properties to make them queryable and returnable in search results.
| Schema component | Limit | Notes |
|---|---|---|
| Total managed properties per tenant | 50,000 | Includes auto-created properties; SharePoint creates new managed properties when it encounters new crawled property patterns |
| Result sources per site collection | 50 | Result sources define the scope and query transformation for a search vertical |
| Managed property aliases per property | 50 | Aliases allow a managed property to be referenced by multiple names in KQL queries |
Tenants with many custom document libraries, multiple content type hubs, and varied column naming conventions can accumulate auto-created managed properties quickly. If your tenant is approaching the 50,000 property limit, audit the search schema in the SharePoint admin centre to identify and remove duplicate or unused auto-mapped properties.
Promoted Results and Content Promotion
Promoted results (also called best bets) let admins pin specific pages or documents to the top of search results for particular queries. They are configured per site collection in the Search settings panel.
At 1,000 promoted results per site collection, most tenants have ample capacity. The practical constraint is maintenance: large promoted result sets become stale quickly as URLs change, pages are renamed, or content is superseded. Review promoted results quarterly and remove entries pointing to outdated or moved content. ShareMaster's Replace Master tool can help identify documents that have been moved or renamed, flagging cases where a promoted result URL may no longer be valid.
For tenant-wide search promotion across all sites, query rules with result blocks are the appropriate mechanism. Query rules fire at the tenant, site collection, or site level and can inject additional result sets or reorder results based on query conditions. They are managed in the SharePoint admin centre under More features > Search > Manage query rules.
Frequently Asked Questions
How long does it take for a new SharePoint file to appear in search?
New and modified files in SharePoint Online typically appear in search results within 15 minutes of being saved or uploaded. Newly created sites may take 1-4 hours to be fully indexed on first crawl. These are target timelines, not guaranteed service-level commitments, and high-volume tenants or large bulk uploads may see longer delays.
What is the maximum number of search results I can retrieve from SharePoint Online?
SharePoint Online returns a maximum of 500 results per single search query. To retrieve more than 500 results programmatically, use paged queries via the SharePoint Search REST API or Microsoft Graph, incrementing the startRow offset between requests until the result set is exhausted.
How many managed properties can I create in SharePoint Online?
SharePoint Online supports a maximum of 50,000 managed properties per tenant. This total includes properties SharePoint auto-creates when it discovers new crawled properties, as well as custom managed properties defined by an admin. Most tenants never approach this limit, but large deployments with many custom content types can accumulate auto-created properties at scale.
For related reference material, see the SharePoint audit log retention reference for how long search-related activity events are kept, and the SharePoint Online general limits reference for site, library, and list capacity figures.
Try ShareMaster free for 14 days