Provision and Manage Azure Playwright Workspaces

This .NET reference covers the Azure Resource Manager management plane for Microsoft Playwright Testing workspaces. It describes creating, retrieving, listing, updating, and deleting workspaces, checking name availability, and reading subscription or workspace quotas. It also explains workspace properties used to configure test execution. This package manages workspaces; a separate test-execution package runs Playwright tests at scale on cloud browsers.

Use this material when provisioning or administering Playwright Testing workspaces from a .NET application. Use the separate test-execution library when the task is to run the browser tests themselves. The management package provisions and administers workspaces; test execution itself belongs to the separate runner package. Its API and version notes are time-sensitive and should be compared with the linked official documentation before use.

Inputs include a subscription identifier, Azure credentials, resource group, region, workspace name, tags, regional-affinity setting, local-auth setting, and quota query region. The client hierarchy begins with ArmClient, then subscription and resource group resources, workspace collections, and workspace resources. Creation uses an asynchronous long-running operation; callers can wait for completion or request that it start and poll separately. Results include the workspace identifier, provisioning state, and data-plane URI for configuring test execution. Other operations return existence, name-availability, update, and quota information.

A namespace import used by the examples is:

using Azure.Identity;

DefaultAzureCredential can authenticate an ArmClient used to retrieve a subscription. A workspace can be created or updated with regional affinity, local authentication, and tags. Existing workspaces can be fetched by name or checked before retrieval, and collections can be enumerated at the resource-group or subscription level. A patch updates tags, while a name-availability request returns a boolean and explanatory reason when unavailable.

The guide covers Azure Resource Manager, Azure Identity, the Azure Resource Manager Playwright library, and separate Microsoft Playwright Testing NUnit and client libraries. After workspace creation, the data-plane URI can be saved as a test-execution service URL for the separate test runner. Quota examples query both subscription-level limits for a region and workspace-level quota resources.

Operational recommendations include using WaitUntil.Completed when later steps depend on successful completion, using WaitUntil.Started when polling manually, avoiding hard-coded credentials, handling RequestFailedException, using create-or-update operations for idempotency, navigating resources through their Get* methods, and storing the data-plane URI. Error examples distinguish conflict and bad-request responses from other Resource Manager errors.

.NET platform engineers and test infrastructure maintainers can use this reference to manage cloud browser testing workspaces and connect their metadata to a separate test execution workflow.