HTTP ERROR 502

Question

HTTP ERROR 502

Kevin Tahon 86

Hi,

When I try to run a normal flow in azure adb2c, I got the error 502.
This morning it was working, but now it's failing on all our adb2c tenants.
Is there a connection problem with ADB2C today?

Kind regards,

Kevin Tahon

Martin Pichler 1 Reputation point

2020-10-27T10:02:57.98+00:00

I have the same problem on all of my 2 tenants...

Did you get any Infos on that issue?

Thanks Martin
Kevin Tahon 86 Reputation points

2020-10-27T10:05:34.897+00:00

Hi @MartinPichler-8844 ,

I just send a Direct Message Tweet on Twitter to @Azuresupport and the only response I currently got back is following:

"Hi there! Thank you for reaching out. We are aware of this and are currently looking into this".

So I'm waiting for response when it's fixed. When it's fixed I'll also update this post.

Kind regards,

Kevin Tahon
Kevin Tahon 86 Reputation points

2020-10-27T11:04:48.22+00:00

Hi @MartinPichler-8844 ,

It's working again at our side.

Kind regards,

Kevin Tahon

Accepted answer

1 additional answer

Your answer

Martin Pichler 1 Reputation point

2020-10-27T10:02:57.98+00:00

I have the same problem on all of my 2 tenants...

Did you get any Infos on that issue?

Thanks Martin
Kevin Tahon 86 Reputation points

2020-10-27T10:05:34.897+00:00

Hi @MartinPichler-8844 ,

I just send a Direct Message Tweet on Twitter to @Azuresupport and the only response I currently got back is following:

"Hi there! Thank you for reaching out. We are aware of this and are currently looking into this".

So I'm waiting for response when it's fixed. When it's fixed I'll also update this post.

Kind regards,

Kevin Tahon
Kevin Tahon 86 Reputation points

2020-10-27T11:04:48.22+00:00

Hi @MartinPichler-8844 ,

It's working again at our side.

Kind regards,

Kevin Tahon

Answer 1

AmanpreetSingh-MSFT 56,866 Moderator

Hi @Kevin Tahon · You can check service health status at https://status.azure.com/en-us/status which doesn't show any error. I tested user flow in my tenant and it is executing successfully. This could be due to any network changes at your end. You can try running user flow from a machine in different network e.g., Azure VM to confirm the same.

-----------------------------------------------------------------------------------------------------------

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

Kevin Tahon 86 Reputation points

2020-10-27T10:00:13.223+00:00

Hi @AmanpreetSingh-MSFT it shows no error in the graph but on twitter there are a lot of tweets about people who concerns the same problem.I already send a Direct Message to Azure Support and they're aware of this and are currently looking for the problem.

Thanks for the link, it's maybe usefull for later.

Kind regards,

Kevin Tahon
AmanpreetSingh-MSFT 56,866 Reputation points Moderator

2020-10-27T10:25:47.193+00:00

Hi @Kevin Tahon · Thanks for your response. I checked internally and confirmed there is an ongoing issue. There is an internal ticket opened with B2C product team as well and they are working on it. I will post an update to this thread once the issue is resolved.
Kevin Tahon 86 Reputation points

2020-10-27T11:05:16.56+00:00

Hi @AmanpreetSingh-MSFT ,

It's working again at our side.

Kind regards,

Kevin Tahon

Answer 2

Ivan Pogorelyi 1

I also had about 2 hours out of service for my B2C tenant. Would be nice to know the reason.

Kevin Tahon 86 Reputation points

2020-10-27T15:54:37.03+00:00

Hi @Ivan Pogorelyi ,

When I browsed to the issue, I saw following explanation:

27-10

Azure Active Directory B2C - North Europe / West Europe - Mitigated (Tracking ID 8SHB-PD0)
Summary of impact: Between 08:40 UTC and 11:10 UTC on 27 Oct 2020, a subset of customers using Azure Active Directory B2C in North Europe/West Europe may have experienced errors when signing in to the B2C application.

Preliminary root cause: We determined that some instances of a backend service responsible for processing service management requests had reached an operational threshold, preventing requests from completing.

Mitigation: We performed a change to the service configuration, freeing up capacity in the affected regions to mitigate the issue.

Next steps: We will continue to investigate to establish the full root cause and prevent future occurrences.

Share via

HTTP ERROR 502

1 additional answer

Your answer