Summary
The Azure Integration connects Microsoft Azure (Microsoft Entra ID / Azure AD) to KnowledgeCity as your identity and provisioning platform. KnowledgeCity acts as a Service Provider so your people sign in with the credentials they already have, and it can automatically provision and keep user accounts, groups, and access in sync with your Azure directory. This removes the need for separate passwords and manual account maintenance.
Introduction
Microsoft Azure (Microsoft Entra ID, formerly Azure AD) is one of the identity platforms KnowledgeCity supports through its Integrations settings. In this arrangement, KnowledgeCity works as a Service Provider with your Azure directory, letting employees reach their training using their existing organizational sign-in rather than a separate KnowledgeCity password.
This integration is intended for administrators who manage user access at scale. By pairing single sign-on with automated provisioning, your directory becomes the source of truth: users, their groups, and their access stay aligned from a person's first day to their last, with minimal manual effort and fewer errors.
Key Concepts
- Microsoft Entra ID (Azure AD): Microsoft's cloud identity platform. KnowledgeCity supports it as a standards-based identity provider using SAML 2.0 or OAuth2 / OIDC.
- Service Provider (SP): in this integration KnowledgeCity is the Service Provider; your Azure directory authenticates the user, and KnowledgeCity trusts that authentication to grant access.
- Single Sign-On (SSO): lets users sign in to KnowledgeCity with the credentials they already use in Azure, so there are no new passwords to remember and no separate accounts to manage.
- SSO type: each SSO configuration is set up as either SAML or OAuth, matching the protocol you use with Azure.
- Automated provisioning (SCIM): uses the SCIM protocol so Azure can automatically create and maintain KnowledgeCity accounts, keeping users and access in sync as your organization changes.
- SCIM API URL and token: the endpoint your identity provider connects to, plus the credential that authenticates provisioning requests. Treat the token like a password and store it securely.
- Auto-license and logging: provisioning options that control whether provisioned users are automatically assigned a license, and whether provisioning activity is recorded for review and troubleshooting.
Steps to Follow
Open the Integrations settings
Sign in to KnowledgeCity as an administrator. From the Settings menu, select Integrations to open the configuration area where single sign-on and user provisioning are managed.
Choose how Azure will connect
Decide which protocol you will use with Microsoft Azure. KnowledgeCity supports SAML 2.0 and OAuth2 / OIDC, both of which Azure (Microsoft Entra ID) provides. When you create the SSO configuration, set the SSO type to SAML or OAuth to match your choice.
Configure single sign-on with Azure
Set up the SSO configuration so KnowledgeCity acts as the Service Provider for your Azure directory. Setting up SSO involves exchanging configuration details between KnowledgeCity and Azure so each side trusts the other. Complete the required details for your chosen protocol and save the configuration, so users can authenticate with their Azure credentials.
Enable SCIM provisioning
To automate account creation and maintenance, locate the SCIM provisioning option within the Integrations settings and turn it on. Enabling SCIM activates the provisioning endpoint so Azure can begin sending user data to KnowledgeCity.
Retrieve your SCIM API URL and token
After enabling SCIM, obtain the SCIM API URL and the SCIM token provided in the settings. You will enter these values in Azure's provisioning configuration so it can connect to KnowledgeCity. Copy the token carefully and store it securely, since it authenticates all provisioning requests.
Set the auto-license and logging options
Configure the auto-license option based on how you want new accounts handled. When enabled, users provisioned from Azure are automatically assigned a license as their accounts are created, so they can access content without an extra manual step. Set the logging option to control whether provisioning activity is recorded, which is useful for confirming that users are created and updated as expected and for troubleshooting issues.
Connect Azure and verify
In Microsoft Azure, enter the SCIM API URL and SCIM token in the provisioning configuration and enable provisioning to KnowledgeCity. Azure will then begin sending users automatically. Use the logging option to confirm accounts are being provisioned correctly, and test the sign-in flow before your organization relies on it in production.
Conclusion
Connecting Microsoft Azure lets KnowledgeCity use your existing directory for both sign-in and account management: users authenticate with their Azure credentials through single sign-on, while SCIM keeps accounts, groups, and access in sync automatically. Configure SSO, enable SCIM with its API URL and token, set the auto-license and logging options, then verify the flow so access stays accurate with minimal manual effort.