Configure SAML in Azure
In this page, we will walk you through the process of setting up SAML in Azure, enabling you to establish single sign-on (SSO) capabilities for your applications and services.
Prerequisites
To be able to follow this guide you need to have access to Azure Portal. You also need a Federation Metadata file sent to you from Ebbot. Please contact us to request the file.
Add an enterprise application
To add an enterprise application to your tenant:
Go to Azure portal and sign in using your account
Browse to Azure Active Directory and select Enterprise applications.
Click on New application -> Create your own application
Give the app a name
Select Integrate any other application you don't find in the gallery(Non-gallery)
Click on Create
Set up single sign on
Click on Set up single sign on and choose SAML at the next step.
On the next step you need to configure the Basic SAML Configuration.Our recommendation is to upload the metadata file but you can also configure it manually if you like.
| Parameter | Value |
|---|---|
Identifier (Entity ID) | |
Reply URL ( Assertion Consumer Service URL) | Will be provided by Ebbot |
Sign on URL | Will be provided by Ebbot |
Relay State | not needed |
Logout Url | not needed |
Attributes & Claims
You need to configure the following attributes.
| Attribute | Description | Example value |
|---|---|---|
First Name | ||
Last Name | ||
Must be email | ||
Username | Must be email | |
Bots | The id of the bot or bots that the user should have access to | ebbot-access-bot-eby03403249 |
Skills | The id of the skill. Only needed if you use skills | ebbot-access-bot-3204230 |
Roles | The name of the role. Custom name of one of our default roles: admin,owner,chat user | ebbot-access-role-admin |
Information needed by Ebbot
As a last step you need to provide Ebbot with some information to be able to finish the configuration.
Provide Ebbot with the following information.
App Federation Metadata Url
Login URL
Azure AD Identifier
Logout URL
Last updated
