Connect your AI tools to your capacity
Connect Microsoft 365 Copilot
Parade works as a connector in Microsoft 365 Copilot Chat, including Copilot in Teams and Outlook. Your Microsoft 365 admin sets it up once for your organization. Then each person connects with their own Parade login.
What you need
- Microsoft 365 Copilot licenses for the people who'll use it.
- A Microsoft 365 admin with the Global Administrator or AI Administrator role, and access to the Teams Developer Portal.
- Connector credentials from Parade. Ask your Parade account team, and we'll issue a client ID and secret for your organization.
- A Parade login with an email and password for each user. SSO accounts aren't supported yet.
For your Microsoft 365 admin (one time)
1. Register Parade's sign-in in the Teams Developer Portal
In the Teams Developer Portal, go to Tools → OAuth Client Registration and select + New OAuth connection. Enter:
| Field | Value |
|---|---|
| Name | Parade |
| Client ID | from Parade |
| Client secret | from Parade |
| Authorization endpoint | https://mcp.app.parade.ai/authorize |
| Token endpoint | https://mcp.app.parade.ai/token |
| Refresh endpoint | https://mcp.app.parade.ai/token |
| Scopes | parade:read |
Turn on Proof Key for Code Exchange (PKCE). It's required: sign-in fails without it. Select Save, then copy the OAuth client registration ID that appears.
2. Create the connector
In the Microsoft 365 admin center, go to Copilot → Connectors → Gallery. Under Created by your org, choose Create a new connector → Connect to MCP server → Add. Enter:
| Field | Value |
|---|---|
| Display name | Parade |
| Description | Read-only access to your company's Parade freight data: open loads, carrier quotes, and carrier bid-rate estimates for lanes. |
| Base URL | https://mcp.app.parade.ai/mcp |
| OAuth registration ID | the ID from step 1 |
| Developer name | Parade |
| Website | https://mcp.app.parade.ai/help |
| Privacy policy | https://www.iubenda.com/privacy-policy/86638042 |
| Terms of use | Ask your Parade account team |
Select Save.
3. Roll it out
Select the connector in Your connections. Use Staged rollout to try it with a small group first, then Deploy to all users. It only reaches people who are allowed by all of these:
- Agents → Settings → Agent and plugin access: Allow agents and plugins built by your organization must be on, or the connector turned on individually.
- Agents → Settings → User access.
- A Microsoft 365 Copilot license.
Changes can take up to 10 minutes to appear.
For everyone: connect your Parade account
- Open Copilot Chat at m365.cloud.microsoft/chat, or Copilot in Teams or Outlook.
- Go to Settings → Sources, find Parade, and select Connect.
- A Parade sign-in page opens. Check that it says Microsoft Copilot wants read-only access and that you'll be returned to teams.microsoft.com. Then sign in with your Parade email and password.
- Ask away, for example:
Use Parade to show our open loads picking up out of Dallas this week.
See Getting good answers for more examples.
Troubleshooting
Parade isn't listed in Sources. Ask your admin to check the rollout and the settings in step 3, and that you have a Copilot license. After a change, wait 10 minutes, then refresh Copilot.
Sign-in completes but Copilot says it couldn't connect. Usually PKCE isn't turned on, or the client ID or secret was mistyped, in the Teams Developer Portal (step 1). Your admin can fix the registration. If the secret has been lost, ask Parade for new credentials.
Disconnecting. Disconnect Parade in Settings → Sources. Your admin can disable the connector for everyone in the admin center. Parade can also switch off your organization's credentials on request.
More help: Troubleshooting & FAQ.