Hi @Atmaram Dutta,
Thank you for posting your question in the Microsoft Q&A forum. From what you’ve described and based on what I’ve researched, this is a known UX limitation in how Microsoft Entra handles expired OTP flow tokens during MFA. The backend correctly detects the issue and returns the error code AADSTS50089 (flow token expired) when the OTP exceeds the 10-minute validity window.
However, the MFA interface does not surface any error message or validation feedback to the user, resulting in a silent failure even though the network trace shows the error. This limitation can be inconvenient because users have no indication that the code has expired. They simply see the process fail without explanation. It can lead to confusion, repeated attempts, and unnecessary troubleshooting.
If you are using the built-in Entra MFA form, you can raise this as feedback directly via Microsoft Entra so the product team can review and consider improving the user experience. For example, you might suggest adding a countdown timer for OTP validity or a clear error message when the code has expired.
As a forum moderator, I don’t have the ability to make changes to the product and I also cannot submit feedback on your behalf.
However, I truly appreciate you bringing this situation to light. Feedback like yours is extremely valuable for improving the overall experience. I’ll also do my best to raise this internally so the related team is aware of the impact.
I hope my explanation and insights are helpful to you. Thank you again for raising this question.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.