When you build a custom agent in Copilot Studio, you may find that it fails to send an Adaptive Card to a user in Microsoft Teams or another channel. The agent either returns a plain text fallback or shows an error that the card could not be delivered. This problem usually occurs because the Adaptive … Read more
You built an Adaptive Card in Copilot Studio and the Submit button does nothing when a user clicks it. The card renders correctly, but tapping Submit produces no response, no error message, and no conversation flow change. This failure usually occurs because the card action type is misconfigured or the bot’s topic logic does not … Read more
Your Copilot Studio agent responds in the wrong language despite your users typing in English or another expected language. This problem occurs when the agent’s language detection engine misidentifies the user’s locale or when the agent configuration lacks explicit language fallback rules. Microsoft Copilot Studio uses both the user’s browser language header and the agent’s … Read more
You built a Copilot Studio agent and want to embed it on your company website, but the agent refuses to load or the embed code produces an error. This problem usually occurs because the website domain is not authorized in the Copilot Studio publishing settings, or because the agent requires authentication that the website cannot … Read more
When you embed a Copilot agent from Copilot Studio into your website, the chat pane sometimes appears completely blank. No welcome message, no response, and no error text. This problem typically occurs because the website domain is not authorized in the Copilot Studio channel settings, or because a required authentication or data source configuration is … Read more
You may need to move a Copilot Studio agent from a development environment to a test or production environment. The export and import process transfers the agent definition, topics, entities, and settings without recreating the agent manually. This article explains the exact steps to export a Copilot Studio agent and import it into a target … Read more
When a user who created a Copilot Studio agent leaves your organization, the agent becomes orphaned. No other administrator can edit, update, or manage that agent. This happens because Copilot Studio ties ownership to a single user account by default. Once that account is disabled or deleted, the agent loses its owner and becomes locked. … Read more
You are trying to delete a Copilot Studio agent from a Microsoft 365 environment, but the delete option is grayed out or fails with an error. This typically happens because the agent is still published, has active dependencies, or the user lacks the required permissions. The system prevents deletion to avoid breaking connected workflows or … Read more
When you build a custom agent in Copilot Studio, you might find that the agent gets stuck in an infinite loop after a topic redirect. Instead of moving to the next logical step, the agent repeats the same conversation path over and over. This happens because the redirect is not properly configured or the trigger … Read more
Your Copilot Studio agent is triggering its fallback topic on nearly every user question. This makes the agent appear unhelpful and forces users to repeat themselves. The root cause is almost always an incorrect trigger phrase configuration or a missing intent mapping for common queries. This article explains why the fallback topic fires too frequently … Read more