How to connect an existing Azure AI Search index to a Microsoft 365 Copilot agent when the connector is blocked by policy?

Question

How to connect an existing Azure AI Search index to a Microsoft 365 Copilot agent when the connector is blocked by policy?

Mohamed, Rihan 60

Hello,

I'm exploring how to make content from an existing Azure AI Search index available through a dedicated agent in Microsoft 365 Copilot Chat.

I have an existing Azure AI Search index named book-index, containing approximately 50,162 documents. I verified that the index is working using Azure AI Search Search Explorer.

I created a dedicated agent in Microsoft Copilot Studio and explored the available Knowledge and Tools options.

During my investigation, I found that:

Azure AI Search is not available as a direct Knowledge source in the current environment.
Azure AI Search is listed under Tools → Connectors, but it is marked "Blocked by policy" and cannot be added to the agent.

My questions are:

What is the recommended Microsoft-supported approach to connect an existing Azure AI Search index to a Microsoft 365 Copilot agent?
Can an MCP server, a custom connector, or another supported integration be used to retrieve content from the existing index?
If the Azure AI Search connector is blocked by a DLP policy, what permissions or policy changes are required to enable the integration?
How can we ensure that responses are restricted to the indexed content, with source citations and appropriate user-level access controls?

The objective is to allow users to access existing indexed content directly through Microsoft 365 Copilot Chat while maintaining governance, security, and source attribution.

Any guidance, documentation, or reference architecture would be appreciated.

Thank you.

0 comments

1 answer

Your answer

Answer 1

Based on the investigation, Azure AI Search is not currently available as a native Knowledge source for Microsoft 365 Copilot agents in the affected environment. Although the Azure AI Search connector is visible under Tools → Connectors, it is currently marked as "Blocked by policy", indicating that a Power Platform DLP policy is preventing its use.

For an existing Azure AI Search index, the recommended approach is typically to expose the indexed content through a supported integration layer, such as:

A Custom Connector that queries the Azure AI Search index via API.
An MCP Server that retrieves relevant content from the index and returns grounded results to the Copilot agent.
Where applicable, storing content in Microsoft 365 repositories (e.g., SharePoint or OneDrive) and leveraging native Microsoft 365 knowledge sources, which provide built-in security trimming and citations.

To enable direct use of the Azure AI Search connector, the tenant's Power Platform administrator will need to review the applicable DLP policies and determine whether the connector can be moved from the blocked category to an allowed business connector category.

From a governance and security perspective, the recommended design is to:

Use the Azure AI Search index as the retrieval source.
Restrict agent responses to retrieved/indexed content only.
Return document metadata to support source citations and attribution.
Enforce user-level access controls through Microsoft Entra ID authentication and security trimming so that users only receive content they are authorized to access.

In summary, the existing Azure AI Search index can be surfaced through a Microsoft 365 Copilot agent, but this is generally achieved through a supported retrieval layer (such as a Custom Connector or MCP Server). The current blocker appears to be the environment's DLP policy, which would need to be reviewed by the administrator before the Azure AI Search connector can be used directly.