This blog:
about the ASP.NET identity provider states:
Persistence control
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:
http://www.asp.net/web-api/overview/security/external-authentication-services
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?
Thanks...
-Ben