Run Playwright Tests at Scale on Azure

Runs Playwright tests at scale using Azure Playwright Workspaces' cloud-hosted browsers with integrated Azure portal reporting, via the @azure/playwright TypeScript SDK - the successor to the now-retired @azure/microsoft-playwright-testing, which retires March 8, 2026. Installation is via npm init @azure/playwright@latest (auto-generates config) or manually installing @azure/playwright, @playwright/test@^1.47, and @azure/identity, requiring Playwright 1.47+ for basic usage and 1.57+ for Azure reporter features. The service endpoint is set via PLAYWRIGHT_SERVICE_URL (a wss:// workspace URL).

# Recommended: Auto-generates config
npm init @azure/playwright@latest

# Manual installation
npm install @azure/playwright --save-dev
npm install @playwright/test@^1.47 --save-dev
npm install @azure/identity --save-dev

Authentication defaults to Microsoft Entra ID via Azure CLI login (az login) and an explicit credential (e.g. DefaultAzureCredential or ManagedIdentityCredential) passed into createAzurePlaywrightConfig; an access-token auth mode is also available via ServiceAuth.ACCESS_TOKEN. The core workflow wraps the existing Playwright config with createAzurePlaywrightConfig(config, { os, connectTimeout, exposeNetwork, credential }), runs with npx playwright test --config=playwright.service.config.ts --workers=20, and can add the Azure reporter (@azure/playwright/reporter) alongside the HTML reporter, listed first. It also supports manually connecting to a cloud browser via getConnectOptions() and browser.connect(wsEndpoint, options) for custom test flows, documents its PlaywrightServiceAdditionalOptions config type (serviceAuthType, os, runName, connectTimeout, exposeNetwork, credential), the ServiceOS (LINUX/WINDOWS) and ServiceAuth (ENTRA_ID/ACCESS_TOKEN) enums, and a migration table plus before/after code mapping the old @azure/microsoft-playwright-testing API (getServiceConfig, timeout, runId, implicit credential) to the new one (createAzurePlaywrightConfig, connectTimeout, runName, explicit credential).

CI/CD examples cover GitHub Actions (Azure login via azure/login@v2 with OIDC id-token: write permission, then running tests against PLAYWRIGHT_SERVICE_URL) and Azure Pipelines (an AzureCLI@2 task running the same test command). Stated best practices: use Entra ID auth over access tokens, always pass an explicit credential, enable artifacts (trace: "on-first-retry", video: "retain-on-failure"), scale with --workers=20 or higher, pick the region closest to test targets, and list the HTML reporter before the Azure reporter.

Use it to run Playwright test suites at scale against Azure-hosted cloud browsers with centralized portal reporting, or to migrate an existing @azure/microsoft-playwright-testing setup to @azure/playwright before the March 8, 2026 retirement. As with any skill output, verify configuration against the current environment, and stop to ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Input is an existing Playwright test suite and config, an Azure Playwright Workspace service URL, and an Azure credential. Output is a playwright.service.config.ts wiring tests to cloud-hosted browsers, test runs executed against those browsers (optionally in parallel across many workers), and results reported to the Azure portal alongside the standard HTML report.

Integrates Playwright with Azure Playwright Workspaces via @azure/playwright and @azure/identity (Entra ID / managed identity credentials), and plugs into GitHub Actions (via azure/login) and Azure Pipelines (via the AzureCLI@2 task) for CI/CD execution.

Engineering teams running Playwright end-to-end tests who want cloud-hosted, horizontally scaled browser execution with centralized Azure portal reporting instead of local or self-hosted runners.