Open the Microsoft 365 Copilot web app in Microsoft Edge, choose Agents > New agent, and use Skip to configure to build a change-management FAQ agent from approved SharePoint documents. Test it in Try it, then select Create and share it with a few named employees as chat users. The browser steps are the same on Windows 11 and Windows 10 version 22H2; there’s no local installation or Windows restart. Microsoft still services Edge on Windows 10 22H2, but standard Windows 10 support ended on October 14, 2025. Use an organization-approved device that still receives Windows security updates.

Coworkers review Copilot’s change-management plan and rollout guidance on a laptop during a meeting. Get the account, documents, and pilot group ready​

Allow about 30 minutes to configure and test the agent and send the pilot invitation, assuming the documents and access are in place. Collecting feedback and deciding whether to expand the pilot come later.

  • Use your organizational account in Edge. Open Microsoft 365 Copilot from your organization’s Microsoft 365 portal, rather than using the Edge sidebar or a personal Copilot session. The controls below follow Microsoft’s November 2026 Agent Builder documentation; the surrounding Copilot navigation can vary as the interface rolls out.
  • Confirm access for you and the testers. A Microsoft 365 Copilot license is the straightforward path. If someone uses Copilot Chat without that license, ask your Microsoft 365 admin to confirm that the tenant permits agent use and has usage-based billing available for agents grounded in shared organization data such as SharePoint. Being able to open Copilot Chat does not, by itself, establish access to this agent.
  • Pick a small, approved document set. Start with one change initiative and a few employee-facing files: the current rollout notice, the employee action checklist, and the support or escalation guide. Open each file in Edge and check that it identifies the applicable audience, effective date, required actions, and support contact where relevant. Leave out draft announcements, old schedules, and project-team notes. If two approved files disagree, have the document owner resolve the conflict before testing.
  • Choose three to five testers who already have appropriate SharePoint access. Include employees who will experience the change and someone who handles their support questions. Ask at least one tester to confirm they can open the original documents from their own account. That makes it easier to separate an agent problem from a file-permissions problem later.

Configure and test the FAQ agent​

  1. Open Agent Builder. In Microsoft 365 Copilot, select New agent under Agents in the navigation pane. Choose Skip to configure to open the Configure tab. Set Name to Change Management FAQ and use a description such as: “Answers employee questions about the approved rollout schedule, required steps, training, and where to get help.” If the agent covers one named rollout, put its name in the description.
  2. Enter the answer rules. Paste the following into Instructions, replacing the two placeholders with the initiative name and the official fallback contact or channel. Use a contact that employees are authorized to see.
    You answer employee questions about [initiative name]. Base all claims about this rollout on the selected, approved SharePoint documents. Give the short answer first, then list any required action, the applicable date or time zone if documented, and where to get help. Identify the document that supports the answer.
    If the answer depends on a team, location, or rollout wave and the employee has not specified it, ask one clarifying question. If the approved documents do not answer the question or give conflicting answers, say what you could not verify and direct the employee to [official support contact or channel]. Do not guess dates, eligibility, or exceptions. Explain the documented process, but do not claim to approve exceptions, submit requests, or confirm an individual’s status.
  3. Attach the approved SharePoint files. Under Knowledge, select the Attach cloud files cloud icon and browse to the files. Use More places in the picker if your site is not in the recent list. If the picker doesn’t show the site, you can also enter a direct SharePoint path that includes the site path and has no query parameters, then press Enter. Prefer individual files for this pilot: a site or folder URL also covers its subpaths, which can bring in material you didn’t intend to test.
    Use the SharePoint originals, not Upload. Uploading a local copy embeds its content in the agent and does not preserve the original SharePoint permissions as the access boundary. Once attached, confirm that only the intended sources appear in Knowledge. If a newly added file shows Preparing, wait for it to become ready before judging any response that depends on it. You can use the refresh control at the top of Knowledge to check its status.
  4. Prioritize the approved sources and add starter questions. Turn off Search all websites if it is enabled, leave public websites out of Knowledge, and turn on Only use specified sources. Despite the wording, Microsoft documents that this setting prioritizes the configured sources for lookup questions; it does not block all general AI knowledge. Treat the instructions and testing below as quality checks, not as access controls. In Starter Prompts, add a few employee-facing questions, such as “When does this change affect my team?”, “What do I need to do before rollout?”, and “Where do I get help?”
  5. Run a short test in Try it before selecting Create. Write down the expected answers from the documents first. Use New chat when testing a stand-alone question so that the prior conversation doesn’t supply a missing detail. Check the substance of each answer and open the source if the response provides one. A reference to the right file is not enough if the answer gives the wrong date, audience, or action.
    Test questionWhat a passing answer does
    “When does the change start for my team?”Gives the approved date for a specified team, or asks which team or wave applies if the answer depends on it.
    “What do I need to do before the switch?”Identifies the documented steps and distinguishes requirements from recommendations.
    “I missed the training. Where can I get help?”Uses the approved support route and doesn’t invent a recording, session, or contact.
    “Am I approved to skip this step?”Explains the documented exception process, if there is one, without claiming personal approval.
    “What is the rollout date for a group not listed in the documents?”Says the date can’t be verified instead of extrapolating from another group’s schedule. Use a real gap in your sources for this test.
  6. Create the private agent. If the tests pass, select Create. The confirmation should indicate that the agent is private. Open the created agent and repeat one known-answer question before sharing. If it fails, fix the source or instructions first rather than asking pilot users to work around a known defect.

Share with named testers and verify their experience​

  1. Grant chat access only. From the creation confirmation, select Share. Leave Org-wide sharing for chat access off. Enter each tester in Add a name, group, or email, choose Can chat in Add people, and select Add. Don’t use Can edit for testers: that role grants ownership, including the ability to manage sharing.
    Do not broaden SharePoint permissions in the sharing dialog just to complete the pilot. Agent access and document access are separate. If your interface offers to share source files or folders, don’t grant new permissions unless the document owner has approved the specific audience and content. For this pilot, use the testers’ existing access.
  2. Send the chat link with a specific assignment. Select Copy chat link and send it to the named testers. Ask each person to open it in Edge with their work account, ask one question from the test set and one they actually need answered, then open any source the agent cites. Have them confirm that the answer gives them enough information to act. For a practical access check, ask a colleague outside the pilot to try the link with their own work account; they should not be able to chat if they have not been granted access.
  3. Collect feedback somewhere the pilot owner can read it. Use a restricted Teams thread or an internal form approved for the pilot. Ask for the question, whether the answer was correct, whether the source opened, and what was missing or wrong. Tell testers not to paste personal case details or restricted text into the feedback. Before widening access, rerun the tests after any fixes, have a tester confirm the live result, and resolve any wrong deadlines, incorrect required actions, or access problems.

Troubleshoot, update, or stop the pilot​

  • New agent is missing, or a tester gets an access error. First confirm that the person is in the right Microsoft 365 tenant with their work account. For a tester, check the agent’s Share dialog for their Can chat entry. If that is correct, have the Microsoft 365 admin check agent access policy, licensing, and whether SharePoint-grounded use is covered for that account. A Windows restart won’t change those settings.
  • A SharePoint file won’t attach, or the agent doesn’t use it. Open the original file with the same account you used to build the agent. Check that you added the intended file rather than a broad parent path, and check for Preparing in Knowledge. If SharePoint grounding is unavailable across the tenant, ask the admin whether Restricted SharePoint Search is enabled; Microsoft documents that it prevents use of SharePoint as a knowledge source in Agent Builder. Don’t bypass that policy by uploading local copies.
  • An answer works for the owner but not for a tester. Ask the tester to open the exact source in Edge with their own work account. If they can’t, have the document owner or SharePoint admin review permissions and any applicable sensitivity label. If the file opens but the answer is wrong for both users, check for overlapping rollout notices or unclear audience labels before changing the prompt.
  • A fix appears in preview but not through the pilot link. In the Copilot navigation pane, open the agent’s More (...) menu, choose Edit, and make the correction in Configure. Test it, then select Update. Edits can be saved without being visible to users, and an update can take several minutes to reach them. Microsoft advises resharing agents that use SharePoint files or folders with the same users after an update; before doing so, review any source-sharing choices so the update doesn’t grant unintended file access. Retest from the chat link using a tester’s account.
  • You need to suspend access. Open Share, make sure org-wide access is off, then use the role menu beside each pilot recipient and choose Remove. Reopen the link as a removed tester to verify the change. If SharePoint permissions were granted separately for the pilot, ask the document owner to review the affected files’ sharing settings and remove only the pilot-specific grants. Removing agent access does not undo file sharing. Keep the agent private while you repair it; use Delete from its More (...) menu only if you intend to retire it permanently.