Hello Mahir,
Thanks for reaching out. Copilot Studio now requires that each skill (Bot Framework Composer bot) be registered as an app in the same Microsoft Entra ID (Azure AD) tenant as your Copilot Bot, and the App Registration's Home Page URL or Publisher Domain must match the skill endpoint or tenant.
- If your bot gets stuck when called as a skill, it's often due to authentication or tenant mismatch—ensure the skill's App Registration is in the same tenant as the Copilot Bot and that the endpoint and manifest details are correct.
- Check for these common issues:
- The skill's App Registration is not in the same tenant as the Copilot Bot (APPID_NOT_IN_TENANT).
- The Home Page URL or Publisher Domain in the App Registration does not match the skill endpoint.
- The skill endpoint is not online or not responding (ENDPOINT_HEALTHCHECK_FAILED).
- The agent (Copilot Bot) is not allow-listed in the skill (ENDPOINT_HEALTHCHECK_UNAUTHORIZED).
- Review the full troubleshooting guide for Copilot Studio skill registration and Bot Framework authentication issues.
- For detailed steps on configuring the App Registration and tenant alignment, see the section on setting up the environment for Composer skills with Copilot Studio. Thanks, Smita ************************************************************************* If the response is helpful, please click "Accept Answer" and upvote it. You can share your feedback via Microsoft Teams Developer Feedback link. Click here to escalate.