Chat now with support
Chat with Support

Unified Communications Analytics 8.8.3 - Deployment Guide

Prerequisites for your installation Installing UC Analytics Configuring UC Analytics Adding data sources for Active Directory or Azure Active Directory Adding data sources, chargeback costs, and thresholds for Exchange and Exchange Online
Permissions needed to collect Exchange on-premises or hybrid data Permissions needed to collect from native Exchange Online Creating an Exchange Configuration data source Creating an Exchange Tracking Logs data source Creating an Exchange Mailbox Contents data source Do I need both Exchange Tracking Logs and Exchange Mailbox Contents collections? Creating an Exchange IIS Logs data source Creating an Exchange Mailbox Content Summary data source Creating an Exchange Calendar data source Creating an Exchange Public Folders data source Adding Exchange Online hybrid data sources for hybrid Office 365 Adding Exchange Online data sources for native Office 365 Setting chargeback costs for Exchange Setting thresholds for Exchange metrics Omitting words when filtering by subject or body
Adding data sources, chargeback costs, and thresholds for Skype for Business/Lync Adding data sources, chargeback, and thresholds for Cisco Managing which insights can seen by users Configuring and managing subscriptions Making changes to your deployment Appendix A:Configuring Exchange and Office 365 Appendix B:Configuring the Skype for Business or Lync Server Appendix C:Configuring IIS Log Files to capture ActiveSync or OWA events Appendix D:PowerShell cmdlets used by data sources Appendix E:Backup and recovery options Appendix F:Custom configurations Appendix G: Questions and answers about UC Analytics

Appendix A:Configuring Exchange and Office 365

Overview

This section describes configuration tasks that you must perform in the Microsoft Exchange and Office 365 environments before you start to configure UC Analytics. These tasks include the following:

Any credentials that are used to collect data using the Exchange Mailbox Contents or the Exchange Online Mailbox Contents data sources must have application impersonation rights or “Exchange Impersonation” permissions to all the target mailboxes:

To see instructions about how to register the UC Analytics application in the Microsoft Azure portal so that you can use OAuth authentication for EWS, see Registering UC Analytics with the Microsoft Azure portal .

If you want to use a multi-forest environment with a one-way trust, see Setting up a multi-forest environment with a one-way trust .

Microsoft has announced that it will soon decommission Basic Authentication for EWS as a method to access Exchange Online. You can configure UC Analytics to use OAuth by specifying an Azure Application ID for UC Analytics in the Target Environments page. For the procedure to register an application with Microsoft Azure AD and create the Azure Application ID, see Registering UC Analytics with the Microsoft Azure portal .

To use OAuth modern authentication when accessing Exchange Online with remote PowerShell you must have the Exchange Online PowerShell module (v1 or v2) installed. You can install the v1 module using the Exchange admin center (EAC) or install the v2 module using the Microsoft article titled Install and Maintain the Exchange Online PowerShell V2 Module. See Installing the Exchange Online PowerShell module .

Setting impersonation for Exchange 2013/2016/2019

To collect data from Exchange 2013/2016/2019, the credentials used to collect Exchange data must have Application Impersonation rights for the mailboxes from which you are collecting.

2
Click Permissions.
4
6
Select ApplicationImpersonation and click add->.
7
10
Click Save.

Configuring impersonation for Office 365

To collect data from Exchange Online (Office 365) using the Exchange Online Mailbox Contents data source, the credentials used to collect the data must have Application Impersonation rights. The account must be assigned to a Role-Based Access Control group that has Application Impersonation rights. By default, no groups have Application Impersonation rights in Office 365.

You must sign in as an administrator to the Office 365 portal and add this right either to an existing role group or to a new role group that you create.

For example, you could create a new role group named Impersonation for Office 365 and add the Application Impersonation right to the group.

3
Click admin roles.
4
Click the + Icon to add a new role group.
6
7
Select ApplicationImpersonation from the list of roles
8
Click Add and click OK.
11
Click Add and click OK.
12
Click Save.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating