{"id":36904,"date":"2017-10-17T12:36:10","date_gmt":"2017-10-17T19:36:10","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/aspnet\/?p=22096"},"modified":"2017-10-17T12:36:10","modified_gmt":"2017-10-17T19:36:10","slug":"user-accounts-made-easy-with-azure","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/user-accounts-made-easy-with-azure\/","title":{"rendered":"User accounts made easy with Azure"},"content":{"rendered":"

One of the most common requirements for web applications is for users create accounts for the purpose of access control and personalization. While ASP.NET templates have always made it easy to create an application that uses a database you control to register and track user accounts, that introduces other complications over the long term. As laws around user information get stricter and security becomes more important, maintaining a database of users and passwords comes with an increasing set of maintenance and regulatory challenges.<\/p>\n

A few weeks ago I tried out the new Azure Active Directory B2C<\/a> service, and was really impressed with how easy it was to use. It added user identity and access control to my app, while moving all the responsibility for signing users up, authenticating them, and maintaining the account database to Azure (and it\u2019s free to develop with<\/a>).<\/p>\n

In this post I\u2019ll briefly walk through how to get up and running with Azure B2C in a new ASP.NET Core app. It\u2019s worth noting it works just as well with ASP.NET apps on the .NET Framework with slightly different steps (see walkthrough<\/a>). I\u2019ll then include some resources that will help you with more complex scenarios including authenticating against a backend Web API.<\/p>\n

Step 1: Create the B2C Tenant in Azure<\/h2>\n