I did indeed report it to Microsoft. It was the first time I have ever witnessed this behavior… it was extremely concerning. I believe with something so critical… there should be at least two checks in the Authenticator in order to deny or accept… just in case there is an “accidental brush” or anomaly. That’s just my opinion. Anyway, I’ve taken steps to hopefully mitigate this problem from happening again.