QuickStart: Deploy CAEVES Copilot Connector

Prerequisites

Before starting, ensure the following are in place:

1. CAEVES SaaS Subscription is activated in the customer’s Azure Tenant.

2. CAEVES Instance is deployed, including:

   • Corresponding Storage Account with an Object Storage Container containing files to index.

   • Metadata (Process) table used by Copilot for extended search and indexing.

3. User-assigned Managed Identity is created (manual step).

4. Graph Module installed in the subscription (manual step).

5. Permissions & IAM Role Assignments configured:

   • Managed Identity must have explicit roles for the CAEVES storage account.

   • Ability to assign IAM roles at resource and subscription level.

   • Configure Graph API permissions (Graph Owner) via Azure CLI.

6. Ability to provision a new Azure Container Instance, VNET, and Subnet.

Getting Started

Step 1: Create Copilot Connector Instance via Azure Marketplace

• Navigate to Azure Marketplace → CAEVES Copilot Connector.

• Select your Subscription and Plan, then click Create.

       
• Select your desired subscription, resource group and region, click Next.

• Select the User-assigned Managed Identity created earlier, click Next.
  
• Select the Storage Account belonging to your CAEVES Instance, click Next

                      Tip: Only storage accounts in the same subscription and region will be shown.

Step 2: Configure Deployment Options

• Validate the CAEVES_WORKER_TABLE_URL and CAEVES_CONFIG_TABLE_URL is constructed correctly, click Next.

  

• Optionally, check Override Default Configuration to customize:

  • Metadata Process table

  • CAEVES Config table

    
• Configure Container Instance

• Enter Container Instance details:
        Provide your Container Instance details (VNET, Subnet, LogAnalytics Workspace)
  

• Provide your Configuration details for the CAEVES Copilot Connector

• Confirm Azure Client ID and Tenant ID placeholders.
  

  
  
  

Step 3: Validate Configuration

• Click Next and review deployment summary.

  

• Click Create to start the deployment.

  

Step 4: Monitor Deployment

• Validate the Deployment completes successfully

  

• Confirm the Azure Container Instance is Starting / Running

  

• Validate the Azure Container Instance events and confirm the image has been pulled

  

• Validate the User-Assigned Managed Identity is associated with the Azure Container Instance

  

• Confirm all “Properties” are in line with configuration parameters

  

• Confirm all “Environmental Variables” are specified correctly

  

• Validate logs

  
  

• Confirm the new CAEVES Connector has been deployed in your M365 admin portal

  

• Check logs inside LogAnalytics

  
  • • Invoke any other CURL commands to trigger a health check, status or reindex:
    • Run health check on the container:
      curl http://localhost:8000/health
      
      

    • Confirm the response indicates the connector is healthy.

    • A healthy connector shows "status": "ok" and confirms environment variables and Graph SDK connectivity are functioning.

    • Check queue statistics:
      curl http://localhost:8000/queue/stats
      

    • Displays the number of pending, claimed, completed, failed, and expired indexing jobs.

    • Ensure these numbers align with the expected workload.

    • Start indexing immediately:
      curl -X POST http://localhost:8000/run-now

    • This triggers processing of queued items.

    • Confirm the command indicates the job has started successfully.

      Connect to open a command line /bin/bash

• 

• Give Visibility to Copilot

  

• Validate the CAEVES connector is in “Ready” state, which means the connector is available as a custom connector to all users with a Copilot license.

  • Configure staged roll-out by clicking “Add Staging” to test the new connector

  

• From a user workstation, create a new agent and validate the new custom connector data source is available.

  
  
  

You have successfully deployed the CAEVES Copilot Connector .