Users topic update

includes/mobile-services-register-authentication.md

@@ -1,21 +1,8 @@
 
-First, you need to register your app with an identity provider at their site, then set those credentials in your mobile service. 
+* Click Azure Portal > **Mobile Services** > your mobile service > **Dashboard**, and make a note of the **Mobile Service URL** value.
 
-1. In the [Azure Management portal], navigate to your mobile service, then click **Dashboard** and make a note of the **Mobile Service URL** value.
+* Register your app with [Google](mobile-services-how-to-register-google-authentication.md), [Facebook](mobile-services-how-to-register-facebook-authentication.md), [Twitter](mobile-services-how-to-register-twitter-authentication.md), [Microsoft](mobile-services-how-to-register-microsoft-authentication.md), or [Azure Active Directory](mobile-services-how-to-register-active-directory-authentication.md). Make a note of the client identity and client secret values generated by the provider. Do not distribute or share the client secret.
 
-2. Register your app with one of the following supported identity providers. 
+* Click Azure Portal > **Mobile Services** > your mobile service > **Identity** > your identity provider settings. Enter the app ID and secret value from your provider. You've now configured both your app and your mobile service to work with your auth provider. You may optionally repeat all these steps for each additional identity provider you'd like to support.
 
-	* [Google](mobile-services-how-to-register-google-authentication.md)
-	* [Facebook](mobile-services-how-to-register-facebook-authentication.md)
-	* [Twitter](mobile-services-how-to-register-twitter-authentication.md)
-	* [Microsoft](mobile-services-how-to-register-microsoft-authentication.md)
-	* [Azure Active Directory](mobile-services-how-to-register-active-directory-authentication.md).  
-
-    >[AZURE.IMPORTANT]Make sure to correctly set the redirect URI for your mobile service in the identity provider's developer site. As described in the linked instructions for each provider above, the path of the redirect URL is different for a .NET backend mobile service (`/signin-<provider>`) compared to a JavaScript backend mobile service (`/login/<provider>`). An incorrectly configured redirect URI prevents the client from being able to sign in to your app.
-    <br/>Do not distribute or share the client secret.
-
-3. Back in your mobile service in the [Azure Management portal], click the **Identity** tab and enter the app ID and secret values that you just obtained from the identity provider. 
-
-Now that you've configured both your app and your mobile service to support one identity provider for authentication, you can repeat these steps to add support for additional identity providers.
-
-[Azure Management portal]: https://manage.windowsazure.com/
+    > [AZURE.IMPORTANT] Verify that you've set the correct redirect URI on your identity provider's developer site. As described in the linked instructions for each provider above, the redirect URI may be different for a .NET backend service vs. for a JavaScript backend service. An incorrectly configured redirect URI may result in the login screen not being displayed properly and the app malfunctioning in unexpected ways.