Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into agc-pricing

Author: halkazwini

.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/concept-determine-optimal-configuration.md

@@ -122,7 +122,7 @@ Experiment with the number of parallel workers to run your tests. Measure the te
 Notice at which point the test completion time no longer reduces as you add more workers. Move to the next step to further optimize your setup.
 
 > [!NOTE]
-> While the service is in preview, the number of [parallel workers per workspace is limited](./resource-limits-quotas-capacity.md) to 50. You can [request an increase of this limit for your workspace](https://aka.ms/mpt/feedback).
+> While the service is in preview, the number of [parallel workers per workspace is limited](./resource-limits-quotas-capacity.md) to 50. You can [request an increase of this limit for your workspace](https://aka.ms/pww/feedback).
 
 ### 6. Scale the client
 

articles/app-testing/playwright-workspaces/how-to-configure-visual-comparisons.md

@@ -53,7 +53,7 @@ import { getServiceConfig, ServiceOS } from '@azure/playwright';
 import { DefaultAzureCredential } from '@azure/identity';
 import config from './playwright.config';
 
-/* Learn more about service configuration at https://aka.ms/mpt/config */
+/* Learn more about service configuration at https://aka.ms/pww/docs/config */
 export default defineConfig(
   config,
   getServiceConfig(config, {

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

@@ -9,7 +9,7 @@ author: ninallam
 ms.author: ninallam
 ms.date: 08/07/2025
 ms.custom: playwright-workspaces-preview
-zone_pivot_group_filename: playwright-workspaces/zone-pivots-groups.json
+zone_pivot_group_filename: app-testing/playwright-workspaces/zone-pivots-groups.json
 zone_pivot_groups: playwright-workspaces
 ---
 
@@ -59,9 +59,9 @@ To enable authentication using access tokens:
 
     ```typescript
     import { getServiceConfig, ServiceAuth } from '@azure/playwright';
-
-    /* Learn more about service configuration at https://aka.ms/mpt/config */
-    export default defineConfig(config, getServiceConfig( config {
+    
+    /* Learn more about service configuration at https://aka.ms/pww/docs/config */
+    export default defineConfig(config, getServiceConfig( config, {
         serviceAuthType: ServiceAuth.ACCESS_TOKEN
     }));
     ```
@@ -87,7 +87,7 @@ To enable authentication using access tokens:
             credential: new DefaultAzureCredential(),
             options: new PlaywrightServiceBrowserClientOptions()
             {
-                
+                ServiceAuth = ServiceAuthType.AccessToken
             }
         )
         {
@@ -103,47 +103,47 @@ 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.
+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.
+We recommend that you use the `dotenv` module to manage your environment. With `dotenv`, you define your environment variables in the `.env` file.
 
-    1. Add the `dotenv` module to your project:
+1. Add the `dotenv` module to your project:
 
-        ```shell
-        npm i --save-dev dotenv
-        ```
+    ```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}
-        ```
+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.
-
-    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
 
-## Run tests on the service and publish results
+## Run tests on the service
 
-Run Playwright tests against cloud-hosted browsers and publish the results to the service using the configuration you created above.
+Run Playwright tests against cloud-hosted browsers using the configuration you created above.
 
 ::: zone pivot="playwright-test-runner"
+
 ```typescript
 npx playwright test --config=playwright.service.config.ts --workers=20
 ```
 ::: zone-end
 
 ::: zone pivot="nunit-test-runner"
+
 ```bash
 dotnet test -- NUnit.NumberOfTestWorkers=20
 ```

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

@@ -9,7 +9,7 @@ ms.subservice: playwright-workspaces
 author: ninallam
 ms.author: ninallam
 ms.custom: playwright-workspaces-preview
-zone_pivot_group_filename: playwright-workspaces/zone-pivots-groups.json
+zone_pivot_group_filename: app-testing/playwright-workspaces/zone-pivots-groups.json
 zone_pivot_groups: playwright-workspaces
 ---
 

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

@@ -9,7 +9,7 @@ ms.subservice: playwright-workspaces
 author: ninallam
 ms.author: ninallam
 ms.custom: playwright-workspaces-preview
-zone_pivot_group_filename: playwright-workspaces/zone-pivots-groups.json
+zone_pivot_group_filename: app-testing/playwright-workspaces/zone-pivots-groups.json
 zone_pivot_groups: playwright-workspaces
 ---
 

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

@@ -9,7 +9,7 @@ ms.subservice: playwright-workspaces
 author: ninallam
 ms.author: ninallam
 ms.custom: playwright-workspaces-preview
-zone_pivot_group_filename: playwright-workspaces/zone-pivots-groups.json
+zone_pivot_group_filename: app-testing/playwright-workspaces/zone-pivots-groups.json
 zone_pivot_groups: playwright-workspaces
 ---
 
@@ -64,17 +64,18 @@ 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 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.
 
@@ -106,7 +107,7 @@ This command updates your project's `csproj` file by adding the service package
 
 ```xml
   <ItemGroup>
-    <PackageReference Include="Azure.Developer.Playwright.NUnit" Version="1.0.0-beta.1" />
+    <PackageReference Include="Azure.Developer.Playwright.NUnit" Version="1.0.0-beta.2" />
   </ItemGroup>
 ```
 
@@ -217,6 +218,7 @@ You can generate an access token from your Playwright workspace and use it in yo
 ## Update the workflow definition
 
 ::: zone pivot="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.

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

@@ -9,7 +9,7 @@ ms.subservice: playwright-workspaces
 author: ninallam
 ms.author: ninallam
 ms.custom: playwright-workspaces-preview
-zone_pivot_group_filename: playwright-workspaces/zone-pivots-groups.json
+zone_pivot_group_filename: app-testing/playwright-workspaces/zone-pivots-groups.json
 zone_pivot_groups: playwright-workspaces
 ---
 
@@ -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
@@ -135,7 +135,8 @@ We recommend that you use the `dotenv` module to manage your environment. With `
 ::: zone-end
 
 ::: zone pivot="nunit-test-runner"
-## Set up service configuration 
+
+## Set up service configuration
 
 Create a file `PlaywrightServiceSetup.cs` in your project with the following content. 
 
@@ -156,7 +157,7 @@ public class PlaywrightServiceNUnitSetup  : PlaywrightServiceBrowserNUnit
 ```
 
 > [!NOTE]
-> Make sure your project uses `Microsoft.Playwright.NUnit` version 1.47 or above.
+> Make sure your project uses `Microsoft.Playwright.NUnit` version 1.50 or above.
 
 ::: zone-end
 ## Set up Authentication
@@ -350,10 +351,12 @@ 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"
+
 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"
+
 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/resource-limits-quotas-capacity.md

@@ -35,7 +35,7 @@ While the service is in preview, the following limits apply on a per-subscriptio
 
 ## Test code limitations
 
-- The service supports Playwright OSS version 1.47 or higher.
+- The service supports Playwright OSS version 1.50 or higher.
 - The service supports the Playwright test runner and the NUnit test runner only.
 
 ## Supported operating systems and browsers