| Component | Role | Why It’s Needed |
| Copilot / Client Application | The user-facing interface where a query or request is initiated. | This is the starting point of the user’s interaction. |
| Azure API Management (APIM) | Acts as a secure gateway for all API calls. It handles authentication, rate limiting, and request routing. | It provides a secure, unified entry point and manages the API lifecycle. |
| Azure Function | A serverless compute service that executes the business logic for the request. It orchestrates calls to other services. | It performs the specific task requested by the user, such as a search or data retrieval. |
| Vector Database / Data Source | Stores and manages the raw data and its vector embeddings, enabling semantic search to find relevant information. | It allows the Copilot to understand the user’s intent and find highly relevant data, even if it doesn’t match a keyword. |
| Other Services | External or internal systems (e.g., CRM, ERP) that provide live, real-time data or specific functionalities. | They ensure the Copilot has access to the most current information and can perform dynamic tasks beyond a simple search. |
