Common pitfall with Microsoft Account auth

pull/2090/head
01binary 2016-11-10 22:02:10 -08:00
parent 7efffdd53f
commit 0724df6aa5
2 changed files with 5 additions and 0 deletions

View File

@ -104,6 +104,11 @@ You are now logged in using your Microsoft credentials:
![image](sociallogins/_static/Done.PNG)
> [!NOTE]
> If the Microsoft Account provider redirects you to a login error page, note the error title and description directly following the `#` (hashtag) in the Uri. The most common cause is your application Uri not matching any of the **Redirect URIs** specified for the **Web** platform. In this case, ensure protocol, host, and port are all correct. Your application should be using `https` protocol and the redirect uri should end with **signin-microsoft** as that's the route Microsoft Account middleware will request the login provider to redirect to.
![image](sociallogins/_static/MicrosoftLoginError.png)
## Next steps
* This article showed how you can authenticate with Microsoft. You can follow a similar approach to authenticate with [Facebook](facebook-logins.md), [Twitter](twitter-logins.md), [Google](google-logins.md) and other providers.

Binary file not shown.

After

Width:  |  Height:  |  Size: 82 KiB