In this video, Sharon walks through registering your custom applications that can be accessed by the B2C leveraging AAD sign-in options.
- [Instructor] Now that our B2C directory has been created, we can go ahead and associate an application that our consumers will use. To do so, in the B2C settings, I'm going to go ahead and click applications, and then add. Provide the name of the application. I'm using the very creative name of external app. Next, is this a web app or web API? If yes, do you need to allow implicit flow? If you select yes, then OpenID Connect will be required.
Next, enter the reply URL. This is the location where the Azure Active Directory B2C sends an authentication response. As I don't actually have an application, I'm just going to go ahead and put in a fictitious URL. And finally, do you need to include a native client? For this demo, we're not going to include a native client. And then simply click create. And that's it. Our application has now been added into our B2C Azure Active Directory.
- Azure AD
- Adding company branding
- Adding a custom domain
- AD Connect configuration
- AD Connect Health
- Administering users and groups
- Configuring SaaS applications
- Granting conditional access
- Revoking access
- Application proxy and discovery
- Integrating web and desktop applications
- Creating an Azure AD B2C directory
- Registering an application
- Creating a Microsoft identity