Managing external identities to enable secure access for partners, customers, and other non-employees
Hello @Lars Bøgeskov Hyttel , thank you for reaching out. I did check the backend logs based on the information you shared. It looks like the Auth is failing at the MFA level. After the first-factor auth is done, I see that the second-factor is initiated and then the MFA failed as the user has not proofed up. The MFA got triggered due to a Conditional Access Policy that got triggered while accessing this application.
- Policy Name: Enforce MFA for non MAN ES Proxy source traffic
- Policy ID: ddfcfd81-7ccf-4886-8c79-5ac9d70076e5
To get rid of this error, you would need to get the user proof up for MFA first and then complete the second-factor auth. Or else, you can remove the Conditional Access policy for that user (exclude the user from CA policy) and then give it a try, and this MFA error won't come up.
I would suggest finishing up the proof up so that you need not to make a compromise with security.
Hope this helps.
Do let us know if this helps and if there are any more queries around this, please do let us know so that we can help you further. Also, please do not forget to accept the response as an Answer; if the above response helped in answering your query.