Microsoft shipped two Windows 365 updates the week of July 13, 2026, and both are about making Cloud Apps and provisioning policy management more flexible, more precise, and less dependent on workarounds. One breaks Cloud Apps free from Start menu–only discovery; the other reorganizes the provisioning policy experience in Intune with a tabbed layout that brings devices, actions, and apps together in one place.

Let’s break down what’s new, why it matters, and what you should do about it.

1. Add Cloud Apps from a File Path (Public Preview)

The Problem It Solves

Windows 365 Cloud Apps — which let you stream individual applications from Cloud PCs instead of full desktops — has been a game-changer for frontline and shift-based workers. But since its initial preview, app discovery has been tied to the Start menu. Cloud Apps could only find and publish executables that registered themselves in the device image’s Start Menu, and only for Win32 apps (APPX/MSIX support came later).

This created several pain points:

  • No Start menu shortcut, no Cloud App. Legacy LOB applications, utility executables, and tools installed in custom directories were invisible to Cloud Apps discovery.
  • One executable, one Cloud App. You couldn’t publish the same binary as multiple Cloud Apps with different configurations — say, a CRM client pointed at test vs. production environments.
  • No command-line parameter support. If your app needed specific startup arguments, you were out of luck — you’d need separate images or scripts to handle different run modes.
  • Image dependency. Getting an app to appear in Cloud Apps often meant modifying the device image just to create a Start menu shortcut, adding complexity to image management.

What’s New

Admins can now manually add Cloud Apps by specifying a file path to an executable on the Cloud PC image. This public preview capability unlocks:

  • File path targeting — Point directly to any executable path, like C:\Program Files\Vendor\App\app.exe or D:\LOBApps\MyTool\tool.exe. No Start menu entry required.
  • Command-line parameters — Pass startup arguments to the executable. Create “CRM – Production” with app.exe /env:prod and “CRM – Test” with app.exe /env:test — same binary, two different Cloud Apps.
  • Duplicate app entries — Publish the same executable multiple times with different names, descriptions, icons, and parameters. This is huge for multi-tenant, multi-region, or multi-environment scenarios.
  • Custom app properties — Define display name, description, and icon at creation time, aligned with business function rather than whatever the executable’s metadata says.

How It Works

The file path workflow builds on the existing Cloud Apps architecture:

  1. The executable must be present on the Cloud PC image (gallery or custom) at the specified path.
  2. Cloud Apps run on Windows 365 Flex Cloud PCs in shared mode, streaming only the app window to users.
  3. Apps are tied to a Cloud Apps–type provisioning policy with the “Access only apps” experience type.
  4. Once added, the Cloud App behaves like any other — it can be published, unpublished, and assigned to user groups.

The key shift is from automatic discovery (system scans Start menu) to manual registration (admin specifies the path and properties). This doesn’t replace Start menu discovery — both mechanisms coexist — but it fills the gaps that Start menu–only discovery couldn’t cover.

Scenarios This Unlocks

Line-of-business apps without Start menu shortcuts Legacy applications, internal tools, and diagnostics utilities that install to custom directories can now be published directly without image modifications or shortcut workarounds.

Multi-profile apps from one executable A single LOB client can be published as multiple Cloud Apps — different environments, different feature flags, different user groups — all from the same binary. This eliminates the need for separate images or complex scripting.

Kiosk and POS scenarios Store point-of-sale systems, ticketing applications, and medical record viewers that don’t create standard shell shortcuts can now be delivered as Cloud Apps to frontline workers.

Complementing Intune/Autopilot app delivery As Microsoft aligns Cloud Apps with Intune as the “single pane of glass” for app deployment — including publishing Intune apps as Cloud Apps via Autopilot Device Preparation — file path publishing makes it possible to register Intune-installed apps that land in non-standard locations.

What IT Admins Should Do

Evaluate your current Cloud Apps:

  • Identify apps you wanted to publish but couldn’t due to Start menu limitations
  • Catalog LOB apps, utilities, and tools installed in non-standard paths

Plan your app architecture:

  • For multi-environment apps, define naming conventions (e.g., “CRM – Prod”, “CRM – Test”)
  • Document command-line parameters and their purposes
  • Consider whether duplicate app entries with different parameters can replace more complex image-based solutions

Test in a pilot policy:

  • Create a test Flex shared provisioning policy
  • Add apps via file path with various parameter combinations
  • Validate the end-user experience in the Windows App

Update your app delivery documentation:

  • File path publishing is a new tool in the admin toolkit — document when to use it vs. Start menu discovery vs. Intune app publishing via Autopilot Device Preparation

Learn more in Windows 365 Cloud Apps.

2. Updated Provisioning Policy Page in Microsoft Intune

The Problem It Solves

Managing Windows 365 provisioning policies in Intune has been a fragmented experience. Policy configuration, device management, and Cloud Apps management lived in different parts of the admin center. If you needed to:

  • See which Cloud PCs were provisioned under a specific policy → navigate to “All Cloud PCs” and filter
  • Restart or reprovision those Cloud PCs → go to a different blade for bulk device actions
  • Check the status of a recent reprovision → find the action in yet another view
  • Manage Cloud Apps for a Flex shared policy → jump to the global “All Cloud Apps” page

Every operational task required context-switching across multiple blades, losing track of the policy you were working on. As Windows 365 deployments scaled — especially with Flex shared environments supporting up to 5,000 Cloud PCs per policy — this friction became increasingly painful.

What’s New

The provisioning policy page has been redesigned with a multi-tab layout that brings everything into one place:

Overview tab A single-pane summary of policy status, Cloud PC and Cloud App counts, and high-level health indicators. No more jumping between blades just to understand the state of a policy.

Properties tab Centralized view of all policy configuration: experience type (full Cloud PC vs. access-only apps), image, region, license type (Flex, Enterprise, Reserve), network, and join type (Entra ID join or hybrid). Edit policy settings without losing context.

Devices tab Shows all Cloud PCs scoped to the current provisioning policy. This is where the new bulk device actions live — admins can restart, reprovision, or reset Cloud PCs directly from the policy context. Previously, bulk actions were performed from separate device lists, creating risk of acting on the wrong devices.

Action Status tab Surfaces pending, in-progress, and completed actions (reprovision, resize, policy changes) for the selected policy. This makes troubleshooting and change management transparent — you can see exactly which operations succeeded, failed, or are still running.

Cloud Apps tab (Flex shared only) For Windows 365 Flex shared provisioning policies with the “Cloud App” experience type, this new tab lists all Cloud Apps associated with the policy. Admins can publish, unpublish, and edit Cloud Apps directly within the policy context — no more navigating to a global “All Cloud Apps” page.

How It Improves Day-to-Day Operations

Policy-centric workflows Instead of thinking “go to All Cloud PCs, filter by policy, then go to Actions, then check status somewhere else,” admins can now open a provisioning policy and do everything from that context. This is especially powerful for organizations managing distinct worker groups — retail stores, clinics, call centers — where each group has its own policy.

Faster incident response When a policy-wide update is needed (image change, network change, app update):

  1. Open the policy → Properties to adjust settings
  2. Switch to Devices to bulk reprovision or restart affected Cloud PCs
  3. Check Action Status to monitor completion
  4. Go to Cloud Apps (if Flex shared) to update app publishing

All in one place, without losing context.

Integrated Cloud Apps management The Cloud Apps tab is the most significant structural change. It aligns Cloud Apps management with the provisioning policy that governs the underlying shared Cloud PCs. Combined with the file path feature, admins can now:

  • Open a Flex shared policy
  • Go to the Cloud Apps tab
  • Add an app via file path with custom parameters
  • Publish it to users
  • Reprovision the affected Cloud PCs
  • Track the action status — all without leaving the policy page

Consistency with Intune patterns The tabbed layout mirrors how other Intune workloads are organized (device configurations, app deployments, compliance policies). This makes Windows 365 management feel native to Intune rather than a bolted-on experience, reducing the learning curve for admins already familiar with Intune.

What IT Admins Should Do

Explore the new layout:

  • Navigate to Devices > Provision Cloud PCs > Provisioning policies in the Intune admin center
  • Select a policy and explore each tab
  • Verify that the Devices tab shows the expected Cloud PCs for that policy

Update operational runbooks:

  • Document the new tab-based workflow for common operations (reprovision, restart, app publishing)
  • Update change management procedures to reference the Action Status tab for tracking

Leverage the Cloud Apps tab for Flex shared:

  • If you’re managing Flex shared policies with Cloud Apps, start using the integrated Cloud Apps tab instead of the global All Cloud Apps view
  • Combine with file path publishing for a complete in-policy app delivery workflow

Train your team:

  • The new layout is intuitive but represents a structural change — brief your help desk and operations teams on the new navigation

Learn more in View provisioning policies.

The Bigger Picture

These two updates are part of Microsoft’s broader trajectory for Windows 365 Cloud Apps and Intune management:

  1. Moving app publishing from images to Intune and Autopilot — Cloud Apps started with image-based Start menu discovery. File path publishing is the next step toward flexible, admin-controlled app registration. The roadmap points to Intune app publishing via Autopilot Device Preparation as the unified future.

  2. Making Windows 365 management fully integrated into Intune — The multi-tab provisioning policy page is the latest in a series of Intune UI improvements (dedicated navigation area, Admin Insights, Cloud PC Monitoring). The goal: Windows 365 should feel like a native Intune workload, not a separate console bolted on.

  3. Empowering frontline and shared-device scenarios — Both features specifically benefit Windows 365 Flex shared environments. File path publishing makes it easier to deliver specialized apps to frontline workers. The Cloud Apps tab in provisioning policies gives admins a dedicated workspace for managing those app-delivery policies.

Both features are in public preview or newly available, meaning now is the time to evaluate them in test environments and plan for production rollout.

Action Items Summary

  1. Cloud Apps file path publishing: Catalog apps that were previously unpublishable, plan multi-profile app configurations, test in a pilot Flex shared policy
  2. Provisioning policy UI: Explore the new multi-tab layout, update operational runbooks, train help desk teams on the new workflow
  3. Combined workflow: Use the Cloud Apps tab within provisioning policies to add apps via file path, publish, reprovision, and track status — all in one place

Big Hat Group helps organizations deploy and optimize Windows 365 and Microsoft Intune environments. Need help with Cloud Apps strategy, provisioning policy design, or Flex shared deployments? Get in touch.

Follow us on X @kkaminski for daily Microsoft ecosystem updates.