This morning, I received a notice of a new version of Microsoft’s on-premises Azure Multi-Factor Authentication Server product.
According to the release notes, this version includes a new feature, logging improvements and a bug fix that might plague your Azure Multi-Factor Authentication implementation.
Version 188.8.131.52 of the Azure Multi-Factor Authentication Server adds the following additional functionality:
- Directory integration support for Oracle LDAP
- Fixed a bug with trusted IP addresses in the Multi-Factor Authentication User Portal, when selectable authentication methods are used
- Web Service SDK Logging
- Reduce MultiFactorAuthSvc.log authentication entries
Version 184.108.40.206 of the Azure Multi-Factor Authentication Server does not support Windows Authentication for Terminal Services for Windows Server 2012 R2.
All other features and components are backwards-compatible with all previous versions.
- Log on to the Azure Portal.
- In the column on the left that lists all the available items and services, scroll down until you reach ACTIVE DIRECTORY.
- In the main pane, select the default directory.
- Just above the list of directories, click the text MULTI-FACTOR AUTH PROVIDERS.
- Click the Multi-Factor Authentication Provider that you’ve configured for your organization and is marked as Active in the STATUS column.
- Click MANAGE in the bottom pane on the general settings for the Multi-Factor Authentication Provider.
- This will redirect you to your tenant view of the PhoneFactor Portal.
- In the main pane of the portal click on the Downloads header.
- Click the Download link below the list of supported platforms.
Save MultiFactorAuthenticationServerSetup.exe to a network location where you can use it from each of the Windows Servers that have Azure Multi-Factor Authentication installed.
Version 220.127.116.11 of Azure MFA Server provides new functionality.
When your organization hungers for the new and improved features, please install this version. Otherwise, you might want to hold off on installing and check for any misconfigurations on the Azure Multi-Factor Authentication forum.
Azure Multi-Factor Authentication Server version 18.104.22.168 is here
Azure Multi-Factor Authentication Server reaches version 22.214.171.124
Knowledgebase: You receive a “Web Service Requests must be protected by authentication” error when activating a Multi-Factor Auth app
KnowledgeBase: Users in Azure Multi-Factor Authentication Server 6.3.x and up can not select One-Way OTP or PIN options in the User Portal
KnowledgeBase: Azure MFA Portal shows error “Error communicating with the local Multi-Factor Authentication service. Please contact your administrator.”
Choosing the right Azure MFA authentication methods