Getting started with the Remote Help web app

This week is all about the Remote Help web app. Remote Help on itself is nothing new, but it does have an often overlooked feature that can be useful in multiple occasions. That feature is the Remote Help web app. The Remote Help web app can be used to help users on managed and unmanaged devices, without installing the Remote Help app, and in some scenarios even on Linux devices. The former might sound a little bit weird, but due to the nature of the web app, it does technically work in some scenarios to provide support on Linux. Together that makes the Remote Help web app an interesting feature to be familiar with. It is good to know that the web app only supports viewing the shared screen. Besides that, it also good to be familiar with the growing feature set of Remote Help. Remote Help now already provides support for Windows, Android (dedicated devices), and MacOS. This post will focus on the configurations that are specific to fully utilizing the Remote Help web app. This post will end with experiencing the Remote Help web app.

Note: Keep in mind that, even though it might work, Linux isn’t officially supported by Remote Help.

Enabling Remote Help in the tenant

Before using the Remote Help web app, on any platform, Remote Help must be enabled for the tenant. After it’s enabled for the tenant, it can be used for providing remote assistance to the different platforms. Especially for providing support to unmanaged devices, there is a specific configuration to keep in mind. That setting is related to unenrolled devices. The following two steps walk through the process of enabling Remote Help for managed and unmanaged devices.

  1. Open the Microsoft Intune admin center portal and navigate to Tenant admin > Connectors and tokens > Remote Help
  2. On the Connectors and tokens | Remote Help page,  as shown below in Figure 1, click Settings > Configure with the following settings and click Save
  • Enable remote help: Select Enabled to enable the Remote Help functionality within the tenant
  • Allow remote help to unenrolled devices: Select Allowed to also allow Remote Help on unmanaged devices
  • Disable Chat: Select No to leave the chat functionality enabled

After enabling Remote Help in the tenant, it’s important to align Conditional Access with the scenario that is going to be used. In this case, that means that Conditional Access is aligned with the usage of the Remote Help web app. And not just using the Remote Help web app, but also the scenarios that must be supported. So, if a user is allowed to use the Remote Help web app on unmanaged devices that must also reflect in Conditional Access. In that scenario don’t require a managed for using Remote Help. That will make the Remote Help web app unavailable on unmanaged devices. For more details around using Conditional Access with Remote Help, please refer to this earlier post about using Conditional Access for Remote Help.

Using Remote Help web app

The usage of the Remote Help web app is pretty straight forward and comparable to using the Remote Help apps. Main differentiator is that there is no app required and that it only provides view permissions to the helper. There are many different scenarios in which the Remote Help web app can be useful. The most common scenario is when their is no client app installed. Both, helper and sharer have their own URL for setting up the session. Those are the following URLs:

These URLs are usable on Windows, on MacOS, and in some case on Linux devices. Besides that, the Remote Help web app also generates different security codes compared to the Remote Help client app that is available on the different platforms. When using the Remote Help web app a security code of eight characters is used. The helper shares that security code with the sharer, and after starting and allowing the remote connection, the connection will actually be started (as shown below in Figure 2).

Good to know is that there also warnings when the device that the helper is connecting to is either unmanaged or noncompliant. Both important and good to know, before the helper is actually connecting to the device of the sharer.

Note: During testing, nearly all Linux distributions, used by sharers, would show the helper an RBAC message.

More information

For more information about Remote Help and the Remote Help web app, refer to the following docs.

5 thoughts on “Getting started with the Remote Help web app”

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.