External Identity

Previously in this blog I've discussed AAD B2B guest user collaboration ("B2B") and AAD B2C ("B2C"). There is some confusion in the marketplace about the suitability for these products for different external identity scenarios.  Just last week at the Kocho Identity & Security summit we had some interesting questions around this from the audience. I'm going to address this under several headings but then provide a simple flow chart for choosing your path. Integration Both platforms integrate well with off-the-shelf SAML or OAuth apps and anything you want to write yourself, be it C#, Node, Java, or PHP. Security B2B and B2C live on the same Microsoft Azure infrastructure, taking full advantage not only of the end-to-end enterprise-grade secure protocols and secure storage, but also of Microsoft's threat detection capabilities.  In both cases the threat detection can be configured using Conditional Access (CA). UI (user interface) customisation B2C all

It was the last bright sunny day in September and with a couple of colleagues, I was queueing for the lift which would take us to the top of the Space Needle in Seattle. What were we doing so far from home and what were we going to see? The Identity ‘Airlift’ (now the Entra Airlift) has been an event aimed at bringing key Microsoft partners together with the engineering team at Microsoft to discuss technical topics and plans for the future.  It has been 3 years since an in-person Identity Airlift conference at Microsoft – and many of their team were meeting in person for the  first time since the pandemic, so this event meant a lot to organisers and attendees. As we reached the top of the Space Needle we could see a huge 360’ vista – the landscape including distant peaks on the horizon, and nearby, downtown Seattle Bellevue and Redmond, and above the ground, seaplanes and helicopters taking off and landing.   It was breath-taking. Back on the ground, we had not only seen the latest and