Unable to give desired API permission even when uri is present

[nikunjheron0409]

We have the url present in App authentication but it is not reflecting while giving admin approval for the application.
Due to which I am getting the below mentioned error my teams application.
AADSTS500011: The resource principal named https://trivia.springworks.in/ was not found in the tenant named MSFT. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You might have sent your authentication request to the wrong tenant. Trace ID: 72543f10-4ed6-424a-94b6-da32a84ace00 Correlation ID: 0266fcc1-41fb-4601-9546-4ca93f5762a9 Timestamp: 2025-05-12 17:11:08Z

I have https://trivia.springworks.in/ present in app authentication but when I give admin consent to application it is not being viewed.

Can you please help us in figuring this out.

[m365-agent-toolkit-assistant]

👋 Hi @nikunjheron0409,

Thank you for reporting this issue! We want to let you know that:

⏱️ Our team will personally review your issue
🎯 You can expect a response within 1 business day

✨ This is an AI-generated initial response
🤖 AI-Generated Preliminary Analysis:

Issue Analysis

You are encountering an AADSTS500011 error indicating that the resource principal named https://trivia.springworks.in/ was not found in the tenant named MSFT.

Context Required

1. Development environment: Are you using Visual Studio Code, Visual Studio, or CLI?
2. Teams Toolkit Version: Which version are you using?
3. Reproduction Steps: Specific steps leading to the error.
4. Error Logs: Full error logs could provide additional insights.

Possible Solutions

1. Check Application Registration:

   • Ensure the Application ID URI in Azure AD is correctly set to https://trivia.springworks.in/.
   • Validate that the admin consent process is completed successfully for the app.

2. Tenant and Multi-Tenant Configuration:

   • Ensure the application is configured to support multi-tenant if it’s intended to be accessed across different tenants.

3. Permission and Admin Consent:

   • Ensure the required API permissions are granted and admin consent is accepted.

Additional Resources

For more information, you can check relevant GitHub issues that encountered similar problems:

• Resource Principal Not Found
• Resource Principal Error During Deployment

Apologies for any inconvenience. If the issue persists, please share detailed context for further assistance.

✨We'd love your feedback! Please take a moment to fill out our survey.

---

Note: This is an automated first response generated by AI. A human team member will review your issue and provide a more detailed response soon. We appreciate your patience!

[Nivedipa-MSFT]

@nikunjheron0409 - Thanks for bringing this issue to our attention.
Could you please verify below checkpoints?

1. Verify that the app with the identifier URI https://trivia.springworks.in/ is registered in the correct tenant
2. In the app registration, under Expose an API, confirm that the Application ID URI is set to https://trivia.springworks.in/.
3. If you're trying to give admin consent, make sure you're logged in as a Global Administrator.
   Use the following format to trigger admin consent:
   https://login.microsoftonline.com/{tenant-id}/adminconsent?client_id={app-client-id}
4. If your app is multi-tenant, ensure that it has been consented to by an admin in the MSFT tenant.
   If it’s single-tenant, it must be registered in the MSFT tenant itself.
5. Under Authentication, ensure that the redirect URIs are correctly configured and match what your app is using.

[Tagliari43]

como eu falo com vcs por favor me ajudem não sei muito mas gostaria de aprender

[nikunjheron0409]

@Nivedipa-MSFT ,
I confirm that all above mentioned points from 1-5 are being taken care of.

[Nivedipa-MSFT]

@nikunjheron0409 - Could you please verify that the Application ID URI in the "Expose an API" section matches the webApplicationInfo in the manifest? If it does not, please update the value of webApplicationInfo in the manifest to match the Application ID URI.

[Nivedipa-MSFT]

@nikunjheron0409 -Could you please verify the suggested checkpoint above?

[nikunjheron0409]

Hi, It does match . Can we have a debugging call. It will be faster that way I think. Thank you

…

On Thu, 29 May 2025, 11:44 Nivedipa-MSFT, ***@***.***> wrote: *Nivedipa-MSFT* left a comment (OfficeDev/Microsoft-Teams-Samples#1675) <#1675 (comment)> @nikunjheron0409 <https://github.com/nikunjheron0409> -Could you please verify the suggested checkpoint above? — Reply to this email directly, view it on GitHub <#1675 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BSXNHUUEJZQ6YENTIBE24BD3A2QV3AVCNFSM6AAAAAB5UHAQ6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMJYGQYTQMBZHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>