MicrosoftSince upgrading to v3 and replacing the Skype Network Assessment Tool with the Teams Network Assessment Tool, the M365 Teams Network Assessment Status Monitor on all watchers intermittently alerts with this:
This monitor has detected an issue while attempting to perform a Teams Network Assessment.Program 'C:\Program Files (x86)\Microsoft Teams Network Assessment Tool\NetworkAssessmentTool.exe' did not run long enough to complete the test call.
Output: Microsoft Teams - Network Assessment Tool
Failed to read parameters from ECS: One or more errors occurred.
Attempting to use relay FQDN from app config file (NetworkAssessmentTool.exe.config).
Change 'Relay.FQDN' key in app config to set custom relay FQDN. Recommend consulting MS Support to do so.
Does the Teams Network Assessment Tool need configuring on each watcher perhaps?
I ran the "C:\Program Files (x86)\Microsoft Teams Network Assessment Tool\NetworkAssessmentTool.exe" and it has a whole lot of information, but we didn't need to touch this with the Skype one, so just wondering if we do for the new tool?
Or perhaps more Proxy rules are required to M365 when using v3/Teams Network Assessment Tool? In saying that, I ran traces on our Proxy against a watcher and no traffic is dropped.
I do see Relay : 52.114.22.43 is the relay load balancer (VIP), Relay : 52.114.22.43 is not reachable using Protocol UDP and Port 3478 but is this something I now need to configure in the Proxy or is it a test that I turn off in the tool?
05/08/2022 - UPDATE - as there has not been any feedback about this, I am reluctant to transition v3 into our Production environment with this (one of two that I commented on) issue still not addressed. I could raise a Microsoft Support case but I don't know if this new version has a bug and typically before it goes live, I would have hoped this would be addressed.
Does anyone have anything to add or anyone else see this behaviour? Thanks
26/08/2022 - UPDATE - still no feedback about this so logged Microsoft Support case today.
