B2c: Override Custom AccountEnabled (Block Sign-In) behaviour

There is a possibility to Block Sign-In for AD users using Block Sign-In property in b2c. It is general solution to use "accountEnabled" property to manage it via Graph API.

But it seems it doesn't work for external IDPs (Social (Google, Facebook) etc.)

https://learn.microsoft.com/en-us/answers/questions/1164502/b2c-block-sign-in-for-social-(google-facebook)-and

There is two ways to do this:

• use custom claim (for example "extension_accountEnabled") and manage is through the graph api.
• use default accountEnabled property and manage it via Graph or using b2c user edit screen (Block Sign-In) And rewrite custom policies in a way described here https://stackoverflow.com/questions/63599125/azure-ad-b2c-disable-block-sign-in-for-social-federated-user. Check claim and redirect to the custom error page before giving user a token.

Unfortunately, in a solution with default accountEnabled prop it is impossible to reach the redirect orchestration step cause default validator throws and error if Block Sign-In is TRUE and terminates UserJourney for users which are using AAD as IDP.

Is it possible to override default validating accountEnabled behavior to have same redirection for all types of IDPs? Or the only one way is to use custom extension_accountEnabled prop and redirect on error page based on it?

Thanks.