@dan Thanks for your quick reply. Part of my confusion might be that I don't fully understand the sequence of events when the linking occurs. I can attest to this:
-
We are using Azure AD's OIDC identity provider.
-
The user in question already has an active AD account that they've logged into for years.
-
This process has worked in the past and now mysteriously doesn't work.
I'm wondering if something has changed on the Azure side that is preventing communication between Azure AD and FA.