...
A proxy server capturing Teams traffic between the client and the cloud
Scripts injection from Agat cloud directly to the client
Possible issues in SphereShield proxy solution
User can’t sign in to Teams
Slow sign in process
Slowness in messages reaching destination
Slowness joining meetings \ user can’t join meetings
...
Issues (3) and (4) are probably server\database issues
How do I know to which Bastion server the client is connected?
From a client connected to Agat proxy run:
https://teams.microsoft.com/teams_protection/healthcheck/proxytest
In the response you should see the “Server Name”
...
Collecting logs for issues (1) or (2)
Browse C:\Agat\Bastion\filters\fw_proxy
Edit Teams_Protector.xml; <severity>debug</severity>
...
Gathering Teams Client Logs to Send to AGAT
Proxy diagnostic
From a Teams client machine, browse https://proxytest.agatcloud.com and take a screenshot of the output
From a Teams client machine, browse https://teams.microsoft.com/teams_protection/healthcheck/proxytest and take a screenshot of the output
Prepare logs to Agat:
Comperes server and client logs + screenshots
Enter ticket number (password will be provided by Agat)
Upload compressed file
In the ticket you open to Agat specify username and time of issue as well as screenshots if available
Collecting logs for issues (3) or (4)
Browse C:\Agat\Bastion\filters\fw_proxy
Edit Teams_Protector.xml; <severity>debug</severity>
...