Skip to main content
All CollectionsIntegrations
Azure Active Directory Integration
Azure Active Directory Integration

Learn how you use Microsoft's leading SSO solution in your dashboard.

Tom Bachant avatar
Written by Tom Bachant
Updated over 2 years ago

This article is a step-by-step guide to configure SSO for your Everyspace account using Azure Active Directory as your primary user management system.

In your Azure dashboard, go to the App registrations page and click "+ New Registration". In the new registration screen, enter the following:

  • Name: Everyspace

  • Supported account types: Accounts in any organizational directory

  • Redirect URI (Web): This is based on the subdomain associated with your account. For example, if you access your dashboard through "piedpiper.everyspacehq.com", enter https://piedpiper.everyspacehq.com/__/auth/handler.

This will bring you to the app overview screen. From here, you'll see the "Application (client) ID" field. Send this along to your Everyspace support representative.

Next, navigate to the "Certificates & secrets" tab from the left menu, and click "+ New client secret". Name the secret "Everyspace Secret", give it an expiration of 12 months, and click save. You will then see the secret in the "value" column. Send this to your Everyspace support representative immediately, as it will not be visible again after this point.

Lastly, head to the "API permissions" tab from the left menu. Click the "+ Add a permission" button, and a window will appear to request permissions. Follow the steps in the gif below to add all "OpenID" permissions. Be sure to click the "Grant admin consent" button when you've added the permissions.

In summary:

  • You'll have a new "App registration" called Everyspace

  • Use the auth URL associated with your account as your redirect URI, for example https://piedpiper.everyspacehq.com/__/auth/handler.

  • Supported account type is set to "Accounts in any organizational directory (Any Azure AD directory - Multitenant)"

  • Create a secret key and assign API permissions, making sure to grant admin consent

  • Send along the secret key and the application (client) ID to your support representative

Did this answer your question?