Summary
In this module, you tested, published, and managed a support policy agent. You can now:
- Choose the Preview tab for quick checks and the Evaluate tab for tests that you need to run again.
- Create test conversations for common requests, unclear requests, out-of-scope questions, and escalations.
- Run an evaluation and review its General quality results.
- Use the Monitor tab to find quality, tool, permission, and credit-capacity problems.
- Publish an agent to Teams and Microsoft Copilot and test it with typical user permissions.
- Explain how solutions, environments, pipelines, data policies, and access controls support ALM.
- Identify activities that use Copilot Credits and where administrators track usage.
In the exercise, you created the Contoso Support Policy Agent and tested it with four conversations. You fixed an escalation instruction, ran the tests again, and tested the published agent in Microsoft Teams.
What you learned
- Plan and run agent evaluations: Use the Preview tab for quick checks. Use the Evaluate tab to run the same tests before release and after important changes. General quality scores the response against quality standards. It doesn't compare the response with your optional expected response.
- Monitor and improve agents: The Monitor tab shows activity, reactions, response quality, tool use, and credit usage. Identify the type of problem before you make a change.
- Publish and validate channels: Publishing to Teams or Microsoft Copilot depends on tenant policy and administrator approval. Always validate as a published user with typical permissions—not as the agent's author or an administrator.
- Govern agent lifecycle and costs: Solutions, separate environments, and pipelines help teams control releases. Administrators track Copilot Credit usage in the Power Platform admin center.