Keeper Security launches privileged access controls in Microsoft Teams

Keeper Security has released the Keeper Teams App, a new Microsoft Teams integration that lets users request, approve and manage privileged access without leaving the chat platform. The launch is meant to reduce credential risk, preserve zero-trust controls and keep access workflows auditable for security teams.

Why it matters: - Keeper Security is pushing privileged access management closer to where employees already work, which can reduce the urge to bypass controls when access requests feel too slow. - The Teams-based workflow is designed to preserve zero-standing privilege and keep credentials out of Keeper’s cloud, which matters for organisations trying to tighten auditability without adding friction.

What happened: - Keeper Security announced the availability of the Keeper Teams App on June 25, 2026. - The new integration brings privileged access request and approval workflows directly into Microsoft Teams. - The app is powered by Keeper Secrets Manager and Commander Service Mode. - The launch extends Keeper’s workflow integrations after earlier rollouts with Jira, ServiceNow and Slack.

The details: - The Keeper Teams App lets users initiate and approve privileged access actions inside Teams across five core workflows. - Record and Folder Access Requests support justification, custom permissions and time-limited access windows. - Requests involving PAM User records or PAM User folders include an auto-rotation option that is enabled by default for approvers. - When a time-limited access window ends, credentials automatically rotate on the vault side. - One-Time Share Requests create self-destructing share links for passwords or secrets, with optional editable and bi-directional sharing. - Keeper Endpoint Privilege Manager approvals route just-in-time elevation requests to approvers in real time through a dedicated Teams channel. - SSO Cloud device approvals can be handled directly in Teams when the Keeper Automator service is not deployed. - Self-Service Secret Creation lets users create new login records with auto-generated passwords from Teams. - Created records are saved to a designated shared folder in the Keeper Vault and support Nested Shared Folder records. - Users can choose a Classic or NSF target folder, select a subfolder and create secrets, while the app detects the correct permission model automatically. - Search results identify whether an item is a Classic shared record or an NSF record. - The approval interface shows standard permissions for Classic items and role-based NSF permissions for NSF items, including viewer, share-manager, content-manager and full-manager. - The app is customer-hosted and deployed via Docker alongside Commander Service Mode on the customer’s own infrastructure. - No credentials or secrets pass through Keeper’s cloud. - Configuration is secured and retrieved via Keeper Secrets Manager. - A streamlined teams-app-setup command in Keeper Commander automates setup for faster deployment. - The app is available now for organisations with a Keeper Secrets Manager or KeeperPAM license. - Setup documentation is available at docs.keeper.io. - More information on KeeperPAM is available at KeeperSecurity.com.

Between the lines: - Keeper is positioning Microsoft Teams as a control point for privileged access, not just a place where requests are discussed. - The customer-hosted design reinforces Keeper’s zero-knowledge model by keeping cryptographic operations and secret data inside the customer environment. - The company is also signaling a broader strategy: embed governance inside collaboration and IT tools instead of making users jump between separate portals.

What’s next: - Organisations using Microsoft Teams and Keeper’s licenses can deploy the app now. - Security teams that want tighter access controls may use the Teams workflow to replace email chains, tickets and portal-based approvals. - Keeper’s ecosystem of embedded workflows is likely to keep expanding as the company adds more integrations around privileged access governance.

The bottom line: - Keeper Security wants privileged access approvals to happen where work already happens, while keeping credentials controlled, auditable and outside its cloud.