502538 – Microsoft Copilot (Microsoft 365): [Copilot Extensibility] ​​[DevX] Schema enrichment & validation for custom connectors for better relevance & UX

Product:

Copilot

Platform:

Web, World tenant

Status:

In development

Change type:

Links:

Details:

Schema enrichment & validation for custom connectors for better relevance & UX (Property descriptions, content Category attributes and additional semantic labels)

Change Category:
XXXXXXX ... free basic plan only

Scope:
XXXXXXX ... free basic plan only

Release Phase:
General Availability, Preview

Created:
2025-10-17

updated:
2025-10-17

Public Preview Start Date

XXXXXXX ... free basic plan only

Docu to Check

XXXXXXX ... free basic plan only

MS workload name

XXXXXXX ... free basic plan only

summary for non-techies**

XXXXXXX ... free basic plan only

Direct effects for Operations**

Schema Enrichment Issues
Without proper preparation, the implementation of schema enrichment may lead to incorrect data mapping, resulting in users receiving irrelevant or misleading information from custom connectors.
   - roles: Data Analysts, End Users
   - references: https://techcommunity.microsoft.com/t5/microsoft-365-developer-blog/announcing-microsoft-365-copilot-integration-with-power-automate/ba-p/3701230, https://www.microsoft.com/en-us/microsoft-365/blog/2023/03/16/introducing-microsoft-365-copilot/

User Experience Degradation
If schema validation is not properly implemented, users may experience a degraded user experience due to inconsistent data presentation and functionality across custom connectors.
   - roles: Product Managers, End Users
   - references: https://www.forbes.com/sites/bernardmarr/2023/03/17/what-is-microsoft-365-copilot-and-how-can-it-help-your-business/, https://www.zdnet.com/article/microsoft-365-copilot-what-it-is-and-how-it-works/

Configutation Options**

XXXXXXX ... paid membership only

explanation for non-techies**

Microsoft is enhancing its Copilot feature within Microsoft 365 by improving how custom connectors work. Think of custom connectors like adapters that allow different software systems to communicate with each other. The goal of these improvements is to make the user experience smoother and more relevant.

Imagine you have a universal remote control that can operate your TV, stereo, and air conditioner. For the remote to work correctly with each device, it needs to understand the specific signals each device uses. Similarly, custom connectors need to understand the data and commands they are dealing with. Microsoft is enriching the "schema" of these connectors, which is like giving the remote more detailed instructions on how to interact with each device.

Schema enrichment involves adding more detailed descriptions and labels to the data that flows through these connectors. This is akin to adding labels to the buttons on your remote, so you know exactly what each one does. For example, if a connector is used to access customer data, schema enrichment might involve adding labels that describe what each piece of data represents, such as "customer name" or "purchase history."

Validation is another part of this process, ensuring that the data being exchanged is accurate and in the correct format. This is similar to checking that the batteries in your remote are working and that it's sending the right signals to your devices.

By enhancing these connectors, Microsoft aims to improve the relevance and user experience of its Copilot feature. This means that when you use Copilot to perform tasks or retrieve information, it will be more accurate and tailored to your needs, much like how a well-programmed universal remote makes controlling your devices easier and more intuitive.