Configuring Azure AD for SAML 2.0 Integration

Created by Chris W Jordan, Modified on Tue, 28 Feb 2023 at 04:56 PM by Chris W Jordan

Configuring Azure AD for SAML 2.0 Integration

Support Email:

About this document

Using the Clientless Remote Desktop platform, you can access your existing Sage FAS server leveraging single sign-on via SAML 2.0 with Azure AD as your Identity Provider. This document will highlight information and requirements to configure this on the Azure AD portal.

What you will need to complete the connection

  • Application ID - Provide to WebHouse, Inc.

  • Identifier(Entity ID) - Provided by WebHouse, Inc.

  • Reply URL (ACS URL) - Provided by WebHouse, Inc.

  • App Federated Metadata URL - Provide to WebHouse, Inc.

  • Login URL - Provide to WebHouse, Inc.

Creating the Azure AD App

  1. To configure the integration into Microsoft Azure AD, you need to create a new app. For this, go to the Microsoft Azure portal, and click on the Azure Active Directory tab.

  1. Click on Enterprise Applications on the left panel, and click on + New application on the top.

  1. Click on Non-gallery application to create a new application that is not already present in the gallery.

  1. Provide a name to your app, for example, “test-sso,” and click on Add.

  1. This will lead you to the Overview page where you will see the overview details of your application. Make a note of the Application ID, as you will need to provide this to WebHouse. Under the Getting Started section, click on the 2. Set up single sign on tab.

  1. On the Select a single sign-on method page, select the SAML mode to enable single sign-on.

  1. You will be led to the Set up Single Sign-On with SAML page where you can perform the further steps after creating your app.

  1. Click on the “Edit” (pencil) icon beside the Basic SAML Configuration section, add the following details:

  • Identifier (Entity ID): Enter the “Entity ID” provided by WebHouse.

  • Reply URL (Assertion Consumer Service URL): Enter the ACS URL provided by WebHouse.

  1. Make note of the App Federation Metadata URL and the Login URL. You will provide these pieces of information to WebHouse to complete SAML connection. 

  1. Next, edit the User Attributes & Claims section. Under Claim Name, you will see the primary claim, Unique User Identifier (Name ID), with the claim Value set to user.userprincipalname [nameid-format:emailAddress]. On clicking this claim, ensure your nameID format and Source attribute are as below:

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article