Azure¶
Warning
This guide should be used as a functional example only. Identity Admins should follow their company's policies and best practices when implementing Single Sign-On (SSO).
Similarly, because these guides are for services that Horizon3 does not control, screenshots and configuration options might be different then what you see here.
All sections of this page should be completed by someone with permissions for Identity Team Admin.
Create Azure Enterprise Application¶
-
Log into Azure Portal and browse to the
Azure Active Directoryservice. -
In the left-hand menu's
Managesection, clickEnterprise applications. -
Then click
New Application. -
Then click
Create your own application.Required role
You will need to have one of the following Azure AD roles in order to create a new application:
Global AdministratororApplication Administrator. -
Name your app
NodeZero Portal. -
Select
Register an application to integrate with Azure AD (App you're developing). -
Click
Create. -
On the
Register an applicationpage, you can choose to set a different user-facing name for the app, if desired. -
Ensure that the
Supported account typesoption is set toSingle tenant. -
Leave the
Redirect URIsection blank for now. -
Click
Register.
Copy Client ID¶
After registering the app, you'll be taken back to the Browse Azure AD Gallery page. Navigate back to
the Enterprise applications page, find your newly created app, and click it.
- Click on the
Overviewpage. - Save the
Application ID. This is theClient IDthat you will need to provide to your Portal Org Admin later.
Configure Single Sign-On¶
Under the Manage section of the left hand menu:
- Click
Single sign-on. - Click
Go to application.
Copy Issuer URL¶
On the new Overview page (step 1), click the Endpoints tab (step 2) and copy the OpenID Connect metadata document value (step 3). This is this Issuer URL that you will need to
provide to your Portal Org Admin later.
Configure Authentication¶
Under the Manage section,
- Click
Authentication. - Ynder the
Platform configurationssection, clickAdd a platform. - In the
Web applicationssection that opens to the right, click theWebbutton.
Use the information in the table below to fill out the Redirect URIs field. Be sure to select
the correct tab, based on which regional Portal your users access.
| Field | Value |
|---|---|
| Sign-in redirect URIs | https://portal.horizon3ai.com https://auth.horizon3ai.com/oauth2/idpresponse |
| Field | Value |
|---|---|
| Sign-in redirect URIs | https://portal.horizon3ai.eu https://auth.horizon3ai.eu/oauth2/idpresponse |
Adding multiple sign-in redirect URIs
The initial form appears to only allow you to enter a single URI. Enter the first URI from the appropriate
table below, click Configure, then click the Add URI link in the Web > Redirect URIs section on the main
page. Enter the second URI and click Save.
Create Client Secret¶
Under the Manage section,
- Click
Certificates & Secrets. - Click
New client secret. - Enter a description.
- Set the
Expirescolumn to a value that aligns with your company's policies. -
Click
Add. -
Copy the
Secret Value.
This is the Secret VALUE that you will need to provide to your Portal Org Admin later.
Configure API Permissions¶
Under the Manage section,
- Click
API permissions. - Ensure that the Microsoft Graph
User.Readpermission is configured (it should be by default).












