Issue Summary

When a user interacts with Rovo Chat through 1:1 in Teams app, they were unable to perform write actions like creating work items on Jira or creating a page in Confluence.

• We noticed that these users don't permissions for approving the initial consent prompts during their OAuth Flow. 
• The Global admin approves it on behalf of the users in Microsoft Entra admin center for the first time.
• The same works fine as expected for Global admins without any issues.

Steps to Reproduce

1. User installs Rovo app in MS Teams
2. User prompts Rovo to create a page in a Confluence space or create a Jira work-item.
3. Rovo suggests to review the page/work-item that would be created.
4. Upon clicking Review button, Rovo asks for granting consent.
5. Post user's sign-in, the request is approved by the Global admin in MS Entra Admin Center.
6. User reviews the page/work-item and proceed with create and submit actions.
7. Rovo shows the error "Unable to reach app. Please try again" and doesn't create the page in Confluence or work item in Jira.

Expected Results

Rovo to create a Confluence page without showing any error.

Actual Results

Users notice the error below in Rovo Chat:

"Unable to reach app. Please try again" in Rovo for Teams.

The below error is thrown in the Network logs:

No account found for external ID: <Microsoft Account ID>

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available