Home

Office 365 Network Onboarding tool POC update

%3CLINGO-SUB%20id%3D%22lingo-sub-1160933%22%20slang%3D%22en-US%22%3EOffice%20365%20Network%20Onboarding%20tool%20POC%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1160933%22%20slang%3D%22en-US%22%3E%3CP%3EEarlier%20this%20week%20we%20published%20an%20update%20to%20this%20tool%20at%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fconnectivity.office.com%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fconnectivity.office.com%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20are%20actively%20developing%20this%20tool%20in%20support%20of%20your%20networking%20evaluation.%20Please%20continue%20to%20test%20out%20the%20proof%20of%20concept%20and%20provide%20feedback.%20Our%20teams%20next%20planned%20release%20is%20the%20private%20preview%20in%20the%20Microsoft%20365%20Admin%20Center%20which%20you%20can%20read%20about%20here%3A%20%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fnetignite%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Faka.ms%2Fnetignite%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20have%20used%20the%20tool%20before%2C%20I%E2%80%99d%20recommend%20using%20SHIFT-F5%20with%20the%20new%20release%20the%20first%20time%20you%20are%20back.%20Here%E2%80%99s%20the%20changes%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3ECompatibility%20with%20Edge%20Chromium.%20ClickOnce%20deployed%20applications%20are%20not%20enabled%20by%20default%20in%20Edge%20and%20a%20message%20will%20be%20shown%20when%20using%20Edge%20Chromium%20explaining%20how%20to%20turn%20this%20on.%20If%20you%20haven%E2%80%99t%20enabled%20it%2C%20expect%20to%20see%20an%20error%20that%20contains%20this%20text%20%E2%80%9CSystem.Deployment.Application.InvalidDeploymentException%20(Zone)%E2%80%9D%3C%2FLI%3E%0A%3CLI%3EWe%20corrected%20an%20error%20reporting%20on%20the%20client%20DNS%20server%20where%20IPv6%20DNS%20servers%20were%20not%20tested%20correctly.%3C%2FLI%3E%0A%3CLI%3EFor%20proxy%20servers%20and%20DNS%20recursive%20resolvers%20we%20now%20test%20distance%20first%20with%20ICMP%2C%20and%20then%20with%20TCP%20Ping%2C%20and%20then%20with%20IP%20Address%20geolocation.%3C%2FLI%3E%0A%3CLI%3ECorrected%20an%20error%20on%20the%20map%20where%20a%20single%20Microsoft%20datacenter%20was%20identified%20by%20two%20names%20and%20shown%20as%20overlapping.%3C%2FLI%3E%0A%3CLI%3EAlthough%20we%20do%20DNS%20server%20lookups%20on%20the%20test%20client%2C%20these%20are%20not%20relevant%20when%20a%20proxy%20server%20is%20in%20use%20since%20the%20actual%20data%20plan%20DNS%20lookup%20is%20done%20on%20the%20proxy%20server.%20We%20added%20a%20note%20to%20explain%20this%20if%20a%20proxy%20server%20is%20detected.%3C%2FLI%3E%0A%3CLI%3EA%20correction%20so%20that%20IP%20Addresses%20do%20not%20appear%20to%20be%20telephone%20numbers%20in%20some%20web%20browsers.%3C%2FLI%3E%0A%3CLI%3EIf%20we%20do%20not%20detect%20a%20proxy%20server%20but%20we%20do%20detect%20SSL%20Inspection%20then%20we%20added%20a%20note%20that%20there%20is%20probably%20a%20proxy%20server%20since%20that%E2%80%99s%20the%20most%20likely%20cause%20of%20SSL%20Inspection.%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsharepoint%2Ftroubleshoot%2Fadministration%2Ftls-1.0-and-1.1-deprecation-for-office-365%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ETLS%201.0%20and%20TLS%201.1%20are%20deprecated%3C%2FA%3E%20but%20some%20people%20still%20have%20machines%20with%20those%20enabled.%20We%20had%20an%20exception%20in%20this%20situation%20which%20we%E2%80%99ve%20added%20code%20to%20show%20more%20gracefully.%3C%2FLI%3E%0A%3CLI%3ESeparated%20the%20report%20into%20sections%20for%20Exchange%20Online%2C%20SharePoint%20Online%2C%20and%20Microsoft%20Teams%3C%2FLI%3E%0A%3CLI%3EEach%20test%20in%20the%20report%20now%20has%20a%20hover%20text%20for%20the%20test%20description.%3C%2FLI%3E%0A%3CLI%3EWe%20collapse%20the%20intro%20text%20for%20the%20web%20page%20if%20being%20viewed%20on%20a%20smartphone%20sized%20screen.%3C%2FLI%3E%0A%3C%2FOL%3E%3C%2FLINGO-BODY%3E
Paul Andrew
Microsoft

Earlier this week we published an update to this tool at https://connectivity.office.com.

 

We are actively developing this tool in support of your networking evaluation. Please continue to test out the proof of concept and provide feedback. Our teams next planned release is the private preview in the Microsoft 365 Admin Center which you can read about here: http://aka.ms/netignite

 

If you have used the tool before, I’d recommend using SHIFT-F5 with the new release the first time you are back. Here’s the changes:

 

  1. Compatibility with Edge Chromium. ClickOnce deployed applications are not enabled by default in Edge and a message will be shown when using Edge Chromium explaining how to turn this on. If you haven’t enabled it, expect to see an error that contains this text “System.Deployment.Application.InvalidDeploymentException (Zone)”
  2. We corrected an error reporting on the client DNS server where IPv6 DNS servers were not tested correctly.
  3. For proxy servers and DNS recursive resolvers we now test distance first with ICMP, and then with TCP Ping, and then with IP Address geolocation.
  4. Corrected an error on the map where a single Microsoft datacenter was identified by two names and shown as overlapping.
  5. Although we do DNS server lookups on the test client, these are not relevant when a proxy server is in use since the actual data plan DNS lookup is done on the proxy server. We added a note to explain this if a proxy server is detected.
  6. A correction so that IP Addresses do not appear to be telephone numbers in some web browsers.
  7. If we do not detect a proxy server but we do detect SSL Inspection then we added a note that there is probably a proxy server since that’s the most likely cause of SSL Inspection.
  8. TLS 1.0 and TLS 1.1 are deprecated but some people still have machines with those enabled. We had an exception in this situation which we’ve added code to show more gracefully.
  9. Separated the report into sections for Exchange Online, SharePoint Online, and Microsoft Teams
  10. Each test in the report now has a hover text for the test description.
  11. We collapse the intro text for the web page if being viewed on a smartphone sized screen.