Just-In-Time (JIT) provisioning
Automatically create a Keeper Vault when a user first signs in through Entra ID, with the default role policies configured for their Keeper node.
Connect Microsoft Entra ID to Keeper to simplify sign-in, automate provisioning and secure access to machines and databases. Extend protection across your Azure environment with remote desktop connections, Entra ID database authentication and automated credential rotation.

Keeper SSO Connect Cloud lets users sign in to their Keeper Vault through Microsoft Entra ID using SAML 2.0. Employees use their existing sign-in experience while Keeper maintains zero-knowledge encryption.
Automatically create a Keeper Vault when a user first signs in through Entra ID, with the default role policies configured for their Keeper node.
Use the authentication methods and access policies configured for the Keeper enterprise application in Entra ID.
Log in through Entra with Windows Hello, Microsoft Authenticator or FIDO2 passkey.
Start sign-in from Keeper or launch Keeper from your identity provider's application dashboard.
Reach your Keeper Vault even when SSO isn't available.
Connect Entra ID to the Keeper Admin Console through SCIM to provision users and teams, update account information and manage access as employees join, change roles or leave.
Lock Keeper accounts when Entra ID sends a deprovisioning update through SCIM. Access changes follow your configured provisioning process.
Create Keeper accounts and map Entra ID groups to Keeper teams. Automatically update team membership as directory assignments change.
Assign shared folders to Keeper teams so users receive access to the credentials and resources their team needs.
Zero knowledge means new users and teams need a key exchange before provisioning is finished. The Automator service handles it, so no admin approves each one by hand.
Connect to supported SQL Server databases with Microsoft Entra ID authentication. Keeper supports browser-based sign-in and Entra access tokens, allowing users to authenticate with their individual identities.
Launch a configured database connection from the Keeper Vault and sign in through Microsoft. The browser-based authentication flow supports MFA.
Connect to Azure SQL from KeeperDB Desktop using Microsoft Entra ID instead of a stored database password. Users authenticate through Microsoft and access the database with their assigned permissions.
Use KeeperDB Proxy to access configured PAM Database resources from native database clients. Supported Entra ID authentication methods also apply to these connections.
Launch remote desktop connections to Azure Windows virtual machines directly from the Keeper Vault. The Keeper Gateway connects to the target machine, while Keeper permissions control who can launch the session.
Open an RDP session to a configured Azure Windows VM from its PAM Machine record, giving users a central place to access authorized machines.
Share machine connections with employees and contractors without giving them direct access to the linked administrative credentials.
Enable graphical session recording and keystroke capture for review. Configure supported launch credentials to rotate automatically when a session ends.
Use KeeperPAM to rotate supported Entra ID and Azure credentials. Manage rotation schedules centrally and keep updated credentials in the Keeper Vault.
Rotate supported Entra ID user passwords, Azure VM account credentials and Azure-managed database credentials through the Keeper Gateway.
Use Keeper's built-in Azure Client Secret SaaS rotation plugin to rotate client secrets for Azure app registrations. Run rotation on a schedule or on demand, and automatically update the stored secret in Keeper.
Automatically push updated secrets from Keeper to Azure Key Vault with Universal Secrets Sync. Applications can continue retrieving secrets through their existing Azure Key Vault integration.
Extend your integration with audit reporting and configuration options for Azure Government environments.
Configure Azure authentication and Microsoft Graph endpoints for supported credential rotation in Azure Government and other sovereign cloud environments.
Use Advanced Reporting & Alerts to monitor Keeper activity, create custom reports and send events to supported SIEM platforms.
Point a Keeper node at each Entra directory and run several side by side.
Simplify employee sign-in, automate account management and secure access to Azure machines, databases and application secrets.
Keeper connects to Microsoft Entra ID for single sign-on and automated user and team provisioning. With KeeperPAM, organizations can also secure infrastructure connections, authenticate to supported databases through Entra ID and rotate supported Azure credentials and application client secrets.
Yes, Keeper supports Microsoft Entra ID authentication for Azure SQL through KeeperDB Desktop and configured KeeperPAM database connections. Users can complete Microsoft sign-in in their browser or provide an Entra access token. They must have the required access in the target database.
Yes, KeeperPAM supports RDP connections to Azure Windows virtual machines from the Keeper Vault. Administrators can grant connection access without exposing linked credentials and enable session recording for review.
Yes, Keeper's built-in Azure Client Secret SaaS rotation plugin supports scheduled and on-demand rotation. Keeper updates the stored secret after rotation completes.
When Entra ID sends a deprovisioning update through SCIM, Keeper locks the user's account. The timing depends on when Entra processes and delivers the provisioning update.
Yes, through KeeperPAM, the KeeperPAM Gateway rotates directory users, Azure-managed SQL and MySQL databases, application secrets and service accounts using the Microsoft Graph API, and can push the new values to Azure Key Vault with Universal Secrets Sync.
Yes, Keeper supports both commercial Entra at portal.azure.com and Azure Government Cloud at portal.azure.us, and honors your Entra conditional access policies.
您必须启用 Cookie 才能使用在线聊天。