NotAllAboutCode

NoSQL technologies have been around for a while now; in the past I wrote about both MongoDB and Graph Databases . Recently Microsoft introduced the Cosmos DB offer within its Azure Cloud , where Cosmos DB is not a Database , but instead a set of Common Data Services for NoSQL DBs in the Cloud (such as scalability, distribution, partitioning, etc), described as a “globally distributed database service designed to enable you to elastically and independently scale throughput and storage across any number of geographical regions with a comprehensive SLA. You can develop document , key/value , or graph databases with Cosmos DB using a series of popular APIs and programming models”. Azure Cosmos DB currently supports the following NoSQL DBs: DocumentDB MongoDB Table API Graph API The price unit in Cosmos DB is called Request Unit , which is defined as:  “ A Request Unit (RU) is the measure of throughput in Azure Cosmos DB. 1 RU corresponds to the throughpu

So, you’re finally deploying your apps to Azure like there’s no tomorrow, through a solid CI and CD process, and everyone is happy about it. Then you realize you still have one challenge: you need to provide those apps to your customers in a smooth but secure way, just like you’ve been doing for years with Active Directory Federation , where the customer logs onto his own AD , and from there he can access your apps. How to achieve that in Azure ? Turns out that (after solving a few puzzles – we know MS documentation, don’t we) it is quite simple! First you need to invite your customer to join your Azure Active Directory ; this is done in the New Portal by opening the Azure Active Directory “menu blade”. Then click on the menu item Users and groups . Then click on the menu item All users . Here you can invite an external user to join your AAD as a Guest ; this will give your customer enough permission to use your Azur