Mar 14 2022 03:46 PM - edited Apr 05 2022 07:54 PM
The Microsoft 365 network connectivity test tool has just been updated with a stand-alone EXE added for more flexibility in testing. The stand-alone EXE allows you to run the same tests without having to load the web site. This will be useful if you want to automate the tests and you can deploy the EXE to the client machines using your software distribution tools. The output of the tests is saved to a JSON file on the local hard drive rather than showing up on the web page or in the Microsoft 365 Admin Center.
You can read the help and download the stand-alone EXE here:
We also updated both the stand-alone EXE and the original test tool to .NET 6.0 and this means if you have run the tool from the web site before and run it again you will be prompted to update.
https://connectivity.office.com
Please try out the new stand-alone EXE and let us know your feedback here.
Mar 16 2022 06:56 AM
@Paul Andrew Not sure if im being dumb but i dont see any dl link to the standalone .exe ?
Mar 16 2022 08:56 AM
Apr 05 2022 06:40 PM
The link Paul provided is not going to the correct anchor. This is the correct one: Microsoft 365 network connectivity test tool - Microsoft 365 Enterprise | Microsoft Docs
Apr 25 2022 01:50 PM
May 09 2022 12:48 PM
May 09 2022 12:51 PM
@alexourique the JSON entries align with the web page tabular report. Is there some specific node that you are not understanding?
May 09 2022 01:06 PM
Jul 20 2022 01:46 PM
@Paul Andrew is this tool the same tool as the one located at
https://connectivity.office.com/report/ ?
either way it keeps asking me to install .net 6.0 over and over even after reboot.
is there something i'm missing?
Jul 21 2022 09:43 AM
Hi @HAPPYSLAPS, these are different tools. But we use .net 6 for both of them. Please ensure you selected the right download of .net 6 which is
Paul
Nov 23 2023 06:31 AM
@Paul Andrew: I would like to use the command line tool and the parameter "-proxy <account><password> Proxy account name and password can be provided if you require a proxy to access the internet"
But the error message still is Unhandled exception. System.Net.Http.HttpRequestException: The proxy tunnel request to proxy 'XXX' failed with status code '407'."
How is the right way to use the paramter to get the tool working with a proxy and authentication?