Microsoft Copilot Setup

Connect Copilot via a Copilot Studio REST tool, custom connector, or MCP.

Connection endpoints

AiM Continuity API base URL

/api

OpenAPI schema URL

/api/openapi.json

MCP server URL

/mcp

Copy these into your Microsoft Copilot configuration. The actual API key is never shown here.

Supported connection methods

Copilot Studio ConnectorREST / OpenAPI ActionRemote MCP

Setup steps

1.In Copilot Studio, create a new custom connector from the AiM OpenAPI schema.
2.Set the API base URL and authentication to Bearer using your AiM credential.
3.If your tenant supports remote MCP, add the AiM MCP server URL as an MCP connection.
4.Publish the connector and confirm the AiM tools appear.
5.Run the connection test.

Authentication

·Authentication: Bearer token on the REST tool / connector.
·Store the key in the connector's security configuration.
·MCP connection available where supported by the tenant.

Example request

http

POST /api/continuity/intake
Authorization: Bearer YOUR_AIM_CREDENTIAL
Content-Type: application/json

{
  "provider": "microsoft_copilot",
  "conversation": { "title": "Strategy sync" },
  "organization": { "primary_project": "Website Redesign" },
  "tasks": [{ "title": "Follow up with design", "status": "OPEN" }],
  "recommendations": [{ "action": "ASSIGN_TO_PROJECT", "confidence": 0.8 }]
}

Microsoft Copilot setup prompt

Paste this into Microsoft Copilot's system / instructions so it knows how to push conversations, decisions, tasks, and ideas into AiM Continuity as PENDING REVIEW.

prompt

You are connected to AiM Continuity, my work-intelligence layer, via a
Microsoft Copilot Studio custom connector.

When I describe or reference work — a conversation, decision, task, idea, or
asset — ALWAYS submit it to AiM using POST /api/continuity/intake with:

{
  "provider": "microsoft_copilot",
  "source": "copilot_studio_connector",
  "external_conversation_id": "<current conversation id or slug>",
  "conversation": { "title": "<title>", "summary": "<summary>", "date": "<ISO date>" },
  "organization": {
    "primary_project": "<project>",
    "workstream": "<workstream>",
    "related_projects": ["<related>"],
    "brands": ["<brands>"],
    "websites": ["<urls>"]
  },
  "decisions": [{ "title": "<decision>", "status": "PROPOSED" }],
  "tasks": [{ "title": "<task>", "priority": "HIGH|MED|LOW", "status": "OPEN" }],
  "ideas": [{ "title": "<idea>" }],
  "assets": [{ "name": "<name>", "type": "url", "url": "<url>" }],
  "recommendations": [{ "action": "ASSIGN_TO_PROJECT", "reason": "<why>", "confidence": 0.8 }]
}

Before submitting, call GET /api/search?q=<topic> and GET /api/projects to
check for existing records. If a record exists, recommend UPDATE EXISTING.
All submissions land as PENDING REVIEW for a human to approve.

First connection test

After connecting, have Microsoft Copilot run these two prompts. The second must land as PENDING REVIEW — never auto-approved.

1. “Show me my active AiM Continuity projects.”

2. “Recommend adding a task called Test AiM Connection to my selected project.”

Guided setup

Prefer a guided flow? Use the connection wizard to choose a method, create a credential, test, choose permissions, and finish — in six steps.

Open the wizard

Principle

AI Recommends. Humans Decide. Microsoft Copilot may read organizational records and submit recommendations, but may never delete, approve its own work, or change configuration.