2.1 Dataverse Search, Quick Find & Relevance Indexing
Key Takeaways
- Dataverse Search (formerly Relevance Search) leverages Azure Cognitive Search / Azure AI Search behind the scenes to deliver AI-driven, relevance-ranked global search across multiple tables through a single unified search box.
- Enabling Dataverse Search is an environment-wide setting configured in the Power Platform Admin Center (PPAC) under Settings > Product > Features, which provisions an external dedicated search index.
- Tables must have 'Track changes' enabled in their table properties to participate in Dataverse Search, and their searchable attributes must be configured as 'Find Columns' within the table's Quick Find Active Records View.
- Dataverse Search supports Lucene query syntax, wildcards (*), exact phrase matching with quotation marks, fuzzy matching (~), term boosting (^), and natural language queries.
- Security trimming executes in real time: search results strictly enforce Dataverse record-level ownership, business unit privileges, sharing, and column-level security profiles so users only see authorized data.
Dataverse Search, Quick Find & Relevance Indexing
Efficient information discovery is a core requirement of enterprise business applications. In Microsoft Dataverse, users interact with multiple search mechanisms ranging from single-table lookups to cross-entity, AI-powered natural language queries. For the PL-200: Microsoft Power Platform Functional Consultant exam, you must master the architecture, administration, configuration, and behavioral differences among Dataverse Search, Categorized Search, and table-specific Quick Find Views.
Understanding how Dataverse indexes data, synchronizes records with cloud search engines, and enforces security boundaries ensures you can design high-performing search experiences without compromising compliance or data governance.
1. Search Architecture in Microsoft Dataverse
Microsoft Dataverse provides three primary search experiences, each built on distinct back-end technologies and tailored to specific operational needs.
+-----------------------------------------------------------------------------------+
| DATAVERSE SEARCH ARCHITECTURE OVERVIEW |
| |
| [Model-Driven App / Global Search Bar] |
| | |
| +---> Single Unified Query: "Contoso Redmond active order" |
| |
| +---------------------------+ +-----------------------------------+ |
| | DATAVERSE SQL ENGINE | | AZURE COGNITIVE SEARCH | |
| | (Primary Dataverse DB) | | (External Search Index) | |
| | | | | |
| | - Quick Find Views | | - Cross-table relevance ranking | |
| | - Relational queries | | - Natural language parsing | |
| | - SQL 'Like' operators | | - Fuzzy matching & faceting | |
| | - Synchronous execution | | - Asynchronous index sync | |
| +-------------+-------------+ +-----------------+-----------------+ |
| | ^ |
| | (Change Tracking via Service Bus Pipeline) | |
| +=============================================+ |
+-----------------------------------------------------------------------------------+
Comparative Analysis of Dataverse Search Modalities
| Search Feature | Technology Engine | Scope | Query Capabilities | Security & Performance |
|---|---|---|---|---|
| Dataverse Search (formerly Relevance Search) | Azure Cognitive Search (Azure AI Search) | Cross-table (all indexed tables in environment) | Natural language, fuzzy matching (~), Lucene syntax, faceting, lemmatization | Results ranked by relevance score; asynchronous sync; real-time security trimming |
| Categorized Search (Classic Multi-table) | Dataverse Relational SQL DB | Cross-table (up to 10 tables maximum) | SQL wildcard prefix matching (*term*), exact text match | Grouped by entity type; synchronous query; high SQL compute consumption |
| Quick Find (Single Table / Grid) | Dataverse Relational SQL DB | Single Table (e.g., Active Accounts) | Wildcard matching based on configured 'Find Columns' | Evaluated against database view filters and relational indexes |
[!NOTE] Historical Context: Dataverse Search was previously known as Relevance Search. In modern Model-Driven apps, Dataverse Search is the default global search experience when enabled by an administrator. Categorized search is retained for legacy compatibility.
2. Enabling & Administering Dataverse Search in PPAC
Enabling Dataverse Search is an environment-level administrative action performed in the Power Platform Admin Center (PPAC).
+-----------------------------------------------------------------------------------+
| PPAC DATAVERSE SEARCH ENABLING SEQUENCE |
| |
| [PPAC] ---> Environments ---> Select Environment ---> Settings |
| | |
| v |
| [Product] ---> Features ---> Dataverse search: Toggle [ON] |
| | |
| v |
| [Optional] ---> Enable Lucene query syntax & full search capabilities |
| | |
| v |
| [Background] ---> External Azure Cognitive Search Index Provisioned |
| (Initial synchronization starts automatically) |
+-----------------------------------------------------------------------------------+
Step-by-Step Administrative Activation
- Navigate to the Power Platform Admin Center (
admin.powerplatform.microsoft.com). - In the navigation pane, select Environments, then choose the target environment.
- Select Settings from the command bar, expand Product, and click Features.
- Under the Search section, locate Dataverse search and switch the toggle to On.
- Optionally enable advanced search capabilities (Lucene query syntax).
- Click Save at the bottom of the page.
Once enabled, Dataverse begins provisioning an external Azure Cognitive Search index and initiates an asynchronous baseline sync. Depending on database size and the number of indexed tables, initial indexing may take from several minutes to a few hours.
3. Configuring Searchable Tables & Quick Find Views
Enabling the environment-level toggle is only the first step. Functional consultants must configure which tables and which specific columns participate in search indexing.
+-----------------------------------------------------------------------------------+
| TABLE & COLUMN INDEXING CONFIGURATION FLOW |
| |
| 1. TABLE PROPERTY: |
| Enable [Track changes] on Table Definition (Prerequisite) |
| | |
| v |
| 2. SOLUTION EXPLORER / MAKER PORTAL: |
| Add Table to Search Index (Manage Search Index) |
| | |
| v |
| 3. QUICK FIND ACTIVE RECORDS VIEW: |
| +-----------------------------------+-----------------------------------+ |
| | EDIT FIND TABLE COLUMNS | EDIT VIEW COLUMNS | |
| | (Defines what attributes can be | (Defines what attributes are | |
| | searched / matched against) | displayed in search result cards)| |
| +-----------------------------------+-----------------------------------+ |
+-----------------------------------------------------------------------------------+
Prerequisite: Change Tracking
For a table's data to synchronize continuously with the external Azure Cognitive Search engine, Track changes must be enabled on the table properties:
- Open
make.powerapps.com> Solutions > Select your Solution. - Select the Table > Edit Table properties > Expand Advanced options.
- Check Track changes and save.
[!IMPORTANT] If Track changes is disabled on a table, the table cannot be added to the Dataverse Search index. Change Tracking utilizes the Dataverse asynchronous service bus to replicate row inserts, updates, and deletes to Azure Cognitive Search in near-real-time.
Quick Find View Configuration: Find Columns vs. View Columns
Dataverse Search uses the table's default Quick Find Active Records View to determine indexing behavior:
- Find Table Columns (Search Fields): These are the text, numeric, and lookup columns that Azure Cognitive Search indexes. When a user enters a query, Dataverse Search evaluates matches against these columns only. Examples include
Account Name,Account Number,Telephone, andEmail Address. - View Columns (Display Fields): These columns dictate the fields returned and rendered on search result cards and snippet previews in the model-driven user interface.
- Filter Criteria: The view's underlying filter criteria (e.g.,
Status Equals Active) dictate which records are indexed. Inactive or filtered-out rows are automatically excluded from the search index.
| Quick Find View Property | Operational Purpose | PL-200 Exam Impact |
|---|---|---|
| Find Columns | Determines searchable attributes indexed into Cognitive Search. | If users complain they cannot search accounts by Tax ID, add Tax ID to Find Columns and republish. |
| View Columns | Determines visible output fields shown in result lists. | If users complain that search results do not display the Primary Contact, add Primary Contact to View Columns. |
| Filter Criteria | Limits scope of indexed records (typically StateCode = Active). | Deactivated records are excluded from Quick Find and Dataverse search results by default. |
4. Search Syntax, Operators & Lucene Querying
Dataverse Search provides powerful query syntax, supporting plain text, natural language, and advanced Lucene operators.
+-----------------------------------------------------------------------------------+
| DATAVERSE SEARCH SYNTAX EXAMPLES |
| |
| [WILDCARD PREFIX] ---> cont* (Matches Contoso, Continental) |
| [EXACT PHRASE] ---> "northwind inc" (Matches exact phrase inside quotes) |
| [BOOLEAN OPERATOR] ---> legal AND audit (Must contain both terms) |
| [BOOLEAN NEGATION] ---> sales NOT retail(Contains sales, excludes retail) |
| [FUZZY MATCHING] ---> telecom~ (Matches telekom, telecon, etc.) |
| [GROUPING] ---> (corp OR inc) AND seattle |
+-----------------------------------------------------------------------------------+
Detailed Query Syntax Guide
| Operator / Syntax | Behavior | Practical Example | Expected Match |
|---|---|---|---|
| Simple Term | Performs word-stemming and lemmatization across indexed fields. | run | Matches running, runs, ran, and run. |
Exact Phrase (" ") | Matches exact sequence of words enclosed in double quotes. | "Fourth Coffee" | Matches only the full string Fourth Coffee, not Coffee Fourth. |
Wildcard (*) | Matches zero or more characters. Must be placed as a suffix or infix. | tele* | Matches telephone, telecom, telemetry. |
Boolean AND / + | Requires both terms to exist in the record. Must be uppercase. | Redmond AND Hardware | Matches records containing both Redmond and Hardware. |
**Boolean OR / ` | `** | Matches records containing either term. Default behavior. | Dallas OR Houston |
Boolean NOT / - | Excludes records containing the specified term. Must be uppercase. | Consulting NOT Tax | Matches records with Consulting but omits any with Tax. |
Fuzzy Search (~) | Identifies matches with character misspellings or typographic errors. | smth~ | Matches Smith, Smyth, Smooth. |
Grouping (( )) | Precedence grouping for complex multi-condition queries. | (Austin OR Dallas) AND Medical | Matches Medical records located in either Austin or Dallas. |
[!TIP] Boolean Syntax Rules: Boolean operators (
AND,OR,NOT) must be entered in ALL UPPERCASE letters. If entered in lowercase (and,or,not), Dataverse Search treats them as literal search keywords rather than logical operators.
5. Security Trimming & Search Index Governance
A critical architectural advantage of Dataverse Search over external indexing tools is its real-time security trimming.
+-----------------------------------------------------------------------------------+
| SECURITY TRIMMING PIPELINE |
| |
| [User Submits Search] ---> Azure Cognitive Search retrieves candidate rows |
| | |
| v |
| [Dataverse Security Engine] evaluates user context: |
| - User Security Roles & Depth (User, BU, Parent-Child, Org) |
| - Direct Record Sharing & Access Teams |
| - Column-Level Security (Field Security Profiles) |
| | |
| v |
| [Results Rendered] ---> User sees ONLY records they have Read privilege on. |
| Unauthorized columns appear as masked/hidden. |
+-----------------------------------------------------------------------------------+
Index Capacity & Storage Limits
- Azure Cognitive Search indexes do not consume standard Dataverse Database storage; search index costs are bundled into Power Platform capacity.
- Administrators can configure up to thousands of total searchable fields across an environment, but best practice dictates indexing only business-critical lookup and identification columns to preserve indexing throughput and query performance.
A functional consultant is configuring a model-driven app for a client. Users report that when searching globally using Dataverse Search, typing a customer's corporate Tax ID number does not return the expected Account record, even though the Tax ID field is populated on the record. What should the consultant do to resolve this issue?
An organization wants to enable Dataverse Search for a new custom table called 'Equipment Inspection' (cr_equipmentinspection). When the consultant attempts to add the table to the Search Index in the Maker Portal, the table is unavailable and greyed out. What is the root cause of this behavior?
A sales manager searches for active leads using the search term: 'telecom NOT wireless'. What results will Dataverse Search return?
A user with the 'Sales Representative' role executes a Dataverse Search query. Some matching Account records exist in business units to which the user has no access, and several matching Contact records contain secure fields governed by Column Security Profiles. How does Dataverse handle security enforcement for the search results?