Messaging Extension role in the grounding process

Question

Assume the App Manifest version for a partner Teams app (and messaging extension) is upgraded to enable copilot integration.

The user interacts with copilot to ask a question. The extension queries the partner api and database.

Metadata and text/file content will be returned via the partner api. Is this information considered in the grounding process?

If this is the case, then there is less of a reason to utilize a Graph data connector. Correct?

Answer 1

The role of Messaging Extensions in the grounding process is quite significant, especially when integrated with Microsoft Copilot for Microsoft 365. When a user interacts with Copilot to ask a question, the Messaging Extension can query the partner API and database to retrieve metadata and text/file content. This information is then considered in the grounding process, which helps in providing accurate and relevant responses to the user's queries.

In essence, the Messaging Extension acts as a bridge between the user and the partner's data, ensuring that the information returned is grounded in the most relevant and up-to-date data available. This reduces the need to utilize a Graph data connector, as the Messaging Extension can directly access and return the necessary information.