Share via

MSAL OAuth Issue: Missing App Registration in Production for Teams Bot

Sumit Chauhan 0 Reputation points
2024-10-23T05:33:34.8+00:00

A Microsoft Teams Chat Bot has been developed using the Bot Framework and sideloaded to MS Teams for testing via the developer portal. In the staging environment, an app registration was created, and its app ID was used in the manifest file uploaded to the developer portal.

An issue related to MSAL and OAuth was recently resolved by updating the redirect URL in the staging environment's app registration. However, in the production environment, only the enterprise application is visible.

The enterprise application lacks critical details like the redirect URL or client secret, which are essential for the OAuth logic. Is it possible that only an enterprise application exists without an app registration in this scenario?

Azure App Service
Azure App Service

Azure App Service is a service used to create and deploy scalable, mission-critical web apps.

Microsoft Security | Microsoft Entra | Microsoft Entra ID

1 answer

Sort by: Most helpful
  1. Gudivada Adi Navya Sri 21,095 Reputation points Moderator
    2024-11-01T10:10:20.31+00:00

    Hi @Sumit Chauhan

    Thank you for posting this in Microsoft Q&A.

    I understand that you only see the enterprise application in the production environment and do not have access to the app registration.

    Yes, it is possible for only an enterprise application to exist without a visible app registration in certain scenarios, especially in the context of Azure Active Directory (AAD) and Microsoft Teams applications.

    An app registration is where you define your application in Azure AD. This includes setting up elements such as redirect URIs, permissions, and client secrets.

    An enterprise application is an instance of an app registration that is used within a specific tenant. This is what users interact with when they sign in to the application.

    It is possible that the app registration for the production environment was created in a different Azure AD tenant than the one where the enterprise application is visible. You may want to check if you are signed in to the correct Azure AD tenant and if you have the necessary permissions to view the app registration.

    If the app registration was indeed created in a different Azure AD tenant, you can either create a new app registration in the correct tenant or request access to the existing one.

    Hope this helps. Do let us know if you any further queries.

    Thanks,

    Navya.

    If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.