Entra External ID for Customers - first impression

Entra External ID for Customers is a new Azure Tenant type that allows you to create digital identities for your customers. Use cases B2B partners. You can create a dedicated customer tenant for your partners and give them access to your applications, manage users and groups in the tenant without partners’ access to your organisation (workforce tenant). Your data is fully secured and isolated. Online services and web shops for your retail. Full self-service is available to sign up/sign in and manage their accounts. You can also use social logins like Google or Facebook. Product pages, helpdesk and support. Keep customer engagement and provide them with the best experience. Cross-device authentication. User-friendly experience to log in on the TV screen, medical devices, or any other IoT where you can display a QR code or PIN to log in. What is Entra External ID for Customers? In simple words, it is a new tenant type. From now you can decide Workforce or Customer type. It is a new tenant type to create - so for customers, it is separate - and not connected with your organisation’s tenant. Please remember that the service is still in preview mode - but only till the 15th of May, so only limited features may be available. Service will be GA soon!! ...

May 2, 2024 · Mateusz Jendza

Design your CIAM Solution with Azure AD B2C

Here are some tips that can help you with user management: Use CIAM User Interface to create a new user: with Azure AD B2C Policy - User Journey, you can create a single point for all applications to create a new user, making the process efficient, streamlined, easy to improve and change. Don’t share personal information with applications: Adopt a zero-trust approach to avoid sharing personal information with applications. Instead, you can use centralised communication with end-users for marketing and other purposes (It is only possible with some business cases). Avoid using email addresses as user identifiers: Not sharing them reduces the possibility of them being used as identifiers by new and migrating to CIAM applications. Also, for all primary cases, email is a basic user identifier (with password); hiding email from applications gives you independence and flexibility in the future - for example, using FIDO or Passkey or without keeping an email address. Use REST|SCIM API with temporary access for applications: This can be useful for migration purposes, as it provides temporary access for applications - granting limited time-frame access so you can easily monitor API usage. The main channel for sign-up users is the User Interface (Policy) - (KISS rule - it will be easier to maintain one component). Use CIAM solutions like Azure AD B2C for password security: These solutions take care of passwords and other security measures for you, so you don’t have to worry about them. Remember that you don’t have access to the user passwords via API or management portal. ...

January 9, 2024 · Mateusz Jendza