From 3388e82b335a52479354f2d0513be2b10349a729 Mon Sep 17 00:00:00 2001 From: Vinay Pamnani <37223378+vinaypamnani-msft@users.noreply.github.com> Date: Wed, 8 Mar 2023 14:25:58 -0500 Subject: [PATCH] Update policy-csp-networklistmanager.md --- .../mdm/policy-csp-networklistmanager.md | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/windows/client-management/mdm/policy-csp-networklistmanager.md b/windows/client-management/mdm/policy-csp-networklistmanager.md index c10ddea1d6..1c4f398a68 100644 --- a/windows/client-management/mdm/policy-csp-networklistmanager.md +++ b/windows/client-management/mdm/policy-csp-networklistmanager.md @@ -42,20 +42,19 @@ List of URLs (seperated by Unicode character 0xF000) to endpoints accessible onl - +- When entering a list of TLS endpoints in Microsoft Intune using a configuration profile with a custom template and the OMA URI, use the following format: `` - The HTTPS endpoint must not have any more authentication checks, such as sign-in or multi-factor authentication. - The HTTPS endpoint must be an internal address not accessible from outside the organizational network. - The client must trust the server certificate. So the CA certificate that the HTTPS server certificate chains to must be present in the client machine's root certificate store. - A certificate shouldn't be a public certificate. -Test the URL using this command, it MUST return a HTTP_STATUS_OK 200 +To test the URL, use a PowerShell command similar to below: -`Invoke-webrequest https://nls.corp.contoso.com -Method get -UseBasicParsing -MaximumRedirection 0` - -When entering a list of TLS endpoints in Microsoft Intune using a configruation profile with a custom template and the OMA URI, the URLs must be seperated by Unicode character 0xF000. It must be this format: - -`` +```powershell +Invoke-WebRequest -Uri https://nls.corp.contoso.com -Method get -UseBasicParsing -MaximumRedirection 0 +``` +`StatusCode` return by the command must be 200 (`HTTP_STATUS_OK`).