Prompt Error:The calling application’s identity could not be verified AuthorizationIdentityNotFound

Like (0) Share

Report

Posted on 5 Nov 2024 10:53:33 by CU05111015-0

I'm building a chatbot and it was working very well in my own development environment. But it was when I moved the solution to my provided company's environment to configure manual authentication, the same bug keep appearing when the chat flow passes through a custom Prompt block.

The error is: "Error Message: The calling application’s identity could not be verified Error Code: AuthorizationIdentityNotFound Conversation Id: 326bdcfe-825b-47b7-9535-56fef88b18a7 Time (UTC): 2024-11-05T10:26:35.811Z" (of course the Id and Time field changes once the bug appears again)

I have tested my bot a lot and had these information:
- Definitely the Prompt block is bugged, everything else works fine.

- All the Prompt block are bugged, I have tried creating a new Prompt block and it still has the same bug.

- I have tested the output inside the Prompt block successfully (by clicking the Prompt's info and test), but when the chat flow passes through it, there's bug.

- The Prompt block only bugged in this new environment, I ran all the Prompt blocks in my personal environment and it was fine.

- I have found a super long and detailed list of API permissions on Azure (https://learn.microsoft.com/en-us/graph/permissions-reference), I tried to search relevant permissions by keywords but found nothing useful yet. Note that I only have these permissions granted already: Microsoft Graph: Files.Read.All, offline_access, openid, profile, Sites.Read.All, User.Read, User.ReadBasic.All, User.ReadWrite.

- I have already chosen "Accounts in any organizational directory (Any Microsoft Entra ID tenant - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)" to "Who can use this application or access this API?"

(you can see the flow stopped at this box and outputed an error)

(my Prompt block, which outputs fine on its own. Its main purpose is to translate the AI's generated output from English to Vietnamese, since there is no Vietnamese option in Secondary Language)

Please help me with this bug, I would be very much appreciated!

Thank you so much!

Categories:

General

All responses (4)

Answers (0)

CU05111015-0 on 06 Nov 2024 at 06:50:16

Like (0)

Report

Prompt Error:The calling application’s identity could not be verified AuthorizationIdentityNotFound

Hi Vinoth Selvam, thank you so much for your answer! But I still can't solve my problem.

I had exactly followed the "Configure user authentication with Microsoft Entra ID" guide to set up Authentication manually (https://learn.microsoft.com/en-us/microsoft-copilot-studio/configuration-authentication-azure-ad)

My app is also successfully registered in App registration, and I think my Redirect URI is correct too.

-----

-----

These are my current permissions on my app, which are all granted and have Admin consent.

I believe that I may have missed some of the API permissions needed by the Prompt blocks in the list above. And I can't find any documentation for which specific API permissions that is needed.

If possible, can you tell me all the API permissions needed by the Prompt blocks? And then I would ask my Admin for his consent for these permissions.

Thank you so much!
Suggested answer

Vinoth Selvam 1,527 Super User 2025 Season 1 on 06 Nov 2024 at 04:52:09

Like (0)

Report

Prompt Error:The calling application’s identity could not be verified AuthorizationIdentityNotFound

Hi CU05111015-0,

Ensure that the API permissions needed by the Prompt blocks are correctly granted in the company's environment, and that Admin consent has been given for these permissions if required. Sometimes, even if permissions are granted, they need explicit admin consent.

Confirm that the Redirect URI of your app registration is set up correctly for your new environment.

Verify with your IT team that the service principal is properly set up and trusted in the company's tenant.

Thanks.
CU05111015-0 on 06 Nov 2024 at 01:46:08

Like (0)

Report

Prompt Error:The calling application’s identity could not be verified AuthorizationIdentityNotFound

I appreciate your answer, Carlos Arteaga!

My old environment used Teams authentication and it worked very well too. But the problem is that I can only deploy the bot to MS Teams and not other channels if I'm using Teams authentication.

Instead, I want to deploy to Facebook Messenger, that's my goal, and I have to choose the "Authenticate manually" option (the "No authentication" option doesn't work too, since Prompts and Generative answers need authentication).

Do you know how to solve this bug while choosing the "Authenticate manually" option? I would love to hear your opinion!
Carlos Arteaga 2 on 05 Nov 2024 at 21:54:27

Like (0)

Report

Prompt Error:The calling application’s identity could not be verified AuthorizationIdentityNotFound

Hola.

Si usas la autenticación para Teams, te funcionará :)

If you use authentication for Teams, it will work for you