Chatee ahora con Soporte
Chat con el soporte

Unified Communications Analytics 8.7 - 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

Appendix A:
Configuring Exchange and Office 365

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:

•
Setting impersonation for Exchange and Office 365
•
Registering the UC Analytics app with the Microsoft Azure Portal to use OAuth modern authentication
•
Installing the Exchange Online PowerShell module for PowerShell connections to Exchange Online

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:

•
For information about how to set Exchange impersonation for Exchange 2013, Exchange 2016. or Exchange 2019, see Setting impersonation for Exchange 2013/2016/2019 .
•
For information about how to set Exchange impersonation for Exchange 2010, see the following Microsoft article: Configuring Exchange Impersonation.
•
For information about how to set impersonation for Office 365, see Configuring impersonation for Office 365 .

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.

To set impersonation for the collection credentials
1
Open the web-based Exchange Admin Center (EAC) for your Exchange server.
2
Click Permissions.
3
Under Admin Roles, click +.
4
Enter a name for the new role group, such as Impersonation for Exchange.
5
Under the Roles heading, click +.
6
Select ApplicationImpersonation and click add->.
7
Click OK.
8
Under the Users heading, click +.
9
Select an account to be used to collect the mailbox contents data from Exchange and click OK.
Ensure that all the accounts you are using for Exchange Mailbox Contents data collections are added to this role group.
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.

To create a role group with impersonation rights and assign members
1
Log into the Office 365 Exchange Admin Center (EAC).
2
In the navigation tree on the left, select permissions.
3
Click admin roles.
4
Click the + Icon to add a new role group.
5
In the New Role Group dialog, enter the name for your new role group such as Impersonation for Office 365.
6
Under the Roles heading, click the + Icon to add a role.
7
Select ApplicationImpersonation from the list of roles
8
Click Add and click OK.
9
On the New Role Group dialog, under the Members heading, click the + icon to add a new member.
10
Select the account to be used for impersonation.
Ensure that all the accounts you are using for Exchange Online Mailbox Contents data collections are added to this role group.
11
Click Add and click OK.
12
Click Save.

Registering UC Analytics with the Microsoft Azure portal

To use modern authentication (OAuth) with the Exchange Online (hybrid and native) for EWS as a method to access Exchange Online, you must register the UC Analytics application with the Microsoft Azure portal. When you configure the Target Environments admin page in UC Analytics for hybrid or native Office 365, you specify the Azure Application ID that you have registered.

The process of registering an application with the Microsoft Azure portal is also described in the Microsoft topic Register an application with the Microsoft identity platform.

Depending on the region from which you are accessing the Microsoft Azure portal site, the user interface can differ.

Data sources that connect to Exchange Online using EWS are:

•
Exchange Online Mailbox Contents
•
Exchange Online Mailbox Content Summary
•
Exchange Online Calendar
To register the UC Analytics application
1
Sign in the Microsoft Azure portal. (You must have global admin rights to register an application.)
2
Search for App registrations in the search box at the top.
- OR-
In the left navigation pane, click the Azure Active Directory service, click App registrations and click New registration.
3
On the Register an application page, enter the application registration information:
•
Name: Enter a name for the application. For example, UC Analytics.
•
Supported account types: Select Accounts in any organizational directory (Any Azure AD directory - Multi tenant)
 
4
Click Register.
The application is registered in the Microsoft Azure portal and the Application (client) ID is displayed. Copy this ID and use it later to set the Azure Application ID in the Target Environments page.
5
Under Manage in the left section, click Authentication.
6
Click Yes for Default client type and click Save.
7
Under Manage in the left section, click API permissions.
8
Click Add a permission.
9
Scroll down to Supported legacy APIs and select Exchange.
10
Select Delegated permissions.
11
Select EWS.AccessAsUser.All.
In some Microsoft National Clouds, you might select full_access_as_user instead.
12
Click Add permissions.
13
Keep the default User.Read permission.
14
Click Grant admin consent for <Your Organization> and click Yes to confirm.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación