Provision and Manage Azure Playwright Workspaces

Azure.ResourceManager.Playwright is the .NET management-plane SDK for provisioning Microsoft Playwright Testing workspaces through Azure Resource Manager - creating, listing, updating, and deleting PlaywrightWorkspaceResource objects, checking workspace-name availability, and reading subscription- and workspace-level quotas. It is explicitly separate from Azure.Developer.MicrosoftPlaywrightTesting.NUnit, the test-execution SDK that actually runs Playwright tests at scale on cloud browsers once a workspace exists.

Use this skill when provisioning or managing the cloud infrastructure behind Microsoft Playwright Testing - creating a workspace in a given Azure region, checking a proposed name is available before creating it, monitoring quota usage, or tagging and updating workspace metadata. It is not for writing or running Playwright tests themselves; once a workspace is created, its DataplaneUri is handed off to the separate test-execution SDK, which is where actual browser test runs happen.

Workspace creation takes a PlaywrightWorkspaceData with a location, optional RegionalAffinity and LocalAuth settings, and tags, submitted via workspaceCollection.CreateOrUpdateAsync(WaitUntil.Completed, name, data) as a long-running operation; the returned PlaywrightWorkspaceResource exposes DataplaneUri (the URL test execution connects to) and a WorkspaceId GUID. Updates go through PlaywrightWorkspacePatch (typically just tags). Name checks use PlaywrightCheckNameAvailabilityContent against subscription.CheckPlaywrightNameAvailabilityAsync, returning IsNameAvailable plus a reason if not. Quota reads (subscription.GetPlaywrightQuotasAsync(location) at the subscription level, workspace.GetAllPlaywrightWorkspaceQuota() per workspace) return Limit/Used pairs.

var workspaceData = new PlaywrightWorkspaceData(AzureLocation.WestUS3)
{
    RegionalAffinity = PlaywrightRegionalAffinity.Enabled,
    LocalAuth = PlaywrightLocalAuth.Enabled
};
var operation = await workspaceCollection.CreateOrUpdateAsync(
    WaitUntil.Completed, "my-playwright-workspace", workspaceData);

Authenticates via DefaultAzureCredential; the resource sits under the Microsoft.LoadTestService resource provider (Microsoft.LoadTestService/playwrightWorkspaces, API version 2025-09-01). After creating a workspace, its DataplaneUri is typically set as the PLAYWRIGHT_SERVICE_URL environment variable consumed by Azure.Developer.MicrosoftPlaywrightTesting.NUnit (test execution at scale) or Azure.Developer.Playwright (the Playwright client library) - this SDK only sets up the infrastructure those packages then run against.

.NET platform teams and developers automating Microsoft Playwright Testing infrastructure - creating workspaces per team or environment, tracking regional quota usage, and wiring a newly-created workspace's DataplaneUri into CI pipelines that run the actual test suites via the separate execution SDKs. The skill's own best practices call out storing DataplaneUri immediately after creation, using CreateOrUpdateAsync for idempotent provisioning, always authenticating with DefaultAzureCredential, and handling RequestFailedException explicitly for 409 (workspace already exists) and 400 (bad request) cases. WaitUntil.Completed is recommended for provisioning steps that must finish before the pipeline continues, while WaitUntil.Started suits cases where the caller wants to poll status manually or kick off several long-running operations in parallel.