Does Key2XS replace Microsoft Entra ID or iLOQ?

No. Key2XS is middleware. Entra ID remains the identity platform, iLOQ remains the locking system. Key2XS connects the two.

Does Key2XS work with on-premises Active Directory synchronized to Entra ID?

Yes. Key2XS reads identities and group memberships from Entra ID, so users synchronized from on-premises Active Directory through Entra Connect are handled like any other Entra ID identity.

What happens to physical keys when a user is disabled in Entra ID?

Key2XS withdraws the person's iLOQ key rights in near real-time as part of the same flow. Physical and digital access are revoked together, and the revocation is logged.

How long does a Microsoft Entra ID iLOQ integration take?

A standard integration is live in under two hours. Key2XS connects to Entra ID and iLOQ through pre-built connectors, so no custom development is required.

Is the Entra ID iLOQ integration suitable for NIS2 and CER compliance?

Yes. Both directives require governed, auditable control over physical access to premises. Key2XS provides the policy enforcement and audit trail that connects the Entra ID lifecycle to physical keys.

Microsoft Entra ID iLOQ Integration

Your identity lifecycle stops at the front door

Almost every organization already lives in Entra ID. Accounts are created when people join, group memberships change when they switch roles, and everything is disabled the moment they leave. That lifecycle governs email, files and applications reliably.

Physical keys sit outside it. The person who disables a leaver’s account in Entra ID is usually not the person who manages the key cabinet, and the two actions rarely happen on the same day. In practice this means:

Leavers whose account is blocked but whose keys still open every door
Contractors with long-expired engagements holding active keys
Role changes that update application access but not building access
No single place to answer “who can physically enter this location, and why”

For critical entities under NIS2 and the CER Directive, that gap between digital and physical access is exactly what regulators expect you to close.

Group-based physical access, the Entra ID way

Key2XS is middleware that treats iLOQ key rights the way Entra ID treats application access: assigned through groups, driven by lifecycle events, and always auditable.

How it works

Connect. Key2XS connects to your Entra ID tenant and your iLOQ environment through their standard APIs. A standard integration is live in under two hours, with no custom development.
Map. Entra ID groups and roles are mapped to iLOQ key rights and lock groups. A security group like “Facilities - Technical Rooms” can correspond to exactly those doors and cylinders in iLOQ, in the same way it would grant an application role.
Orchestrate. When a user is added to or removed from a mapped group, or their account is disabled, Key2XS applies the change to their iLOQ key rights in near real-time. Blocking a leaver in Entra ID withdraws their physical access in the same movement.
Prove. Every key right traces back to an identity, a group and a moment in time, in one tamper-evident audit trail.

What synchronizes between Entra ID and iLOQ

From Microsoft Entra ID	To iLOQ via Key2XS
Users (joiners, movers, leavers)	Key holders created, updated or deactivated
Group and role memberships	Key rights and access to lock groups
Account disablement and expiration	Immediate withdrawal of key rights
Assignment history	Documented authorization behind every key

Changes flow through in near real-time, so revoking access in Entra ID does not wait for a nightly batch to reach your keys.

Built for critical environments

Key2XS is used where physical access affects public safety, service continuity or regulatory compliance: utilities, government, transport, healthcare and industry.

NIS2 and CER ready. A continuous, tamper-evident audit trail links every physical access right to an identity and a policy decision.
Built for continuity. The Key2XS platform is engineered for 99.99% availability, matching the uptime expectations of critical infrastructure operations.
Security by design. All communication between Key2XS, Entra ID and iLOQ is encrypted in transit with TLS 1.3, and data at rest is protected with AES-256.
Non-disruptive. Key2XS orchestrates access rights through the iLOQ management interface. Your locking plan, locks and keys remain untouched.

Why not build this yourself?

Entra ID has a powerful Graph API, and iLOQ has an API too, so a custom integration is technically possible. In practice it means owning connector code against two evolving APIs, building your own audit layer, handling every edge case in the joiner-mover-leaver flow, and maintaining it all for years. Key2XS delivers this as a maintained platform:

Live in under 2 hours. A standard Entra ID to iLOQ integration is up and running in under two hours, not weeks or months
Maintained connectors that absorb API changes on both sides
Purpose-built audit and reporting for physical access governance
Certified by ASSA ABLOY for its locking system integrations, and a certified SailPoint Technology Alliance Partner on the IAM side
Support for additional IAM systems (SailPoint, Okta, One Identity, OpenText) and key systems (ASSA ABLOY eCLIQ and PROTEC) from the same platform, so your architecture is not locked to one vendor pairing

Manage iLOQ keys from Microsoft Entra ID