Configure single sign-on to Telax for your organization , using Microsoft Azure Active Directory.
Getting Started
First, you'll need to sign in to your Azure account. You can do so at https://azure.microsoft.com. If you don't yet have an Azure account, you can use this same URL to set one up.
...
| Info |
|---|
Please note that URI is required for SSO with Telax, although the Azure portal labels it as optional. |
...
- Name: A user-friendly name to display when using the SSO Service in Telax, e.g. Telax SSO.
- Supported account types: There are three options. At this time, we strongly recommend using the option: Accounts in this organizational directory only (Default Directory). All user and guest accounts in your directory can use your application or API. Use this option if your target audience is internal to your organization.
- Redirect URI (optional): For Telax, this This is mandatory. Select “Web” and type in the return Url URL textbox one of these two URLs:
- https://pop0-apps.mycontactcenter.net/sso/saml/azuread/acs.aspx (for clients in Facility 0 AKA Toronto), OR
- https://pop1-apps.mycontactcenter.net/sso/saml/azuread/acs.aspx (for Facility 1 AKA Chicago).
...
| Info |
|---|
As an administrator, you can grant consent on behalf of all users in this directory. Granting admin consent for all users means that end-users will not be shown a consent screen when using the application. |
...
Scope name: user_impersonation
Who can consent? Select Admins and users
Admin consent display name: provide a name, such as "Access My Contact Center (Telax)."
Admin consent description: enter a description, such as "Allow the application to access My Contact Center (Telax) on behalf of the signed-in user."
User consent display name: provide a display name, such as "Access My Contact Center (Telax)."
User consent description: enter a description, such as "Allow the application to access My Contact Center (Telax) on behalf of the signed-in user.
State: Enabled.
...