Microsoft Dynamics 365 | Integration, Dataverse...

Regarding the Dataverse search

(0) Share

Report

Posted on by SP-16101533-0

After enabling Dataverse Search, certain fields are newly available and automatically selected for the entity. If we remove these fields from indexing, will there be any impact?

Categories:

Dynamics 365 general

I have the same question (0)

All responses (10)

Answers (0)

Suggested answer

11manish 365 on at

Like (0)

Report
Copy link

Link copied!
Yes, removing fields from the Dataverse Search index does have direct impacts because search relies on a separate indexed store.

Key Impacts
1. Search & Discovery Limitations
Users cannot search using data from removed fields

Example: If City is removed, searching “Seattle” won’t return results unless it exists in another indexed field

Removed fields will not appear in search results (views, filters, snippets)

2. Copilot / AI Impact

Reduced AI context

Copilot or generative AI features cannot use data from unindexed fields, leading to less accurate or incomplete responses

3. Storage & Performance Benefits

Reduced storage usage (less duplicated data in the search index)

Improves efficiency, especially when removing large text fields (e.g., descriptions, emails)

4. Technical & Capacity Benefits

Frees up column/index capacity limits in Dataverse Search

Allows indexing of more important business-critical fields

Best practice: Keep only high-value, searchable fields in the index and remove unused or noisy fields after proper validation.

Was this reply helpful? Yes No
SP-16101533-0 8 on at

Like (0)

Report
Copy link

Link copied!

“I am not referring to custom fields. After enabling Dataverse Search, some system fields and tables are created automatically. Will deleting those fields cause any impact?”

Was this reply helpful? Yes No
11manish 365 on at

Like (0)

Report
Copy link

Link copied!

Do NOT delete system-created fields/tables related to Dataverse Search

Safe approach = configure, not remove system artifacts

Was this reply helpful? Yes No
Suggested answer

ManoVerse 935 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
When you enable Dataverse Search, Microsoft does not create removable business fields. Instead, it provisions platform‑managed system components, including
1. System search metadata tables
These are internal tables used to Store search index mappings , Track table/column eligibility ,Support relevance ranking and AI enrichment

These tables are hidden from normal customization, cannot be deleted, and are owned by the Dataverse platform.

2. System-managed searchable flags and metadata
Some system fields may appear as newly available or enabled, such as:
Internal “searchable” metadata
Search-index descriptors
AI/Copilot search annotations

These are not real data fields in the traditional sense and are not user-managed schema columns. Removing or modifying them is not supported.

3. Auto-enabled system tables
Certain out of box tables (Account, Contact, Case, etc.) may automatically be:

Added to Dataverse Search , Reconfigured for unified global search

This is a configuration change, not the creation of new user tables. I read that these tables are required for first‑class search and Copilot experiences.

Dataverse Search system components are platform-owned and non-removable and microsoft does not support those activities, if you forcely remove then you can have impact like

Dataverse Search may stop working

Global search and lookup search may fail

Copilot responses may degrade or error

Environment health may be impacted

Microsoft support may require environment restore

What is safe to change there is

Remove tables from Dataverse Search indexing

Remove columns from search indexing

Change Quick Find views

Disable search on specific tables

These actions do not delete anything they only change whether data is indexed for search

Was this reply helpful? Yes No
SP-16101533-0 8 on at

Like (0)

Report
Copy link

Link copied!
I will not delete these fields. My question is: if I remove indexing for these fields, will only search stop working for them, or will there be any other impact?

For example, fields or tables with names like:

msdyn_copilot*

msdyn_ai*

msdyn_insights*

msdyn_knowledge*

msdyn_summary*

msdyn_search*

Was this reply helpful? Yes No
Suggested answer

ManoVerse 935 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

No, it’s not only search. If you remove indexing from msdyn_* fields: Data will not have any impact but search will stop finding those fields , Copilot, AI, Insights, Knowledge, and Summaries may stop working or give poor results , performance can be downgraded for views, background processes, AI jobs as these are all integrated with these managed fields. Also, Microsoft automatic updates may re‑add the indexes later or cause issues.
That’s why removing indexing is also not recommended for these system fields.

Was this reply helpful? Yes No
SP-16101533-0 8 on at

Like (0)

Report
Copy link

Link copied!

Okay, fine. In the image below, I have highlighted some fields. These fields are required to have an index, and there are many such fields. If I uncheck these fields from the index, could it cause any issues?

Was this reply helpful? Yes No
ManoVerse 935 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

these are related to Copilot/AI tables , uncheck these indexes only if you are sure you don’t use Copilot / AI / agent features in that environment, They are indexed on purpose so Copilot and AI features can read them, Copilot, AI, memory, insights, and conversation features may stop working correctly or give you unexpected behavior when you will uncheck them.

Was this reply helpful? Yes No
Suggested answer

Niki Patel 91 on at

Like (0)

Report
Copy link

Link copied!
Hi,

If you uncheck those fields from Dataverse Search indexing, it will not break any functionality or data, but it will impact search behavior.

Specifically:

Users will no longer be able to search/filter using those fields in Dataverse Search (Relevance Search).
Any Copilot, AI, or search-based features relying on those fields may return incomplete or less accurate results.
Forms, views, plugins, workflows, etc. will continue to work normally no impact there.

So, the real rule is:

Safe to remove -> Fields that are never used in search

Risky to remove -> Fields used in:

Global search

Copilot / AI scenarios

Frequently queried columns by users

For the fields you highlighted (like Agent-related, Conversation, Memory, etc.):
These are typically tied to AI/Copilot and conversation intelligence features, so removing them may degrade AI/search experience, even if nothing visibly “breaks.”

Recommendation:
Only uncheck them if you are 100% sure they are not used in search or AI scenarios. Otherwise, it’s safer to keep them indexed.

Was this reply helpful? Yes No
11manish 365 on at

Like (0)

Report
Copy link

Link copied!
For system/AI-related fields (msdyn_*):

Avoid removing unless:

You are sure they are not used by Copilot or Insights

You have tested in non-production

No system-level breaking impact
No metadata or configuration issues
Only impacts:

Search

AI/Copilot capabilities

Search relevance

Was this reply helpful? Yes No