Merge pull request #311615 from MicrosoftDocs/main

Auto Publish – main to live - 2026-02-10 12:00 UTC

Author: learn-build-service-prod[bot]

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

@@ -24,15 +24,15 @@ In this article, you learn how to manage access to a workspace in Playwright Wor
     1. In the [Azure portal](https://portal.azure.com), go to your Playwright workspace.
     1. On the left pane, select **Access Control (IAM)**, and then select **View my access**.
 
-## Default roles
+## Playwright Workspaces roles
 
-Playwright workspaces uses three Azure built-in roles. To grant users access to a workspace, you assign them one of the following Azure built-in roles:
+Playwright workspaces uses three types of roles. To grant users access to a workspace, you assign them one of the following roles:
 
 | Role | Access level |
 | --- | --- |
-| **Reader** | - Read-only access to the workspace in the Azure portal.<br/>- View test results for the workspace.<br/>- Can't [create or delete workspace access tokens](./how-to-manage-access-tokens.md).<br/>- Can't run Playwright tests on the service. |
-| **Contributor** | - Full access to manage the workspace in the Azure portal but can't assign roles in Azure RBAC.<br/>- Full access to the workspace in the Azure portal.<br/>- [Create and delete their access tokens](./how-to-manage-access-tokens.md).<br/>- Run Playwright tests on the service. |
-| **Owner** | - Full access to manage the workspace in the Azure portal, including assigning roles in Azure RBAC.<br/>- Full access to the workspace in the Azure portal.<br/>- [Create and delete their access tokens](./how-to-manage-access-tokens.md).<br/>- Run Playwright tests on the service. |
+| **Playwright Workspace Reader** | - Read-only access to the workspace in the Azure portal.<br/>- View test results for the workspace.<br/>- Can't [create or delete workspace access tokens](./how-to-manage-access-tokens.md).<br/>- Can't run Playwright tests on the service. |
+| **Playwright Workspace Contributor** | - Full access to manage the workspace in the Azure portal but can't assign roles in Azure RBAC.<br/>- Full access to the workspace in the Azure portal.<br/>- [Create and delete their access tokens](./how-to-manage-access-tokens.md).<br/>- Run Playwright tests on the service. |
+| **Playwright Workspace Owner** | - Full access to manage the workspace in the Azure portal, including assigning roles in Azure RBAC.<br/>- Full access to the workspace in the Azure portal.<br/>- [Create and delete their access tokens](./how-to-manage-access-tokens.md).<br/>- Run Playwright tests on the service. |
 
 > [!IMPORTANT]
 > Before you assign an Azure RBAC role, determine the scope of access that is needed. Best practices dictate that it's always best to grant only the narrowest possible scope. Azure RBAC roles defined at a broader scope are inherited by the resources beneath them. For more information about scope for Azure RBAC role assignments, see [Understand scope for Azure RBAC](/azure/role-based-access-control/scope-overview).
@@ -51,9 +51,9 @@ You can grant a user access to a Playwright workspace by using the Azure portal:
 
     :::image type="content" source="./media/how-to-manage-workspace-access/add-role-assignment.png" alt-text="Screenshot that shows how to add a role assignment to your workspace in the Azure portal." lightbox="./media/how-to-manage-workspace-access/add-role-assignment.png":::
 
-1. On the **Role** tab, select **Privileged administrator** roles.
+1. On the **Job function roles** tab, enter **Playwright**.
 
-1. Select one of the Playwright Workspaces [default roles](#default-roles), and then select **Next**.
+1. Select one of the Playwright Workspaces roles, and then select **Next**.
 
     :::image type="content" source="./media/how-to-manage-workspace-access/add-role-assignment-select-role.png" alt-text="Screenshot that shows the list of roles when adding a role assignment in the Azure portal." lightbox="./media/how-to-manage-workspace-access/add-role-assignment-select-role.png":::
 

articles/app-testing/playwright-workspaces/media/how-to-manage-workspace-access/add-role-assignment-select-role.png

@@ -105,6 +105,106 @@ builder.AddAzureAppConfiguration(o =>
     });
 ```
 
+### [JavaScript](#tab/javascript)
+
+The Audience for the target cloud must be configured for the following packages.
+
+- Azure SDK for JavaScript: @azure/app-configuration >= 1.9.0
+- JavaScript configuration provider: @azure/app-configuration-provider >= 1.0.0
+
+In the **Azure SDK for JavaScript**, audience is configured by passing the `audience` option to the `AppConfigurationClient` constructor.
+
+The following code snippet demonstrates how to instantiate a configuration client with a cloud-specific audience.
+
+```javascript
+const client = new AppConfigurationClient(myStoreEndpoint, new DefaultAzureCredential(), {
+    audience: "{Cloud specific audience here}",
+});
+```
+
+In the **JavaScript configuration provider**, audience is configured by passing the `clientOptions` with the `audience` property to the `load` function.
+
+The following code snippet demonstrates how to load Azure App Configuration in a JavaScript application with a cloud-specific audience.
+
+```javascript
+const appConfig = await load(myStoreEndpoint, credential, {
+    clientOptions: {
+        audience: "{Cloud specific audience here}"
+    }
+});
+```
+
+### [Go](#tab/go)
+
+The Audience for the target cloud must be configured for the following packages.
+
+- Azure SDK for Go: azappconfig >= 2.1.0
+- Go configuration provider: azureappconfiguration >= 1.0.0
+
+You need to import the following packages:
+
+```golang
+import (
+    "github.com/Azure/azure-sdk-for-go/sdk/azcore/cloud"
+    "github.com/Azure/azure-sdk-for-go/sdk/azcore/policy"
+)
+```
+
+In the **Azure SDK for Go**, audience is configured by utilizing the cloud configuration.
+
+The following code snippet demonstrates how to instantiate a configuration client with a cloud-specific audience.
+
+```golang
+credential, _:= azidentity.NewDefaultAzureCredential(nil)
+
+cloudConfig := cloud.Configuration{
+    Services: map[cloud.ServiceName]cloud.ServiceConfiguration{
+        azappconfig.ServiceName: {
+            Audience: "{Cloud specific audience here}",
+        },
+    },
+}
+
+clientOptions := &azappconfig.ClientOptions{
+    ClientOptions: policy.ClientOptions{
+        Cloud: cloudConfig,
+    },
+}
+
+client, _ := azappconfig.NewClient(myStoreEndpoint, credential, clientOptions)
+```
+
+In the **Go configuration provider**, audience is configured by passing the `ClientOptions` with the cloud configuration to the `Load` function.
+
+The following code snippet demonstrates how to load Azure App Configuration in a Go application with a cloud-specific audience.
+
+```golang
+credential, _:= azidentity.NewDefaultAzureCredential(nil)
+
+authOptions := azureappconfiguration.AuthenticationOptions{
+    Endpoint: myStoreEndpoint,
+    Credential: credential,
+}
+
+cloudConfig := cloud.Configuration{
+    Services: map[cloud.ServiceName]cloud.ServiceConfiguration{
+        azappconfig.ServiceName: {
+            Audience: "{Cloud specific audience here}",
+        },
+    },
+}
+
+options := &azureappconfiguration.Options{
+    ClientOptions: &azappconfig.ClientOptions{
+        ClientOptions: policy.ClientOptions{
+            Cloud: cloudConfig,
+        },
+    },
+}
+
+appConfig, _ := azureappconfiguration.Load(context.Background(), authOptions, options)
+```
+
 ---
 
 ### Audience

articles/azure-app-configuration/concept-enable-rbac.md

@@ -6,7 +6,7 @@ author: b-ahibbard
 ms.service: azure-netapp-files
 ms.custom: references_regions
 ms.topic: concept-article
-ms.date: 11/11/2025
+ms.date: 02/10/2026
 ms.author: anfdocs
 # Customer intent: As a storage administrator, I want to review the requirements and limitations of large volumes in Azure NetApp Files, so that I can effectively plan the deployment and management of storage solutions to meet my organization's data capacity and performance needs.
 ---
@@ -127,6 +127,7 @@ Support for Azure NetApp Files large volumes is available in the following regio
 * South Africa North 
 * South Central US
 * Southeast Asia
+* Spain Central
 * Sweden Central
 * Switzerland North
 * Switzerland West

articles/azure-netapp-files/large-volumes-requirements-considerations.md

@@ -3,7 +3,7 @@ title: Restore Azure VMs using REST API
 description: In this article, learn how to manage to restore operations of Azure Virtual Machine Backup using REST API.
 ms.topic: how-to
 ms.service: azure-backup
-ms.date: 02/09/2025
+ms.date: 02/10/2026
 ms.assetid: b8487516-7ac5-4435-9680-674d9ecf5642
 author: AbhishekMallick-MS
 ms.author: v-mallicka
@@ -12,13 +12,13 @@ ms.author: v-mallicka
 
 # Restore Azure Virtual machines using REST API
 
-This article describes how to restore an Azure VM or disks using the REST API.
+This article describes how to restore Azure Virtual Machines or individual disks from a recovery point by using REST API. It covers selecting recovery points, triggering restore operations, and performing cross-region restores.
 
 ## Prerequisites
 
 After completing an Azure VM backup with Azure Backup, you can restore entire VMs, disks, or files from the same backup copy. For any restore operation, you have to first identify the relevant recovery point.
 
-## Select Recovery point
+## Select Recovery point for Azure VM restore
 
 The available recovery points of a backup item can be listed using the [list recovery point REST API](/rest/api/backup/recovery-points/list). It's a simple *GET* operation with all the relevant values.
 
@@ -116,9 +116,9 @@ X-Powered-By: ASP.NET
 
 The recovery point is identified with the `{name}` field in the given response.
 
-## Restore operations
+## Trigger the restore operations for Azure VM
 
-After selecting the [relevant restore point](#select-recovery-point), proceed to trigger the restore operation.
+After selecting the [relevant restore point](#select-recovery-point-for-azure-vm-restore), proceed to trigger the restore operation.
 
 ***All restore operations on the backup item are performed with the same *POST* API. Only the request body changes with the restore scenarios.***
 
@@ -211,7 +211,7 @@ Since the restore job is a long running operation, it should be tracked as expla
 
 ### Restore disks
 
-If there's a need to customize the creation of a VM from the backup data, restore the disks into a chosen storage account and create a VM from those disks according to their requirements. The storage account should be in the same region as the Recovery Services vault and shouldn't be zone redundant. The disks, as well as the configuration of the backed-up VM ("vmconfig.json"), is stored in the given storage account. As explained [here](#restore-operations), the relevant request body for restore disks is provided below.
+If there's a need to customize the creation of a VM from the backup data, restore the disks into a chosen storage account and create a VM from those disks according to their requirements. The storage account should be in the same region as the Recovery Services vault and shouldn't be zone redundant. The disks, as well as the configuration of the backed-up VM ("vmconfig.json"), is stored in the given storage account. As explained [here](#trigger-the-restore-operations-for-azure-vm), the relevant request body for restore disks is provided below.
 
 #### Create request body
 
@@ -247,7 +247,7 @@ The following request body defines properties required to trigger a disk restore
 
 ### Restore disks selectively
 
-If you're [selectively backing up disks](backup-azure-arm-userestapi-backupazurevms.md#excluding-disks-in-azure-vm-backup), then the current backed-up disk list is provided in the [recovery point summary](#select-recovery-point) and [detailed response](/rest/api/backup/recovery-points/get). You can also selectively restore disks and more details are provided [here](selective-disk-backup-restore.md#selective-disk-restore). To selectively restore a disk among the list of backed up disks, find the LUN of the disk from the recovery point response and add the **restoreDiskLunList** property to the [request body above](#example-request) as shown below.
+If you're [selectively backing up disks](backup-azure-arm-userestapi-backupazurevms.md#excluding-disks-in-azure-vm-backup), then the current backed-up disk list is provided in the [recovery point summary](#select-recovery-point-for-azure-vm-restore) and [detailed response](/rest/api/backup/recovery-points/get). You can also selectively restore disks and more details are provided [here](selective-disk-backup-restore.md#selective-disk-restore). To selectively restore a disk among the list of backed up disks, find the LUN of the disk from the recovery point response and add the **restoreDiskLunList** property to the [request body above](#example-request) as shown below.
 
 ```json
 {
@@ -273,7 +273,7 @@ Once you track the response as explained [here](#responses), and the long runnin
 
 ### Replace disks in a backed-up virtual machine
 
-While restore disks creates disks from the recovery point, replace disks replaces the current disks of the backed-up VM with the disks from the recovery point. As explained [here](#restore-operations), the relevant request body for replacing disks is provided below.
+While restore disks create disks from the recovery point, replace disks replaces the current disks of the backed-up VM with the disks from the recovery point. As explained [here](#trigger-the-restore-operations-for-azure-vm), the relevant request body for replacing disks is provided below.
 
 #### Create request body
 
@@ -314,7 +314,7 @@ The following request body defines properties required to trigger a disk restore
 
 ### Restore as another virtual machine
 
-As explained [above](#restore-operations), the following request body defines properties required to trigger a virtual machine restore.
+As explained [above](#trigger-the-restore-operations-for-azure-vm), the following request body defines properties required to trigger a virtual machine restore.
 
 ```json
 {
@@ -340,7 +340,7 @@ As explained [above](#restore-operations), the following request body defines pr
 
 The response should be handled in the same way as [explained above for restoring disks](#responses).
 
-## Cross Region Restore
+## Cross Region Restore for Azure VMs
 
 If Cross Region Restore (CRR) is enabled on the vault with which you've protected your VMs, the backup data is replicated to the secondary region. You can use the backup data to perform a restore operation. To trigger a restore operation in the secondary region using REST API, follow these steps:
 
@@ -613,4 +613,4 @@ Similar to the primary region restore operation, this is an asynchronous operati
 For more information on the Azure Backup REST APIs, see the following documents:
 
 - [Azure Recovery Services provider REST API](/rest/api/recoveryservices/)
-- [Get started with Azure REST API](/rest/api/azure/)
+- [Get started with Azure REST API](/rest/api/azure/)

articles/backup/backup-azure-arm-userestapi-restoreazurevms.md

@@ -2,7 +2,7 @@
 title: Troubleshoot Azure Database for PostgreSQL - Flexible server backup
 description: Troubleshooting information for backing up Azure Database for PostgreSQL - Flexible server.
 ms.topic: troubleshooting
-ms.date: 02/17/2025
+ms.date: 02/10/2026
 ms.service: azure-backup
 ms.custom:
   - ignite-2024
@@ -15,7 +15,7 @@ ms.author: v-mallicka
 
 This article provides the recommended actions to troubleshoot the issues you might encounter during the backup or restore of Azure Database for PostgreSQL - Flexible server.
 
-## Common errors for the backup and restore operations
+## Common errors for the PostgreSQL Flex backup operation
 
 ### PostgreSQLFlexOperationFailedUserError 
 
@@ -63,11 +63,13 @@ This article provides the recommended actions to troubleshoot the issues you mig
 
 **Inner error code**: `UserErrorMaxConcurrentOperationLimitReached`
 
-**Cause**: Limit to the number of backups that can be performed on a backup instance has reached to maximum.
+**Cause**: Limit to the number of backups that can be performed on a backup instance reached to maximum.
 
-**Recommended action**: The recommended backup frequency for backing up a server is **Weekly**. If you need frequent backups for achieving your RPO requirement, try to trigger a backup operation after the current backup job is complete.
+**Recommended action**: The recommended backup frequency for backing up a server is **Weekly**. If you need frequent backups for achieving your Recovery Point Objective (RPO) requirement, try to trigger a backup operation after the current backup job is complete.
 
 
+## Common errors for the PostgreSQL Flex restore operation
+
 ### UserErrorMSIMissingPermissions 
 
 **Error code**: UserErrorMSIMissingPermissions 

articles/backup/backup-azure-database-postgresql-flex-troubleshoot.md

@@ -1,7 +1,7 @@
 ---
 title: Automation in Azure Backup support matrix
 description: This article summarizes automation tasks related to Azure Backup support.
-ms.date: 12/19/2025
+ms.date: 02/10/2026
 ms.topic: reference
 ms.service: azure-backup
 author: AbhishekMallick-MS
@@ -26,7 +26,7 @@ You  can automate most backup related tasks using programmatic methods in Azure
 | Backup | Selective disk backup | Supported  <br><br> [See the examples](./selective-disk-backup-restore.md#use-powershell) | Supported  <br><br> [See the examples](./selective-disk-backup-restore.md#use-the-cli). | Supported  <br><br> [See the examples](./backup-azure-arm-userestapi-backupazurevms.md#excluding-disks-in-azure-vm-backup). | N/A | N/A | N/A | Currently not supported. | 
 | Backup | Run on-demand backup | Supported   <br><br> [See the examples](./quick-backup-vm-powershell.md#trigger-an-azure-vm-backup-job). | Supported -  <br><br> [See the examples](./quick-backup-vm-cli.md#trigger-an-azure-vm-backup-job). | Supported   <br><br> [See the examples](./backup-azure-arm-userestapi-backupazurevms.md#trigger-an-on-demand-backup-for-a-protected-azure-vm). | N/A | N/A | N/A | N/A | 
 | Restore | Restore disks to primary region | Supported   <br><br> [See the examples](./backup-azure-vms-automation.md#restore-an-azure-vm). | Supported  <br><br> [See the examples](./tutorial-restore-disk.md#restore-a-vm-disk). | Supported  <br><br> [See the examples](./backup-azure-arm-userestapi-restoreazurevms.md). | N/A | N/A | N/A | N/A |
-| Restore | Cross-region restore | Supported   <br><br> [See the examples](./backup-azure-vms-automation.md#restore-disks-to-a-secondary-region). | Supported   <br><br> [See the examples](/cli/azure/backup/restore#az-backup-restore-restore-disks). | Supported   <br><br> [See the examples](./backup-azure-arm-userestapi-restoreazurevms.md#cross-region-restore). | N/A | N/A | N/A | N/A |
+| Restore | Cross-region restore | Supported   <br><br> [See the examples](./backup-azure-vms-automation.md#restore-disks-to-a-secondary-region). | Supported   <br><br> [See the examples](/cli/azure/backup/restore#az-backup-restore-restore-disks). | Supported   <br><br> [See the examples](./backup-azure-arm-userestapi-restoreazurevms.md#cross-region-restore-for-azure-vms). | N/A | N/A | N/A | N/A |
 | Restore | Restore selective disks | Supported   <br><br> [See the examples](./backup-azure-vms-automation.md#restore-selective-disks). | Supported   <br><br> [See the examples](./selective-disk-backup-restore.md#restore-disks-with-the-cli). | Supported   <br><br> [See the examples](./backup-azure-arm-userestapi-restoreazurevms.md#restore-disks-selectively). | N/A | N/A | N/A | N/A |
 | Restore | Create a VM from restored disks | Supported   <br><br> [See the examples](./backup-azure-vms-automation.md#using-managed-identity-to-restore-disks). | Supported   <br><br> [See the examples](./tutorial-restore-disk.md#using-managed-identity-to-restore-disks). | Supported   <br><br> [See the examples](/rest/api/backup/restores/trigger). | N/A | N/A | N/A | N/A |
 | Restore | Restore files | Supported   <br><br> [See the examples](./backup-azure-vms-automation.md#create-a-vm-from-restored-disks). | Supported   <br><br> [See the examples](./tutorial-restore-disk.md#create-a-vm-from-the-restored-disk). | Supported   <br><br> [See the examples](./backup-azure-arm-userestapi-restoreazurevms.md#restore-disks). | N/A | N/A | N/A | N/A |