Skip to main content

Guide

Connect Kopexa to Microsoft Entra ID: Configure SAML SSO

Connect Entra ID to Kopexa: configure SAML SSO, check application metadata and plan certificate changes. Distinguish sign-in from compliance data import.

Connect Kopexa to Microsoft Entra ID: Configure SAML SSO
Julian Köhn
|Read time: 3 minutes

“Connect Entra to Kopexa” can mean two things: employees should sign in through Microsoft, or technical data should feed into security work. These are separate connections with different permissions.

This guide covers SAML sign-in and helps isolate errors across application assignment, metadata and Kopexa permissions. Microsoft 365 security data import is configured separately.

Prepare prerequisites

First verify the organisation domain in Kopexa. Define who gets access. You can use a dedicated Entra security group; check licensing requirements for group assignment. Individual assignments are an alternative.

Plan MFA or suitable Conditional Access rules in Entra. Kopexa does not issue its own additional two-factor challenge after successful SSO.

Create the SAML application

Create a non-gallery enterprise application in Entra and select SAML single sign-on. Import Kopexa metadata or use the documented values:

FieldValue
Entity IDhttps://id.kopexa.com/sso/saml/metadata
Reply URLhttps://id.kopexa.com/sso/saml/acs

Kopexa needs the email address. If user.mail is empty, a suitable alternative must actually supply the same address, for example a correctly maintained user principal name. Check the value on the test account, beyond the attribute name.

Use application-specific metadata

Use the application’s App Federation Metadata URL or its XML. General tenant metadata is not equivalent to application metadata. Kopexa’s Entra guide explicitly identifies the application-specific URL containing appid.

Enter this metadata in your verified domain’s SSO settings. Assign required users in Entra before activation. The transition applies to every Kopexa user of this domain, including existing password accounts.

Test three cases

  1. An assigned existing user can sign in and sees the intended Spaces.
  2. A new user receives the expected organisation membership or needs an invitation.
  3. An unassigned user receives no unexpected access.

Review failures in Entra sign-in logs. If authentication succeeds but business visibility is wrong, investigate Kopexa permissions separately.

When sign-in fails, isolate the layer

ObservationCheck first
Entra denies accessApplication assignment and applicable access policies
Entra authenticates, Kopexa rejectsApplication-specific metadata, signing certificate and actual transmitted email address
Kopexa opens, organisation is missingInvitation or auto-join setting
Organisation visible, Space missingAssigned Kopexa permissions

Change one layer at a time to isolate the cause. Retest each correction with the same intended account.

SSO and Microsoft 365 integration have different approvals

Authentication confirms an identity. A data integration needs separate permissions for the data it reads. Kopexa’s Microsoft 365 documentation describes integration separately.

For data access, assess the intended scope and requested administrator consent. Approved SSO access is no reason to accept every additional permission automatically. Record the connections as distinct measures with their own purposes and owners.

Maintain certificates in operation

Plan rotation before expiry. After updating Entra, adopt the appropriate metadata in Kopexa too. A metadata URL is not a promise of continuous automatic rotation. Microsoft describes certificate rotation, including coordination with the application.

Record owners and a review date in your access control policy. Retain the renewed sign-in test result with evidence for the access measure.

Quick answers

Frequently Asked Questions

Still have a question? Find the answers here.

Does SSO automatically import Entra security data?

No. SAML governs authentication. A data integration must be configured separately and assessed for permissions and scope.

Sources

  1. SSO with Entra ID — Kopexa [Accessed ]
  2. Organisation domains and SAML SSO — Kopexa [Accessed ]