![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 66%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJG%3C/text%3E%3C/svg%3E)
9,727 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Good morning, sorry for the delay! I was also waiting on a user response. Ironically, although they were getting the Duo authorization prompt in the tab they were in, if they opened a new to tab to O365, they would be logged in and functioning. Any other open doc would also still be accessible. Their login is saved on Edge. They didn't need to log in in the morning, just go through this Duo prompt after an hour.
I had them do just that. First, I had them log out of O365 on their Edge browser. I asked them to use Chrome for a start. They logged in and were up and running all day. I asked them again to log back in to Edge and test that out but their cooperation for my testing came to an end! :-/