Views:

Applies to Product - Power Apps

What’s happening?
The custom Copilot fails to initialize when accessed through the PowerApp, while it functions correctly in the Copilot studio.
 

Reason:

  • A 403 error may indicate a data boundary violation, suggesting that the Copilot bot is located in a different region than the request being made.
  • The requirement for enabling data movement across regions for generative AI features may not be met, especially if the organization and environment are located in different regions.
  • Security settings on the Copilot may also be a factor, particularly if a customer-managed key or a Customer Lockbox is enabled.

 

Resolution:

  1. Ensure that data movement across regions is enabled for generative AI features in the environment.
  2. Verify that the personal environment where the Copilot works is located in the same region as the affected environment.
  3. Check if the environment has a customer-managed key or a Customer Lockbox enabled, as these settings can prevent the Copilot from functioning correctly.
  4. If a 403 error is encountered, review the security settings and consider disabling the web channel security option by switching "Require secured access" to Disabled. Note that this change can take up to two hours to propagate.