This article is from before the rebranding to SelfGuide. Text and images can include the old product name ProductivityPerformer or its abbreviation PP.
The SelfGuide integration with Microsoft Azure Active Directory (Azure AD) adds the ability to use a Microsoft work- or schoolaccount to get access to SelfGuide. For the user, no additional account is needed, for the organization security is improved by support for multi-factor authentication. Enabling the integration just changes the way users authenticate, existing data like Instructions, trainingen and user guides are kept.
Using Azure AD as identity provider is optional and requires some preparation in Azure AD. After following the steps below, get in touch with support to enable the integration.
After contacting support, a moment will be scheduled to configure the integration. While configuring the integration, SelfGuide is temporary not available.
Existing accounts created in SelfGuide can't be used anymore after enabling the Azure AD integration
Single-tenant vs Multi-tenant
Azure AD integration can be configured in two ways:
Single-tenant: Accounts defined in one Azure AD tenant get access to SelfGuide. Use this option if the organization uses one Azure AD tenant and no external users need access to SelfGuide
Multi-tenant: Accounts defined in several Azure AD tenants get access to SelfGuide. Use this option if the organization uses more then one Azure AD tenant or users from other organizations need access to SelfGuide.
This article explains the required steps for a single-tenant Azure AD integration, for multi-tenant Azure AD integration see this kb article.
Sign-in with an account having permissions to create an Azure AD app registration
Open Azure Active Directory
Open App registrations and choose New registration
Give the new application a name, select Accounts in this organizational directory only, choose Single-page application (SPA) for the redirect url and specify the SelfGuide tenant URI. The Redirect URI always follows the syntax https://<tenant>.selfguide.com, where <tenant> must be changed to the name of the SelfGuide tenant.Final, press Register to create the application.
The new application is created and will be opened. Navigate to Expose an API and press Add a scope.
An application ID URI will be generated with the syntax api://<guid>, don't change this default value and press Save and continue.
The new created scope must be configured, always use user_impersonation as name for the scope. All other fields must be filled based on the organization policies. Finally, press Add scope.
Navigate to API permissions and choose Add a permission.
Add the created scope by pressing My APIs and selecting the created scope
After selecting the API, you need to specify how the API is used. Select Delegated permissions, make sure user_impersonation is selected and press Add permissions.
With the current configuration, all users will need to consent personally when using SelfGuide for the first time. By giving admin consent for the tenant, consent is given once for all users. Press Grant admin consent for <tenant name> and press Yes to confirm the action.
The app registration is finished, to be able to configure the integration some information is need. Navigate to Overview and copy the Application ID and Directory ID. Get in touch with firstname.lastname@example.org, request to enable the Azure AD integration and include the application id, directory id and SelfGuide tenant name in the request.