There are a couple of approaches to handle identity and authentication in Azure. You can set up the Azure Mobile App Service to use Facebook, Twitter, Microsoft Account, Google, or even Azure Active Directory as a trusted identity provider. You can also create your own custom identity provider if you want to use account data stored in your database instead of one of the social providers. You can use one of these options or a combination of several of them—they will all provide an access token that can be used by your mobile app to communicate with your API on behalf of your users. In this section, we will use only one provider, Facebook.
In order to use a social network as an identity provider, you will need ...
