The following checklist describes the tasks to perform on the Microsoft Azure portal and Application Center for enabling and configuring the Microsoft Teams SSO integration with Avaya Experience Platform™ Public Cloud:
No. |
Task |
Description |
Notes |

|
1. |
Create a SAML application. |
On the Microsoft Azure portal, create a SAML application to configure and enable SSO integration between Microsoft Teams and Avaya Experience Platform™ Public Cloud. |
Creating a SAML application on the Microsoft Azure portal |
|
2. |
Download the federation metadata file. |
On the Microsoft Azure portal, from the SAML-based Sign-on page, download the federation metadata .xml file. You need this file for SAML configuration in Application Center Administration. |
Creating a SAML application on the Microsoft Azure portal |
|
3. |
Provide existing Microsoft Azure users with access to the created SAML application. |
On the Microsoft Azure portal, assign users to the created application so that they can use SSO login in Avaya Workspaces. |
Providing Microsoft Azure users with access to the SAML application |
|
4. |
Add a SAML element to Element Inventory. |
In Application Center Administration, add a SAML server element to Element Inventory and upload the obtained federation metadata file. |
Adding a SAML element to Element Inventory |
|
5. |
Map Avaya Workspaces users with their Microsoft Azure accounts. |
In Application Center Administration, add the Microsoft Azure user email addresses obtained in step 3 to the Avaya Workspaces users. |
Mapping Avaya Workspaces users with Microsoft Azure accounts |
|
6. |
(Optional) If the browser where you use Avaya Workspaces blocks third-party cookies, add http://microsoftonline.com/ to the browser whitelist. |
For example, in Google Chrome, you can add a URL to the whitelist by going to and adding an exception for the site. The procedure is similar in Mozilla Firefox. |
For more information about adding a URL to the whitelist in Google Chrome, see the Allow or block access to websites section in Google Chrome Help. |
|