Broker guide
Copilot Agents for Brokerages: Build, Use and Limits
See what Microsoft 365 Copilot agents are, how to build one for brokerage work, what to ground it on and where agents fall short on lender policy.
- Published
- Updated
Copilot agents are versions of Microsoft 365 Copilot configured with instructions, knowledge sources and supported actions for a specific job. A brokerage can build one that drafts client updates from approved SharePoint templates. Use current lender documents for policy decisions because a saved copy can go out of date.
What is a Copilot Agent?
A Copilot agent takes a request, follows the instructions you give it and uses the sources and capabilities you configure. For a processing team, that can mean turning a confirmed application status into a draft that follows the brokerage’s template.
Users with Microsoft 365 Copilot (Premium) can create and use SharePoint-backed agents when their organisation allows agent access. The paid Copilot Business add-on is available for Microsoft 365 Business Basic, Business Standard and Business Premium. Microsoft 365 E7 includes Copilot, while plans such as E3 and E5 can add it.
Eligible Copilot Chat users can create agents in Agent Builder when their organisation enables agents. They can use agents grounded in instructions or public websites, subject to admin settings.
For Copilot Chat (Basic) and Microsoft 365 Copilot (Basic), SharePoint-backed agents require pay-as-you-go billing. It’s off by default, so your Microsoft 365 admin must enable it for eligible users. See Microsoft’s agent licensing guide for the licence and billing requirements.
Agent Builder or Copilot Studio?
Agent Builder is the built-in tool for configuring an agent in Microsoft 365 Copilot. Use it when the job is to answer questions or draft text from approved material. The client update example fits because staff supply the confirmed status and review the draft before sending it.
Copilot Studio is the separate tool for workflows and integrations. Use it when the agent needs to call a supported connector to retrieve a case status from another system or start an approval workflow. It also supports publishing to other channels where the chosen setup allows it.
How to Build an Agent for Your Brokerage
Set up a draft-only agent named Client Update Drafts. Put two fictional templates in a dedicated SharePoint folder before you start. Give one the heading “Application submitted” and the other “More information needed”, with a distinct subject line for each.
- Open Microsoft 365 Copilot in your work account and select New agent, then Skip to configure. Name the agent and describe its purpose as drafting updates from a status the processor supplies.
- In Instructions, tell the agent to select the matching template and use only confirmed facts from the prompt in the draft. Tell it to ask for the status if it’s missing and never to invent a lender response or turnaround time.
- In Knowledge, select the dedicated templates folder using the SharePoint file picker. Turn off Search all websites and turn on Only use specified sources to prioritise the templates. Microsoft explains that this setting still allows general AI knowledge in some responses.
- Run a private check on the Try it tab, then select Create. The agent starts private. In Share, give a named pilot processor Can chat and confirm that they already have access to the templates in SharePoint.
- Ask the processor to open the shared agent and enter “Draft a client update. The application was submitted and we have no decision yet.” Expect the submitted template’s subject line and a draft that leaves the decision and approval timing open. Ask for a draft again with the status missing and check that the agent asks for it.
If New agent is missing or the processor gets an access error, have your admin check agent access and the assigned licence or billing policy for that account. If the agent opens but misses the template, check that the file is ready in Knowledge and that the processor can open it directly in SharePoint. After you correct the source or instructions, repeat both prompts before sharing more widely.
What to Ground It on and What to Keep Out
Ground an agent in the specific SharePoint files or folders that support its job. For brokerage work, that can include approved email templates, process notes and current checklists. Link the folder the team maintains so its owner can remove superseded files from the source set.
Microsoft’s agent sharing guidance explains that agents respect existing SharePoint permissions and sensitivity labels. Sharing the agent and granting access to its source files are separate decisions. Leave out client files beyond the intended users’ permissions, identity documents and material restricted by your brokerage’s privacy policy.
Use the Copilot safety guide to assess how it handles client data before expanding the use case.
Copilot Agent Limits for Lender Policy
A Copilot agent can pull answers from saved lender policy files even after a lender changes its rules. When several lenders’ documents cover the same topic, an answer can blend one lender’s condition with another’s or give a summary without the exact clause. A link to a file helps you trace the answer, but it still leaves you to check the wording and version.
Test one question across three lenders using the same fictional scenario. Ask, “How does each of these lenders assess casual income for this borrower? Give a separate answer for each lender and quote the clause you used.” Open each lender’s current document and check the answer, conditions and quoted wording against it.
If a quote is missing, the source is out of date or a condition belongs to the wrong lender, use the lender’s own document for the file. Bulma’s Policy Advisor answers from current residential policy documents across 52+ lenders and quotes the wording behind each answer, so you can keep the relevant clause with your file notes. Its policy sources refresh as lenders publish changes.
Licences, Sharing and Governance
Put agent ownership and access rules in the brokerage’s AI policy template under the section on approved tools and uses. Have the brokerage principal or compliance lead approve the purpose and sources. Give the process owner responsibility for maintaining the templates and sharing the agent with the approved team.
Ask your Microsoft 365 admin to manage agent access settings and approve any publication to the organisation’s catalogue. Keep a register with the owner, approved audience, source folder and review date for each agent. Have the owner remove sharing when the agent is retired, and have the admin remove any catalogue version.
Before you roll the client update agent out to the processing team, record who signed it off and keep the pilot’s two test results with the agent register.