Playwright Workspaces & Azure App Testing: What Changed (2026)

Playwright has become the dominant end-to-end testing framework, with 52M+ weekly npm downloads, 96.1K GitHub stars, and a 45.1% adoption rate among frontend teams. Over 12,000 companies use it in production. As adoption scaled, so did the demand for cloud-hosted test infrastructure — and Microsoft responded by evolving its cloud offering.

In 2026, what was previously called Playwright Testing became Playwright Workspaces — a rebranded, enhanced service now grouped under Azure App Testing alongside Azure Load Testing. This guide covers everything you need to know about the transition.

What Are Playwright Workspaces?

Playwright Workspaces is Microsoft's managed cloud service for running Playwright tests at scale. It provides cloud-hosted browser grids — Chromium, Firefox, and WebKit — so teams can execute hundreds or thousands of parallel tests without provisioning their own infrastructure.

The rebrand from "Playwright Testing" to "Playwright Workspaces" reflects two strategic moves by Microsoft:

• Consolidation under Azure App Testing — Microsoft grouped its quality-focused services (Playwright Workspaces + Azure Load Testing) under a single umbrella, making it easier for teams to manage functional and performance testing from one place
• Workspace-centric architecture — the new name reflects the shift toward isolated, configurable workspaces where teams can manage browser grids, trace storage, and test configurations independently across projects

The core value proposition remains the same: run your existing Playwright tests in the cloud with minimal config changes. You write tests locally, point your playwright.config.ts at the cloud endpoint, and the service handles browser provisioning, parallel execution, and result collection.

What Changed: Old vs New

Here's a side-by-side comparison of the old Playwright Testing service and the new Playwright Workspaces:

The most significant technical improvements are the enhanced auto-scaling (the service now spins up browser instances faster and scales down more aggressively to reduce costs), 90-day trace storage (critical for debugging flaky tests that appear intermittently), and MCP Server compatibility (enabling AI-driven test generation against cloud-hosted browsers).

Key Features of Playwright Workspaces

Playwright Workspaces delivers the cloud infrastructure that teams need for production-scale test execution. Here are the features that matter most:

Parallel execution at scale

Run hundreds of tests simultaneously across cloud-hosted browser instances. The service auto-provisions workers based on your test suite size and tears them down when finished. No idle infrastructure costs.

Built-in trace viewer

Every test run captures a full Playwright trace — screenshots, DOM snapshots, network requests, and console logs. Traces are stored for 90 days and accessible directly from the Azure portal or via API.

Cross-browser cloud grids

Execute tests across Chromium, Firefox, and WebKit without installing browsers locally. The cloud grids always run the latest stable browser versions, eliminating version-mismatch issues.

CI/CD integration

First-class integration with GitHub Actions and Azure DevOps. Pre-built pipeline templates let you add cloud execution to your CI in minutes. Also works with Jenkins, GitLab CI, and any system that can run npx playwright test.

Reporting dashboard

A centralized dashboard shows test results, pass/fail trends, execution times, and flakiness scores. Filter by browser, project, or time range to identify problematic tests quickly.

Geo-distributed testing

Run tests from multiple Azure regions to validate performance and behavior across geographies. Particularly valuable for teams building globally distributed applications where latency affects user experience.

How to Set Up Playwright Workspaces

Getting started with Playwright Workspaces takes about 15 minutes. Here's the step-by-step process:

Step 1: Create an Azure account

If you don't have one, create an Azure account at azure.microsoft.com. The free tier includes 100 browser minutes per month — enough to evaluate the service with a real test suite.

Step 2: Provision a workspace

In the Azure portal, navigate to Azure App Testing → Playwright Workspaces → Create. Choose your subscription, resource group, region, and workspace name.

Step 3: Install the service package

npm install --save-dev @azure/playwright-workspaces

Step 4: Configure playwright.config.ts

import { defineConfig } from '@playwright/test';
import { getConnectOptions } from '@azure/playwright-workspaces';

export default defineConfig({
  use: {
    connectOptions: getConnectOptions(),
  },
  workers: 20, // Scale up — cloud handles parallel execution
  projects: [
    { name: 'chromium', use: { browserName: 'chromium' } },
    { name: 'firefox', use: { browserName: 'firefox' } },
    { name: 'webkit', use: { browserName: 'webkit' } },
  ],
});

Step 5: Set your access token

export PLAYWRIGHT_SERVICE_ACCESS_TOKEN="your-token-from-azure-portal"
export PLAYWRIGHT_SERVICE_URL="wss://your-workspace.api.playwright.microsoft.com"

Step 6: Run tests in the cloud

npx playwright test

That's it. Your tests now execute on cloud-hosted browsers. Locally, Playwright connects to the remote browser grids via WebSocket — your test code doesn't change at all.

Playwright Workspaces vs Self-Hosted CI

Not every team needs cloud browser grids. Here's how to decide between Playwright Workspaces and running tests on your own CI infrastructure:

The sweet spot: Teams with 50–500 tests that need cross-browser coverage and fast feedback loops benefit most from Playwright Workspaces. Smaller teams with Chromium-only testing can often run everything on GitHub Actions or a single CI runner at lower cost.

Pricing: What You'll Pay in 2026

Playwright Workspaces uses a per-minute billing model based on browser execution time, with tiered pricing depending on your plan:

Ballpark monthly costs

• Small team (50 tests, 2 browsers, daily) — ~300 browser min/month → ~$15/month
• Mid team (200 tests, 3 browsers, daily) — ~1,800 browser min/month → ~$90/month
• Large team (500 tests, 3 browsers, 3x/day) — ~13,500 browser min/month → ~$675/month

Compare this to maintaining your own Docker-based Playwright grid: the infrastructure cost might be lower at high volume, but the engineering time to maintain it often exceeds the Workspaces bill. For most teams, the managed service wins on total cost of ownership.

Integrating with Claude AI & MCP Server

One of the most powerful patterns in 2026 is combining local AI test generation with cloud-scale execution. Here's how Playwright Workspaces fits into an AI-powered testing workflow:

The hybrid pattern: local AI + cloud execution

1. Generate tests locally — use Claude AI with the Playwright MCP Server to generate tests against your running application. Claude sees the live DOM, suggests locators, and writes complete test files.
2. Validate locally — run the generated tests on your machine to confirm they pass. Fix any issues with Claude's help.
3. Execute at scale in Workspaces — push the tests to CI, where they run across Chromium, Firefox, and WebKit in Playwright Workspaces with 20+ parallel workers.
4. Debug failures with traces — when a test fails in the cloud, pull the trace from Workspaces and use Claude to analyze the failure and suggest fixes.

import { defineConfig } from '@playwright/test';

const isCloud = !!process.env.PLAYWRIGHT_SERVICE_URL;

export default defineConfig({
  workers: isCloud ? 20 : 4,
  use: {
    connectOptions: isCloud
      ? getConnectOptions()
      : undefined,
  },
});

This pattern gives you the best of both worlds: Claude's intelligence for test authoring and Playwright Workspaces' infrastructure for execution. Teams using this hybrid approach report 3–5x faster test creation and near-instant feedback on cross-browser compatibility.

Migration Guide: From Playwright Testing to Workspaces

If you were already using the old Playwright Testing service, the migration is straightforward. Here's what changes:

1. Update the npm package

# Remove the old package
npm uninstall @azure/playwright-testing

# Install the new package
npm install --save-dev @azure/playwright-workspaces

2. Update imports in playwright.config.ts

import { getConnectOptions } from '@azure/playwright-testing';

import { getConnectOptions } from '@azure/playwright-workspaces';

3. Update Azure portal resources

In the Azure portal, your existing Playwright Testing resources will appear under the new Azure App Testing section. No action is required — Microsoft migrates existing resources automatically. Your access tokens and WebSocket endpoints remain the same.

4. Update environment variable names (optional)

The old PLAYWRIGHT_SERVICE_ACCESS_TOKEN and PLAYWRIGHT_SERVICE_URL environment variables still work. Microsoft introduced new aliases (AZURE_PLAYWRIGHT_TOKEN and AZURE_PLAYWRIGHT_URL) but the legacy names are supported indefinitely.

5. Verify CI pipelines

Update any CI pipeline files that reference the old package name. If you use GitHub Actions, update the package install step in your workflow YAML:

- name: Install dependencies
  run: |
    npm ci
    npx playwright install --with-deps

The npm ci command will pull the new @azure/playwright-workspaces package from your updated package.json. No other pipeline changes are needed.

Frequently Asked Questions

Asim Noaman

Senior QA Automation Engineer & AI Testing Specialist