about the ASP.NET identity provider states:
By default the ASP.NET Identity system will store all the user information in a database. ASP.NET Identity uses Entity Framework Code First to implement all of its persistence mechanism.
If your application requirements are that this information might be stored in a different storage mechanism such as SharePoint, Azure Table Service, No Sql databases etc. it is now possible to plug in different storage providers.
But how can one use the Azure table service with this? My research shows that you cannot use the entity framework with the table service, so I think you'd have to replace the code that uses the entity framework entirely, but I'm not sure.
Related question: I'm new to EF in general. How can we customize how data is stored (even in SQL server)? I've found two examples that show adding extra fields to the user table:
But it's not clear to me what's going on exactly. I think that it's using Entity Framework code first, but I see very little documentation about how to customize how data is being stored by EF for this. For example, can I rename entities? Can I define what the database will be called?
Asp.Net Identity has default implementation of storage using EntityFramework.
Microsoft.AspNet.Identity.Core has a list of interfaces, that need to be implemented to store the data where and how you want. These interfaces provide minimum required members and methods.
IdentityManager is the main entry point where you can pass your custom store interface implementation.
Look this customization for framework (not relating to store/storage, it will guide you further)
This ought to provide most, if not all, of the details the OP asks about: How To: Use Azure Table Storage as an OAuth Identity Store with Web API 2
It looks like K. Scott Allen has started a series of blog posts headed in this general directions (MongoDB vs. Azure Tables) as well.