MFA & Verification Issues

How to Fix InfoPath 2013 Sign-In Issues with Microsoft 365 MFA

Steven ParkerSteven Parker Nov 2, 2026 869 views

Question details

Users are unable to sign in to InfoPath Designer 2013 when Microsoft 365 multi-factor authentication (MFA) is enabled, resulting in a persistent account error.

How to Fix InfoPath 2013 Sign-In Issues with Microsoft 365 MFA
Product
InfoPath Designer 2013
Device & OS
Windows 10
Scenario
Attempting to sign in to a Microsoft 365 account using the legacy InfoPath 2013 application in an environment where multi-factor authentication is enforced.
Observed behavior
InfoPath displays the error message 'There is a problem with your account' and blocks the sign-in process because it defaults to legacy authentication protocols rather than modern authentication.
Before you start

Before modifying the Windows Registry, ensure you have administrative privileges on your Windows 10 device and create a System Restore point or back up your registry.

Solution 1Recommended

Enable Modern Authentication (ADAL) via Registry Editor

Manually force Office 2013 legacy applications to use the Active Directory Authentication Library (ADAL) to support modern Microsoft 365 MFA prompts.

InfoPath 2013 relies on basic authentication by default, which fails when Microsoft 365 enforces MFA. By adding a specific key to your Windows Registry, you can activate modern authentication, allowing the secure MFA login prompt to render correctly inside the application.

1
Open the Registry Editor

Press the Windows Key + R to open the Run dialog. Type 'regedit' and press Enter. Click Yes if prompted by User Account Control.

2
Navigate to the Office Identity Key

In the Registry Editor, navigate to the following path: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\15.0\Common\Identity.

3
Create the EnableADAL DWORD

Right-click on an empty space in the right pane, select New, and click on DWORD (32-bit) Value. Name the new value 'EnableADAL'.

4
Modify the Value Data

Double-click the newly created 'EnableADAL' value, change its Value data to 1, and click OK.

5
Restart InfoPath

Close the Registry Editor and restart InfoPath Designer 2013. Attempt to sign in again to trigger the standard Microsoft 365 MFA prompt.

Enable Modern Authentication (ADAL) via Registry Editor
Security Recommendation: While disabling MFA on your work account might temporarily allow InfoPath to connect, it severely compromises your account security. Always use the registry workaround to maintain active MFA protection.
Free Microsoft Office alternative

Upgrade Your Office Experience with WPS Office

Tired of dealing with legacy software issues, outdated configurations, and complex registry fixes? WPS Office provides a modern, lightweight, and completely free alternative to Microsoft Office. With a familiar interface and no legacy authentication errors to hold you back, you can seamlessly create and manage your documents.

  1. 1. Visit the Website: Go to the official WPS Office website on your device.
  2. 2. Download the Installer: Click on the 'Free Download' button to get the latest installation package.
  3. 3. Install the Suite: Run the downloaded file and follow the on-screen prompts to easily install WPS Office.
Fully compatible with Microsoft Office formats (.docx, .xlsx, .pptx).Modern software architecture with robust cloud sync and built-in AI tools.Completely free to download and use without complex login errors.Familiar tabbed user interface ensures zero learning curve for Office users.
microsoft office alternative - wps office

Frequently Asked Questions

Why does InfoPath 2013 show 'There is a problem with your account'?

This error occurs because InfoPath 2013 is a legacy application that does not natively support the modern multi-factor authentication (MFA) prompts used by current Microsoft 365 accounts. It attempts to use basic authentication, which is blocked by MFA policies.

Should I disable MFA on my Microsoft 365 account to use InfoPath?

No, disabling MFA drastically reduces your account security and is not recommended. Instead, you should enable modern authentication (ADAL) via the Windows Registry so InfoPath can securely process the MFA prompt.

Will creating a new Windows user profile fix the InfoPath sign-in issue?

Creating a new user profile generally will not resolve this issue if modern authentication is not enabled system-wide. The core problem lies within the Office 2013 identity components, which specifically require the EnableADAL registry key to function with MFA.