Ensure users can successfully sign in to Workvivo using Azure AD (Microsoft Entra ID) SAML Single Sign-On by confirming that the Identifier (Entity ID) and Reply URL (Assertion Consumer Service URL) are configured correctly for the appropriate Azure tenant and Workvivo data center.
Error Message
If a user encounters the following error:
“Sorry, but we’re having trouble signing you in”
“Application with identifier was not found in the directory”
This error is generated by Azure AD and typically indicates a configuration mismatch within the Azure Enterprise Application, rather than an issue with the user’s Workvivo account.
Where the Issue Occurs
This issue occurs during the SAML authentication flow in Azure AD, before the request reaches Workvivo.
Because Azure AD cannot match the request to a configured Enterprise Application, Workvivo is unable to process the login.
Common Cause
This issue is most often caused by incorrect or mismatched SAML configuration values, such as:
- The Identifier (Entity ID) or Reply URL not matching exactly
- The wrong Workvivo data center being used in the URLs
For example:
- Using
.usinstead of.com - Using
.cominstead of.eu
Even a small mismatch will cause Azure AD to reject the authentication request.
How to Resolve the Issue
Your Azure AD administrator should review the Enterprise Application configuration and confirm:
- The Identifier (Entity ID) matches the value provided by Workvivo
- The Reply URL (Assertion Consumer Service URL) is correct
- Both values are set in the correct Azure tenant
- The URLs point to the correct Workvivo environment and region
- The values are copied exactly, with no extra spaces or characters
The correct SAML values can be found in the Workvivo Technical Resources documentation.
Additional Information
- This error is generated by Azure AD, not Workvivo
- It indicates Azure AD cannot find a matching Enterprise Application for the request
- It does not typically mean there is an issue with the user’s Workvivo account
Once the Identifier and Reply URL are corrected, users should be able to sign in immediately.
Still Having Issues?
If everything looks correct and the issue persists, please reach out to Workvivo Support and include details of the Azure configuration so we can investigate further.