New: AI-assisted search! Ask questions and follow-ups in full sentences for smarter, faster help. Try asking things like: “How do I change a builder's or borrower's email address?”

Setting Up Built Partner MCP in Microsoft 365 Copilot

Prev Next

Purpose

Built Partner MCP lets authorized Built users access Built from compatible AI assistants. For Microsoft 365 Copilot, your organization creates an agent in Microsoft Copilot Studio and adds Built Partner MCP as a tool. Your organization then publishes the agent and makes it available to selected users or groups.

Each user signs in to Built individually. The agent uses end-user credentials, not credentials supplied by the agent maker or an administrator. The first time a user asks for something that needs Built, they sign in with the same Built credentials they use in the Built application. Each user's Built identity, permissions, and access controls stay in place.

For an introduction to Partner MCP, see Built Partner MCP Overview.


Target Users

Microsoft 365 administrators, AI administrators, and Copilot Studio makers who want to make Built available to users through Microsoft 365 Copilot.


How It Works

Before You Begin

You need:

  • Access to Microsoft Copilot Studio with permission to create or modify an agent.

  • Permission to publish or submit the agent for distribution in your Microsoft 365 organization.

  • The Built Partner MCP server URL, provided by Built.

  • The OAuth configuration values, provided by Built.

  • An appropriate Microsoft 365 Copilot license for each user who will use the agent.

  • A Built account for each user who needs to access Built through the agent.

Important:

  • Don't set up the Built connection with a shared Built account or the credentials of the person creating the agent. The connection must use end-user authentication so that each user accesses Built with their own Built identity and permissions.

Step 1: Create a Built Agent in Copilot Studio

  1. Sign in to Microsoft Copilot Studio with your organization's Microsoft 365 work account.

  2. Create a new agent.

  3. Give the agent a recognizable name, such as Built or Built Construction Finance.

  4. Add instructions describing when the agent should use Built. For example, tell it to use Built tools when a user asks about projects, loans, draws, inspections, documents, or other information in your organization's Built environment.

  5. Save the agent.

Your organization can customize the agent's name, instructions, description, branding, and conversation starters to match its internal AI governance standards.

Step 2: Add the Built Partner MCP Server

  1. Open the agent's Tools configuration.

  2. Select Add a tool.

  3. Select Model Context Protocol (MCP), or the equivalent option for adding an existing MCP server.

  4. Enter the Built Partner MCP server URL provided by Built.

  5. Continue to the authentication configuration.

The Built MCP server supplies the list of tools available to the agent automatically.

Step 3: Configure OAuth Authentication

Set up the MCP connection to authenticate users with Built using OAuth 2.0 and the following values:

Setting

Value

Authentication type

OAuth 2.0

Client ID

Provided by Built

Client secret

Provided by Built

Authorization URL

Provided by Built

Token URL

Provided by Built

Refresh URL

Provided by Built

Scopes

openid email profile

Built provides the client secret to your IT admin team as a secure credential. Store and share it according to your organization's secrets-management policies. Don't include it in tickets, screenshots, documentation, chat messages, or other broadly accessible locations.

Authentication ownership: Where Copilot Studio offers a choice between the end user's credentials and credentials supplied by the maker/agent author, select End-user credentials / User authentication. This setting is required. Don't set up a shared Built user, service account, or the agent maker's Built credentials for general user access.

Step 4: Test the MCP Connection

Before publishing the agent broadly:

  1. Save the MCP tool configuration.

  2. Allow Copilot Studio to connect to the Built MCP server and discover its available tools.

  3. Start a test conversation with the agent.

  4. Ask a question that requires access to Built.

  5. When prompted, connect or sign in to Built.

  6. Sign in with your own Built credentials.

  7. Complete any authorization or consent prompt from Built.

  8. Confirm the agent successfully uses a Built tool and returns an appropriate result.

Access reflects the permissions of the Built user who signed in. For example, if a user can't access a project in Built, connecting through Microsoft 365 Copilot doesn't give them access to it.

Step 5: Publish the Agent

  1. Publish the agent in Copilot Studio.

  2. Enable the appropriate Microsoft 365 Copilot or Microsoft Teams channel for your organization's deployment model.

  3. Submit the agent for organizational approval if your Microsoft 365 policies require it.

  4. Complete any review required by your Microsoft 365, Teams, security, or AI administrators.

Publishing the agent doesn't give all users a shared connection to Built. Each user's Built access is set up separately when that user connects.

Step 6: Make the Agent Available to Users

Your Microsoft 365 administrator can make the published agent available according to your organization's policies, for example to:

  • A pilot group

  • Specific Microsoft 365 users

  • One or more Entra ID groups

  • A business unit or department

  • The broader organization

Users don't need to set up the MCP server themselves. Your organization's agent administrators manage the MCP connection and agent configuration centrally.

Step 7: What Users Experience

  1. The user opens Microsoft 365 Copilot.

  2. The user selects the Built agent your organization provides.

  3. The user asks a question or requests an action involving Built.

  4. If the user hasn't connected Built yet, Microsoft prompts them to connect or sign in.

  5. The user goes through Built's sign-in and signs in with their Built credentials.

  6. The user approves access if prompted.

  7. The conversation continues, and the agent can use Built tools on the user's behalf.

Sign-in is per Built user. A user's access through Microsoft 365 Copilot follows the same Built account status, organization membership, roles, and permissions that apply when they use Built directly.

Step 8: Validate the Deployment

Before completing rollout, test with at least two Built users who have different permissions. Confirm that:

  • Each user is prompted separately to sign in to Built.

  • Each user signs in with their own Built account.

  • Users can access only the Built information they're authorized to access.

  • Changing or removing a user's permissions in Built affects their access through the agent as expected.

  • No agent maker or administrator credentials are shared across users.

Troubleshooting

If the agent can't connect to Built, check that:

  • The MCP server URL exactly matches the value provided by Built.

  • The OAuth client ID and client secret are correct.

  • The authorization, token, and refresh URLs are correct.

  • The tool uses end-user credentials, not maker-provided credentials.

  • The user has an active Built account and can sign in to Built directly.

  • The user has access to the relevant Built information.

  • Your Microsoft 365 administrator has approved the agent and made it available to the user.

  • The user has the Microsoft licensing your organization's Copilot deployment requires.

Note:

  • Microsoft 365 Copilot provides the agent experience, while Built remains in control of access to Built. The administrator sets up the connection once but never signs in to Built on behalf of other users. Each user sets up their own Built connection.


Best Practices

  • Start with a small pilot group before rolling out to your whole organization.

  • Always select end-user credentials so each user signs in to Built as themselves.

  • Keep the client secret in your organization's secrets-management tools, never in tickets, chats, or screenshots.

Footer Example