Azure Multi-Factor Authentication Server 8.0.1.1 was released

Microsoft Azure Multi-Factor Authentication

Roughly four months ago, we saw the release of a new major version of Microsoft’s Azure Multi-Factor Authentication (MFA) Server, version 8.0.0.3. Last week, Microsoft released a minor version, dubbed version 8.0.1.1 that addresses a couple of issues you might experience with version 8.0.0.3.

 

What’s New

Incompatibility with Japanese Windows installations

The team fixed an issue that admins might experience when launching the Azure Multi-Factor Authentication (MFA) Server Admin Console on Japanese version of Windows.

Language selection for the User Portal

Azure Multi-Factor Authentication (MFA) Server’s User Portal is an additional component that allows end-users to make changes to their on-premises MFA registrations in a web-based environment. The User Portal is available in several languages and offers end-users a selection of languages for text messages, phone calls and other authentication-related settings.

The team fixed an issue with retaining the selected language in the User Portal.

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, Mobile Portal or AD FS adapter. Read the guidance in the How to Upgrade section in this blogpost for more information.

 

Download

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

 

Version information

This is version 8.0.1.1 of Azure Multi-Factor Authentication (MFA) Server.
It was signed off on July 26, 2018.

3 Responses to Azure Multi-Factor Authentication Server 8.0.1.1 was released

  1.  

    Thank you for the post, I tried updating as you outlined https://dirteam.com/sander/2016/04/06/azure-multi-factor-authentication-server-reaches-version-7-0-0-9/, but I didn’t find any executable (.msi) for the Multi-Factor Authentication Mobile App Web Service.

    Any ideas how to upgrade that part?

  2.  

    I have a big question… Why is a user enabled on Authentication Server on prem not enabled on Azure Cloud 🙁
    If I want to do a conditional access over a cloud application the users have to enroll themselves again…

    • Currently, Azure Multi-Factor Authentication (MFA) Server and Azure MFA (as-a-Service) are completely different products and systems. There is no overlap between the two products or systems in terms of configuration or management, only in licensing and functionality.

      Where MFA Server was designed for on-premises strong authentication, Azure MFA was designed for cloud-based strong authentication. These lines have blurred significantly when the AD FS adapter was introduced for MFA Server on-premises, as this enabled many Conditional Access-like, cloud-oriented scenarios. Likewise, Azure MFA now also offers an AD FS adapter on Windows Server 2016 and an NPS add-on for RADIUS strong authentication, encroaching on MFA Server’s traditional turf.

       

leave your comment

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