Team Operations/ Channel Operations Test

Microsoft Teams provides a great out-of-the-box collaboration experience for your organization. Besides using teams and channels for communication, users are also optionally allowed to use different add-ons such as bots, tabs and connectors. Using these add-ons will help users communicate more efficiently with other users in the organization. To know which of these add-ons are popular amidst users, administrators need to measure the workload of each add-on type. In other words, administrators have to know how many add-ons are created/modified/deleted for each add-on type. Administrators may also need to be aware of the teams and channels created on Microsoft Teams. The Team Operations/ Channel Operations test provides administrators with this insight!

This test reports the number of teams created on Microsoft Teams and the number of channels added to /deleted from teams. Also, this test throws light on the add-ons such as bots, connectors and tabs. Using this test, administrators can figure out the unique count of tabs and connectors that were added to/removed from channels. Similarly, administrators can figure out the count of bots that were added to /removed from team. Using these metrics, administrators can gauge the popularity of each add-on on Microsoft Teams. With the help of the detailed diagnostics of this test, you can also identify which add-on was most commonly used by the users.

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
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.
DD Frequency	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 the 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.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise 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 enabled/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.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Team creations	Indicates the number of teams created.	Number	A team is a collection of people who gather together around a common goal. The detailed diagnosis of this measure lists the name of the teams created, the time at which the teams were created, the User ID of the team creator, user type and the Team GUID.
Channel additions to team	Indicates the number of channels added to the teams.	Number	Channels are the collaboration spaces within a team where the actual work gets done. The detailed diagnosis of this measure lists the name of the team, the name of the channel added to the team, the time at which the channels were created, the User ID of the channel creator, user type and the Team GUID.
Channel deletions from team	Indicates the number of channels deleted from the teams.	Number	The detailed diagnosis of this measure lists the name of the team, the name of the channel added to the team, the time at which the channels were deleted, the User ID of the channel creator, user type and the Team GUID.
Bot additions to team	Indicates the number of bots added to the teams.	Number	Bots are automated programs that respond to queries or give updates and notifications about details users find interesting or want to stay informed about. Bots allow users to interact with cloud services such as task management, scheduling, and polling in a Teams chat. Teams supports bots in private chats and channels. The detailed diagnosis of this measure lists the time at which the bot was added to the team, the name of the team to which the bot was added, the name of the bot, the User ID who added the bot, the type of user and the Team GUID.
Bot removals from team	Indicates the number of bots removed from the teams.	Number	The detailed diagnosis of this measure lists the time at which the bot was removed to the team, the name of the team from which the bot was removed, the name of the bot, the User ID who removed the bot, the type of user and the Team GUID.
Tab additions to channel	Indicates the number of tabs added to the channels.	Number	Tabs are Teams-aware webpages embedded in Microsoft Teams. They are simple iframes that point to domains declared in the app manifest and can be added as part of a channel inside a team, a group chat, or as a personal app for an individual user. There are two types of tabs available in Teams - channel/group and personal. A channel/group tab delivers content to channels and group chats, and are a great way to create collaborative spaces around dedicated web-based content. Personal tabs, along with personally-scoped bots, are part of personal apps and are scoped to a single user. The detailed diagnosis of this measure lists the name of the tab added to the channel, the time at which the tab was added, the name of the team and the name of the channel, the User ID who added the tab, user type and the Team GUID.
Tab removals from channel	Indicates the number of tabs removed from the channels.	Number	The detailed diagnosis of this measure lists the name of the tab removed from the channel, the time at which the tab was removed, the name of the team and the name of the channel, the User ID who removed the tab, user type and the Team GUID.
Tab modifications in channel	Indicates the number of tabs that were modified on the channels.	Number	The detailed diagnosis of this measure lists the name of the tab that was modified on the channel, the time at which the tab was modified, the name of the team and the name of the channel, the User ID who modified the tab, user type and the Team GUID.
Connector additions to channel	Indicates the number of connectors that were added to the channels.	Number	Connectors keep your team current by delivering frequently used content and service updates directly into a channel. With connectors, your Microsoft Teams users can receive updates from popular services such as Trello, Wunderlist, GitHub, and Azure DevOps Services within the chat stream in their team. The detailed diagnosis of this measure lists the name of the connector added to the channel, the time at which the connector was added, the name of the team and the name of the channel, the User ID who added the connector, user type and the Team GUID.
Connector removals from channel	Indicates the number of connectors that were removed from the channels.	Number	The detailed diagnosis of this measure lists the name of the connector removed from the channel, the time at which the connector was removed, the name of the team and the name of the channel, the User ID who removed the connector, user type and the Team GUID.
Connector modifications in channel	Indicates the number of connectors that were modified on the channels.	Number	The detailed diagnosis of this measure lists the name of the connector that was modified on the channel, the time at which the connector was modified, the name of the team and the name of the channel, the User ID who modified the connector, user type and the Team GUID.

The detailed diagnosis of the Team creations measure lists the name of the teams created, the time at which the teams were created, the User ID of the team creator, user type and the Team GUID.

Figure 1 : The detailed diagnosis of the Team creations measure

The detailed diagnosis of the Channel additions to team measure lists the name of the team, the name of the channel added to the team, the time at which the channels were created, the User ID of the channel creator, user type and the Team GUID.

Figure 2 : The detailed diagnosis of the Channel additions to team measure

The detailed diagnosis of the Channel deletions from team measure lists the name of the team, the name of the channel added to the team, the time at which the channels were deleted, the User ID of the channel creator, user type and the Team GUID.

Figure 3 : The detailed diagnosis of the Channel deletions from team measure

The detailed diagnosis of the Tab additions to channel measure lists the name of the tab added to the channel, the time at which the tab was added, the name of the team and the name of the channel, the User ID who added the tab, user type and the Team GUID.

Figure 4 : The detailed diagnosis of the Tab additions to channel measure

The detailed diagnosis of the Tab modifications in channel measure lists the name of the tab that was modified on the channel, the time at which the tab was modified, the name of the team and the name of the channel, the User ID who modified the tab, user type and the Team GUID.

Figure 5 : The detailed diagnosis of the Tab modifications in channel measure

The detailed diagnosis of the Tab removals from channel measure lists the name of the tab removed from the channel, the time at which the tab was removed, the name of the team and the name of the channel, the User ID who removed the tab, user type and the Team GUID.

Figure 6 : The detailed diagnosis of the Tab removals from channel measure

The detailed diagnosis of the Connector additions to channel measure lists the name of the connector added to the channel, the time at which the connector was added, the name of the team and the name of the channel, the User ID who added the connector, user type and the Team GUID.

Figure 7 : The detailed diagnosis of the Connector additions to channel measure

The detailed diagnosis of the Connector removals from channel measure lists the name of the connector removed from the channel, the time at which the connector was removed, the name of the team and the name of the channel, the User ID who removed the connector, user type and the Team GUID.

Figure 8 : The detailed diagnosis of the Connector removals from channel measure

The detailed diagnosis of the Connector modifications in channel measure lists the name of the connector that was modified on the channel, the time at which the connector was modified, the name of the team and the name of the channel, the User ID who modified the connector, user type and the Team GUID.

Figure 9 : The detailed diagnosis of the Connector modifications in channel measure

The detailed diagnosis of the Bot additions to team measure lists the time at which the bot was added to the team, the name of the team to which the bot was added, the name of the bot, the User ID who added the bot, the type of user and the Team GUID.

Figure 10 : The detailed diagnosis of the Bot additions to team measure

The detailed diagnosis of the Bot removals from team measure lists the time at which the bot was removed to the team, the name of the team from which the bot was removed, the name of the bot, the User ID who removed the bot, the type of user and the Team GUID.

Figure 11 : The detailed diagnosis of the Bot removals from team measure