Cloudpager now supports application deployments across Active Directory, Entra ID, and BYOD environments
Today, we’re thrilled to introduce Nimbus, an intelligent authentication capability within Cloudpager that gives IT teams greater flexibility to deploy and manage applications across physical and virtual Windows environments.
Cloudpager is all about making application packaging and management as effortless as possible. Since Cloudpager’s launch, it has natively integrated to Entra ID enabling IT teams to seamlessly provision applications to security groups and users.
With Nimbus, employees can now authenticate with their Entra ID credentials on devices that are not managed by Active Directory or Entra ID.
Here’s an overview of the different device configurations now supported by Cloudpager:
- Microsoft Entra Joined Devices: Devices that are directly managed via Entra ID.
- Microsoft Entra Hybrid Joined Devices: Devices that are joined to on-premises Active Directory (AD) and registered with Microsoft Entra ID.
- Cross-Tenant Joined Devices: Corporate devices that are joined to a different Active Directory or Entra ID tenant.
- Bring Your Own Device (BYOD): Devices that are not managed via Active Directory or Entra ID.
So, what does that mean for you?
Cloudpager Can Deploy Applications to Devices Outside Your Primary Entra ID Domain
Many of our customers are actively supporting multiple Entra ID tenants and domains. With the launch of Nimbus, they can leverage a single Cloudpager tenant to deploy and manage applications across all their business units regardless of whether they are joined to Entra ID.
Nimbus Introduces Support for BYOD Scenarios
In some cases, Active Directory and/or Entra ID may not be used to manage devices at all. It is not uncommon for organizations to rely on people accessing resources from their own devices, often referred to as Bring Your Own Device (BYOD) environments, to get their work done. A prime example is an engineering team onboarding a remote software developer on a short-term contract. These BYOD scenarios are extremely common in school districts and higher education institutions, as well!
In Rory Monaghan’s video below, you’ll see an example of a BYOD scenario where he’s provisioning applications from Cloudpager to a device that isn’t managed by Entra ID or Active Directory.
All Cloudpager requires is the latest version of the Cloudpager client and authenticating with your Entra ID credentials. All your applications are then ready to be provisioned across your enterprise.
Nimbus Drastically Simplifies Mergers and Acquisitions for IT
We have several large enterprise customers that recently completed mergers and acquisitions. This can be challenging from an IT perspective. It can take months or even years to consolidate infrastructure and domains to fully integrate newly acquired firm’s systems and employees. During this period, while you may have a master Entra ID tenant, you’re stuck with a series of lingering Entra tenants and domains.
The optimal state is a single pane of glass to manage applications across their existing Entra ID joined devices, as well as all the new physical and virtual desktops from the new companies they are onboarding to the systems, regardless of which Active Directory or Entra ID tenant they are managed by (if at all).
Cloudpager now offers a way for you to provide an Entra ID account to these employees and start provisioning application containers to them on their existing Windows desktops. No need to spin up full-fledged virtual desktops or sessions hosts, the applications can be delivered directly to their desktops and start menus via Cloudpager Workpods.
Conclusion
Nimbus enables Cloudpager customers to streamline application management more than ever. By extending application management capabilities to Windows endpoints outside your primary Entra ID tenant, you gain a single pane of glass for orchestrating application deployments to your entire company, regardless of whether they are managed by Active Directory or Entra ID.
