Agave AI in Copilot

Connect Agave to Microsoft 365 Copilot to ask questions about your Project Management and ERP data directly in Copilot. Your company sets up the connector once, then each person connects their own Agave account.

Use Think deeper for better results

For better results with Agave, open the response-mode dropdown next to Work IQ in Copilot and select Think deeper before sending your question.

For even more advanced results, switch to Opus 5.5 from the Anthropic model submenu.

Select Think deeper before asking Copilot to work with your Agave data.

Select Think deeper before asking Copilot to work with your Agave data.

For more advanced results, select Opus 5.5 from the Anthropic model submenu.

For more advanced results, select Opus 5.5 from the Anthropic model submenu.

Who sets this up?

Part	Who completes it	What you'll have when you're done
1. Generate credentials in Agave	An Agave admin	An Agave client ID and client secret
2. Register OAuth in Microsoft	Your Microsoft admin	A Microsoft OAuth client registration ID
3. Enable the company connector	Your Microsoft admin	An Agave connector available to your company
4. Connect your own account	Each user, including admins who want to use Copilot	Copilot connected with that user's Agave permissions

Already set up for your company? Skip to Connect as an end user.

The written steps include every value you need. Screenshots appear below each step; select an image to enlarge it in a viewer without leaving the guide. Close the viewer or press Escape to return to your place. The examples use a demo account; generate your own credentials rather than copying values from the images.

Before you start

• Agave: an admin who can open AI Analytics settings and generate the credentials. Each person who will use the connector also needs their own Agave account with access to the relevant data.
• Microsoft administration: an AI Administrator or Global Administrator with access to the Microsoft 365 admin center and Teams Developer Portal. See Microsoft's custom connector prerequisites.
• Copilot access: a work or school account with a license eligible for federated connectors. Microsoft lists a Microsoft 365 Copilot add-on license or Microsoft 365 E7; check its current licensing requirements for your users.

Use the same Microsoft 365 organization in Teams Developer Portal, the admin center, and Copilot. This applies whether your company uses a custom email domain or an onmicrosoft.com domain. The Agave URLs below stay the same.

Microsoft sign-in and Agave sign-in are separate

Choose OAuth 2.0 for this setup, even if your company uses Microsoft accounts or Microsoft SSO. Users authorize access through Agave and use their organization's usual Agave sign-in process. A Microsoft email domain alone does not make Microsoft Entra SSO the correct connector authentication option.

1. Generate credentials in Agave

Who: an Agave admin.

1. Sign in to the Agave admin portal.
2. Open AI Analytics → Settings → Report Customization and scroll to MCP.
3. Review Configurations shown in MCP and save any changes. This setting controls which configuration types are available through the connector; see MCP settings.
4. On the Microsoft Copilot card, select Set up Copilot.
5. Select Generate OAuth client.
6. Copy both the Client ID and Client secret. Keep them available for your Microsoft admin to enter in the next part.

Save the client secret before closing

The secret is shown only once. Save it securely before selecting Done. Individual users do not need this secret; they connect with their own Agave accounts in Part 4.

Open the Microsoft Copilot setup card in Agave's MCP settings.

Open the Microsoft Copilot setup card in Agave's MCP settings.

Generate the OAuth client.

Generate the OAuth client.

Copy your client ID and the one-time client secret.

Copy your client ID and the one-time client secret.

Agave creates the client with Microsoft's callback URL already configured: https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect. You do not need to register that callback separately.

2. Register OAuth in Microsoft

Who: your Microsoft admin, using the credentials from Part 1.

This saves Agave's credentials in Microsoft and produces a registration ID for the connector. Microsoft's OAuth configuration documentation explains the portal fields and organization/app restrictions.

Open a new registration

1. Open Teams Developer Portal.
2. Select Tools → OAuth client registration.
3. Select New OAuth client registration.

Choose OAuth client registration under Tools.

Choose OAuth client registration under Tools.

Start a new registration.

Start a new registration.

Enter the registration settings

Use these values, replacing only the client ID and secret with the pair generated for your company:

Field	Value
Registration name	Agave
Base URL	https://app.agaveapi.com
Restrict usage by organization	My organization only
Restrict usage by Teams app	Any Teams app (for testing and store validation only), as shown for this custom connector setup
Client ID	The Client ID from Agave, generated in Part 1
Client secret	The Client secret from Agave, generated in Part 1
Authorization endpoint	https://app.agaveapi.com/oauth/authorize
Token endpoint	https://app.agaveapi.com/oauth/token
Refresh endpoint	https://app.agaveapi.com/oauth/token
Scope	mcp:use
Enable Proof Key for Code Exchange (PKCE)	On
Client password authentication method	Request body parameters (default)

The Base URL here is the Agave host. You'll enter the full /mcp/erp-sync endpoint when creating the connector in Part 3. Keep My organization only selected for a connector used within your company.

Enter the app settings and Agave credentials.

Enter the app settings and Agave credentials.

Enter the endpoints and scope, enable PKCE, and use request body parameters.

Enter the endpoints and scope, enable PKCE, and use request body parameters.

Save and copy Microsoft's registration ID

Select Save, then copy the OAuth client registration ID displayed at the top of the page.

Two different IDs

The Agave client ID identifies the client you generated in Agave. The Microsoft OAuth client registration ID identifies the configuration you just saved in Teams Developer Portal. Use the Microsoft registration ID in the connector's Reference ID field in Part 3.

Copy the Microsoft OAuth client registration ID.

Copy the Microsoft OAuth client registration ID.

3. Enable the company connector

Who: your Microsoft admin.

This uses Microsoft's custom federated connector setup in the Microsoft 365 admin center.

Add an MCP connector

1. Open the Microsoft 365 admin center.
2. Go to Copilot → Connectors → Gallery.
3. Under Created by your org, select Add on Create a new connector.
4. On the Custom connector panel, select Add under Connect to MCP server.

Start from the connector gallery.

Start from the connector gallery.

Choose Connect to MCP server.

Choose Connect to MCP server.

Enter the connector details

Field	Value
Display name	Agave
Description	Connect to your company's Project Management and ERP data in Agave.
MCP endpoint URL	https://app.agaveapi.com/mcp/erp-sync
Developer name	Agave
Website URL	https://www.agaveapi.com
Privacy policy URL	https://www.agaveapi.com/privacy
Terms of use URL	https://www.agaveapi.com/terms
Authentication type	OAuth 2.0
Reference ID	The Microsoft OAuth client registration ID copied at the end of Part 2

Enter the connector details and Microsoft registration ID.

Enter the connector details and Microsoft registration ID.

Authorize with the admin's Agave account

1. Select Authorize.
2. If your browser blocks the sign-in window, allow popups and redirects for the Microsoft admin center, then select Authorize again.
3. In the Agave window, sign in with your Agave account. If you're already signed in, you may go straight to the authorization screen.
4. Confirm the displayed Agave account and team, then select Approve for Microsoft Copilot (Your Team Name).

Each user must connect separately

The admin signs in here to authorize and validate the setup. Every individual user must also connect their own Agave account in Copilot. They do NOT inherit the permissions of the admin who created the connection. Agave applies the permissions of the user who is signed in, together with your team's MCP settings.

Allow the admin center's popup if the browser blocks it.

Allow the admin center's popup if the browser blocks it.

Confirm your Agave identity and approve the request.

Confirm your Agave identity and approve the request.

Create and make it available

1. Return to the admin center and confirm the Reference ID shows a green check.
2. Review Microsoft's Notice and terms, and check the box when you're ready to accept them for your organization.
3. Select Create.
4. Wait for Success, with both Created connection and Linking data source checked, then select Done.

Create the connection after authorization succeeds.

Create the connection after authorization succeeds.

Confirm that the connection was created and the data source was linked.

Confirm that the connection was created and the data source was linked.

In Copilot → Connectors → Your Connections, open Agave and check that it is enabled for the intended users. If using Staged rollout, assign your pilot users or groups; use Deploy to all users when you're ready for company-wide access. See Microsoft's rollout instructions. Changes can take up to 15 minutes to appear.

If your tenant restricts connectors or agent types, your Microsoft admin must also allow this connector for its intended audience. Microsoft's connector availability guidance explains how tenant policies and allowed-user scopes interact.

Send your users the next section. They don't need access to Teams Developer Portal or the OAuth client secret.

4. Connect as an end user

Who: everyone who wants to use Agave in Copilot, after their admin completes Parts 1–3.

Connect your Agave account

1. Open Microsoft 365 Copilot and sign in with your company's Microsoft work or school account.
2. Open Settings using the gear icon near your profile, then select Sources.
3. Find the Agave connection your admin created and select Connect. If several Agave connections are listed, choose the one your admin enabled for you; the screenshots also show separate Local and Alpha test connections.
4. Select Continue to Agave.
5. Sign in with your own Agave account, confirm the account and team on the authorization screen, and select Approve. Allow the sign-in popup if your browser blocks it.
6. Return to Copilot. Agave's source details should now show Disconnect and the available tools.

An existing Agave session or a previous authorization can mean you aren't asked to type your password again. Your connection still uses your own Agave account and permissions.

Open Settings from Copilot.

Open Settings from Copilot.

Find the correct Agave connection under Sources and select Connect.

Find the correct Agave connection under Sources and select Connect.

Continue to Agave to sign in and authorize your own account.

Continue to Agave to sign in and authorize your own account.

Check that the connected source shows Disconnect and its available tools.

Check that the connected source shows Disconnect and its available tools.

Ask your first question

1. Refresh Copilot and start a new chat.
2. If needed, use the composer's + → Change data sources (or Sources) menu and enable Agave. See Microsoft's guide to controlling Copilot's sources.
3. Try: “Use Agave to list my data sources.”
4. Look for Connecting to Agave… and an answer with Agave source citations. Your results depend on the data and configurations you can access.

Copilot calls the Agave connector.

Copilot calls the Agave connector.

The answer includes Agave source citations.

The answer includes Agave source citations.

Troubleshooting

What you see	What to check
The authorization window never opens	Allow popups for the Microsoft site you're using and retry Authorize or Connect.
The connector's Reference ID fails validation	Use the Microsoft registration ID, not the Agave client ID. Check that both the registration and connector belong to the same Microsoft 365 organization.
Agave is missing from Copilot's Sources	Ask your admin to check your license, the connector's enabled status, and its allowed users/groups. Refresh Copilot after rollout changes have propagated.
Agave shows as connected, but Copilot cannot use it	Confirm you selected the correct Agave connection, enable it in the chat's sources, then refresh and start a new chat.
Expected configurations or data are missing	Check your own Agave permissions and the team's MCP settings. Connecting through an admin-created connector does not expand your access.

If you still need help, contact your Agave admin with the step that failed and the error message. Keep client secrets and tokens out of support screenshots.