Microsoft Previews Building Authentication Processes into Apps with Visual Studio App Center Auth

Microsoft on Thursday announced an "early preview" of Visual Studio App Center Auth, which lets developers build user authentication processes into their applications.

Visual Studio App Center is a solution that provides automation and lifecycle management capabilities for developers building applications. It works with applications built for Android, iOS, macOS and Windows machines, and previously was known by the "Mobile Center" name.

The new Auth addition to Visual Studio App Center is based on using the Azure Active Directory B2C (Business to Consumer) identity authentication service, which is used to address scalability issues. Visual Studio App Center Auth leverages the Microsoft Identity Platform 2.0, which is Microsoft's newly announced replacement for Azure Active Directory 1.0.

In particular, Visual Studio App Center Auth taps the Microsoft Authentication Library (MSAL), an open source library for single sign-on and passwordless authentications. MSAL serves as a replacement for the current Azure Active Directory Library (ADAL).

MSAL and ADAL integrate with different endpoints. Using MSAL particularly lets developers leverage both personal and work accounts when adding user authentications to apps, according to this Microsoft document description:

Active Directory Authentication Library (ADAL) integrates with the Azure AD for developers (v1.0) endpoint, where MSAL integrates with the Microsoft identity platform (v2.0) endpoint. The v1.0 endpoint supports work accounts, but not personal accounts. The v2.0 endpoint is the unification of Microsoft personal accounts and work accounts into a single authentication system. Additionally, with MSAL you can also get authentications for Azure AD B2C.

The authentication flow for applications using MSAL is shown in this Microsoft diagram:

[Click on image for larger view.] Identity authentication flow for apps tapping the Microsoft Authentication Library (MSAL) and the Azure Active Directory B2C service, and using a Facebook social media ID. (Source: Microsoft blog)

Organizations wanting to use Visual Studio App Center Auth will need to have an Azure subscription. They'll also need to be using the Azure AD B2C service. There's a five-step wizard process to set it up.

Microsoft is planning to add support for the use of other identity provider services with Visual Studio App Center Auth in a future release. It's also planning to simplify the setup so that organizations will be able to create their own Azure AD B2C tenant within Visual Studio App Center. There also are plans to support enterprise Azure AD scenarios, such as "authentication against a corporate domain and managing access to sensitive data."

About the Author

Kurt Mackie is senior news producer for 1105 Media's Converge360 group.


  • Surface and ARM: Why Microsoft Shouldn't Follow Apple's Lead and Dump Intel

    Microsoft's current Surface flagship, the Surface Pro X, already runs on ARM. But as the ill-fated Surface RT showed, going all-in on ARM never did Microsoft many favors.

  • IT Security Isn't Supposed To Be Easy

    Joey explains why it's worth it to endure a little inconvenience for the long-term benefits of a password manager and multifactor authentication.

  • Microsoft Makes It Easier To Self-Provision PCs via Windows Autopilot When VPNs Are Used

    Microsoft announced this week that the Windows Autopilot service used with Microsoft Intune now supports enrolling devices, even in cases where virtual private networks (VPNs) might get in the way.

  • Most Microsoft Retail Locations To Shut Down

    Microsoft is pivoting its retail operations to focus more on online sales, a plan that would mean the closing of most physical Microsoft Store locations.

comments powered by Disqus

Office 365 Watch

Sign up for our newsletter.

Terms and Privacy Policy consent

I agree to this site's Privacy Policy.