Share
Report
2What I’m trying to achieve:
I want to deploy a public-facing Copilot agent that can answer technical questions accurately and authoritatively, using our approved technical PDFs stored in Canto document asset management system as the single source of truth.
Key constraints:
- The agent must be publicly accessible (no login).
- Answers must be strictly grounded in approved documents (no hallucinations).
- Canto must remain the master system for document management and approvals.
- The setup must scale and stay maintainable as documents change.
- Document and long and contain lists and tables of data.
Proposed Approach (High level)
Because public Copilot agents cannot read SharePoint or authenticated sources, the proposal is to use Azure AI Search as the public consumption layer.
Proposed architecture:
Canto (master DAM)
↓ API-based sync
Azure Blob Storage (private)
↓
Azure AI Search (PDF extraction + vector index)
↓
Public Copilot Studio agentHow it works:
- Approved technical PDFs are pulled from Canto via API (folders / metadata rules).
- PDFs are stored privately in Azure Blob Storage.
- Azure AI Search indexes and chunks the PDF content (text extraction).
- The public Copilot agent queries Azure AI Search as its only knowledge source.
- If information isn’t in the documents, the agent is instructed to say so explicitly.
- Is this the best/right architecture for a public for this use case?
I have the same question (0)
All responses (
Answers (
