Agents Administration - Tests
 

Configuration of MTMWHFdBckSmryTest

This test monitors the feedback provided by users on Microsoft Teams and helps administrators determine the count of poor feedback rating provided by the users. The overall rating of Microsoft Teams provided by users helps administrators determine the user experience on Microsoft Teams.

Note:

This test uses Webhooks to collect metrics. Before running the Webhooks-based tests for Teams, make sure that the following pre-requisites are fulfilled:

  • Make sure that all the pre-requisites under Monitoring Office 365 are fulfilled;

  • Install and start the Webhooks service on the same system that hosts the eG agent.

  • A public HTTPS URL is required for the endpoint, so it can receive call records from Microsoft. To enable this transmission, make sure that the firewall is configured to allow traffic from the internet to the system hosting the Webhooks service. Also, make sure that the port at which the service listens is open.

  • Ensure that the Webhooks service is SSL - enabled.

  • The Microsoft Graph app should be configured with the User.Read.All Delegated Permission and the CallRecords.Read.All Application Permission; to know how to register the Microsoft Graph app on Azure Active Directory and assign permissions.

For more details on the above listed steps, refer to Pre- requisites for Monitoring Microsoft Office 365 Environments and Using Webhooks to Measure Call Quality documents.

The default parameters associated with this test are as follows:

  • The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

  • In the HOST text box, the host for which the test is to be configured has to be specified. By default, this is portal.office.com

  • The parameter TENANT NAME applies only if you want the eG agent to use Azure AD Certificate-based Authentication for accessing and monitoring an O365 tenant and its resources.

    Azure AD certificate-based authentication (CBA) enables customers to allow or require users to authenticate with X.509 certificates against their Azure Active Directory (Azure AD) for applications and browser sign-in. When monitoring highly secure Office 365 environments, you can configure the eG agent to identify itself to a tenant using a valid X.509 certificate, so that it is allowed secure access to the tenant and its resources.

    By default, the value of this parameter is none. This means that, by default, the eG agent does not use certificate-based authentication to connect to an O365 tenant.

    On the other hand, if you want the eG agent to use this modern authentication technique to securely access a tenant's resources, you should do the following:

    1. Enable Azure AD Certificate-based authentication for the target O365 tenant; this can be achieved manually, via the Office 365 portal, or automatically, using Powershell scripts we provide. For the manual and automatic procedures, refer to Monitoring Microsoft Office 365 document.

      When enabling certificate-based authentication, an X.509 certificate will be generated for the target tenant.

    2. Configure the TENANT NAME parameter with the name of the tenant for which certificate-based authentication is enabled. Using the tenant name, the eG agent will be able to read the details of the X.509 certificate that is generated for that tenant, and use that certificate to access that tenant's resources. To determine the tenant name, do the following:

      • Log in to the Microsoft 365 Admin Center as an administrator

      • Under Setup, click on Domains
      • Find a domain that ends with .onmicrosoft.com - this is your Microsoft O365 tenant name

    • For execution, this test requires the privileges of an O365 user who has been assigned the SERVICE SUPPORT ADMIN role and is vested with the VIEW-ONLY AUDIT LOGS and TEAM ADMINISTRATOR permissions. Specify the credentials of such a user in the O365 USERNAME and O365 PASSWORD text boxes. Confirm the password by retyping it in the CONFIRM PASSWORD text box.

      While you can use the credentials of any existing O365 user with the afore-said privileges, it is recommended that you create a special user for monitoring purposes using the Office 365 portal and use the credentials of that user here. To know how to create a new user using the Office 365 portal and assign the required privileges to that user, refer to Creating a New User in the Office 365 Portal.

    • This parameter is applicable only for Domain - Microcsoft Teams component. Specify the name of the domain that is to be monitored. For example, if the user wants to monitor the performance of eginnovations.com domain, then the domain name has to be keyed in as eginnovations.com in the Lookup Domain text box.

    • The below-highlighted parameters are applicable only if the eG agent needs to communicate with the Office 365 portal via a Proxy server.

      In this case, in the DOMAIN NAME text box, specify the name of the Windows domain to which the eG agent host belongs. In the DOMAIN USERNAME text box, mention the name of a valid domain user with login rights to the eG agent host. Specify the password of that user in the DOMAIN PASSWORD text box and confirm that password by retyping it in the CONFIRM PASSWORD text box.

      On the other hand, if the eG agent is not behind a Proxy server, then you need not disturb the default setting of these parameters. By default, these parameters are set to none.

    • The below-highlighted parameters are applicable only if the eG agent needs to communicate with the Office 365 portal via a Proxy server.

      In this case, specify the IP/host name and port number of the Proxy server that the eG agent should use in the PROXY HOST and PROXY PORT text boxes, respectively.

      If the Proxy server requires authentication, then specify the credentials of a valid Proxy user in the PROXY USERNAME and PROXY PASSWORD text boxes. Confirm that password by retyping it in the CONFIRM PASSWORD text box. If the Proxy server does not require authentication, then specify none in the the PROXY USERNAME, PROXY PASSWORD, and CONFIRM PASSWORD text boxes.

      On the other hand, if the eG agent is not behind a Proxy server, then you need not disturb the default setting of any of the Proxy-related parameters. By default, these parameters are set to none.

    • By default, this parameter SHOW TOP N DD is set to 10, indicating that the detailed diagnostics will report the top-10 data. You can change the ‘N’ in SHOW TOP N DD by specifying any number of your choice in this text box.

    • The DD FREQUENCY parameter refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD FREQUENCY .

    • To make diagnosis more efficient and accurate, the eG suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the DETAILED DIAGNOSIS capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

      The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

      • The eG manager license should allow the detailed diagnosis capability.

      • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

    • If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

    • Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

    When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.