addressed comments and fixed errors

Author: vvs11

articles/playwright-testing/how-to-manage-authentication.md

@@ -81,9 +81,9 @@ To enable authentication using access tokens:
 
 ::: zone pivot="playwright-test-runner"
 
-1. Set up your environment
+3. Set up your environment
 
-    To set up your environment, you have to configure the `PLAYWRIGHT_SERVICE_ACCESS_TOKEN` environment variable with the value you obtained in the previous steps. Make sure this environment variable is available in your setup where you are running tests.
+    To set up your environment, configure the `PLAYWRIGHT_SERVICE_ACCESS_TOKEN` environment variable with the value you obtained in the previous steps. Ensure this environment variable is available in your setup where you are running tests.
 
     We recommend that you use the `dotenv` module to manage your environment. With `dotenv`, you define your environment variables in the `.env` file.
 
@@ -93,7 +93,7 @@ To enable authentication using access tokens:
         npm i --save-dev dotenv
         ```
 
-    1. Create a `.env` file alongside the `playwright.config.ts` file in your Playwright project:
+    2. Create a `.env` file alongside the `playwright.config.ts` file in your Playwright project:
 
         ```
         PLAYWRIGHT_SERVICE_ACCESS_TOKEN={MY-ACCESS-TOKEN}
@@ -107,7 +107,7 @@ To enable authentication using access tokens:
 
 3. Set up your environment
 
-    To set up your environment, you have to configure the `PLAYWRIGHT_SERVICE_ACCESS_TOKEN` environment variable with the value you obtained in the previous steps. Make sure this environment variable is available in your setup where you are running tests.
+    To set up your environment, configure the `PLAYWRIGHT_SERVICE_ACCESS_TOKEN` environment variable with the value you obtained in the previous steps. Ensure this environment variable is available in your setup where you are running tests.
 
 ::: zone-end
 

articles/playwright-testing/how-to-test-local-applications.md

@@ -1,12 +1,14 @@
 ---
-title: Use remote browsers for local applications
+title: Use remote browsers for local or private applications
 description: Learn how to run end-to-end for locally deployed applications with Microsoft Playwright Testing Preview. Use cloud-hosted browsers to test apps on localhost or private networks.
 ms.topic: how-to
 ms.date: 10/04/2023
 ms.custom: playwright-testing-preview
+zone_pivot_group_filename: playwright-testing/ZonePivotGroups.json
+zone_pivot_groups: microsoft-playwright-testing
 ---
 
-# Use cloud-hosted browsers for locally deployed apps with Microsoft Playwright Testing Preview
+# Use cloud-hosted browsers for locally deployed or privately hosted apps with Microsoft Playwright Testing Preview
 
 Learn how to use Microsoft Playwright Testing Preview to run end-to-end tests for locally deployed applications. Microsoft Playwright Testing uses cloud-hosted, remote browsers for running Playwright tests at scale. You can use the service to run tests for apps on localhost, or that you host on your infrastructure.
 
@@ -21,7 +23,9 @@ To expose local networks and resources to remote browsers, you can use the `expo
 
 You can specify one or multiple networks by using a list of rules. For example, to expose test/staging deployments and [localhost](https://en.wikipedia.org/wiki/Localhost): `*.test.internal-domain,*.staging.internal-domain,<loopback>`.
 
-You can configure the `exposeNetwork` option in `playwright.service.config.ts`. The following example shows how to expose the `localhost` network by using the [`<loopback>`](https://en.wikipedia.org/wiki/Loopback) rule:
+::: zone pivot="playwright-test-runner"
+
+You can configure the `exposeNetwork` option in `playwright.service.config.ts`. The following example shows how to expose the `localhost` network by using the [`<loopback>`](https://en.wikipedia.org/wiki/Loopback) rule. You can also replace `localhost` with a domain that you want to enable for the service.
 
 ```typescript
 import { getServiceConfig, ServiceOS } from "@azure/microsoft-playwright-testing";
@@ -43,6 +47,27 @@ You can now reference `localhost` in the Playwright test code, and run the tests
 ```bash
 npx playwright test --config=playwright.service.config.ts --workers=20
 ```
+::: zone-end
+
+
+::: zone pivot="nunit-test-runner"
+
+You can configure the `ExposeNetwork` option in `.runsettings`. The following example shows how to expose the `localhost` network by using the [`<loopback>`](https://en.wikipedia.org/wiki/Loopback) rule. You can also replace `localhost` with a domain that you want to enable for the service. 
+
+```xml
+    <TestRunParameters>
+        <!--Use this option to connect to local resources from your Playwright test code without having to configure additional firewall-->
+        <Parameter name="ExposeNetwork" value="loopback" />
+    </TestRunParameters>
+```
+
+You can now reference `localhost` in the Playwright test code, and run the tests on cloud-hosted browsers with Microsoft Playwright Testing:
+
+```bash
+dotnet test --settings:.runsettings --logger "microsoft-playwright-testing" -- NUnit.NumberOfTestWorkers=20
+```
+
+::: zone-end
 
 ## Related content
 

articles/playwright-testing/how-to-use-service-config-file.md

@@ -13,14 +13,14 @@ zone_pivot_groups: microsoft-playwright-testing
 ::: zone pivot="playwright-test-runner"
 
 This article shows you how to use the options available in the `playwright.service.config.ts` file that was generated for you. 
-If you don't have this file in your code, follow the QuickStart guide, see [Quickstart: Run end-to-end tests at scale with Microsoft Playwright Testing Preview](./quickstart-run-end-to-end-tests.md) 
+If you don't have this file in your code, follow [Quickstart: Run end-to-end tests at scale with Microsoft Playwright Testing Preview](./quickstart-run-end-to-end-tests.md) 
 
 ::: zone-end
 
 ::: zone pivot="nunit-test-runner"
 
 This article shows you how to use the options available in the `.runsettings` file. 
-If you don't have this file in your code, follow the QuickStart guide, see [Quickstart: Run end-to-end tests at scale with Microsoft Playwright Testing Preview](./quickstart-run-end-to-end-tests.md) 
+If you don't have this file in your code, follow [Quickstart: Run end-to-end tests at scale with Microsoft Playwright Testing Preview](./quickstart-run-end-to-end-tests.md) 
 
 ::: zone-end
 
@@ -171,6 +171,8 @@ Here's version of the `.runsettings` file with all the available options:
         <Parameter name="RunId" value="sample-run-id1" />
         <!--Select if you want to use cloud-hosted browsers to run your Playwright tests.-->
         <Parameter name="UseCloudHostedBrowsers" value="true" />
+        <!--Use this option to connect to local resources from your Playwright test code without having to configure additional firewall-->
+        <Parameter name="ExposeNetwork" value="loopback" />
         <!--Select the authentication method you want to use with Entra-->
         <Parameter name="AzureTokenCredentialType" value="DefaultAzureCredential" />
         <!--Enable/disable GitHub summary in GitHub Actions workflow.-->
@@ -223,7 +225,6 @@ Here's version of the `.runsettings` file with all the available options:
       <Parameter name="ServiceAuthType" value="EntraId" />
       ```
 
-
 * **`os`**:
     - **Description**: This setting allows you to choose the operating system where the browsers running Playwright tests are hosted.
     - **Available Options**:
@@ -256,6 +257,12 @@ Here's version of the `.runsettings` file with all the available options:
       ```xml
       <Parameter name="UseCloudHostedBrowsers" value="true" />
       ```   
+* **`ExposeNetwork`**
+    - **Description**: This setting allows you to connect to local resources from your Playwright test code without having to configure another firewall settings. To learn more, see [how to test local applications](./how-to-test-local-applications.md)
+    - **Example**:
+      ```xml
+      <Parameter name="ExposeNetwork" value="loopback" />
+      ```
 
 * **`reporter`**
     - **Description**: You can publish your test results and artifacts to the service using `microsoft-playwright-testing` logger. You can disable reporting by removing this from your `.runsettings` or by setting it to false. 
@@ -264,6 +271,7 @@ Here's version of the `.runsettings` file with all the available options:
       ```xml
       <Logger friendlyName="microsoft-playwright-testing" enabled="True" />
       ```
+
 * **`EnableGitHubSummary`**:
     - **Description**: This setting allows you to configure the Microsoft Playwright Testing service reporter. You can choose whether to include the test run summary in the GitHub summary when running in GitHub Actions.
     - **Default Value**: true

articles/playwright-testing/quickstart-automate-end-to-end-testing.md

@@ -153,7 +153,7 @@ Update the CI workflow definition to run your Playwright tests with the Playwrig
         branches: [ main, master ]
       pull_request:
         branches: [ main, master ]
-    permissions: # Required when using Micosoft Entra ID to authenticate
+    permissions: # Required when using Microsoft Entra ID to authenticate
       id-token: write
       contents: read
     jobs:
@@ -231,7 +231,7 @@ Update the CI workflow definition to run your Playwright tests with the Playwrig
 
 Update the CI workflow definition to run your Playwright tests with the Playwright NUnit CLI. Pass the `.runsettings` file as an input parameter for the Playwright CLI. You configure your environment by specifying environment variables.
 
-1. Open the CI workflow definition
+1. Open the CI workflow definition.
 
 1. Add the following steps to run your Playwright tests in Microsoft Playwright Testing.
 
@@ -340,12 +340,12 @@ Update the CI workflow definition to run your Playwright tests with the Playwrig
 
 ::: zone-end
 
-1. Save and commit your changes.
+3. Save and commit your changes.
 
     When the CI workflow is triggered, your Playwright tests run in your Microsoft Playwright Testing workspace on cloud-hosted browsers, across 20 parallel workers. The results and artifacts collected are published to the service and can be viewed on service portal.
 
 > [!NOTE]
-> Reporting feature is enabled by default for existing workspaces. This is being rolled out in stages and will take a few days. To avoid failures, confirm that `Rich diagnostics using reporting` setting is ON for your workspace before proceeding. See, [Enable reporting for workspace](./how-to-use-service-features.md#manage-feature-for-the-workspace).
+> Reporting feature is enabled by default for existing workspaces. This is being rolled out in stages and will take a few days. To avoid failures, confirm that `Rich diagnostics using reporting` setting is ON for your workspace before proceeding. For more information, see, [Enable reporting for workspace](./how-to-use-service-features.md#manage-feature-for-the-workspace).
 
 > [!CAUTION]
 > With Microsoft Playwright Testing, you get charged based on the number of total test minutes consumed and test results published. If you're a first-time user or [getting started with a free trial](./how-to-try-playwright-testing-free.md), you might start with running a single test at scale instead of your full test suite to avoid exhausting your free test minutes and test results.

articles/playwright-testing/quickstart-generate-rich-reports-for-tests.md

@@ -195,7 +195,7 @@ Microsoft Entra ID is the default and recommended authentication for the service
 az login
 ```
 > [!NOTE]
-> If you're a part of multiple Microsoft Entra tenants, make sure you sign in to the tenant where your workspace belongs. You can get the tenant ID from Azure portal. See [Find your Microsoft Entra Tenant](/azure/azure-portal/get-subscription-tenant-id#find-your-microsoft-entra-tenant). Once you get the ID, sign-in using the command `az login --tenant <TenantID>`
+> If you're a part of multiple Microsoft Entra tenants, make sure you sign in to the tenant where your workspace belongs. You can get the tenant ID from Azure portal. For more information, see [Find your Microsoft Entra Tenant](/azure/azure-portal/get-subscription-tenant-id#find-your-microsoft-entra-tenant). Once you get the ID, sign-in using the command `az login --tenant <TenantID>`
 
 ##### Set up authentication using access tokens
 
@@ -228,7 +228,7 @@ Enable artifacts such as screenshot, videos and traces to be captured by Playwri
 - For videos, see [record videos for your tests](https://playwright.dev/dotnet/docs/videos#introduction)
 - For traces, see [recording a trace](https://playwright.dev/dotnet/docs/trace-viewer-intro#recording-a-trace)
 
-Once you collect these artifacts, make sure you attach them to the test path. For more information and example, see [sample configuration for NUnit](https://aka.ms/mpt/nunit-sample)
+Once you collect these artifacts, make sure you attach them to the test path. For more information, see [sample configuration for NUnit](https://aka.ms/mpt/nunit-sample)
 
 ::: zone-end
 
@@ -261,7 +261,7 @@ You've now prepared the configuration for publishing test results and artifacts
 dotnet test --settings:.runsettings
 ```
 
-The settings for your test run is defined in `.runsettings` file. See [how to use service package options](./how-to-use-service-config-file.md#options-in-runsettings-file)
+The settings for your test run is defined in `.runsettings` file. For more information, see [how to use service package options](./how-to-use-service-config-file.md#options-in-runsettings-file)
 
 > [!NOTE]
 > For the Reporting feature of Microsoft Playwright Testing, you get charged based on the number test results published. If you're a first-time user or [getting started with a free trial](./how-to-try-playwright-testing-free.md), you might start with publishing single test result instead of your full test suite to avoid exhausting your free trial limits.

articles/playwright-testing/toc.yml

@@ -42,7 +42,7 @@ items:
     - name: Manage workspace access
       displayName: RBAC, permissions, access, role-based access control, users, roles, security, authorization, authentication, grant, revoke
       href: how-to-manage-workspace-access.md
-    - name: Run tests for local apps
+    - name: Run tests for local and private apps
       displayName: local, localhost, internal app, private apps, private endpoint
       href: how-to-test-local-applications.md
     - name: Configure visual comparisons