Imprivata Virtual Desktop Access

Name: Imprivata Virtual Desktop Access
Brand: Imprivata
Rating: 4.5 (118 reviews)

Simple and secure access management for mission-critical industries

Est 2000|Valuation $492.5M|Raised $2.6B

LinkedIn 28K|Website|Web traffic 466K|FTEs 833|HQ Waltham, Massachusetts, US

MarketsIdentity Provider (IdP) & SSO Identity Provider (IdP) & Single Sign-On (SSO)

Published May 16, 2026

01Common complaints

- If the organization does not require shared-workstation roaming workflows: for primarily personal-device use cases, a cloud-first identity provider (Entra ID/Okta/Ping) may be more appropriate. - If the primary need is SCIM-driven lifecycle automation and SaaS governance: Okta/Entra combined with identity governance tools are often stronger. - If the VDI environment is highly heterogeneous or unstable: VDA relies on predictable VDI images, broker configurations, and endpoint standards. - For budget-constrained deployments without clear ROI: community feedback frequently notes perceived expense; consider native VDI platform features and modern passwordless approaches first. - If transparent public pricing and easy self-serve trials are required: Imprivata is primarily enterprise- and partner-sold.

Deal disqualifiers (poor fit)

Environments with mostly personal devices and minimal shared workstations
Low tolerance for agent-based tooling or complex multi-vendor VDI integration
Very small clinics where Windows Hello for Business and Entra ID SSO may meet requirements at lower complexity and cost

Limitations implied by architecture

Agent dependency: Requires agent installation on endpoints and VMs, increasing operational overhead.
Multi-vendor integration risk: Troubleshooting often spans Imprivata, Citrix/Omnissa/Microsoft components, thin client operating systems, and EHR integrations.

Roadmap / "what's new" signals

Release notes indicate ongoing work in VDA support across Citrix, Azure Virtual Desktop, MRDS, and VMware Horizon, plus configuration options for auto-launch desktop selection.
Public roadmap PDFs exist but may be dated; verify current roadmap details with the account team.

Security/compliance gaps

Public certification status is not consolidated in a single downloadable page. Organizations should request:
- SOC 2 Type II report
- ISO 27001 certificate scope statement
- Data processing addendum (DPA) and subprocessor list (if applicable)

Where it struggles

Environments with complex Citrix StoreFront/FAS/virtual channel policy interactions can cause "SSO INACTIVE"-type issues (community reports).
Shared device lock/unlock transitions have been reported to create unexpected application behavior (for example, browser closure on lock reported in 2026).

02Why they buy

Reported by customer feedback (not just vendor claims)

Multiple practitioners report that badge tap workflows operate smoothly once deployed in hospital environments.
Some reviewers and peers report operational reliability in production environments; for example, a Gartner reviewer described the product as "rock solid" in their experience.

Differentiation

Focus on clinical workflow speed and shared workstation scenarios rather than only generic SSO capabilities.
Broad support for thin/zero clients and roaming "follow-me" desktop patterns.

Where competitors have advantages

Okta/Entra: breadth of modern SaaS integrations, conditional access, and lifecycle automation.
Native VDI vendors: tighter control over end-to-end brokering and session stack.

Why customers chose it

Common decision drivers reported across reviews and discussions:

Shared workstation workflows (fast tap-in/out, roaming sessions, and reduction in repetitive credential entry)
Healthcare alignment (integration patterns with EHR workflows, auditability)
VDI ecosystem integration (Citrix and Horizon support; partnerships with thin/zero client vendors)

03Field reports

Review platforms (Gartner Peer Insights, G2, Capterra, PeerSpot)

**Gartner Peer Insights (Imprivata Enterprise Access Management):** - Some reviewers report positive operational experience. For example, a reviewer in early 2026 described EAM with phrases such as "rock solid" and "it just works," and noted reduced password entry; the same reviewer also flagged that agent upgrades remain time-intensive. **G2 (Imprivata Enterprise Access Management / OneSign reviews page):** - Reviews include positive feedback about simplifying multiple logins, but also mention scenarios where password changes required manual updates in some cases, indicating potential friction depending on application profile design. **Capterra (Imprivata OneSign):** - Verified reviews provide sentiment sampling; VDA-specific experiences may be mixed into broader OneSign/EAM feedback. **PeerSpot:** - PeerSpot summaries emphasize stability and support in some accounts, with anecdotal reports of extended rollouts at large scale. These are directional; validate with reference calls.

Community/social (Reddit)

Recurring practitioner discussion themes: - **Perceived value in healthcare workflows:** Multiple threads describe badge tap workflows functioning smoothly once deployed in hospital settings. - **Expense concerns:** Some users describe Imprivata as expensive, particularly if only used for badge authentication without broader SSO/workflow features. - **Operational issues and environment-specific quirks:** Examples reported by practitioners include: - Horizon-related posts where desktops appear with the agent in a disabled state, requiring capacity or spare VM strategies to avoid token expiry issues. - A sysadmin post in early 2026 describing browser closure on lock/sign-in transitions on shared computers, while still indicating an overall positive experience in that specific account. - Citrix-focused threads in recent months reporting "SSO INACTIVE" in a test environment and pointing to Citrix policy requirements (virtual channel allowance) and documentation.

Why some customers leave / don’t purchase

Signals from community discussions and review snippets include: - Cost-to-scope mismatch: Organizations that only need modern cloud SSO (SAML/OIDC) often choose cloud-native identity providers instead. - Agent-heavy architecture: Some organizations prefer cloud-forward identity stacks that minimize endpoint or image agents. - Integration rigidity: At least one practitioner reported challenges chaining to other security providers for certain MFA/SSO needs (anecdotal; validate during procurement).

Vendor-published examples (useful but not independently validated)

Vendor materials cite multiple healthcare organizations adopting the no-click access workflow for roaming desktops and claim clinician productivity improvements.
A partner-authored case study describes bedside EMR access enabled by virtualized desktops; this collateral is vendor- or partner-authored and should be validated.

Vendor survey / productivity metrics (methodology caveats)

A vendor-conducted survey reported average time-savings metrics (for example, a cited per-user time-savings figure based on a modest respondent pool).

Critical note:

These are vendor-sponsored findings; methodology summaries are limited in the public release. Organizations should treat vendor-provided productivity numbers as hypotheses and consider running their own time-motion or pilot studies to validate operational impacts.

04Best fit

Company sizes

Most aligned with:

Mid-market to large healthcare providers (organizations at a mid-market to enterprise scale)
Multi-site environments with heavy shared endpoints: hospitals, emergency departments, perioperative areas, and inpatient units

Industries / verticals

Primary: Healthcare and provider organizations; secondary: other regulated environments with shared workstations

Roles and personas

Decision makers: CIO, CISO, VP Infrastructure, VP Clinical Informatics
Buyers/influencers: End-user computing (EUC) / VDI leads, identity & access management teams, clinical engineering
End users: Nurses, physicians, allied health professionals, pharmacists

Primary pain points addressed

Multiple logins on shared workstations
Slow session switching between rooms/devices
Audit and compliance requirements for access to protected health information (PHI)
Password reset burden (when using broader EAM SSO capabilities)

Qualification criteria (good fit)

Organizations with Citrix / Omnissa Horizon / MRDS/AVD deployed in clinical areas
Heavy shared device usage requiring fast user switching
Willingness to deploy and maintain endpoint and VDI agents and to operate a disciplined image management process

05The pitch

What the product does (core value proposition)

Imprivata Virtual Desktop Access (VDA) is a virtual-desktop login automation and session-roaming component of Imprivata Enterprise Access Management (EAM, formerly OneSign). It is designed to reduce repetitive manual logins when clinicians (or other shared-workstation users) access Citrix, Omnissa Horizon (formerly VMware Horizon), and Microsoft Remote Desktop/Azure Virtual Desktop environments—typically via badge tap and/or biometric authentication—and then chain into single sign-on (SSO) for downstream applications. The vendor describes a feature called "no-click access" (badge/biometric tap-in) to launch the virtual desktop and provide continued SSO inside the session, together with centralized access management and audit logs.

Target market and market positioning

Primary market: Healthcare delivery organizations (hospitals, clinics, integrated delivery networks) running shared workstations, carts, thin/zero clients, and VDI.
Positioning: The vendor presents the product as workflow-oriented access security for mission- and life-critical environments where rapid access is important, focusing on roaming sessions, shared endpoints, and regulatory pressure (HIPAA/HITECH, EPCS, auditability).

Get a comprehensive analysis of Imprivata Virtual Desktop Access including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published May 16, 2026

01Common complaints

If the organization does not require shared-workstation roaming workflows: for primarily personal-device use cases, a cloud-first identity provider (Entra ID/Okta/Ping) may be more appropriate.
If the primary need is SCIM-driven lifecycle automation and SaaS governance: Okta/Entra combined with identity governance tools are often stronger.
If the VDI environment is highly heterogeneous or unstable: VDA relies on predictable VDI images, broker configurations, and endpoint standards.
For budget-constrained deployments without clear ROI: community feedback frequently notes perceived expense; consider native VDI platform features and modern passwordless approaches first.
If transparent public pricing and easy self-serve trials are required: Imprivata is primarily enterprise- and partner-sold.

Deal disqualifiers (poor fit)

Environments with mostly personal devices and minimal shared workstations
Low tolerance for agent-based tooling or complex multi-vendor VDI integration
Very small clinics where Windows Hello for Business and Entra ID SSO may meet requirements at lower complexity and cost

Limitations implied by architecture

Agent dependency: Requires agent installation on endpoints and VMs, increasing operational overhead.
Multi-vendor integration risk: Troubleshooting often spans Imprivata, Citrix/Omnissa/Microsoft components, thin client operating systems, and EHR integrations.

Roadmap / "what's new" signals

Release notes indicate ongoing work in VDA support across Citrix, Azure Virtual Desktop, MRDS, and VMware Horizon, plus configuration options for auto-launch desktop selection.
Public roadmap PDFs exist but may be dated; verify current roadmap details with the account team.

Security/compliance gaps

Public certification status is not consolidated in a single downloadable page. Organizations should request:
- SOC 2 Type II report
- ISO 27001 certificate scope statement
- Data processing addendum (DPA) and subprocessor list (if applicable)

Where it struggles

Environments with complex Citrix StoreFront/FAS/virtual channel policy interactions can cause "SSO INACTIVE"-type issues (community reports).
Shared device lock/unlock transitions have been reported to create unexpected application behavior (for example, browser closure on lock reported in 2026).

02Why they buy

Reported by customer feedback (not just vendor claims)

Multiple practitioners report that badge tap workflows operate smoothly once deployed in hospital environments.
Some reviewers and peers report operational reliability in production environments; for example, a Gartner reviewer described the product as "rock solid" in their experience.

Differentiation

Focus on clinical workflow speed and shared workstation scenarios rather than only generic SSO capabilities.
Broad support for thin/zero clients and roaming "follow-me" desktop patterns.

Where competitors have advantages

Okta/Entra: breadth of modern SaaS integrations, conditional access, and lifecycle automation.
Native VDI vendors: tighter control over end-to-end brokering and session stack.

Why customers chose it

Common decision drivers reported across reviews and discussions:

Shared workstation workflows (fast tap-in/out, roaming sessions, and reduction in repetitive credential entry)
Healthcare alignment (integration patterns with EHR workflows, auditability)
VDI ecosystem integration (Citrix and Horizon support; partnerships with thin/zero client vendors)

03Field reports

Review platforms (Gartner Peer Insights, G2, Capterra, PeerSpot)

Gartner Peer Insights (Imprivata Enterprise Access Management):

Some reviewers report positive operational experience. For example, a reviewer in early 2026 described EAM with phrases such as "rock solid" and "it just works," and noted reduced password entry; the same reviewer also flagged that agent upgrades remain time-intensive.

G2 (Imprivata Enterprise Access Management / OneSign reviews page):

Reviews include positive feedback about simplifying multiple logins, but also mention scenarios where password changes required manual updates in some cases, indicating potential friction depending on application profile design.

Capterra (Imprivata OneSign):

Verified reviews provide sentiment sampling; VDA-specific experiences may be mixed into broader OneSign/EAM feedback.

PeerSpot:

PeerSpot summaries emphasize stability and support in some accounts, with anecdotal reports of extended rollouts at large scale. These are directional; validate with reference calls.

Community/social (Reddit)

Recurring practitioner discussion themes:

Perceived value in healthcare workflows: Multiple threads describe badge tap workflows functioning smoothly once deployed in hospital settings.
Expense concerns: Some users describe Imprivata as expensive, particularly if only used for badge authentication without broader SSO/workflow features.
Operational issues and environment-specific quirks: Examples reported by practitioners include:
- Horizon-related posts where desktops appear with the agent in a disabled state, requiring capacity or spare VM strategies to avoid token expiry issues.
- A sysadmin post in early 2026 describing browser closure on lock/sign-in transitions on shared computers, while still indicating an overall positive experience in that specific account.
- Citrix-focused threads in recent months reporting "SSO INACTIVE" in a test environment and pointing to Citrix policy requirements (virtual channel allowance) and documentation.

Why some customers leave / don’t purchase

Signals from community discussions and review snippets include:

Cost-to-scope mismatch: Organizations that only need modern cloud SSO (SAML/OIDC) often choose cloud-native identity providers instead.
Agent-heavy architecture: Some organizations prefer cloud-forward identity stacks that minimize endpoint or image agents.
Integration rigidity: At least one practitioner reported challenges chaining to other security providers for certain MFA/SSO needs (anecdotal; validate during procurement).

Vendor-published examples (useful but not independently validated)

Vendor materials cite multiple healthcare organizations adopting the no-click access workflow for roaming desktops and claim clinician productivity improvements.
A partner-authored case study describes bedside EMR access enabled by virtualized desktops; this collateral is vendor- or partner-authored and should be validated.

Vendor survey / productivity metrics (methodology caveats)

A vendor-conducted survey reported average time-savings metrics (for example, a cited per-user time-savings figure based on a modest respondent pool).

Critical note:

These are vendor-sponsored findings; methodology summaries are limited in the public release. Organizations should treat vendor-provided productivity numbers as hypotheses and consider running their own time-motion or pilot studies to validate operational impacts.

04Best fit

Company sizes

Most aligned with:

Mid-market to large healthcare providers (organizations at a mid-market to enterprise scale)
Multi-site environments with heavy shared endpoints: hospitals, emergency departments, perioperative areas, and inpatient units

Industries / verticals

Primary: Healthcare and provider organizations; secondary: other regulated environments with shared workstations

Roles and personas

Decision makers: CIO, CISO, VP Infrastructure, VP Clinical Informatics
Buyers/influencers: End-user computing (EUC) / VDI leads, identity & access management teams, clinical engineering
End users: Nurses, physicians, allied health professionals, pharmacists

Primary pain points addressed

Multiple logins on shared workstations
Slow session switching between rooms/devices
Audit and compliance requirements for access to protected health information (PHI)
Password reset burden (when using broader EAM SSO capabilities)

Qualification criteria (good fit)

Organizations with Citrix / Omnissa Horizon / MRDS/AVD deployed in clinical areas
Heavy shared device usage requiring fast user switching
Willingness to deploy and maintain endpoint and VDI agents and to operate a disciplined image management process

05The pitch

What the product does (core value proposition)

The vendor describes a feature called "no-click access" (badge/biometric tap-in) to launch the virtual desktop and provide continued SSO inside the session, together with centralized access management and audit logs.

Target market and market positioning

Primary market: Healthcare delivery organizations (hospitals, clinics, integrated delivery networks) running shared workstations, carts, thin/zero clients, and VDI.
Positioning: The vendor presents the product as workflow-oriented access security for mission- and life-critical environments where rapid access is important, focusing on roaming sessions, shared endpoints, and regulatory pressure (HIPAA/HITECH, EPCS, auditability).

Get a comprehensive analysis of Imprivata Virtual Desktop Access including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →