What an Autonomous Workspace Looks Like in Practice With Omnissa

What happens when workplace technology can configure itself, repair problems, and respond to security risks before an employee opens a support ticket?

In this episode of Across the Tech Pond, David Marshall from VMblog.com, Antony Savvas from IT Europa, and I speak with Bharath Rangarajan, Chief Product Officer at Omnissa. We examine the company’s autonomous workspace vision and its three operating principles of self-configuring, self-healing, and self-securing endpoints.

Bharath explains that Omnissa coined the term several years before the generative AI boom. Its development began with telemetry agents covering laptops, phones, servers, and infrastructure. Omnissa then created distributed operational storage, an analytics data lake, and machine learning models for anomaly detection and root cause analysis. That data foundation now supports automation and AI-driven workplace operations.

The practical examples are particularly interesting. Bharath describes zero-touch PC provisioning across retail stores, automation supporting healthcare workflows, and over 10 billion workflows processed through Omnissa’s no-code Freestyle platform. He also discusses an organization that reduced help desk tickets by 50 percent and another managing hundreds of thousands of devices with two IT employees.

We also consider the limits of autonomy. Desired State Management allows organizations to define an intended outcome and correct configuration drift, but AI governance now requires input from IT, security, legal, privacy, and compliance teams. The level of acceptable automation also depends on the task. Resolving a routine support request carries a very different risk from automatically deploying a software patch across thousands of devices.

Bharath also explains Omnissa’s channel-first model, its relationships with Microsoft, Google, Apple, AWS, Azure, Nvidia, HP, and Dell, and what customers and partners can expect from Omnissa One in Orlando, Amsterdam, and Japan. The discussion closes with the growing problem of tool sprawl and Omnissa’s finding that a typical end-user computing team uses over 11 tools to manage its environment.

Which workplace decisions would you allow AI to make autonomously, and which would always need human approval? We would love to hear your thoughts.