title: Adding Scope, "wl.emails", to MicrosoftAccountAuthenticationOptions in Startup.Auth.cs causes issues
body: <p>Please tell me what is wrong.</p>
  
  <pre><code>    public void ConfigureAuth(IAppBuilder app)
      {
          var mo = new MicrosoftAccountAuthenticationOptions();
          mo.ClientId = "xxxxxxxxxxxxxxxxx";
          mo.ClientSecret = "yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy";
          mo.Scope.Add("wl.basic"); // No effect if this commented out
          mo.Scope.Add("wl.emails");
  
          // IF I COMMENT NEXT TWO PROPERTIES, USER IS AUTHENTICATED, BUT THE DB IS NOT
          // UPDATED. LEAVE THEM AND THE REDIRECT FROM MSLIVE ENDS ON LOGIN PAGE
  
          mo.SignInAsAuthenticationType = "External";
          mo.Provider = new MicrosoftAccountAuthenticationProvider()
          {
              OnAuthenticated = (context) =&gt;
                  {
           // Set breakpoint here to see the context.Identity.Claims HAS CLAIMS DESIRED.
           // SO IT APPEARS TO ME Nothing to do here but verify they exist in the debugger.
           //(context.Identity.Claims).Items  ARE:  
           //{http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier: xxxxxxxxx}
           //{http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name: yyyy yyyyy} 
           //{urn:microsoftaccount:id: xxxxxxxx}  
           //{urn:microsoftaccount:name: yyyy yyyyy}  
           //{http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress: xxxxxxxx@hotmail.com}
                  return Task.FromResult(0);
                  }
          };
          // Enable the application to use a cookie to store information for the signed in user
          app.UseCookieAuthentication(new CookieAuthenticationOptions
          {
              AuthenticationType = DefaultAuthenticationTypes.ApplicationCookie,
              LoginPath = new PathString("/Account/Login")
          });
          // Use a cookie to temporarily store information about a user logging in with a third party login provider
          app.UseExternalSignInCookie(DefaultAuthenticationTypes.ExternalCookie);
  
          app.UseMicrosoftAccountAuthentication(mo);
      }
  </code></pre>
  
  <p>A reasonable expectation asserts that the framwework will transparently handle the addition of a Scope to the default <code>*AuthenticationOptions</code>. Subsequently, wrt the MVC5 template, the developer <a href="http://forums.asp.net/post/5544846.aspx" rel="nofollow">can extract and persist Claims</a> in <code>ExternalLoginConfirmation</code> code.  Another reasonable expectation is that the framework will transform incoming <em>standard</em> <code>ClaimTypes</code> into Claims in the <code>ClaimsIdentity</code> exposed by the framework.</p>
  
  <p>I am very glad source code is available <a href="http://katanaproject.codeplex.com/SourceControl/latest#src/Microsoft.Owin.Security.MicrosoftAccount/MicrosoftAccountAuthenticationHandler.cs" rel="nofollow">MicrosoftAccountAutheticationHandler.cs</a>, and I will check it to solve this; lacking a response. Best wishes to Katana as the documentation and the framework are maturing. Is there a way for the framework to help the developer spot config issues?.  </p>