How do I resolve a 404 error when using Azure AD B2C custom OpenID Connect provider with Azure Static Web Apps?

Question

I'm trying to integrate Azure AD B2C as a custom OpenID Connect provider with Azure Static Web Apps (SWA). My app is a static HTML and JavaScript site (no frontend framework), and I'm using staticwebapp.config.json to configure authentication.

The deployment succeeds, and the config file is being picked up (confirmed via deployment logs). Here's my custom provider config:

"customOpenIdConnectProviders": {

  "aadb2c": {

    "registration": {

      "clientIdSettingName": "B2C_CLIENT_ID",

      "openIdConnectConfiguration": {

        "wellKnownOpenIdConfiguration": "https://

Answer 1

Hi @Kevin Petteys,

Based on your query, here is my understanding: You would like to add Azure AD B2C as Open ID connect provider using static web app.

Here is the official documentation on how to configure custom identity provider: Configure a custom identity provider.

In order to perform this operation, you need to have at least Standard plan for Azure static web apps: Azure Static Web Apps hosting plans. This comes under Authentication provider integration of custom registrations.

I hope this information is helpful. Please feel free to reach out if you have any further questions.

If the answer is helpful, please click "Accept Answer" and kindly "upvote it". If you have extra questions about this answer, please click "Comment"