Is anyone else here seeing issues with users getting redirected to EAM even though they are excluded from the EAM conditional access policy? This issue seems to have started last week. When a user does not have SSPR set up instead of redirecting them...
Have you tried the MSI installer as a workaround instead of EXE? We successfully updated all our servers to Duo for Windows 5.0.0 using the MSI with /quiet /qn /norestart parameters and didn't experience any unexpected reboots.
The Verified Duo Push for Windows logons code is too small leading to confusion for end users. Anyone who agrees, please log in to the DUO support portal and create a feature request case. If there are enough requests, perhaps this will get improved ...
With the preview of verified push for windows logon and now the general availability of this feature in duo for windows logon 5.0.0 the verified push code is too small and hard to see. Could this be made bigger and more obvious in the future like it ...
