Staged rollout password hash sync

Question

Hello all

This feature is totally not working. What is interesting is it works fine in our dev tenant, but does not work in our production tenant . This is not a difficult task to setup, so i dont understand why this is not working in our production tenant. I have posted this question to this forum before and the typical answer i get back is run a fiddler trace. I dont understand what a fiddler trace is going to reveal ? Its going to show the user is going back to onprem ADFS, and i already know that . Something on the backend of of our tenant that i dont have access to is not working correctly . Like a script is not running

Answer 1

@skip hofmann I checked your previous post where a fiddler was requested to be sent to AzCommunity via email.

Reason why fiddler is required:

1. As you mentioned it is working in your dev tenant but not in production tenant. We need to have the details of your tenant to start investigating into the issue. We can fetch that information from fiddler capture.
2. To look into our backend database, we need to know the exact timestamp, correlation ID and error details if it was captured in the background. We will get this information from fiddler.
3. I understand eventually we will see user is going back to onprem ADFS but before that is there any attempt foll r cloud authentication or this setting was completely ignored?

In worst case, if no error is found in fiddler, we will definitely get exact timestamp, request ID and correlation ID. That will help us to investigate into the issue.

Kindly update the original thread once you share the fiddler.