Azure Multi-Factor Authentication Server was released

Microsoft Azure Multi-Factor Authentication

Roughly a year ago, we saw the release of Microsoft’s Azure Multi-Factor Authentication (MFA) Server, version Last week, Microsoft released another minor version, dubbed version that addresses a couple of issues you might experience with version


What’s New

Fixed issue with AD Sync send email when user enabled state changes

In the Add Synchronization Item window, the option to send email for Only New Users is enabled by default:

The Add Synchronization Item window in Azure MFA Server

However, an issue prevented sending the e-mail message when the Enabled state changed. This issue has been fixed.

Fixed upgrade issue with User Tags

In some scenarios, user tags did not survive Azure MFA Server upgrades.
This issue is now fixed in Azure MFA Server version

Added Kosovo (+383) country code

Former Yugoslavia obtained its +38 code in the 1964 CCITT/ITU Blue Book. However, on October 1, 1993, this country code, was divided into +381 (Serbia), +382 (Montenegro), +385 (Croatia), +386 (Slovenia), +387 (Bosnia and Herzegovina), +389 (Macedonia) when Yugoslavia broke up. At that time, +380, +383 and +388 were not assigned.

+383 was assigned to Kosovo*, after Republic of Serbia and Kosovo reached an agreement in August 2015. Now, the +383 country code can also be used with Azure Multi-Factor Authentication Server.

Ukraine received the +380 country code in 1995, as it left the Russian Federation in 1991. This effectuated its split from the +7 country code. +388 is assigned to groups of countries. The European Telephony Numbering Space (ETNS) embraced +388 3 for Europe-wide services.

Added One-Time Bypass audit logging

In previous versions of Azure Multi-Factor Authentication Server, the MultiFactorAuth service did not log one-time bypasses. Starting with version, one-time bypasses are logged to MultiFactorAuthSvc.log.

Web Service SDK performance improvements

Azure MFA Server’s Web Service SDK offers access to the database and MFA functionality to the AD FS MFA Adapter (when installed), User Portal (when installed) and with third-party applications (when used). Performance improvements on this central communications hub to the back-end means these front-end services work faster, too.

Other minor bug fixes

While the above fixes could be classified as minor fixes, the team reports that they’ve fixed other minor issues in Azure Multi-Factor Authentication (MFA) Server as well.


Upgrade considerations

You must upgrade MFA Server and Web Service SDK before upgrading the User Portal or AD FS adapter. Read the guidance in the How to Upgrade section in this blogpost for more information.



You can download Azure Multi-Factor Authentication Server here.
The download weighs 128.4 MB.


Version information

This is version of Azure Multi-Factor Authentication (MFA) Server.
It was signed off on September 9, 2019.

2 Responses to Azure Multi-Factor Authentication Server was released


    Did not expect this cause MS announced the EOL of the MFA Server. But nice update.

    • I think 'End of Life' is a bit exaggerated.
      I'd use the term 'Fall'. I don't believe it's Winter yet for MFA Server.

      Today, Microsoft just doesn't allow new implementations of Azure MFA Server farms.
      However, many organizations, especially organizations using Microsoft Identity Manager, still rely on their MFA Server implementations.


leave your comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.