This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 90%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
I am implementing a API Connector that is submitting a response to the B2C User Flow. The API always returns:
{
"version": "1.0.0",
"action": "ShowBlockPage",
"userMessage": "Account Block"
}
In Azure AAD Audit, I can see a event "An API was called as part of a user flow" in the "PreTokenIssuance" step. The audit event indicates that the API call was correct, and it received the "ShowBlockPage" action ("{"action":"ShowBlockPage","httpStatus":"200","numberOfAttempts":1").
The problem is that the ShowBlockPage doesn't show the userMessage. It simply proceeds with the authentication process without any block. I can't find any path to have the User Flow recognize the outcome of the API connection. Any idea?
followup -- are local accounts (e.g. azure active directory linked to a azure b2c) in azure b2c ignored when processing via api connectors? I am finding that I can't add claims via the "continue" option, nor "showblockpage". @AmanpreetSingh-MSFT please help, you seem to know alot about this.
In AAD audit logs, i can see that the apis are being called in the authentication sequence (event "An API was called as part of a user flow"). However, none of the actions such as showing block page or adding claims seem to be applied (even through the audit logs show a truncated "action":"Continue","httpStatus":"200","numberOfAttempts":1,"version" message.
Hello @SB , API connectors during local account signup are not invoked. Is this your scenario?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(204.8, 20%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBG%3C/text%3E%3C/svg%3E)
Have been observing the same behavior when api responds with "ShowBlockPage" to the sign-in user flow. While it works fine when sign-up flow, but it simply has no effect for sign-in flows.
Can someone confirm if they have managed to get it done or managed to display the blocking page with user message in their sign-in flows?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 12%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJF%3C/text%3E%3C/svg%3E)
I'm facing the same issue. When I send a ShowBlockPage with 200, B2C always creates a token. ShowBlockPage shouldn't be send with a 4xx code?
Additionally, I've added a "status" property (with value "status": "400"), and this way I can send a "userMessage". But ShowBlockPage is not working.
Hello everybody and thanks for reaching out. Since we may need access to your tenant and resources the best way to deal with this is Creating a Support Request. Please allow Advanced diagnostic information and mention that you want it assigned to Alfredo Revilla (that's me).
We ended up creating a support ticket for this and got response that this is by design. ShowBlockPage response works only with sign-up user flows and not with sign-in user flows and this appears to be by design for now.
I've the very same issue:
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 21%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJT%3C/text%3E%3C/svg%3E)
this post is a bit old but is this still the case? I have exactly the same issue and want to show block page at sign in, not sign up. I am triple checking before diving into custom policies.
Since this is not managed by Microsoft in returns:
I did create NotFoundObjectResult("ShowBlockPage","Whatever")
This creates an exception on client side.
Ugly? YES!
Does it work? YES!