SSONorvia SSO Guide
Part 1 · Entra setup

Prepare Microsoft Entra ID and register the apps

This page shows how to collect your organisation's Entra details and give each Norvia product its own identity in Microsoft Entra ID.

Before you begin

What will Part 1 achieve?

You will record the Entra Tenant ID and domain, then create a separate app registration for IntelliCampus, IntelliBroadcast, and any other Norvia product that will use SSO.

Why is this needed? Entra ID must know which organisation owns the users and which applications are allowed to request a login. The tenant identifies the organisation. An app registration identifies one application.
Keep secrets private: never paste a client secret into source code, screenshots, documents, support tickets, or chat. Store it in Azure Key Vault or an approved secret store. Revoke it immediately if it is exposed.
Step-by-step

Complete these steps in order

1

Find your Entra tenant information

  1. Sign in to portal.azure.com ↗.
  2. Search for Microsoft Entra ID.
  3. Open the Overview page.
  4. Copy the Tenant ID and Primary domain.
  5. Save them in your team's secure configuration record.
  6. If you want to avoid paid identity features, confirm the licence shown is Microsoft Entra ID Free.
Why? All Norvia applications must trust the same Entra tenant. The primary domain is also used later to create usernames such as john.smith@yourtenant.onmicrosoft.com.
Tenant ID<organisation-tenant-guid>
Primary domain<tenant>.onmicrosoft.com
Check: you have saved both values and can identify which Entra directory they belong to.
2

Register IntelliCampus

  1. In Microsoft Entra ID, select App registrations.
  2. Select New registration.
  3. Enter IntelliCampus-SSO as the name.
  4. Select Accounts in this organisational directory only (single tenant).
  5. Leave Redirect URI empty for now.
  6. Select Register.
  7. Copy the Application (client) ID.
Why? The client ID is IntelliCampus's public identifier. It tells Entra which application is asking the user to sign in. The redirect URI is added later when the final application URL and callback path are known.
Application nameIntelliCampus-SSO
Account typeSingle tenant
Client ID<intellicampus-client-guid>
Redirect URINot configured yet
Check: IntelliCampus appears under App registrations and you have recorded its client ID.
3

Create the IntelliCampus client secret

  1. Open the IntelliCampus app registration.
  2. Select Certificates & secrets.
  3. Select New client secret.
  4. Enter a clear description and choose your organisation-approved expiry period.
  5. Select Add.
  6. Copy the secret Value immediately and store it securely. Do not copy only the Secret ID.
  7. Record its owner and expiry date so it can be rotated before it expires.
Why? A server application uses the secret to prove that it really is the registered application. Entra shows the secret value only once.
Important: the secret is a password for the application. Do not place its value in the configuration inventory below—record only where the secret is stored.
Check: the secret is in the approved secret store and a rotation reminder exists.
4

Record IntelliCampus configuration

Keep identifiers in the team configuration record. Keep the secret value only in the secret store.

Application nameIntelliCampus-SSO
Tenant ID<organisation-tenant-guid>
Client ID<intellicampus-client-guid>
Client secretStored securely at <secret-location>
Secret expiry<expiry-date>
Redirect URIPending
Why? A clear inventory prevents teams from mixing up tenant IDs, client IDs, and secrets when several products are connected.
5

Repeat for IntelliBroadcast and other products

  1. Create a new app registration named IntelliBroadcast-SSO.
  2. Use the same single-tenant account type.
  3. Create a new client secret and store it securely.
  4. Record its unique client ID, secret location, owner, and expiry date.
  5. Repeat for each additional Norvia product that will join SSO.
Why? Each product needs its own client ID and secret. Separate registrations make permissions, secret rotation, troubleshooting, and disabling one application safer. Do not reuse one secret across products.
Part 1 is complete when: every planned product has its own app registration, client ID, securely stored secret, and pending redirect URI.
Next step

Continue to user provisioning

Part 2 prepares Norvia Backoffice to create one Microsoft Entra user and reuse that identity across authorised Norvia products.

Open Part 2 →