Hello everyone! Here are the release notes for the most recent updates we’ve made to Duo.
You can subscribe to notifications for new release notes by following the process described here: About the Release Notes category and how to subscribe to updates.
Features, enhancements, and other improvements
- Users going through enrollment on their mobile devices can now activate Duo Mobile by clicking a button labeled “Take me to Duo Mobile”. This replaces the QR code we used to show mobile users.
- Duo’s Phishing Campaigns tool in the Admin Panel has been updated and improved.
- Admins can now customize the “You’ve been phished!” page.
- Admins can now phish their entire organization instead of a group of users by selecting (All Users) in the “Choose a Group (Optional)” field.
- For customers in a trial, we now mark all Admin Panel pages with features that will no longer be accessible after their trial ends with a countdown of days remaining. This functionality has replaced the trial banner that featured a countdown.
- Added a new guide in the Admin Panel for customers on a trial for Duo Access Edition.
- Our Azure Sync feature in the Admin Panel now displays the estimated time of the next scheduled sync. We also show a more detailed status bar while a directory is being synced.
- The Administrator Actions table in the Admin Panel now shows more detailed information about bypass code creation.
- A shortcut to edit global policy has been added to the Mobile Insight page. If your global policy addresses one of the issues on this page, it will be indicated in the same area as the shortcut.
- Our Operating Systems policy in the Admin Panel policy engine now supports iOS 10.1, iOS 10.2, iOS 10.3, and Android 7.1.
- “Duo Mobile Passcode” and “Hardware Token” are now called out as specific authentication methods in the Authentication Log in the Admin Panel instead of a generic “Passcode” factor.
- Fixed an issue where bulk enrolling multiple users with the same email address would cause them to be skipped.
- Fixed an issue where we would try to remove Inactive Users who are active under an Azure AD Sync group. This achieves feature parity with AD Sync.