Setting up Single Sign-On (SSO ) with Azure Active Directory (AD)



Add new application for Single Sign-On (SSO) in Azure Active Directory

  1. Login to Azure. The url should point to
  2. Navigate to Azure Active Directory service. You can search for "Azure Active Directory" in the search box at the top of the page. image__9_.png
  3. In the left-hand panel, navigate to Enterprise Applications. From there, select All Applications.
  4. Click New Application to add a new application. step3b.png
  5. In the Add from the Gallery section, search for “SAML” and add the Azure AD SAML Toolkit. Give it a name.



Add SSO users to app and set up SSO




Once the application you added loads, you are ready to go through the following Getting Started steps:

  1. Assign users and groups. Click + Add User.
    • You will need to add all users you want to be able to login to Formstack via SSO.
  2. Setup Single Sign-On 





Create New Auth Provider in Formstack

Navigate to the Authentication section of your Formstack and Add New Auth Provider

    1. Give it a name and choose SAML 2.0 as provider type.
    2. Paste the App Federation Metadata Url you previously copied from your Azure Active Directory settings into the Import from URL field and then click Create Auth Provider
    3. This will create new URLs that you will add to your setting in Azure Active Directory.


Complete SSO configuration in Azure Active Directory

    1. Copy and paste the following newly created URLs back into Azure “Basic SAML Configuration” box
      • Entity ID -> Identifier
      • ACS URL -> Reply URL
    2. Use this as the Sign-on URL: Click save.
    3. Navigate to User Attributes & Claims. Update the Unique User Identifier to be the user’s email address. 
      • For me, that is user.mail but yours could be different.
      • This is where you can add custom attributes you want to use within Formstack for things such as form prefilling.

Done! You are now ready to enjoy the Single Sign-On experience.












Was this article helpful?
0 out of 2 found this helpful