Service Bus Notification Hubs with @ElioDamaggio

Like what you heard? Try Windows Azure for FREE and enjoy the freedom to use your preferred OS, language, database or tool. Windows Azure can help you deploy sites to a highly scalable environment, deploy and run virtual machines, and create highly scalable application in a rich PaaS environment. Give it a try!
_________________
Abstract:
In Part 6 of of their “Using Windows Azure to Build Back-End Services for Windows 8 apps” series Brian Hitney and Andrew Duthie explore the world of built-in support for authentication in Windows Azure Mobile Services. Tune in as they quickly demo for us the process of adding authentication for your mobile and Windows Store apps. Check out the full article here.
Watch Part 1 | Part 2 | Part 3 | Part 4 | Part 5
After watching this video, follow these next steps:
Step #1 – Try Windows Azure: No cost. No obligation. 90-Day FREE trial.
Step #2 – Download the Tools for Windows 8 App Development
Step #3 – Start building your own Apps for Windows 8
Subscribe to our podcast via iTunes or RSS
If you're interested in learning more about the products or solutions discussed in this episode, click on any of the below links for free, in-depth information:
Register for our Windows Azure Hands-on Lab Online (HOLO) events today!
Blogs & Articles
Videos:
Virtual Labs:
So it doesn't automatically keeps the user logged in the next time you run the app?
@Gerald
For persistent login or single sign-on with Microsoft Accounts, I'd have a look at using Live Connect for login, as discussed here:
http://www.windowsazure.com/en-us/develop/mobile/tutorials/single-sign-on-windows-8-dotnet/
For other account types, check out this post:
Hope that helps!
@Gerald - FYI, I published a new post in the series that covers persistent logins with Azure Mobile Services: http://bit.ly/10U0698 and we also just finished recording the next episode of DevRadio based on that post. We walk through how to enable persistent logins using Twitter (the process is essentially the same for the other identity providers as well), and how to leverage the server-side support for making HTTP requests to retrieve additional user information, such as the Twitter screen name for the logged in user. Should be out in the next couple weeks.
This conversation has been locked by the site admins. No new comments can be made.