You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

Prerequisites

For VSM to receive data from Microsoft Teams you will need a VSM Virtual Collector administered. Details on adding a VSM Virtual Collector can be found here.

Azure Active Directory Configuration

VSM uses Graph API to collect data from Microsoft Teams, the following information is required to add Microsoft Teams to VSM:

  • Tenant ID
  • Application ID
  • Shared Secret

In order to obtain the required fields the following steps need to be executed on the Tenant Azure AD 

  • New APP Registration
  • Assign the appropriate API Permission to the new APP
  • Generate Shared secret Key


All steps from this point forward require the AAD (Azure Active Directory) user permissions

New App Registration

Browse to Azure Portal AD https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade

Navigate to and click on 'App Registrations'


Click (plus) New registration


Enter Application Registration Details using the following table.

Application Registration Table

FieldValue
NameEnter the name you want to give to your application
Supported Account TypeChoose Accounts in this organizational directory only (Virsae Group Limited only - Single tenant)
Redirect URILeave Blank


After creating the Application take note of Application (Client) ID and Directory (tenant) ID

Assign API Permission to the New APP


Navigate to and click on 'API Permissions'


Click (plus) Add a permission


Click on Microsoft Graph


Choose Application Permissions


Choose the following Permissions

Call Records >CallRecords.Read.All permission 

Directory > Directory.Read.All Permission

Reports > Reports.Read.All

ServiceHealth > ServiceHealth.Read.All

TeamMember > TeamMember.Read.All

TeamworkDevice > TeamWorkDevice.Read.All



The following page will appear


Click on the 'Grant admin consent' tab to grant permission for newly created Application


Once Granted the following will be displayed

Generate Shared Secret

Navigate to and click on 'Certificates & secrets'


Click (plus) New client secret


Enter Client Secret Information using the following table.

Client Secret Table

FieldValue
DescriptionEnter description for the client secret
Expires The maximum length is 24 months , make sure to renew the client secret when it expires otherwise VSM won't be able to retrieve MS Teams Calls information 



Take note of Secret Value and Secret ID as it will disappear when you navigate away from the page , The value in the field Value is the value that is going to be added to VSM in Shared Secret Field 


Update Azure Active Directory Settings

 For Azure AAD To Display identifiable user data data (like UPNs) Navigate to

Admin Center >> Settings >> Org Setting >> Reports >> Uncheck  'Display concealed user, group, and site names in all reports'

Web Portal Configuration

Add Microsoft Teams

Log in to the VSM web portal using your VSM credentials and password.

For your customer, select Service Desk > Equipment Locations  Right-click on the Equipment Location (Virtual Collector) and select Manage Cloud Services


At the bottom of Manage Cloud Services click 'Add Services' 

The 'Add Service' form will open, Select the Vendor 'Microsoft' and Service 'Teams Cloud Service'

Populate the 'Friendly Name' field with the name you wish VSM to use for this Teams Service.

The Tenant ID, Application ID, and Shared Secret fields can be populated with details collected earlier in this process.

Web Portal - Add Microsoft Teams Field Description

FieldValue
VendorMicrosoft
ServiceTeams Cloud Service
Friendly NameFriendly Name for MS Teams
Tenant Id

Directory (Tenant)ID displayed under the created Application 

Application Id

Application (client) ID displayed under the created Application 

Shared SecretThe value under Client Secret

When you have completed the form click 'Add'.

Administration of Microsoft Teams in VSM is now complete.


  • No labels