Totalview Teams Presence uses polling to get and show the Teams presence in Totalview.
The polling requires that a polling application is created in Azure and that the TotalviewTeamsPresence connector has granted delegated permission and must be authenticated using a user existing in the Azure tenant.
Teams presence polling currently does not yet support application permissions and it is only possible to poll users in same tenant.
Register an Azure application
Go to https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade to create a new Azure application.
Register the new application
Enter a Name for the application.
Add an available address/port for the redirect URI.
This is where the URI where the TotalviewTemasPresence connector will listen for the OAuth2 access token.
Select Register to register the application.
Note the application id, directory id and redirect URI after the registration.
This information is required when registering the TotalviewTeamsPressence in TotalviewAdmin.
Register a Totalview Teams Presence connector in TotalviewAdmin
Start TotalviewAdmin, go to Connectors and create a new TeamsPresence connector under System extensions.
Add the Tenant Id, Client Id and Redirect Uri created when registering the Azure application.
Change Polling Interval if required. Default is polling every 10 sec.
Authenticate the Totalview Teams Presence connection using delegation.
Go to Overview and Install and register the service. Do not start the service.
Go to the folder where the Totalview Teams Presence connector is installed. By default, it is located on the server in <InstallDir>\TeamsPresence\TemsPresence_<connectorName>.
If Logs folder is not already created in Totalview Teams Presence connector folder, create it, as Administrator user.
Run the Totalview3TeamsPresence.exe. This will start the Totalview Teams Presence connector in console mode and start an authentication prompt in a browser.
Log in with an existing user on the tenant and accept the requested permissions. Any user can be used, but if the user changes password the user must login again. Therefore using an user, that has a password that does not expire is recommended.
If login is ok the console will show the polled users and their Teams presence.
Stop the console, go to Overview and start the connector as a service.
Check the connector log and verify that the connection is ok and that Teams presence is pulled.
Logout/Login with another user
To logout you must add the line <ForceLogin>True</ForceLogin> as a startupparameter to the config.xml and start the connector. The config.xml should look something like:
<?xml version="1.0" encoding="utf-8" ?> <startupparameters> <ServerIpAddress>127.0.0.1</ServerIpAddress> <ServerPort>3350</ServerPort> ... <FileLogLevel>4</FileLogLevel> <ForceLogin>True</ForceLogin> </startupparameters>
Remove the line, or set the value to false, after the logout is completed.