Merge pull request #303986 from MicrosoftDocs/main

Auto Publish – main to live - 2025-08-07 17:00 UTC

Author: learn-build-service-prod[bot]

.openpublishing.publish.config.json

@@ -638,6 +638,12 @@
             "branch": "main",
             "branch_mapping": {}
         },
+        {
+            "path_to_root": "playwright-workspaces",
+            "url": "https://github.com/Azure/playwright-workspaces",
+            "branch": "main",
+            "branch_mapping": {}
+        },
         {
             "path_to_root": "playwright-testing-service",
             "url": "https://github.com/microsoft/playwright-testing-service",

articles/app-service/overview-inbound-outbound-ips.md

@@ -4,7 +4,7 @@ description: Learn how inbound and outbound IP addresses are used in Azure App S
 author: msangapu-msft
 ms.author: msangapu
 ms.topic: article
-ms.date: 08/05/2025
+ms.date: 08/07/2025
 ms.update-cycle: 1095-days
 ms.custom:
   - UpdateFrequency3
@@ -139,6 +139,8 @@ You can configure the IP mode behavior using the `IPMode` property:
 - **IPv6**: DNS returns IPv6 address only
 - **IPv4AndIPv6**: DNS returns both IPv4 and IPv6 addresses
 
+IPMode is a DNS-only feature. Every App Service site can receive requests via both IPv4 and IPv6 endpoints—regardless of the configured IpMode. IpMode only influences how DNS resolves the endpoint, so it affects clients that rely on DNS resolution (which should be most clients), but it doesn't restrict which protocol endpoints can be reached.
+
 ### Configure IPv6 support
 
 # [Azure portal](#tab/azure-portal)

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

@@ -55,20 +55,24 @@ To enable authentication using access tokens:
 
 ::: zone pivot="playwright-test-runner"
 
-1. While running the tests, enable access token auth in the `playwright.service.config.ts` file in your setup. 
+### If you're using the **Playwright Test Runner**
 
-    ```typescript
-    import { getServiceConfig, ServiceAuth } from '@azure/playwright';
+While running the tests, enable access token auth in the `playwright.service.config.ts` file in your setup. 
 
+```typescript
+    import { getServiceConfig, ServiceAuth } from '@azure/playwright';
+    
     /* Learn more about service configuration at https://aka.ms/mpt/config */
     export default defineConfig(config, getServiceConfig( config {
         serviceAuthType: ServiceAuth.ACCESS_TOKEN
     }));
-    ```
+```
 ::: zone-end
 
 ::: zone pivot="nunit-test-runner"
 
+### If you're using the **NUnit Test Runner**
+
 1. While running the tests, enable access token auth in the setup file. 
 
     ```c#
@@ -103,33 +107,35 @@ To enable authentication using access tokens:
 
 ::: zone pivot="playwright-test-runner"
 
-3. Set up your environment.
+## Set up your environment.
 
-    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.
+### If you're using the **Playwright Test Runner**
 
-    We recommend that you use the `dotenv` module to manage your environment. With `dotenv`, you define your environment variables in the `.env` file.
+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.
 
-    1. Add the `dotenv` module to your project:
+We recommend that you use the `dotenv` module to manage your environment. With `dotenv`, you define your environment variables in the `.env` file.
 
-        ```shell
-        npm i --save-dev dotenv
-        ```
+1. Add the `dotenv` module to your project:
 
-    2. Create a `.env` file alongside the `playwright.config.ts` file in your Playwright project:
-        
-        ```
-        PLAYWRIGHT_SERVICE_ACCESS_TOKEN={MY-ACCESS-TOKEN}
-        ```
+    ```shell
+    npm i --save-dev dotenv
+    ```
+
+2. Create a `.env` file alongside the `playwright.config.ts` file in your Playwright project:
+    
+    ```
+    PLAYWRIGHT_SERVICE_ACCESS_TOKEN={MY-ACCESS-TOKEN}
+    ```
 
-        Make sure to replace the `{MY-ACCESS-TOKEN}` text placeholder with the value you copied earlier.
+    Make sure to replace the `{MY-ACCESS-TOKEN}` text placeholder with the value you copied earlier.
 
 ::: zone-end
 
 ::: zone pivot="nunit-test-runner"
 
-3. Set up your environment.
+### If you're using the **NUnit Test Runner**
 
-    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.
+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
 
@@ -138,12 +144,16 @@ To enable authentication using access tokens:
 Run Playwright tests against cloud-hosted browsers and publish the results to the service using the configuration you created above.
 
 ::: zone pivot="playwright-test-runner"
+
+### If you're using the **Playwright Test Runner**
 ```typescript
 npx playwright test --config=playwright.service.config.ts --workers=20
 ```
 ::: zone-end
 
 ::: zone pivot="nunit-test-runner"
+
+### If you're using the **NUnit Test Runner**
 ```bash
 dotnet test -- NUnit.NumberOfTestWorkers=20
 ```

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

@@ -30,6 +30,8 @@ You can specify one or multiple networks by using a list of rules. For example,
 
 ::: zone pivot="playwright-test-runner"
 
+### If you're using the **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
@@ -58,6 +60,8 @@ npx playwright test --config=playwright.service.config.ts --workers=20
 
 ::: zone pivot="nunit-test-runner"
 
+### If you're using the **NUnit Test Runner**
+
 You can configure the `ExposeNetwork` option in the setup file. 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. 
 
 ```c#

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

@@ -17,13 +17,17 @@ zone_pivot_groups: playwright-workspaces
 
 ::: zone pivot="playwright-test-runner"
 
+### If you're using the **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 [Quickstart: Run end-to-end tests at scale with Playwright Workspaces](./quickstart-run-end-to-end-tests.md) 
 
 ::: zone-end
 
 ::: zone pivot="nunit-test-runner"
 
+### If you're using the **NUnit Test Runner**
+
 This article shows you how to use the options available in the `PlaywrightServiceSetup.cs` file. 
 If you don't have this file in your code, follow [Quickstart: Run end-to-end tests at scale with Playwright Workspaces](./quickstart-run-end-to-end-tests.md) 
 
@@ -38,6 +42,8 @@ If you don't have this file in your code, follow [Quickstart: Run end-to-end tes
 
 ::: zone pivot="playwright-test-runner"
 
+### If you're using the **Playwright Test Runner**
+
 Below is a complete example of a `playwright.service.config.ts` file showing all supported configuration options:
 
 ```typescript
@@ -125,6 +131,8 @@ export default defineConfig(
 
 ::: zone pivot="nunit-test-runner"
 
+### If you're using the **NUnit Test Runner**
+
 
 Here's version of the setup file with all the available options:
 

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

@@ -64,17 +64,20 @@ To get the service endpoint URL and store it as a CI workflow secret, perform th
     | *PLAYWRIGHT_SERVICE_URL* | Paste the endpoint URL you copied previously. |
 
 ::: zone pivot="playwright-test-runner"
+
 ## Add service configuration file
 
+### If you're using the **Playwright Test Runner**
+
 If you don't have Playwright tests configured to run with the service, add a service configuration file to your repository. In the next step, you then specify this service configuration file on the Playwright CLI.
 
 1. Create a new file `playwright.service.config.ts` alongside the `playwright.config.ts` file.
 
-    Optionally, use the `playwright.service.config.ts` file in the [sample repository](https://github.com/microsoft/playwright-testing-service/blob/main/samples/get-started/playwright.service.config.ts).
+    Optionally, use the `playwright.service.config.ts` file in the [sample repository](https://github.com/Azure/playwright-workspaces/blob/main/samples/playwright-tests/playwright.service.config.ts).
 
 2. Add the following content to it:
 
-    :::code language="typescript" source="~/playwright-testing-service/samples/get-started/playwright.service.config.ts":::
+    :::code language="typescript" source="~/playwright-workspaces/samples/playwright-tests/playwright.service.config.ts":::
 
    By default, the service configuration enables you to accelerate build pipelines by running tests in parallel using cloud-hosted browsers.
 
@@ -96,6 +99,8 @@ Update the `package.json` file in your repository to add details about Playwrigh
 
 ## Install service package
 
+### If you're using the **NUnit Test Runner**
+
 In your project, install Playwright Workspaces package. 
 
 ```PowerShell
@@ -217,6 +222,8 @@ You can generate an access token from your Playwright workspace and use it in yo
 ## Update the workflow definition
 
 ::: zone pivot="playwright-test-runner"
+
+### If you're using the **Playwright Test Runner**
 Update the CI workflow definition to run your Playwright tests with the Playwright CLI. Pass the [service configuration file](#add-service-configuration-file) as an input parameter for the Playwright CLI. You configure your environment by specifying environment variables.
 
 1. Open the CI workflow definition.
@@ -317,6 +324,8 @@ Update the CI workflow definition to run your Playwright tests with the Playwrig
 
 ::: zone pivot="nunit-test-runner"
 
+### If you're using the **NUnit Test Runner**
+
 Update the CI workflow definition to run your Playwright tests with the Playwright NUnit CLI. You configure your environment by specifying environment variables.
 
 1. Open the CI workflow definition.

articles/app-testing/playwright-workspaces/quickstart-run-end-to-end-tests.md

@@ -26,7 +26,7 @@ After you complete this quickstart, you have a Playwright workspace to run your
 
 * An Azure account with an active subscription. If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
 * Your Azure account needs the [Owner](/azure/role-based-access-control/built-in-roles#owner), [Contributor](/azure/role-based-access-control/built-in-roles#contributor), or one of the [classic administrator roles](/azure/role-based-access-control/rbac-and-directory-admin-roles#classic-subscription-administrator-roles).
-* A Playwright project. If you don't have project, create one by using the [Playwright getting started documentation](https://playwright.dev/docs/intro) or use our [Playwright Workspaces sample project](https://github.com/microsoft/playwright-testing-service/tree/main/samples/get-started).
+* A Playwright project. If you don't have project, create one by using the [Playwright getting started documentation](https://playwright.dev/docs/intro) or use our [Playwright Workspaces sample project](https://github.com/Azure/playwright-workspaces/blob/main/samples/playwright-tests).
 * Azure CLI. If you don't have Azure CLI, see [Install Azure CLI](/cli/azure/install-azure-cli).
 
 ## Create a workspace
@@ -70,6 +70,8 @@ To get started with running your Playwright tests on cloud browsers, you first n
 
 ::: zone pivot="playwright-test-runner"
 
+### If you're using the **Playwright Test Runner**
+
 To use the service, install the Playwright Workspaces package. 
 
 ```npm
@@ -84,6 +86,8 @@ If you already have this file, the package asks you to overwrite it.
 
 ::: zone pivot="nunit-test-runner"
 
+### If you're using the **NUnit Test Runner**
+
 To use the service, install the Playwright Workspaces package. 
 
 ```PowerShell
@@ -114,6 +118,8 @@ To get the service endpoint URL, perform the following steps:
 
 ## Set up your environment
 
+### If you're using the **Playwright Test Runner**
+
 To set up your environment, you have to configure the `PLAYWRIGHT_SERVICE_URL` environment variable with the value you obtained in the previous steps.
 
 We recommend that you use the `dotenv` module to manage your environment. With `dotenv`, you define your environment variables in the `.env` file.
@@ -135,8 +141,11 @@ We recommend that you use the `dotenv` module to manage your environment. With `
 ::: zone-end
 
 ::: zone pivot="nunit-test-runner"
+
 ## Set up service configuration 
 
+### If you're using the **NUnit Test Runner**
+
 Create a file `PlaywrightServiceSetup.cs` in your project with the following content. 
 
 ```csharp
@@ -193,6 +202,8 @@ You can generate an access token from your Playwright workspace and use it in yo
 
 ::: zone pivot="playwright-test-runner"
 
+### If you're using the **Playwright Test Runner**
+
 You've now prepared the configuration for running your Playwright tests in the cloud with Playwright Workspaces. You can either use the Playwright CLI to run your tests, or use the [Playwright Test Visual Studio Code extension](https://marketplace.visualstudio.com/items?itemName=ms-playwright.playwright).
 
 ### Run a single test with the service
@@ -323,6 +334,8 @@ To run your Playwright test suite in Visual Studio Code with Playwright Workspac
 
 ::: zone pivot="nunit-test-runner"
 
+### If you're using the **NUnit Test Runner**
+
 Run Playwright tests against browsers managed by the service using the configuration you created above. 
 
 ```bash
@@ -350,10 +363,14 @@ Once your tests are running smoothly with the service, experiment with varying t
 With Playwright Workspaces, you can run with up to 50 parallel workers. Several factors influence the best configuration for your project, such as the CPU, memory, and network resources of your client machine, the target application's load-handling capacity, and the type of actions carried out in your tests.
 
 ::: zone pivot="playwright-test-runner"
+
+### If you're using the **Playwright Test Runner**
 You can specify the number of parallel workers on the Playwright CLI command-line, or configure the `workers` property in the Playwright service configuration file.
 ::: zone-end
 
 ::: zone pivot="nunit-test-runner"
+
+### If you're using the **NUnit Test Runner**
 You can specify the number of parallel workers on the Playwright CLI command-line, or configure the `NumberOfTestWorkers` property in the `.runsettings` file.
 ::: zone-end
 

articles/app-testing/playwright-workspaces/tutorial-run-end-to-end-tests.md

@@ -50,8 +50,8 @@ In this step, you are creating a Playwright test suite which is integrated with
 1. Clone the sample repository and navigate to test folder. 
 
 ```powershell
-git clone https://github.com/microsoft/playwright-testing-service
-cd playwright-testing-service/samples/get-started
+git clone https://github.com/Azure/playwright-workspaces
+cd playwright-workspaces/samples/playwright-tests
 ```
 
 2. Install dependencies.

articles/app-testing/toc.yml

@@ -237,7 +237,7 @@ items:
         - name: Contoso Traders cloud testing demo
           href: https://github.com/microsoft/contosotraders-cloudtesting/
         - name: Examples repository
-          href: https://github.com/microsoft/playwright-testing-service/
+          href: https://github.com/Azure/playwright-workspaces/
     - name: Troubleshoot & debug
       items:
         - name: Troubleshoot test run failures

articles/application-gateway/for-containers/how-to-end-to-end-tls-ingress-api.md

@@ -54,6 +54,7 @@ metadata:
   annotations:
     alb.networking.azure.io/alb-name: alb-test
     alb.networking.azure.io/alb-namespace: alb-test-infra
+    alb.networking.azure.io/alb-ingress-extension: https-ingress
 spec:
   ingressClassName: azure-alb-external
   tls:
@@ -100,6 +101,7 @@ metadata:
   annotations:
     alb.networking.azure.io/alb-id: $RESOURCE_ID
     alb.networking.azure.io/alb-frontend: $FRONTEND_NAME
+    alb.networking.azure.io/alb-ingress-extension: https-ingress
 spec:
   ingressClassName: azure-alb-external
   tls:
@@ -137,6 +139,7 @@ metadata:
   annotations:
     alb.networking.azure.io/alb-frontend: FRONTEND_NAME
     alb.networking.azure.io/alb-id: /subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourcegroups/yyyyyyyy/providers/Microsoft.ServiceNetworking/trafficControllers/zzzzzz
+    alb.networking.azure.io/alb-ingress-extension: https-ingress
     kubectl.kubernetes.io/last-applied-configuration: |
       {"apiVersion":"networking.k8s.io/v1","kind":"Ingress","metadata":{"annotations":{"alb.networking.azure.io/alb-frontend":"FRONTEND_NAME","alb.networking.azure.io/alb-id":"/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourcegroups/yyyyyyyy/providers/Microsoft.ServiceNetworking/trafficControllers/zzzzzz"},"name"
 :"ingress-01","namespace":"test-infra"},"spec":{"ingressClassName":"azure-alb-external","rules":[{"host":"contoso.com","http":{"paths":[{"backend":{"service":{"name":"https-app","port":{"number":443}}},"path":"/","pathType":"Prefix"}]}}],"tls":[{"hosts":["contoso.com"],"secretName":"contoso.com"}]}}