Setting up Microsoft Entra SSO in Systam Visit

Modified on Tue, 2 Jun at 9:03 AM

Microsoft Entra SSO lets your team sign in to Systam Visit with your organization's Microsoft credentials. No separate passwords, no new accounts — just the same login you already use for other Microsoft services.

What we need from you

Before we can activate SSO, we need two things from your side.

1. Verify your Azure claims

Ask your IT team to confirm that the following claims are available in your Azure environment:

  • email – email address
  • family_name – last name
  • given_name – first name
  • upn – Azure's own identifier (User Principal Name)

These are standard values and are usually available by default — still worth a quick check before we proceed.

2. Share your Azure Tenant ID

Your organization has its own Azure Tenant ID — it's not sensitive information. We need it to route sign-ins to the right environment.

You can find it in the Azure portal under Azure Active Directory → Overview. Send it to your Systam contact.

3. First sign-in and consent

Once we've activated SSO on our end, someone from your organization needs to sign in to Systam Visit. This triggers a consent request in your Azure environment, which an admin from your organization approves. After that, everyone in your organization can sign in with their Microsoft credentials.

That's it — signing in is now just one click away.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article