Forum Discussion

2 Replies

  • AurelienAtibard's avatar
    AurelienAtibard
    MCT
    Apr 30, 2026

    Hello,

    If your Test Run is failing, here are the things to check depending on what you're seeing.

    Cloud flow error? Open the Test Run record and look at the Error Details section — there's a direct link to the failed cloud flow run in Power Automate. That's usually the fastest way to understand what went wrong.

    Data policy error (AppForbidden)? Your DLP policy is probably blocking one of the connectors the Kit needs. Make sure these are all allowed:

    • Microsoft Dataverse (and the Legacy one)
    • Direct Line channels in Copilot Studio
    • SharePoint, Office 365 Outlook, Microsoft Entra ID, Power Platform for Admins, Power Apps for Makers

    Authentication error? This one is a bit more involved. A few quick things to verify:

    • The Kit and your agent are on the same tenant
    • Your KitAuthApp (used in Copilot Studio Kit agent configurations) has the right Dataverse redirect URI and a valid client secret configured in the Agent Configuration
    • Your CopilotStudioAuthApp (used in Copilot Studio, linked to KitAuthApp) has the two Bot Framework redirect URIs, implicit grant enabled, and the custom scope exposed and authorized
    • The agent in Copilot Studio is published with the auth config applied
    • Try also with and without the Send startConversation event option (in the Advanced tab of the test)
    • Check that your browser allows third-party cookies

    For additional information refer to : Troubleshoot errors in Copilot Studio Kit - Microsoft Copilot Studio | Microsoft Learn

  • Surya_Narayana's avatar
    Surya_Narayana
    MCT
    Apr 22, 2026

    hi TechUser2026​  You’re probably very close in Copilot Studio, the agent usually needs to be both saved/published and then tested from the Test your agent pane.

    A few things to check:

    Make sure the agent is Published

    Open the Test your agent panel on the right side

    Start with a simple prompt like “hello” to verify it responds

    If topics/flows are involved, confirm they are enabled and saved

    If it still does not run, sharing the screenshot (or any error message) would help identify whether it’s a publishing, authentication, or topic trigger issue.