Notifications
Clear all
Topic starter
09/07/2026 3:18 pm
TL;DR: Remote workspace platforms are being pulled deeper into cloud governance and cost management as Microsoft Marketplace updates add Linux desktop deployment, Azure NCv6 support, improved Azure Managed Identities handling, and automated Azure Center creation for regional inventory and power-state control, according to Leostream. The practical question is no longer remote access alone, but which identity, inventory, and control boundaries the platform now owns versus the customer.
NHIMG editorial — what this means for NHI practitioners
Questions worth separating out
Q: How should teams govern managed identities used by remote desktop platforms?
A: Treat managed identities as privileged non-human identities, not backend convenience.
Q: Why do remote desktop platforms create identity governance risk even without secret exposure?
A: Because the platform can still hold delegated authority over inventory, provisioning, and power-state operations.
Q: What do security teams get wrong about managed identities in cloud workspace tooling?
A: They often assume managed identities are inherently low risk because no password is stored.
Practitioner guidance
- Inventory every managed identity used by the platform Document the Azure roles and resource scopes assigned to each managed identity, then recertify them after each region, workload, or feature expansion.
- Add Linux desktop lifecycle checkpoints Require provisioning approval, teardown verification, and access review for Linux desktop deployments so manual configuration shortcuts do not become permanent control gaps.
- Separate inventory control from session authorisation Assign distinct ownership for platform inventory, regional Azure Center creation, and who can approve access policy changes to prevent implicit privilege accumulation.
What's in the full announcement
Leostream's full article covers the operational detail this post intentionally leaves for the source:
- Marketplace deployment specifics for Azure customers using GPU-accelerated virtual machines and Linux desktops.
- The regional Azure Center automation details that affect inventory visibility and power-state management.
- How improved Azure Managed Identities support changes the administrative workflow for hosted desktops and workstations.
- The platform positioning around high-performance computing, virtual desktops, and workstation administration in Azure.
👉 Read Leostream's Marketplace update on Azure remote desktop and Linux desktop support →
Azure remote desktop governance: what do the latest updates change?
Explore further
09/07/2026 3:36 pm
Remote desktop orchestration is becoming an identity governance layer. Platforms that broker access to cloud workstations now influence entitlement, inventory, and infrastructure control in the same transaction. That means IAM teams can no longer treat the connection broker as a neutral transport component. The practical conclusion is that remote access tooling now belongs inside identity governance reviews, not just endpoint or cloud operations.
A few things that frame the scale:
- 96% of organisations store secrets outside of secrets managers in vulnerable locations including code, config files, and CI/CD tools, according to Ultimate Guide to NHIs.
- Only 5.7% of organisations have full visibility into their service accounts, which means most teams cannot confidently inventory every delegated identity in their environment.
A question worth separating out:
Q: Who is accountable when a remote access platform can inventory and control cloud workstations?
A: Accountability sits with the team that approves the delegated Azure roles, the team that owns the remote access platform, and the platform operators who can alter access paths. If those responsibilities are not separated, privilege becomes implicit and difficult to audit.
👉 Read our full editorial: Leostream Marketplace updates tighten Azure remote desktop governance
