Lansweeper Cloud SSO - IdP-Initiated

[Dup-Account]

New setup of Lansweeper Cloud. Configured SSO w/ Azure Entra. It works when logging in via the Lansweeper login page at us.lansweeper.com.

It does not work when launching from Azure My Apps. The Setup Lansweeper SSO KB specifically states you'll get an error if not enabling IdP-initiated Single Sign-on in the SSO configuration, but that enable/disable switch does not exist in my SSO configuration form.

I understand there were some recent changes, so maybe that's why, but it'd be great if someone could confirm and if so, is it safe to assume it's now enabled implicitly?

Also, in the Azure Entra configuration, there's a Sign on URL field that is optional. When we leave that empty, we get the error below. We leave that empty per the Azure Entra instructions provided in the KB named Configure Microsoft Entra ID (Azure AD) with Lansweeper SSO.

I'm guessing this because a Replay URL must accompany a Sign on URL, but any of the URLs we've tried in the Replay URL field do not net a successful login. 

{
  "error" : "invalid_request",
  "error_description" : "The request is missing a required parameter: redirect_uri",
  "error_reason" : "missing_redirect_uri"
}

[jpayneofun]

 I uploaded an example of the claim in Azure to help anyone else who may be struggling.

[jpayneofun]

We experience the exact same error, which was resolved with the information below. There were two changes required for our organization [Disclaimer: Our config does not use IdP initiated SSO];
1. Add the sign on URL (optional) as https://app.lansweeper.com and...
2. Update the Attribute claim with a namespace.

For us, while the attribute claim use is emailaddress (default) the namespace field was empty causing SSO to fail. After Lansweeper SSO migration it appears that the Email Claim schema (found in Lansweeper SSO config) is required in the namespace field (Your Enterprise App > SAML > Attributes and claims).

[MikeLee24]

Same issues here, had some issues that resulted in needing to recreate our cloud instance (not a big deal as it was only small). But can't see where that would apply.

[Dup-Account]

They had me open a case. There are some known issues with IdP-initiated SSO since the migration.