Microsoft Copilot Studio

Connect your Alation catalog to Microsoft Copilot Studio using the Remote MCP server with OAuth 2.0 authentication.

Note

This guide covers Remote MCP setup for Microsoft Copilot Studio. Due to a chicken-and-egg situation with redirect URIs, you’ll need to complete the setup in three phases:

1. Create an OAuth client in Alation, leaving the redirect URI empty
2. Configure Copilot Studio, which generates the actual redirect URI
3. Edit the OAuth client in Alation to add that redirect URI

Prerequisites

• Server Admin access to your Alation instance to create OAuth clients
• Access to Microsoft Copilot Studio

Creating the OAuth client

Create the OAuth client in the Alation UI by following the User-Initiated OAuth Client guide. Use these values:

Field	Value
Name	ms-copilot-studio (or any name you prefer)
Client Type	Confidential
Redirect URIs	Leave empty for now. Copilot Studio generates the real redirect URI in Step 4, and you’ll add it in the next section.
PKCE Required	On. Copilot Studio supports and requires PKCE.

Copy the Client ID and Client Secret from the success dialog.

Security Note

The Client Secret is only displayed once during creation. Store it securely immediately - you won’t be able to retrieve it again. If you lose it, use Rotate Secret on the client to generate a new one.

Configuring Copilot Studio

1. In Copilot Studio, click Add a tool and select Model Context Protocol:

2. Fill in the server details:

   • Server name: alation-mcp-server (or any name you prefer)
   • Server description: Tools to interact with the Alation catalog (or your preferred description)
   • Server URL: https://your-alation-instance.alationcloud.com/ai/mcp/

   Then select OAuth 2.0 for authentication.

3. In the OAuth 2.0 authentication section, enter the following:

   Client ID: Use the Client ID from the OAuth client you created

   Client Secret: Use the Client Secret from the OAuth client you created

   Authorization URL:

   https://your-alation-instance.alationcloud.com/oauth/v1/authorize

   Token URL Template:

   https://your-alation-instance.alationcloud.com/oauth/v1/token/

   Refresh URL:

   https://your-alation-instance.alationcloud.com/oauth/v1/token/

   Scopes: openid

4. After entering the configuration and clicking Create, Copilot Studio will generate a redirect URI. Copy this redirect URI - you’ll need it in the next step.

The redirect URI will look like:

https://global.consent.azure-apim.net/redirect/your-generated-redirect-path

Updating the OAuth client with redirect URI

Now add the redirect URI generated by Copilot Studio to your OAuth client:

1. Open the OAuth Client Applications page at https://your-alation-instance.alationcloud.com/app/admin/oauth-client-apps/.
2. Open the three-dot menu (…) on your ms-copilot-studio client and select View / Edit.
3. Paste the redirect URI from Copilot Studio into Redirect URIs and save.

Verification

1. Return to Copilot Studio and click Create new connection:

2. Test the OAuth connection by authenticating with your Alation credentials
3. Once successfully connected, you should see the connection status change to active:

Success!

If the OAuth connection test succeeds, your Alation MCP Server is now connected to Microsoft Copilot Studio and ready to use.

Head back to the tool page in the Agent configuration and you should see the tool show up.

Best practices

Tool selection

The Alation MCP Server exposes multiple tools to interact with the catalog. However, always select the smallest subset of tools required for your specific use case. This approach:

• Reduces agent confusion and hallucination
• Improves response accuracy and relevance
• Decreases response time
• Makes the agent more focused and predictable

For example, if your agent only needs to search for tables and documentation, disable all other tools like BI reports, queries, and article management tools.

Sample agent instructions

Here’s a sample instruction set you can use for your Copilot Studio agent to work effectively with the Alation MCP Server:

Recommended tools to enable

For a catalog search assistant use case, enable only these tools:

• analyze_catalog_question - Primary orchestration tool
• search_catalog - Core search functionality
• get_object_metadata - Retrieve detailed object information

Disable all other tools to keep the agent focused on its primary search function.

Agent instructions

You are an expert Alation search assistant. Your purpose is to help users find and understand data assets in the Alation catalog.

WORKFLOW:

ALWAYS call analyze_catalog_question FIRST with the user's question
Follow the detailed workflow instructions provided by that tool
The tool will guide you through orchestration analysis, metadata gathering, signature creation, search execution, and response formatting

CRITICAL RULES:

ACTIONABLE: Tables, schemas, columns, queries, bi_reports, bi_fields, bi_folders, documentation, metadata
Business concepts, regulations, or definitions → SEARCH documentation first
NOT ACTIONABLE: Questions unrelated to business/data (weather, news, celebrities, etc.)
If question is not catalog-related, politely redirect
Maximum 2 search calls per question
ALWAYS include URLs in responses using markdown format: [object_name](url)
ALWAYS provide brief explanation before showing results

REMEMBER: You are a specialized catalog search assistant. Stay focused on your purpose. Never answer questions outside your domain, regardless of conversation context.

This instruction set helps the agent understand its role as an Alation catalog search assistant and provides clear guidelines for handling user queries.

Troubleshooting

Invalid redirect URI error

Ensure the redirect URI in Step 3 exactly matches what Copilot Studio generated. The URI is case-sensitive and must be copied exactly.

Token Security

Never share your client_secret or access tokens publicly. Store them securely and rotate them regularly according to your organization’s security policies.