Teams Connectivity Test

If Microsoft Teams is unavailable / inaccessible, then users will not be able to use the same until such time the connection to Microsoft Teams is restored. The lack of Microsoft Teams connectivity, even for a brief while, can severely hamper business correspondence, affect user productivity, and ultimately hit revenues. To avoid this, administrators should continuously track the connectivity to Microsoft Teams so that they promptly detect any break/slowness in connectivity, and proactively initiate corrective measures. This is where the Teams Connectivity test helps!

This test emulates an HTTP connection to the portal URL, portal.office.com. In the process, this test reports whether Microsoft Teams is accessible or not, and if so, how long it takes for the users to connect to. This way, the test proactively reveals poor connectivity to Microsoft Teams, and thus enables administrators to initiate remedial measures before users complain.

Target of the test : Microsoft Teams

Agent deploying the test : A remote agent

Outputs of the test : One set of results for the monitored Microsoft Teams

Configurable parameters for the test
Parameters	Description
Test period	How often should the test be executed
Host	The host for which the test is to be configured. By default, this is portal.office.com
Port	The port at which the specified Host listens to. By default, this is NULL.
Tenant Name	This parameter 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: 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 procedure, refer to Manually Enabling Certificate-based Authentication For an Office 365 Tenantunder Microsoft Office 365. For the automatic procedure, refer to Automatically Fulfilling Pre-requisites in a Modern Authentication-Enabled Environmentunder Microsoft Office 365. When enabling certificate-based authentication, an X.509 certificate will be generated for the target tenant. 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.
O365 User Name, O365 Password, and Confirm Password	These parameters need to be configured only if the Tenant Name parameter is set to none. On the other hand, if a valid Tenant Name is configured, then you should set these parameters to none . 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 permission. Configure the credentials of such a user against O365 User Name 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 under Microsoft Office 365. You can also use eG's proprietary PowerShell script to automatically create a new user, or assign the required privileges to an existing user. To know how to use this script, refer to theAutomatically Fulfilling Pre-requisites in a Basic Authentication-Enabled Environmenttopicunder Microsoft Office 365 .
Domain Name, Domain User Name, Domain Password, and Confirm Password	These 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 text box, specify the name of the Windows domain to which the eG agent host belongs. In the Domain User Name text box, mention the name of a valid domain user with login rights to the eG agent host. Provide 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.
Proxy Host, Proxy Port, Proxy User Name, Proxy Password and Confirm Password	These parameters are applicable only if the eG agent needs to communicate with the Office 365 portal via a Proxy server. In this case, provide the IP/host name and port number of the Proxy server that the eG agent should use in the Proxy Host and Proxy Port parameters, respectively. If the Proxy server requires authentication, then specify the credentials of a valid Proxy user against the Proxy User Name 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 against the Proxy User Name, 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.

Measurements made by the test

Measurement

Description

Measurement Unit

Interpretation

Connection Status

Indicates the current connection status of Microsoft Teams.

The values reported by this measure and its numeric equivalents are mentioned in the table below:

State	Numeric Value
Success	1
Failure	0

Note:

By default, this measure reports the States listed in the table above to indicate the current connection status of Microsoft Teams. The graph of this measure however, is represented using the numeric equivalents only i.e., 0 or 1.

Time taken to connect

Indicates the average time taken by the users to connect to Microsoft Teams.

Seconds

Ideally, the value of this measure should be low. A high value for this measure is often associated with poor user experience indicating that the users took abnormally longer than usual to connect to Microsoft Teams. To ensure a high quality experience for Microsoft Teams users, you need to investigate why connectivity is slow and fix it.