Hydra 2.4.0 is here! Expanding Support for Windows 365 Provisioning and Hydra Agent Insights for Cloud PCs.
Read the full announcement here.

Windows 365 Management Is Getting Too Complicated: The Three-Portal Problem

April 14, 2026

The promise of “do more with less” is a common reason teams turn to Windows 365, and honestly, Microsoft delivers that. They handle compute, networking, and OS delivery, taking a good portion of the load off.

But zoom in a bit, and you’ll find things get a little trickier as IT still owns user access and policies. Meaning, at scale, IT must keep tabs across three separate Microsoft portals:

  • Microsoft 365 Admin Center for licensing
  • Microsoft Entra for identity and Conditional Access
  • Microsoft Intune for device management and provisioning

Before long, that “do more with less” promise starts to feel a lot like a part-time portal management job.

The Three-Portal Problem

Windows 365 workflows require all three portals, often simultaneously, with no unified view across them. That’s what we call the Three-Portal Problem.

Here’s what this looks like in practice: 

It’s Monday morning and your inbox is stacked with three open tickets. One user can’t access their Cloud PC, another needs a license reassigned, and a third is flagged for a Conditional Access policy issue. Three tickets…three portals… you spend the first 45 minutes of your day bouncing between tabs, copying IDs, cross-referencing settings, and piecing together context, as your coffee goes lukewarm.

If your team manages Cloud PCs at scale, you’ve likely already been in the trenches of this. Here are some more common workflows where the Three-Portal Problem crops up:

Onboarding a new user

Windows 365 is a strong candidate for contract workers, and serving as temporary devices for newly hired, or acquired employees before integrating the corporate network, not to mention as a daily desktop. Consider the steps involved:

  1. From the M365 Admin Center, licenses are purchased and assigned to the user or group.
  2. From Entra Admin Center, admins can verify the users’ membership or add them if needed.
  3. From Intune, Provisioning Policies are configured, which dictate the image, network connection, join type, and the Entra Group associated with the Cloud PC Configuration.

Mature organizations may automate this process, but don’t let that fool you. Still, to be efficient, all systems need to be configured in the right sequence, with dependencies lined up correctly. The margin for error is slim before you’re hunting across portals to find the source of the issue.

Conditional Access troubleshooting

When a user can’t connect to their Cloud PC, you don’t immediately know why. Is it a device compliance issue? A Conditional Access policy blocking authentication?  A licensing issue? Each are common issues but living in three different portals delays time to resolution.

Windows 365 Management Shouldn’t Require Three Portals

The promise of Windows 365 is speed and simplicity. No infrastructure to configure or hardware to maintain. Which is a breath of fresh air for Admins who are used to the complexity that comes with traditional on-premises VDI.

Many teams implementing Windows 365 are migrating workloads from Citrix or Omnissa Horizon. These platforms are largely built around a single administrative portal, where admins can provision desktops, manage images, troubleshoot sessions, and monitor the environment’s health. The tooling is purpose-built for how VDI teams operate.

Windows 365 Is Built Around a Different Model

Windows 365 is positioned as the Modern Management stack, designed for device management and identity, at enterprise scale. Fundamentally, this is a different model than what VDI teams are used to, and anyone coming from Citrix Studio or the Horizon Console is likely to feel that gap quickly.

And friction compounds. When an admin must get their bearings across three portals to piece together answers, naturally response times slow and details get missed. That’s not just an inconvenience. It’s a risk.

A Single Pane of Glass for Windows 365 Management

After enough time bouncing between portals, most teams start asking the same question: why isn’t there a single place to manage all of this? In IT, that concept has a name: single pane of glass (SPOG), and it’s exactly what Hydra was designed to deliver for Windows 365.

Hydra brings a unified operational layer purpose-built for Windows 365. It is designed specifically for the teams who live in these environments every day. Think of it as the missing console: sitting on top of Microsoft’s tooling and bringing everything into one place.

For teams migrating from Citrix or Omnissa, Hydra steps into the role that Citrix Studio or the Horizon Console used to fill, purpose-built for how VDI teams actually work, and designed to feel familiar from day one.

Hydra is the solution to the Three-Portal Problem. Here’s How:

Unified Windows 365 Management Console: Operate your entire Windows 365 environment without bouncing between portals. Full inventory, current status, key config details, and user-experience metrics are all in one view.

Windows 365 Image Management: Hydra brings a first-class image management workflow to Windows 365. From scheduled updates, golden image management, and full Azure Compute Gallery integration for versioning and rollback. The same pipeline VDI teams already use in Citrix or Horizon, now applied to Cloud PCs.

Real-Time Cloud PC Session Monitoring: The Hydra Agent runs directly on the Cloud PC, giving admins live resource usage and process tracking without digging through logs. Helpdesk teams can troubleshoot and shadow user sessions from the same console.

Windows 365 License Right-Sizing: Stop guessing whether users are on the right SKU. Hydra gives you a clear view of SKU performance across your fleet so you can right-size machines, catch underutilized licenses, and reclaim wasted spend before it compounds.

RBAC and Multi-Tenant Control: Scope roles by tenant or provisioning policy so teams get the access they need without exposing the entire environment. For larger enterprises and MSPs, the multi-tenant UI makes it easy to manage visibility and clone configuration across tenants.

The Bottom Line

Windows 365 is a powerful platform. However, the Three-Portal Problem is real, and it compounds over time, running counter to everything modernization is supposed to deliver.

Hydra attaches directly to existing environments. No re-architecture, and no migration projects required. And here’s a significant added benefit, if you’re already running Hydra for AVD, Windows 365 management is included at no additional cost.

Ready to see it in action? Start a 30-day free trial or request a demo today!

Hydra

Contact Us

Related Resources

Workspace Weekly: Faster Results Review in Login Enterprise 6.6
BlogMay 13, 2026

Workspace Weekly: Faster Results Review in Login Enterprise 6.6

Announcing Hydra for Microsoft Azure Virtual Desktop Hybrid: Now Available in Private Preview for Hyper-V Environments
BlogMay 12, 2026

Announcing Hydra for Microsoft Azure Virtual Desktop Hybrid: Now Available in Private Preview for Hyper-V Environments

What to Test in Windows 365: 6 Practices That Separate Top IT Teams
BlogMay 7, 2026

What to Test in Windows 365: 6 Practices That Separate Top IT Teams

Ready to see how you can transform with Login VSI?