SSO/SAML with Azure AD

How to configure Steady SSO with Microsoft Azure Active Directory and SAML 2.0

Updated over a week ago

Note: SSO/SAML is available in our 50-99 and 100+ seat plans.

Setup and Configuration

To setup your Steady account with SSO/SAML and Azure AD, you'll need to take the following steps. Right now there is still a manual step on our end, so we'll need the metadata URL from the last step along with a heads-up that you would like to enable SSO/SAML with Azure AD for your account.

Once we confirm that everything works, we'll disable password authentication and magic link sign-in capability completely for your account.

Here are the steps:

  1. Sign in to your Azure Portal and visit the Azure Active Directory section. You'll need to be a tenant administrator.

  2. From Enterprise Applications, click "New Application" and then "Non-Gallery Application"

  3. Name the application "Steady" and click the "Add" button to save it.

  4. Back on the "Enterprise Applications" page, click on "Steady" from the application list

  5. Click on "Set up single sign-on", then click "SAML"

  6. Under the "Basic SAML Configuration", use https://app.steady.space/saml/metadata for the "Identifer" and https://app.steady.space/saml/consume for the "Reply URL"

  7. By default, "User attributes and claims" will use "Email address" as the name identifier format, but if your configuration is different, then you may have to set this up:

8. Under "SAML Signing Certificate", copy the "App Federation Metadata Url" and send it to us (help chat or support@support.steady.space)

9. After you have yourself or other users provisioned, and we've installed the Metadata URL for your account, we can begin testing.

Provisioning Users

We're working on provisioning users in Steady from AD automatically, but for now it's a two step process for each user:

  1. Add the user to the account in Steady and then assign them to a team. Make sure their email address is unique and the same one you have for them in Azure (or skip this step if the user already exists in Steady)

  2. Make sure the user is enabled in Azure AD for the Steady app.

Did this answer your question?