Two updates on the Windows 365 What’s New page this week focus on improving how users access remote applications. First, RemoteApp shortcuts can now be pinned directly to local desktops in public preview — a long-requested feature that closes a usability gap with the Start Menu integration released last year. Second, the Cloud Apps file path publishing capability has moved from public preview to general availability, giving admins a production-ready way to publish apps that don’t appear in the Start Menu.

What Changed

Pin RemoteApp Shortcuts to Local Desktops — Public Preview (Week of August 31, 2026)

Pinning RemoteApp shortcuts to local desktops is now available in public preview for Azure Virtual Desktop. Administrators can pin RemoteApp shortcuts to local desktops on behalf of users, and users can also pin RemoteApp shortcuts themselves. This provides faster access to frequently used remote applications directly from the local desktop.

Add Cloud Apps from File Path — General Availability (Week of August 31, 2026)

Windows 365 administrators can now add Cloud Apps by specifying a file path, expanding the applications available on Windows 365 Flex shared Cloud PCs. Administrators can define custom app properties and configure command-line parameters for applications that require manual configuration. This feature has moved from public preview (announced July 2026) to general availability.

Pin RemoteApp Shortcuts to Local Desktops: Desktop-Level Access for Remote Apps

When Microsoft added Start Menu integration to the Windows App in November 2025, it was a meaningful step — remote apps could finally appear alongside local apps in the Start Menu. But community feedback was immediate: users wanted desktop shortcuts too, not just Start Menu tiles. The Start Menu is fine for discovery, but for frequently used line-of-business apps, a desktop shortcut is the muscle-memory path that most users actually follow.

What this preview delivers

  • Admin-pinned shortcuts. Administrators can pin RemoteApp shortcuts to local desktops on behalf of users, ensuring consistent access across the fleet without requiring user action.
  • User-pinned shortcuts. Users can also pin shortcuts themselves, giving them control over their own desktop layout for the remote apps they use most.
  • Faster access. Instead of launching the Windows App, navigating to the remote resources list, and double-clicking, users click a desktop icon and the remote app opens — closer to the native app experience.
  • Applies to AVD RemoteApps. This is an Azure Virtual Desktop feature that extends to Windows 365 Cloud Apps scenarios where RemoteAppV2 is enabled.

Prerequisites during preview

The desktop pinning feature builds on the RemoteAppV2 enhancements that Microsoft began rolling out in late 2025. During public preview, these requirements apply:

  • Session host or Cloud PC OS: Windows 11 24H2 or 25H2 with SxS Network Stack version 1.0.2507.25750 or newer
  • Client: Windows App for Windows (Insider build) or Remote Desktop client 1.2.6760.0+
  • Enablement: RemoteAppV2 must be enabled via registry key (HKLM\Software\Policies\Microsoft\Windows NT\Terminal Services\EnableRemoteAppV2 = 1) on session hosts or Cloud PCs
  • Policy compatibility: Two Group Policies must remain enabled — “Use advanced RemoteFX graphics for RemoteApp” and “Enable enhanced shell experience for RemoteApp”

Once the feature reaches general availability, the registry enablement requirement is expected to be removed and the enhancements will be enabled by default on supported systems.

Why this matters

For organizations running AVD RemoteApps or Windows 365 Cloud Apps, desktop pinning reduces the friction of the last mile — getting from “the app is published and available” to “the user actually launches it.” The Start Menu integration was a good first step, but desktop shortcuts are the interaction pattern most users default to for frequently accessed applications. This preview closes that gap.

Cloud Apps File Path Publishing: From Preview to Production

When Cloud Apps file path publishing entered public preview in July 2026, it solved a specific problem: Start Menu auto-discovery couldn’t find every app an organization wanted to deliver. Legacy apps installed in non-standard paths, line-of-business tools without Start Menu entries, and apps requiring specific command-line arguments were all effectively invisible to the Cloud Apps discovery mechanism.

With this week’s general availability announcement, file path publishing is now production-ready.

What file path publishing does

Instead of relying on Start Menu discovery to populate the Cloud Apps catalog, admins can manually register an app by specifying:

  • Executable path — Point directly to any path on the Cloud PC image, such as C:\Program Files\Vendor\App\app.exe or D:\LOBApps\MyTool\tool.exe
  • Custom app properties — Define the display name, icon, and other metadata independently of what the executable reports
  • Command-line parameters — Pass startup arguments to the executable, enabling scenarios like “CRM – Production” and “CRM – Training” pointing to the same executable with different parameters
  • Application duplication — Register the same executable multiple times with different properties, which is useful for multi-environment or multi-role configurations

How it fits into the 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
  5. The new multi-tab provisioning policy page in Intune includes a Cloud Apps tab for Flex shared policies, so admins can add, publish, reprovision, and track status without leaving the policy view

What GA means for admins

  • No preview opt-in. The feature is enabled by default — no registry keys, no preview terms, no feature flags.
  • Production support. Microsoft support will handle issues through normal channels rather than preview support pathways.
  • SLA coverage. The feature is covered by the standard Windows 365 service-level agreement.
  • Integration stability. The Cloud Apps tab in the provisioning policy UI and the file path workflow are now permanent parts of the management experience.

Who benefits most

  • Organizations with legacy or custom apps that don’t create Start Menu entries during installation
  • Multi-environment deployments where the same executable needs different launch parameters for different user groups
  • App packaging teams who need to register apps installed by Intune or Custom Script Extension in non-standard locations
  • Any Flex shared deployment where the Start Menu discovery catalog doesn’t cover the full set of apps users need

What Admins Should Do Now

  1. RemoteApp desktop pinning — evaluate in test. Enable RemoteAppV2 on a test session host or Cloud PC, verify the prerequisites, and pilot desktop pinning with a small user group. Gather feedback on shortcut placement and user experience before broader rollout.

  2. Cloud Apps file path — move to production. If you’ve been waiting for GA to adopt file path publishing, now is the time. Catalog apps that were previously unpublishable, plan your Cloud Apps provisioning policy configuration, and begin registering apps via file path in your production Flex shared policies.

  3. Update documentation and runbooks. Both features change the user access story. Document the new desktop pinning capability in your user guides, and update your Cloud Apps management documentation to reflect the GA file path workflow.

  4. Train help desk teams. Desktop pinning introduces a new way for users to access remote apps — make sure support teams know what pinned RemoteApp shortcuts look like and how to troubleshoot them. For Cloud Apps, ensure teams understand the file path registration workflow in the Intune admin center.

Sources