Skip to Main Content
Status Future consideration
Product Area Right Click Tools
Categories Intune/Entra Tools
Created by David Taylor
Created on Feb 14, 2025

Not all parts of RCT for Intune are working properly for Azure only joined devices

Some problems have come up with Azure only joined devices and the RCT for Intune. Specifically, only some of the RCT for Intune Console Tools work (Shutdown, Restart, System Information). However, if we need to RCT to an Azure only joined device, some of the tools we need to use do not work, such as: Computer Management, Regedit, Interactive Powershell prompt, etc. As we migrate from on-prem hybrid join to Azure join only, we need to be able to grant certain individuals admin rights, network configuration operators rights, etc. We also need to be able to remotely access their registry to check things. When we try to launch these tools, they report that the device is not on, and yet when we launch the system information tool, everything shows up. Access to these tools through RCT are critical to us; otherwise we have to remote into the target machines and run the commands locally in an elevated powershell prompt, and interrupt the user. This just slows us down considerably. An option to fix this is to add this functionality to perhaps a subsection of RCT for Intune like RCT for Intune - Azure only, and consolidate the tools that work for Azure only into this submenu in order to make it easier to see what works for those devices and add the new functionality as described above to this submenu as they are created/fixed.

  • Attach files
  • Guest
    Jun 25, 2026

    We are currently experiencing the same issue in our environment. I’m part of a POC, and one of our key evaluation points is how well these tools function for Azure AD–only joined devices.

    Given that this is the direction we are planning to move—away from SCCM and toward Azure-only management—it’s critical that these remote console tools are fully functional. Right now, the limitations around tools like Computer Management, Registry access, and interactive PowerShell are a significant concern and introduce operational inefficiencies.

    If these gaps remain, it will be difficult for us to justify moving forward with this approach, as reliable remote administration is a core requirement for our support model.

  • +4