Forum Discussion

DavidBelanger's avatar
DavidBelanger
Icon for Microsoft rankMicrosoft
Nov 03, 2023

HOW TO: Hiding the consent prompt for Single Sign-On

We've been working on the ability to hide the dialog shown to users on first connection to a new session host when Single Sign-On is enabled to allow the remote desktop connection. The steps have now...
DavidBelanger's avatar
DavidBelanger
Icon for Microsoft rankMicrosoft
Nov 14, 2023
Thank you for the feedback Andrew_Allston. I plan to add a sample step-by-step instruction using Graph Explorer for those less familiar with using Microsoft Graph. Hoping to have it live the week after Thanksgiving at the latest.
Andrew_Allston's avatar
Andrew_Allston
Iron Contributor
Nov 14, 2023
Thank you! Much appreciated! Have a happy Thanksgiving! 🦃
  • Andrew_Allston's avatar
    Andrew_Allston
    Iron Contributor
    Nov 16, 2023

    Andrew_Allston for anyone else a bit confused and wants to try before the detailed instructions are posted. The available links seem to suggest you need to create these attributes/objects. But you are modifying the SPNs for the two applications listed in the docs. This means PATCH should be used and not POST which is the method which is linked to.

    • Sandeep Deo's avatar
      Sandeep Deo
      Icon for Microsoft rankMicrosoft
      Nov 17, 2023

      Andrew_Allston You are right. To create a remoteDesktopSecurityConfiguration object on a supported Service Principal (RDP resource) you have to use PATCH and set the isRemotedDesktopProtocolEnabled property. Once you have created the RDSC object you have to create targetDeviceGroup object and you can do that by using POST. If you need to add more device groups to the targetDeviceGroup object you can do so one at a time by again doing a POST call. The only time you will use PATCH call on targetDeviceGroup is if you need to update display name for the group. Hope this helps. I will updating the docs shortly to reflect this change from POST to PATCH when creating RDSC object.

Resources