{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/21c54be3679d44d6afa11b2f8946b562\" frameborder=\"0\" width=\"1308\" height=\"981\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":981,"width":1308,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":981,"thumbnail_width":1308,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/21c54be3679d44d6afa11b2f8946b562-99d1666ba333a033.gif","duration":555.877,"title":"Testing Copilot Studio to Power Automate Agent","description":"This Loom explains how to test the Copilot Studio MCP connection from Power Automate while the team is blocked on a permissions issue. It confirms the MCP connector works inside Copilot Studio, including a “could not connect” failure when using the older connection in Power Automate where the agent only runs for about two seconds. The speaker hypothesizes the failure is due to the agent using a personal user instead of the service level account, then requests Nate switch the agent node connection to the service level account and verify the end to end run using a provided guide. They also note the trigger checks about every one minute and show how to confirm failure and lack of AI brief output, with the Opportunity agent having a similar issue."}