Microsoft Entra
Microsoft Entra ID is Microsoft's cloud identity and access management platform for employee, partner, and application access. In Keynius projects, it is relevant when locker access needs to align with an organization's Microsoft identity environment, user groups, SSO policies, and joiner-mover-leaver processes.
Services
- Single sign-on alignment
- Identity and access management
- User lifecycle and group-based access support
- Conditional access policy alignment
- Enterprise user governance
Industries
- Corporate Workspace
- Healthcare
- Education
- Government
- Industrial & Logistics
Why Keynius + Microsoft Entra ID matters
Keynius plus Microsoft Entra ID helps organizations connect smart locker access to the same identity foundation already used for Microsoft 365, SaaS applications, and workplace systems. Instead of managing locker users as a separate list, organizations can align access with verified users, groups, policies, and offboarding workflows. This is especially valuable for enterprise workplaces, hospitals, campuses, government sites, and industrial environments where locker access should follow the same governance model as other business-critical systems.
Compatibility
- Keynius Portal user management
- SSO-enabled locker administration
- Group or role-based locker policy design
- Microsoft identity environment
Access Methods
- SSO
- Web Browser Login
- Mobile App
- RFID
- PIN
Integration
- SSO
- Identity federation
- User provisioning pattern
- Group-based authorization
Best For
- Enterprise employee lockers
- Shared workplace storage
- Healthcare staff lockers
- Education campuses
- Regulated organizations
Integration Enablement
- Use Entra ID as the identity source for eligible locker users and administrators.
- Map user groups, departments, or roles to Keynius locker access policies where the project requires it.
- Reduce manual offboarding risk by aligning locker access with enterprise identity lifecycle controls.
Sample Use Cases
- Hybrid office lockers assigned based on employee identity and group membership.
- Healthcare staff storage where access must change when employees move teams or leave the organization.
- Campus or government locker access where SSO and centralized identity governance are mandatory.
Integration Enablement
Step 1
Confirm the Entra tenant, user groups, and Keynius user roles needed for the locker workflow.
Step 2
Agree whether the project requires SSO only, provisioning, group mapping, or a hybrid approach.
Step 3
Configure application registration, redirect URLs, claims, and allowed users with the customer's IT team.
Step 4
Map Entra groups or attributes to Keynius access policies and test joiner, mover, and leaver scenarios.
Step 5
Document support ownership for identity changes, failed logins, and emergency access exceptions.
Technical Requirements
Software
- Keynius platform with SSO/API configuration in scope
- Microsoft Entra tenant
- Supported SAML/OIDC or identity integration pattern as agreed
- Exact provisioning scope to be confirmed per customer
Network
- HTTPS/TLS 1.2 or higher
- Outbound port 443 from the Keynius integration environment
- Firewall allowlisting for partner API endpoints where required
- Stable internet connection for locker controllers, payment devices, or access readers in scope
Credentials
- Entra administrator access
- Keynius administrator access
- Application registration credentials or metadata
- Approved test users and groups
Data and governance
- Use least-privilege application permissions
- Confirm claims, group mappings, and retention needs
- Test deprovisioning before go-live
- Keep emergency override process outside normal user SSO dependency
Need help with the Integration?
Our integration specialists are ready to guide you through the setup process.
%201.svg){kind=logo}
%201.svg){kind=icon}
