Azure AD B2C – PATCH request to b2cUserFlows returns 204 but property is ignored

Question

I am working with Azure AD B2C built-in user flows and Microsoft Graph (beta). I attempted to update an existing B2C user flow using a PATCH request. The request returns HTTP 204 No Content, indicating success, however the property provided in the request body does not appear in subsequent GET responses, and no configuration change is observed in the Azure portal. I want clarification on whether the property is supported, expected behavior, or silently ignored by the Graph API.

Exact API Call Used:
Request Method: PATCH
Request URL: https://graph.microsoft.com/beta/identity/b2cUserFlows/B2C_1_SIGNIN
Request Body:
{  "isJavaScriptEnabled": true }
Response: HTTP 204 No Content

• The PATCH request succeeds with HTTP 204 No Content - No error is returned - The property "isJavaScriptEnabled" does not appear when calling: GET /identity/b2cUserFlows/B2C_1_SIGNIN - No visible change occurs in the B2C user flow configuration

How to fix this?

Answer 1

As per the docs, only these properties can be modified via api after update

Property	Type	Description
isLanguageCustomizationEnabled	Boolean	The property that determines whether language customization is enabled within the B2C user flow. Language customization is not enabled by default for B2C user flows.
defaultLanguageTag	String	Indicates the default language of the b2cIdentityUserFlow that is used when no ui_locale tag is specified in the request. This field is RFC 5646 compliant.

If you want more than this you can create a feature request using the feedback portal

Answer 2

Hello Abhijit Banke

The behavior you are observing is expected.

Updates to Azure AD B2C built-in user flows via the Microsoft Graph API (including the /beta endpoint) are not supported for the property isJavaScriptEnabled. Consequently, the property is silently ignored and the PATCH request returns HTTP 204 No Content, which is why:

• It doesn't show up in later GET answers.
• The Azure portal shows no changes.

Hence,

• Utilize only the properties that are supported and visible in GET /identity/b2cUserFlows
• Use Azure AD B2C Custom Policies (Custom Policies / IEF) rather than the built-in user flows for JavaScript/UI modification.

Let me know if any further queries - feel free to reach out!

Reference https://learn.microsoft.com/en-us/graph/api/b2cidentityuserflow-update?view=graph-rest-beta&tabs=http#request-body

If the resolution was helpful, kindly take a moment to click on and click on Yes for was this answer helpful. And, if you have any further query do let us know.