I have migrated a web application that runs in a Windows Azure cloud service from the default Membership system from the MVC 4 template to the new OWIN-based ASP.NET Identity provider.

The application relies heavily on roles, which for some reason have stopped working on Azure since the upgrade.

My controllers or actions are decorated with `[Authorize]`. This works fine, except when I specify a role `[Authorize(Roles = "User.Test")]` and run it in the Azure compute emulator. Now I will get an infinite redirects to the login page and back (I'm signed in, but for some reason it doesn't accept the role).
Interestingly, if I debug/run the web project directly (so not using the Azure emulator), it all works fine.

Any ideas on how to get this working on Azure as well? I have not had this behavior with anything else yet, so it's kind of left me clueless.

**Update November 26, 2013**

I have discovered similar behavior with the default MVC 5 template in VS2013. Please see this [forum thread on ASP.NET](http://forums.asp.net/t/1952572.aspx) for steps how to reproduce this problem without Azure.