Adding a Microsoft Teams Component

eG Enterprise cannot auto-discover a Microsoft Teams component. This is why, you need to manually add the component to the eG Enterprise system to monitor it. The steps for manually adding a Microsoft Teams component are detailed below:

  1. Login to the eG admin interface as a user with administrative privileges.
  2. Follow the Infrastructure -> Components -> Add/Modify Component menu sequence in the Admin tile menu.
  3. From the page that appears, select Microsoft Teams as the Component type and click the Add New Component button.
  4. Figure 1 will then appear.

    Figure 1 : Adding a Microsoft Teams component

  5. In Figure 1, by default, portal.office.com will be displayed as the Host name of the target Microsoft Teams component.
  6. Provide a unique Nick Name for the Microsoft Teams component being added. Note that any nick name you specify here will be automatically suffixed with the string, _mtm.
  7. Since Microsoft Teams is by default monitored in an agentless manner, the Agentless flag will be enabled. Let the default settings remain in the OS and Mode selection boxes.
  8. Next, select the Remote agent that will monitor the target Microsoft Teams component.
  9. Finally, click the Add button to add the component to the eG Enterprise system.
  10. eG Enterprise allows you the flexibility to automatically manage a SharePoint Online, Exchange Online, Skype for Business Online, Office 365, and/or a Microsoft OneDrive for Business component, when adding a Microsoft Teams component. This is why, when clicking the Add button in Figure 1, you will be immediately prompted to manage the above-mentioned components using the same nick name as the Office 365 component (see Figure 2). Select the components you want to add by checking the corresponding check boxes in Figure 2and click the OK button. If you do not want to add any component other than Microsoft Teams , then click OK without selecting any of the check boxes.

    Figure 2 : A message prompting you to add other Office 365 components

    Note:

    • When Office 365 components are so added, eG Enterprise automatically appends a unique suffix to the nick name of each component. This means that every component will have the same nick name, but with a different suffix. These suffixes are listed in the table below:

      Component Type

      Suffix

      Microsoft Office 365

      _365

      Microsoft Exchange Online

      _exo

      Microsoft SharePoint Online

      _spo

      Microsoft Teams

      _mtm

      Microsoft Skype for Business Online

      _sbo

      Microsoft OneDrive for Business

      _odb

      For instance, say you are adding a component of type Microsoft Teams with the nick name eGTeams. Assume that when adding this component you choose to add a Microsoft Exchange Online component as well. At the end of this exercise, the following components will be added to the eG Enterprise system:

      Component Type

      Nick name

      Microsoft Teams

      eGTeams_mtm

      Microsoft Exchange Online

      eGOffice_exo

    • Whether you add the chosen components using different nick names, or using the same nick name as that of the Microsoft Teams component, each component you add will consume a separate Premium Monitor license.
    • In a SaaS deployment of eG Enterprise, an administrator has to make sure that all Office 365 components of a single tenant are managed in eG Enterprise using the same nick name - i.e., are managed using step 10 above. For instance, tenant A should use a common nick name - say, O365 - to manage all Office 365 components in their environment. Likewise, tenant B should use one nick name, say Office, for managing their entire Office infrastructure. At no point of time should the tenants change the nick name of one/more Office 365 components in their environment.

      This is required because the Office 365 Dashboard in the eG monitoring console groups metrics and visuals using the nick name you choose. To receive meaningful, tenant-specific insights into the performance of the Office 365 infrastructure, the aforesaid 'nick naming conventions' need to be followed.