Summary

  • 2 minutes

You can now take an enterprise requirement and recommend a supported integration approach for an agent powered by the GitHub Copilot harness.

What you learned

  • Identify the capability each business need calls for: Knowledge answers questions from content, tools look up current data or take action in other systems, and connected agents handle specialist work that another agent owns.
  • Compare agent tools: Connectors fit supported services, MCP servers fit custom or internal services, workflows fit fixed multistep processes, and Foundry IQ, Fabric IQ, and Work IQ bring in context that's already managed in Foundry, Fabric, or Microsoft 365.
  • Confirm identity and access for each approach: Decide whether a tool connects with end-user or maker-provided credentials, check each approach's connection requirements, and confirm that your organization's data policies, credential policy, and environment allow it.
  • Write descriptions that help the agent choose: Write names and descriptions that say what each tool, skill, or connected agent does and when to use it. Test with requests that should and shouldn't select each one, and use the activity trace to confirm which capability the agent used.

MCP servers, Fabric IQ, and Work IQ are in preview on the GitHub Copilot harness. Check their current availability before you include them in a production recommendation.

Learn more