3.3.2. Enterprise App Catalog and Remote Help
💡 First Principle: Both tools remove a slow, manual step from the help desk's day. The Enterprise App Catalog removes repackaging: Microsoft prepares common Windows apps so you don't have to build and maintain every installer yourself. Remote Help removes the guesswork of support over the phone: a helper sees the user's screen, inside the same tenant's identity and permissions model as the rest of Intune.
Enterprise App Management (EAM) provides the Enterprise App Catalog, Microsoft and non-Microsoft Windows apps that Microsoft prepares and hosts as Win32 apps, installed by the Intune Management Extension (not WinGet). You add one at Apps > All Apps > Create > Windows > Enterprise App Catalog app, then pick the package by name, language, architecture and version.
Intune then prefills what you'd normally work out by hand — install and uninstall commands, return codes, detection rules and requirements. Microsoft recommends keeping the defaults, and the install behavior (system or user) can't be changed. Intune performs no license check for licensed apps; that stays your job. Catalog apps can be blocking apps in the ESP and in device preparation policies.
Keeping catalog apps current has three paths:
- Self-updating apps: Intune ensures a minimum version and lets the vendor's own updater do the rest.
- Auto-update: for catalog apps with a Required assignment, Intune updates targeted devices to the newer catalog version automatically, with no new app and no supersedence relationship (enable it on the Assignments step). There's no rollback and no phased rollout — every targeted device updates together — and Available assignments keep the old workflow.
- Guided supersedence: Update > Supersede app creates the new app and the supersedence relationship, but scope tags and assignments aren't copied, so you assign the new app again.
Remote Help is cloud remote assistance between a helper and a sharer, and both must sign in with Microsoft Entra accounts from the same tenant — you can't run a session across tenants. It's not enabled by default; turning it on at Tenant administration > Remote Help > Settings enables it tenant-wide. Helping unenrolled devices is a separate setting, also off by default, and chat is on unless you disable it. Both helpers and sharers need a license, with one exception: Samsung and Zebra devices in Android dedicated mode need no sharer license because no user is signed in.
| Session type | Who takes part | Platforms | What the helper needs |
|---|---|---|---|
| Attended: view only | Sharer accepts | Windows, macOS, Android dedicated (Samsung Knox, Zebra), web app sharers | View screen permission (Microsoft's recommended default) |
| Attended: full control | Sharer accepts | Windows, macOS, Android dedicated | Take full control permission |
| Attended: elevation | Sharer accepts | Windows only | Elevation permission (answers UAC prompts) |
| Unattended | No one | Windows and Android dedicated devices | Windows unattended control remote sign-in, or Android unattended control |
Unattended control on Windows went generally available in August 2026, and it has a tight set of requirements. The target must be a physical, Intune-managed, corporate-owned, x64 device that's Entra joined or hybrid joined — Windows 365, Azure Virtual Desktop and personal devices aren't supported. It needs the Azure Virtual Desktop agent and agent bootloader, the Intune Management Extension, Remote Desktop enabled, and the device powered on. The helper chooses Initiate unattended control and signs in inside the remote session with their own account, so a standard account gets no admin rights. A signed-in user is asked to allow it; after 30 seconds with no answer the session starts anyway, locking the user's session with their work preserved. Conditional Access and chat apply only to attended sessions.
Permissions. A helper needs Offer remote assistance, Remote Assistance Connector – Read and at least one Remote Help app permission. The built-in Help Desk Operator role includes view screen, full control, elevation and Android unattended control — but not Windows unattended control remote sign-in, which needs a custom role. A helper can't help a device outside their scope, and the All Devices scope group doesn't include unenrolled devices.
Sessions start from Devices > All devices > device > New remote assistance session > Remote Help. A noncompliant sharer device triggers a warning that doesn't block the session, and Microsoft keeps session metadata for 30 days but no recordings.
⚠️ Exam Trap: Assigning the Help Desk Operator role isn't enough for Windows unattended control. That role lacks the Windows unattended control remote sign-in permission, so the answer is a custom role — and even then, a Windows 365 Cloud PC or a personal device can't be the target.
Reflection Question: An outsourced help desk in its own Microsoft Entra tenant needs to support your employees' laptops with Remote Help. Why won't that work as described, and what workaround does Microsoft suggest?