Microsoft 365

This is a Vendor Integration.

• This integration collects 366 days of history by default upon first connection (and 90 for Copilot).

  • Number of days for Copilot is configurable by customer. Ask your Calero representative for more information.

Onboard This Integration

1. Go to SaaS Management > Applications.

2. Select Add Integration.

3. From the Vendors tab, select the card with the vendor's name.

4. From the API tab, if your company has more than one instance (or “tenant”) of this application, enter a Connection Alias.

5. Retain Phone Numbers is turned by default.

   • Toggle this option off if data masking should be used for phone calls.

6. Select one of the following access options:

   • Read Only — Will extract the required data from the vendor but exclude all functionality that allows actioning of licenses.

   • Read and Action — Will extract data from the vendor and allow actions to be taken for licenses (i.e., enable the “Action” menus) from within Calero.com.

     IMPORTANT!

     Read and Action access is required to support the Optimization process.

7. Select the Authorize button.

8. You will be redirected to the vendor portal login page.

9. Enter your administrator credentials and sign in.

10. Within the vendor portal, authorize the Calero.com application to fetch data.

Reference

See Also:

• Microsoft 365 Read or Action

• Microsoft Application Access Policy

Usage Data Collected by Integration

• Login per app — Per-user last activity across M365 apps on Windows, Mac, Mobile, and Web (Outlook, Word, Excel, PowerPoint, OneNote, Teams).

• LLM interaction — Last activity for Copilot Chat, Teams Copilot, Word, Excel, PowerPoint, Outlook, OneNote, Loop.

• Storage (OneDrive) — OneDrive storage used (bytes) per user/site when the feature flag is enabled.

• Storage (Exchange Online) — Exchange mailbox storage used (bytes) when the feature flag is enabled.

• Outlook activity — Outlook last activity, emails sent, meetings created, meetings interacted.

• Teams — PSTN and Direct Routing call logs; plus Peer-to-Peer, Group Call, and Meeting usage when the feature flag is enabled.

Data Masking for Phone Calls

To help protect personal information, Microsoft Teams call records can be automatically masked before they're stored. When masking is active, phone numbers, names, and other identifying details belonging to external parties (people outside your organization) are replaced with a placeholder value. Details about your own users are not affected.

• Masking is controlled by the Retain Phone Numbers setting, which is chosen during onboarding.

• Masked fields always display as five asterisks: *****

• Masking applies to the following Teams call types: PSTN, Direct Routing, Peer-to-Peer

Which fields are masked depends on the direction of the call, because the external party sits on a different side of the call in each case.