Cisco Catalyst Cloud Portal obtains the following information from your Microsoft tenant and stores it locally in the cloud:

• Microsoft Teams call records data

• User profile data, such as ID, email address, first name, last name, display name, and office location

Catalyst Cloud Portal stores data for one hour before deleting it.

To view the privacy policy for Catalyst Center, refer to the Catalyst Center privacy data sheet.

Only the Cisco Cloud Ops team can access your cloud database information.

Catalyst Cloud Portal stores Microsoft Teams data in an encrypted file system using AWS EBS. It encrypts sensitive data, such as access tokens, and stores them in the database.

Catalyst Cloud Portal requires these API permissions from Microsoft to retrieve your data:

• User.ReadBasic.All

• CallRecords.Read.All

• User.Read

An on-premises Catalyst Center instance polls Catalyst Cloud Portal every five minutes to retrieve data.

When Catalyst Center is integrated with Microsoft Teams, Catalyst Cloud Portal uses these FQDNs:

• dna.cisco.com

• dnaservices.cisco.com

• *.ciscoconnectdna.com

• neoffers.cisco.com

• neoffers-de.cisco.com

• app-experience-connect.cisco.com

• app-experience-connect-de.cisco.com

The Catalyst Cloud Portal service does not use any static IP addresses. If you need to control traffic, use domain names instead.

You cannot integrate an air-gapped Catalyst Center deployment with Microsoft Teams because integration requires a connection to Catalyst Cloud Portal.

For Catalyst Center versions up to 2.3.7.5, register an on-premises Catalyst Center instance in Catalyst Cloud Portal using either the US-West or EU Central region. For Catalyst Center 2.3.7.6 and later, you can only register using the US-West region.

When connected, Catalyst Cloud Portal and Microsoft Teams use these APIs:

• Authentication: {org tenant id}/adminconsent and {org tenant id}/oauth2/v2.0/token

• Subscription: v1.0/subscriptions

• Retrieving call records: v1.0/communications/callRecords/{call record id}?$expand=sessions($expand=segments) and v1.0/users/{user id}

If your Microsoft Teams account uses multifactor authentication (MFA), MFA is used when you enter account details during the consent flow.

Catalyst Center 2.3.7.6 and later use the OAuth2 standard device authentication flow. Earlier Catalyst Center versions used one-time password (OTP) authentication, where users generated a password in Catalyst Cloud Portal and used that password to complete the integration between Catalyst Center and Catalyst Cloud Portal.

After you grant Catalyst Cloud Portal permission, Microsoft Teams issues standard OAuth access and refresh tokens. Catalyst Cloud Portal refreshes the access token every hour using a refresh token. User credentials are never sent to Catalyst Cloud Portal.

Only Microsoft Teams users configured with these roles can initiate integration:

• Global Administrator

• Privileged Role Administrator

• A custom role that has the permission to grant permissions to applications setting enabled

Note

For more information, refer to this article.

During the integration process, complete these steps to provide the consent necessary to authenticate Microsoft Teams:

1. In the Authenticate your application page, click the Click here to start the consent flow link.

2. In the resulting dialog box, enter your Microsoft Teams password and then click Sign in.

3. In the Permissions requested dialog box, choose the first two check boxes and then click Accept.

4. Do one of the following:

   • If you're configured with one of the three roles described in the previous FAQ entry (which means you have admin privileges), first click I am an Admin. Next, in the Permissions requested dialog box, click all three check boxes. And finally, click Accept.

   • If you don't have admin privileges, first click Copy URL. Next, send this URL to a user with admin privileges. And finally, have that user open the URL and provide the necessary consent.

The Application ID for the Catalyst Cloud Portal's OAuth application that is registered with Microsoft is 904c49f0-22c5-4a6f-a96c-613c2c319fc8. The name of the application is Cisco Catalyst Center Applications Experience.

There are no differences in the limitations or restrictions you may encounter when Microsoft Teams has been integrated with a physical Catalyst Center appliance versus a virtual appliance.

You can map one Catalyst Center instance to one Microsoft Teams tenant. Integrate a Catalyst Center instance with the appropriate Microsoft Teams account.

You can register multiple Catalyst Center instances with a single Catalyst Cloud Portal account. Catalyst Cloud Portal collects data from your subscribed Microsoft Teams account. Each registered Catalyst Center instance retrieves data from its managed clients.

If your network only has Catalyst 9000 Series switches, only Microsoft Teams scores and metrics are available. Catalyst 9000 Series switches do not provide qualitative metrics (like packet loss, latency, and jitter), so network application performance management (APM) metrics are not available.