Skip to main content

MCP | SeekOut Sourcing Agent for Microsoft Copilot

Bring SeekOut's talent search directly into your Microsoft 365 environment. This guide walks through setting up the agent in Copilot Studio using a custom MCP connection.

Status: The official SeekOut app for Microsoft’s app store is pending approval. Customers with a Copilot Studio license can complete this setup today.

What you’ll need

Access to Microsoft Copilot Studio with a Copilot Studio license

Microsoft 365 Copilot license assigned to your account

Microsoft 365 admin access (required for the final approval step)

SeekOut MCP server URL and OAuth 2.0 credentials — request from your CSM or [email protected] before starting

Create the agent


Step 1: Open Copilot Studio

Go to copilotstudio.microsoft.com and sign in with your Microsoft 365 account.

Step 2: Create a new agent

Click Agents in the left navigation, then click Create Blank Agent.

Step 3: Enter the agent name

In the Name field, enter exactly:

SeekOut Sourcing Agent

Step 4: Enter the description

Paste the full agent description into the Description field. This tells Copilot what the agent is for and when to surface it.

SeekOut Talent Agent helps recruiters and hiring teams source and engage talent using SeekOut. Search public profiles plus specialized pools (GitHub, healthcare, nursing, academic), your ATS pipeline, and your own internal employees; run role intakes, build hiring-manager shortlists, find similar candidates, size and compare markets, and surface diversity and compensation context. Save searches and candidates to workspaces, retrieve emails and phone numbers, export to your ATS, and draft personalized outreach. 

Step 5: Select the model

Scroll to Select your agent’s model and choose Claude Sonnet 4.6 from the dropdown.

Step 6: Enter the instructions

Scroll to Instructions and click Edit.

Delete any placeholder text and paste the following. This defines how the agent searches and presents candidates.

You are the SeekOut Talent Agent, a sourcing and recruiting assistant for recruiters, sourcers, hiring managers, and talent/RecOps teams. You connect to SeekOut's people-search tools to find and evaluate candidates and move them into the recruiter's pipeline. Be concise, professional, and recruiter-friendly.

## What you help with
- Find candidates by title, skills, location, company, industry, or seniority (public profiles — the default and largest pool).
- Search specialized pools: GitHub open-source contributors; healthcare providers (physicians, specialty, NPI); nurses (RN/LPN/NP, license state, specialty); academics/researchers (papers, h-index); your organization's ATS applicant pipeline; and your internal employees (mobility, redeployment, "who reports to X").
- Run a role intake, build a ranked shortlist for a hiring manager, find people similar to a candidate, and evaluate a candidate against role criteria.
- Size and compare talent markets, surface diversity insights, provide compensation context, and competitive hiring intelligence.
- Save searches and candidates to SeekOut workspaces, retrieve emails and phone numbers, export profiles to a spreadsheet or ATS, and draft personalized outreach.

## How to operate (always drive the SeekOut tools — never guess)
Answer sourcing questions only through the SeekOut tools. Never invent candidates, counts, contact details, or company data, and never answer from your own knowledge.

1. Load the matching workflow skill FIRST. Before any search action, load the SeekOut workflow skill that fits the user's intent (e.g. talent-search, intake, shortlist, outreach, ats-pipeline). If the user is vague or hasn't named a role, load the onboarding skill. Then follow that skill's workflow.

2. Build the search with the tools — set the query, add/remove filters, set the geographic index or vertical. Resolve company, location, title, department, stage, and recruiter values with the entity-search tools instead of guessing; many values are organization-specific.

3. Verify before you show. Always run the search-readiness check before presenting or opening candidate results. Show candidates only when it reports the search is ready. If it asks you to refine, make ONE bounded fix and re-check. If it returns a hard block, stop and explain clearly.

4. Page results carefully. Open the first page (default 15), summarize, and ask whether to go deeper or refine. Never load more pages speculatively.

5. Candidate actions need confirmation. Before retrieving contact info, exporting, saving to a workspace, or sending outreach, confirm intent with the user.

6. Explain every filter. When you set or change a filter, state what you changed and why. Do not silently drop or override filters.

7. Respect scope. Only search and act within the pools the user has licensed. If a pool seems unavailable, say so and offer an alternative.

8. Stay in role. Do not answer general HR or compensation questions from memory. If you lack a tool for a request, say so and suggest what the user can do manually in SeekOut.

## Tone and format
- Use plain, recruiter-friendly language.
- Present candidate summaries as brief bullets: name, current title + company, location, and one notable signal.
- For shortlists, add a one-sentence "why this person" note.
- Use markdown tables only when the user asks for a comparison view.
- Keep responses concise; offer to expand on request.

Step 7: Save the agent

Click Save (or Create). The agent will appear in your Agents list.

Configure authentication


Step 8: Open Settings

With the agent open, click Settings in the top-right toolbar.

Step 9: Navigate to Security

In the Settings panel, click Security, then Authentication.

Step 10: Select Microsoft authentication

Select Authenticate with Microsoft. This enables Entra ID (Azure AD) for Teams, SharePoint, Power Apps, and M365 Copilot. Leave multi-tenant support unchecked, then click Save.

Add the MCP tool


Step 11: Open the Tools tab

Click Tools in the top navigation of the agent editor.

Step 12: Add a new tool

Click Add a tool, then select Model Context Protocol.

Step 13: Configure the MCP server

Fill in the “Add a Model Context Protocol server” form:

  • Name: SeekOut Search MCP

  • Authentication: Select OAuth 2.0 and use the credentials provided by the SeekOut team

  • Server URL: Provided by SeekOut — contact your CSM or support to obtain this

Step 14: Enable all tools

After adding the MCP server, open the SeekOut Search MCP tool.

In the Tools section, toggle Allow all to On. This enables all available MCP tools including execute_app_action, set_query, add_filter, and others without needing to enable each one individually.


Confirm the Connection shows SeekOut Search MCP with a green connected indicator.

Publish to Microsoft 365 and Teams


Step 15: Open the Channels tab

Click the overflow (“+1”) in the top navigation, then select Channels.

Step 16: Select the Microsoft 365 and Teams channel

Click the Microsoft 365 and Microsoft Teams tile.

Step 17: Enable Microsoft 365 Copilot

In the panel that opens, under Turn on Microsoft 365, check the box labeled Make agent available in Microsoft 365 Copilot. This makes the agent discoverable in the M365 Copilot Agent Store.

Step 18: Set availability to the full organization

Click Availability options. Under Show in the store, select Show to everyone in my org.

  • This option requires admin approval and will show the Available in App store badge once approved.

Step 19: Publish the agent

Close the availability panel and click Save in the channel panel. Then click the Publish button in the top-right of the agent editor. Confirm the publish action. The published status will show the date and time.

Microsoft 365 admin approval


Admin required. After publishing, a Microsoft 365 global or Teams admin must approve the agent before it appears in the org-wide Agent Store.

Step 20: Locate the agent in the Teams Admin Center

Sign in to admin.teams.microsoft.com with a global or Teams admin account. Go to Teams apps › Manage apps and search for SeekOut Sourcing Agent.

Step 21: Approve the app

Click on the app name to open its detail page. Review the permissions and app information. Click Allow or change the status from Blocked to Allowed to approve it for your organization.

Step 22: Add the app to an app setup policy (optional)

To pre-install the agent for users without requiring them to find it themselves, go to Teams apps > Setup policies. Select or create a policy, click Add apps, search for SeekOut Sourcing Agent, and add it. Assign the policy to the appropriate users or groups.

Step 23: Verify in the M365 Copilot Agent Store

After approval, users can find the agent by opening Microsoft 365 Copilot, clicking All agents or browsing the Agent Store, and searching for SeekOut Sourcing Agent. Once added, it will appear in their Copilot chat sidebar.


Frequently asked questions

Do users need a special SeekOut license to use the agent?

Users authenticate via OAuth using their existing SeekOut credentials. Standard SeekOut licensing applies — no additional license is required for the Copilot integration itself.


Will this setup be replaced when the official Microsoft listing is live?

Once SeekOut’s app is approved in the Microsoft app store, we’ll provide migration guidance. The custom agent setup described here is a fully supported path in the meantime.


Something isn’t working after setup — what should I do?

Reach out to your Customer Success Manager or [email protected]. Please include your Copilot Studio environment details and a description of where in the setup the issue occurred.

Did this answer your question?