How to troubleshoot Single Sign-On Microsoft Office 365 issues – Breach Secure Now Help Center

This article contains various Microsoft 365 errors and the troubleshooting steps you can take to resolve them. For additional information on Microsoft Office 365 Single Sign-On, see also:

Microsoft 365 Federated Login

Microsoft Office 365 Federated Login Certificates or Secrets

Error:

Solution:

This error broadly says that the Application ID URL it is looking for does not exist in the federated app registration the PA made when setting it up so the process cannot begin the authentication process.

To resolve this issue, check the app registration application ID and redirect URLs and compare what is in the Azure app registration to what is in the portal for the corresponding client in the "information" tab. They are most likely not the same and updating the links on the Azure app will resolve this issue.

Error:

Solution:

Confirm steps 13 and 18. Copying from PDF does not provide a valid URL. Make sure values are copied from the portal as seen below.

Error: User stuck on Redirecting screen

https://portal.pii-protect.com/#/federated?error_description=Invalid+SAML+response+received%3A+PreSignUp+failed+with+error+User++can%27t+be+migrated+from+it%27s+external+provider+either+it%27s+not+existing+on+our+system+or+not+active%21.+&state=us-east-1_0JpfGTm47&error=server_error

Solution:

This error broadly says that the user it is looking for cannot be found in the directory

To resolve this issue, we need to check the email field of the user's Azure profile and make sure it matches their account in the PII portal. Additionally, if they are synced, they need to be synced by EMAIL as portal logon and not UPN.