App registrations - preview or GA?

Adrian Brunton 1 Reputation point
2020-05-01T12:46:08.993+00:00

Hi there,

I've been advised to post here after asking Azure support:
https://twitter.com/ajbrun/status/1255432283084988417

I'm currently evaluating Azure services to be used for production. I have access to two directories, one that already does have some production services within it, and my own. My own directory states app registrations is in preview:
"App registrations (Preview)" is displayed in the breadcumbs and navigation.

The directory that is intended to be used for production does not mention preview.

Could you confirm if app registrations is made available for general availability, or should it be avoided for production use? The differences between my two directories is making me unclear...

Thanks

Microsoft Entra External ID
Microsoft Entra External ID
A modern identity solution for securing access to customer, citizen and partner-facing apps and services. It is the converged platform of Azure AD External Identities B2B and B2C. Replaces Azure Active Directory External Identities.
3,013 questions
Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
23,136 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Marilee Turscak-MSFT 37,141 Reputation points Microsoft Employee
    2020-05-01T16:15:04.01+00:00

    For regular Azure AD, the new app registration experience is generally available and the legacy experience has been deprecated. https://developer.microsoft.com/en-us/identity/blogs/deprecation-of-app-registrations-legacy-experience-and-the-application-registration-portal-apps-dev-microsoft-com/

    For Azure AD B2C, there is a separate experience and you can choose between using the current GA one and the preview one. https://learn.microsoft.com/en-us/azure/active-directory-b2c/tutorial-register-applications?tabs=applications
    https://learn.microsoft.com/en-us/azure/active-directory/develop/app-registrations-training-guide-for-app-registrations-legacy-users

    So you are correct. In Azure AD it's generally available but in B2C it's in preview. Some of the difference between the two experiences are described in those articles:

    In the legacy experience, to register an app you were required to provide: Name, Application type, and Sign-on URL/Redirect URI. The apps that were created were Azure AD only single-tenant applications. They only supported organizational accounts from the directory the app was registered in.

    In the new experience, you must provide a Name for the app and choose the Supported account types. You can optionally provide a Redirect URI. If you provide a redirect URI, you'll need to specify whether it's web/public (mobile and desktop).

    Hope this helps!

    0 comments No comments

Your answer

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