MFA Security Issues

Troubleshoot SharePoint 2016 Azure AD SAML and MFA Errors

Chanuka GeekiyanageChanuka Geekiyanage Nov 20, 2026 869 views

Question details

Find specialized help for errors occurring after Azure AD SAML authentication and MFA in an on-premises SharePoint 2016 environment.

Troubleshoot SharePoint 2016 Azure AD SAML and MFA Errors
Product
SharePoint Server 2016 and Microsoft Entra ID (formerly Azure AD)
Device & OS
not provided
Scenario
Users sign in to an on-premises SharePoint 2016 site through Azure AD SAML single sign-on and multifactor authentication.
Observed behavior
An ASP.NET runtime error or unexpected SharePoint error may appear after authentication.
Before you start

Record the exact error message, the time it occurred, and any SharePoint correlation ID. Have an administrator available who can review SharePoint logs and Microsoft Entra sign-in logs without exposing passwords, tokens, or certificate private keys.

Solution 1Recommended

Gather authentication and SharePoint error details

Use the error time and correlation information to help an administrator narrow down where sign-in or the SharePoint request failed.

These checks collect diagnostic information; the error alone does not establish whether SAML, MFA, or SharePoint configuration is the cause.

1
Capture the error

Reproduce the sign-in attempt and copy the exact error text, timestamp, affected site URL, and correlation ID shown on the error page, if available.

2
Check Entra sign-in logs

In the Microsoft Entra admin center, open Identity > Monitoring & health > Sign-in logs. Find the affected sign-in by user and time, then record its status and any available failure details.

3
Review SharePoint logs

Ask a SharePoint administrator to search the server's Unified Logging Service (ULS) logs around the error time, using the correlation ID if one was displayed.

4
Document the configuration

List the SharePoint web application and authentication setup, SAML identity provider configuration, and MFA policy relevant to the affected sign-in. Remove secrets and personal information before sharing the details.

Gather authentication and SharePoint error details
Free Microsoft Office alternative

Edit Office documents with WPS Office

WPS Office is a free, lightweight Office alternative with a familiar interface and support for common Microsoft Office formats, making it easy to move document work between suites. It does not repair SharePoint Server, SAML, or MFA configuration.

Edit documents, spreadsheets, and presentations in one suite.Open and save common Microsoft Office formats, including DOCX, XLSX, and PPTX.Use a familiar interface to transition document work from Microsoft Office.Work with local Office files independently of the SharePoint authentication issue.
microsoft office alternative - wps office

Frequently Asked Questions

Where can I find the failed Azure AD sign-in?

In the Microsoft Entra admin center, open Identity > Monitoring & health > Sign-in logs and filter or search for the affected user and sign-in time.

What should I include when asking for help?

Include the exact error, time, affected site, correlation ID if shown, relevant sign-in and ULS log findings, and a description of the SAML and MFA configuration. Remove credentials, tokens, private keys, and unnecessary personal data.

Does an error after MFA mean the MFA policy is broken?

Not necessarily. Review the Entra sign-in status and SharePoint ULS logs for the same attempt; the failure may occur at a different point in the authentication or SharePoint request.

What can I do if my support forum post is marked as spam?

Use the community site's moderation or feedback channel to request a review. Reference your existing thread rather than repeatedly posting the same question.