Copilot Components
Creating a Declarative Agent involves orchestrating multiple systems that work together to index content, expose it securely, and allow Microsoft Copilot to query it using natural language. following are the core components and their roles involved in declarative agent setup.
3Sixty Admin UI
It acts as the command center for all Copilot integrations.
Role: Management interface
Used For:
-
Creating Remote Agents
-
Setting up source connectors (e.g., network drive)
-
Configuring indexing jobs
-
Downloading the Declarative Agent package
-
Managing Search Connections
OI Remote Agent
Passes the document and its metadata to OI Service
Role: Content indexing
Tech: Containerized service (in docker-compose.oi-agent.yaml)
Used For:
-
Indexing documents in the OI
OI Search Connector
Acts as the search interface between Copilot and indexed content in the vector database.
Role: Enables hybrid semantic search within the OI platform
Used For:
-
Calls the /search endpoint on the OI Service to perform vector-based or hybrid search
-
Retrieves ranked content chunks along with metadata such as title, filename, and downloadable URLs
OI Service
Internally, this handles the core RAG logic.
Role: RAG pipeline for indexing + retrieval
Used For:
-
Chunking and embedding documents
-
Communicating with vector databases
-
Exposing /search endpoint
-
Exposing /index endpoint
Vector Database
Acts as the search engine backend for the OI.
Database : OpenSearch
Role: Stores document embeddings for semantic search
Used For:
-
Storing indexed vectors
-
Serving similarity search results when Copilot asks a question
Microsoft Azure / Entra ID
This is your identity and permissions layer.
Role: Authentication and app registration
Used For:
-
Registering the Copilot Declarative App
-
Configuring Redirect URIs and Scopes
-
Assigning users and permissions
Teams Developer Portal
Enables Copilot to recognize and talk to your agent.
Role: Declarative agent packaging
Used For:
-
Registering SSO Clients
-
Connecting Entra ID with Microsoft Teams Copilot
Microsoft 365 Admin Center
Final step to deploy and expose your agent to real users.
Role: App publishing hub
Used For:
-
Uploading Declarative Agent .zip package
-
Making it available to users within your Microsoft tenant
SharePoint or Other Data Source
This is the content that Copilot will retrieve answers from.
Role: Actual content to be indexed
Used For:
-
Connecting via API Key / OAuth
-
Feeding documents to indexing jobs