Developer Support

Advocacy and Innovation

To B2B or to B2C?

While one uses B to signify it’s focus on business partnerships, while the other uses C for consumers, at the end of the day either can be used to accomplish roughly the same access. My intent here is to focus on what I see as the fundamental difference; one that is most likely to drive the appropriate choice of technology.

Setting up for Azure B2C development

The following describes some techniques, tools and approaches I found useful when developing applications with Azure AD B2C. The first part deals with setting up a newly created B2C tenant using the Azure portal only. The second part deals with developing custom journeys (Identity Experience Framework) xml policies.

Using B2C to support multi-tenant SaaS apps

AAD multi-tenancy is ideal for medium-to-large enterprises who own and manage their own identity infrastructure. This sample is for small enterprises, usually without their own identity infrastructure. It provides support for an application that needs to group it's users into discrete groups, each representing an application tenant.

Choosing the OAuth2 grant flow

Premier Dev Consultant Marius Rochon explores OAuth2 questions you need to ask and how the answers lead to the selection of the grant. The OAuth2 specifications define six different grant types (https://tools.ietf.org/html/rfc6749 and https://tools.ietf.org/html/draft-ietf-oauth-device-flow-15). Each provides the most optimal (from the ...

Multi-Tenant Applications and Azure AD

Following up on a previous blog post, Premier Developer Consultant Marius Rochon describes recent changes and compares the use of Azure AD multi-tenant features with the custom features in B2C.Read Marius’s first post here.Since then, there have been some changes to the demo application regarding new modes and new features. In his follow-up ...