Resource Groups [https://azure.microsoft.com/en-us/documentation/articles/resource-group-portal/] in Microsoft Azure is used to structure all your apps, databases, services, VMs etc. into logical containers that you can manage at once. But when you create new resources, the Azure Portal often makes a guess about which resource group
This is another post about Custom Authentication in Azure Mobile Services [https://martinnormark.com/how-to-do-custom-login-in-azure-mobile-services/]. Recently I also wrote about how the get the user logged in (owner of the auth token) [https://martinnormark.com/getting-logged-in-api-user-in-azure-mobile-service/] and all the code is available in my "Bootstrap Azure Mobile Services"
Last week I published ZuMo.API [https://martinnormark.com/introducing-zumo-api-a-bootstrapper-for-windows-azure-mobile-services/] to GitHub [https://github.com/martinnormark/ZuMo.API] which is a simple Windows Azure Mobile Service (using the .Net backend) that includes Custom Authentication instead of solely relying on Active Directory or login via Twitter, Facebook, Google or Microsoft. Today
A couple of days ago, I wrote about some issues I had when updating a Windows Azure Mobile Service [https://martinnormark.com/updating-a-windows-azure-mobile-services-project/] to the latest Nu Get Packages. Today I'm releasing ZuMo.API [https://github.com/martinnormark/ZuMo.API] - a small bootstrapper project for setting up