Connecting Microsoft Copilot to ActivityInfo

Microsoft 365 Copilot reaches ActivityInfo through a custom federated connector. Your IT department sets up the connector once for your organization, and each member then signs in with their own ActivityInfo account.

Before you begin

• You need the Global Administrator or AI Administrator role in the Microsoft 365 admin center.
• You need access to the Teams Developer Portal.
• You need a way to send an HTTP request, such as curl or Postman, for the registration step.

Step 1: Register Copilot with ActivityInfo

Register your connector with ActivityInfo to get a client ID. You can only do this through the API. The request needs no authentication.

Copilot sends users back to a callback URL after they sign in to ActivityInfo. That URL is the same for every Copilot connector, so you can use it as it appears below.

curl -X POST https://www.activityinfo.org/oauth/register \
  -H "Content-Type: application/json" \
  -d '{
        "client_name": "My Organization Copilot",
        "redirect_uris": ["https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect"]
      }'

ActivityInfo replies with a client_id:

{
  "grant_types": [
    "authorization_code",
    "refresh_token"
  ],
  "redirect_uris": [
    "https:\/\/teams.microsoft.com\/api\/platform\/v1.0\/oAuthRedirect"
  ],
  "client_id_issued_at": 1788520644,
  "client_name": "My Organization Copilot",
  "token_endpoint_auth_method": "none",
  "client_id": "ec8xxxxxxxxxxxxxxxxx",
  "response_types": [
    "code"
  ]
}

Keep the client_id for the next step. Register once for your organization, not once per user. For more about this step, see Registering an OAuth application.

Step 2: Register the OAuth app in the Teams Developer Portal

1. Sign in to the Teams Developer Portal.
2. Select “Tools” > “OAuth Client Registration”.
3. Select “+ New OAuth connection”.
4. Enter the connection details:

5. Select “Save”.

Include activityinfo.read only. Copilot connectors are read-only: Copilot offers a user just the ActivityInfo tools that read data, and leaves out the tools that add records, change records or alter a form's design.

After you save the registration, the portal shows an “OAuth client registration ID”. Keep this ID for the next step.

Step 3: Create the connector

1. Sign in to the Microsoft 365 admin center.
2. In the left pane, select “Copilot” > “Connectors”.
3. Select the “Gallery” tab.
4. Under “Created by your org”, find the “Create a new connector” tile and select “Add”.

5. On the “Custom connector” page, under “Connect to MCP server”, select “Add”.

6. Enter the following information about your connector:

7. Select “Save”.

Step 4: Roll out the connector

A new connector appears in the “Your Connections” list. Enable it, and either add test users under “Staged rollout” or select “Deploy to all users”.

Changes to a connector take up to 15 minutes to take effect. Wait for that period to pass before you test.

Confirm the connection

Each member signs in to ActivityInfo with their own account the first time they use the connector, and approves it on the “Authorize application” screen. They see only what their own role in ActivityInfo allows.

Ask:

List my ActivityInfo databases.

Troubleshooting

Related articles

• Using ActivityInfo in Microsoft Copilot
• Registering an OAuth application
• Understanding permissions for AI assistants
• Reviewing and revoking connected assistants