Merge pull request #297906 from MicrosoftDocs/repo_sync_working_branch

Taojunshen · web-flow · commit 98f16a341056 · 2025-04-10T00:36:20.000+08:00
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
diff --git a/articles/azure-functions/durable/durable-functions-troubleshooting-guide.md b/articles/azure-functions/durable/durable-functions-troubleshooting-guide.md
@@ -129,7 +129,7 @@ traces
 | extend status = customDimensions["prop__status"]
 | extend details = customDimensions["prop__Details"] 
 | extend reason = customDimensions["prop__reason"]
-| where severityLevel > 1 // to see all logs of  severity level "Information" or greater.
+| where severityLevel >= 1 // to see all logs of severity level "Information" or greater.
 | where instanceId == orchestrationInstanceID
 | sort by timestamp asc 
 ```
diff --git a/articles/azure-maps/migrate-get-traffic-incidents.md b/articles/azure-maps/migrate-get-traffic-incidents.md
@@ -69,22 +69,22 @@ The following table lists the fields that can appear in the HTTP response when r
 
 | Bing Maps response field | Azure Maps response field | Description |
 |--------------------------|---------------------------|-------------|
-| Description (Json)<br>Description (XML)  | `d`  | This output is in the [tm] response element of Azure Maps.  |
-| End (Json)<br>EndTimeUTC (XML)  | `ed`  | This output is in the [tm] response element of Azure Maps. The date is described in the ISO8601 format and includes time in UTC.  |
-| eventList (Json)<br>EventList (XML)  | Not supported | |
-| icon (Json)<br>Icon (XML)  | `ic`  | This output is in the [tm] response element of Azure Maps. See [IconCategory] (`ic`) for more info.  |
-| incidentId (Json)<br>IncidentId (XML)  | `id` | This output is in the [tm] response element of Azure Maps.  |
-| isEndTimeBackfilled (Json)<br>IsEndTimeBackfilled (XML)  | Not supported | |
-| isJamcident (Json)<br>IsJamcident (XML)  | Not supported |
-| lastModified (Json)<br>LastModifiedUTC (XML)  | Not supported | |
-| point (Json)<br>Point (XML)  | `p`  | This output is in the [tm] response element of Azure Maps. See [point] (`p`) for more info.  |
-| roadClosed (Json)<br>RoadClosed (XML)  | See description | The [IconCategory] output of the [tm] response element of Azure Maps can be used to indicate a road closure.   |
-| severity (Json)<br>Severity (XML)  | `ty`  | This output is in the [tm] response element. See [DelayMagnitude]:  (`ty`) for more info.  |
-| severityScore (Json)<br>SeverityScore (XML)              | Not supported | |
-| Start (Json)<br>StartTimeUTC (XML)  | `sd`  | This output is in the [tm] response element of Azure Maps. The date is described in the ISO8601 format and includes time in UTC.  |
-| title (Json)<br>Title (XML)  | See description | The `f` output in the [tm] response element of Azure Maps provides the name of the intersection or location where the traffic caused by the the incident starts and can serve as an alternative to the Bing Maps `title` output.  |
-| toPoint (Json)<br>ToPoint (XML)  | See description | The `t` output in the [tm] response element of Azure Maps provides the name of the intersection or location where the traffic due to the incident ends and can serve as an alternative to the Bing Maps `toPoint` output.  |
-| type (Json)<br>Type (XML)  | `c`  | The `c` output in the [tm] response element of Azure Maps provides the cause of the incident, if available.  |
+| Description (JSON)<br>Description (XML)  | `d`  | This output is in the [tm] response element of Azure Maps.  |
+| End (JSON)<br>EndTimeUTC (XML)  | `ed`  | This output is in the [tm] response element of Azure Maps. The date is described in the ISO8601 format and includes time in UTC.  |
+| eventList (JSON)<br>EventList (XML)  | Not supported | |
+| icon (JSON)<br>Icon (XML)  | `ic`  | This output is in the [tm] response element of Azure Maps. See [IconCategory] (`ic`) for more info.  |
+| incidentId (JSON)<br>IncidentId (XML)  | `id` | This output is in the [tm] response element of Azure Maps.  |
+| isEndTimeBackfilled (JSON)<br>IsEndTimeBackfilled (XML)  | Not supported | |
+| isJamcident (JSON)<br>IsJamcident (XML)  | Not supported |
+| lastModified (JSON)<br>LastModifiedUTC (XML)  | Not supported | |
+| point (JSON)<br>Point (XML)  | `p`  | This output is in the [tm] response element of Azure Maps. See [point] (`p`) for more info.  |
+| roadClosed (JSON)<br>RoadClosed (XML)  | See description | The [IconCategory] output of the [tm] response element of Azure Maps can be used to indicate a road closure.   |
+| severity (JSON)<br>Severity (XML)  | `ty`  | This output is in the [tm] response element. See [DelayMagnitude]:  (`ty`) for more info.  |
+| severityScore (JSON)<br>SeverityScore (XML)              | Not supported | |
+| Start (JSON)<br>StartTimeUTC (XML)  | `sd`  | This output is in the [tm] response element of Azure Maps. The date is described in the ISO8601 format and includes time in UTC.  |
+| title (JSON)<br>Title (XML)  | See description | The `f` output in the [tm] response element of Azure Maps provides the name of the intersection or location where the traffic caused by the the incident starts and can serve as an alternative to the Bing Maps `title` output.  |
+| toPoint (JSON)<br>ToPoint (XML)  | See description | The `t` output in the [tm] response element of Azure Maps provides the name of the intersection or location where the traffic due to the incident ends and can serve as an alternative to the Bing Maps `toPoint` output.  |
+| type (JSON)<br>Type (XML)  | `c`  | The `c` output in the [tm] response element of Azure Maps provides the cause of the incident, if available.  |
 
 For more information about the Azure Maps Get Traffic Incident Detail API response fields, see [Responses].
 
diff --git a/articles/backup/backup-azure-backup-server-vmware.md b/articles/backup/backup-azure-backup-server-vmware.md
@@ -435,7 +435,7 @@ You can modify the number of jobs by using the registry key as shown below (not
 The value should be the number (decimal) of virtual machines that you select for parallel backup.
 
 > [!NOTE]
-> You can modify the number of jobs to a higher value. If you set the jobs number to 1, replication jobs run serially. To increase the number to a higher value, you must consider the VMware performance. Consider the number of resources in use and additional usage required on VMWare vSphere Server, and determine the number of delta replication jobs to run in parallel. Also, this change will affect only the newly created protection groups. For existing protection groups you must temporarily add another VM to the protection group. This should update the protection group configuration accordingly. You can remove this VM from the protection group after the procedure is completed.
+> You can modify the number of jobs to a higher value. If you set the jobs number to 1, replication jobs run serially. To increase the number to a higher value, you must consider the VMware performance. Consider the number of resources in use and additional usage required on VMware vSphere Server, and determine the number of delta replication jobs to run in parallel. Also, this change will affect only the newly created protection groups. For existing protection groups you must temporarily add another VM to the protection group. This should update the protection group configuration accordingly. You can remove this VM from the protection group after the procedure is completed.
 
 ## VMware vSphere 6.7, 7.0, and 8.0
 
diff --git a/articles/backup/backup-azure-data-protection-use-rest-api-backup-postgresql.md b/articles/backup/backup-azure-data-protection-use-rest-api-backup-postgresql.md
@@ -510,7 +510,7 @@ GET "https://management.azure.com/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx
 
 ## Next steps
 
-[Restore data from an Azure PostGreSQL database backup](restore-postgresql-database-use-rest-api.md)
+[Restore data from an Azure PostgreSQL database backup](restore-postgresql-database-use-rest-api.md)
 
 For more information on the Azure Backup REST APIs, see the following articles:
 
diff --git a/articles/backup/backup-azure-data-protection-use-rest-api-create-update-postgresql-policy.md b/articles/backup/backup-azure-data-protection-use-rest-api-create-update-postgresql-policy.md
@@ -65,7 +65,7 @@ The `{policyName}` and `{vaultName}` are provided in the URI. Additional, inform
 
 ## Create the request body
 
-For example, to create a policy for POstgreSQL backup, the request body needs the following components:
+For example, to create a policy for PostgreSQL backup, the request body needs the following components:
 
 |Name  |Required  |Type  |Description  |
 |---------|---------|---------|---------|
@@ -368,7 +368,7 @@ After including all changes, the policy JSON will appear as follows:
 
 ```
 
-For more details about policy creation, see the [PostGreSQL database Backup policy](backup-azure-database-postgresql.md#create-backup-policy) document.
+For more details about policy creation, see the [PostgreSQL database Backup policy](backup-azure-database-postgresql.md#create-backup-policy) document.
 
 ## Responses
 
diff --git a/articles/backup/backup-azure-database-postgresql-flex-use-rest-api-create-update-policy.md b/articles/backup/backup-azure-database-postgresql-flex-use-rest-api-create-update-policy.md
@@ -322,7 +322,7 @@ After including all changes, the policy JSON will appear as follows:
 
 ```
 
-For more details about policy creation, see the [PostGreSQL database Backup policy document](backup-azure-database-postgresql.md#create-backup-policy).
+For more details about policy creation, see the [PostgreSQL database Backup policy document](backup-azure-database-postgresql.md#create-backup-policy).
 
 ### Responses
 
diff --git a/articles/backup/backup-postgresql-cli.md b/articles/backup/backup-postgresql-cli.md
@@ -56,7 +56,7 @@ After the vault is created, let's create a Backup policy to protect Azure Postgr
 
 ## Create a Backup policy
 
-### Understanding PostGreSQL backup policy
+### Understanding PostgreSQL backup policy
 
 While disk backup offers multiple backups per day and blob backup is a _continuous_ backup with no trigger, PostgreSQL backup offers Archive protection. The backup data that's first sent to the vault can be then moved to the _archive_ tier as per a defined rule or a _lifecycle_. In this context, let's understand the backup policy object for PostgreSQL.
 
@@ -268,7 +268,7 @@ Once the vault and policy are created, there are three critical points that you
 
 ### Key entities involved
 
-#### PostGreSQL database to be protected
+#### PostgreSQL database to be protected
 
 Fetch the Azure Resource Manager ID (ARM ID) of PostgreSQL to be protected. This serves as the identifier of the database. We'll use an example of a database named **empdb11** under a PostgreSQL server **testposgresql**, which is present in the resource group **ossrg** under a different subscription.
 
diff --git a/articles/backup/backup-rbac-rs-vault.md b/articles/backup/backup-rbac-rs-vault.md
@@ -134,19 +134,19 @@ The following table captures the Backup management actions and corresponding Azu
 | Restoring a blob | Backup Operator | Backup vault | |
 |  | Storage account backup contributor | Storage account containing the blob | In addition, the backup vault MSI should be given [these permissions](./blob-backup-configure-manage.md#grant-permissions-to-the-backup-vault-on-storage-accounts) |
 
-### Minimum role requirements for Azure database for PostGreSQL server backup
+### Minimum role requirements for Azure database for PostgreSQL server backup
 
 | Management Operation | Minimum Azure role required | Scope Required | Alternative |
 | --- | --- | --- | --- |
 | Validate before configuring backup | Backup Operator | Backup vault |   |
-|  | Reader | Azure PostGreSQL server |   |
+|  | Reader | Azure PostgreSQL server |   |
 | Enable backup from backup vault | Backup Operator | Backup vault |   |
-|  | Contributor | Azure PostGreSQL server | Alternatively, instead of a built-in-role, you can consider a custom role which has the following permissions: Microsoft.DBforPostgreSQL/servers/write Microsoft.DBforPostgreSQL/servers/read    In addition, the backup vault MSI should be given [these permissions](./backup-azure-database-postgresql-overview.md#set-of-permissions-needed-for-azure-postgresql-database-backup) |
-| On demand backup of PostGreSQL server | Backup Operator | Backup vault | |
+|  | Contributor | Azure PostgreSQL server | Alternatively, instead of a built-in-role, you can consider a custom role which has the following permissions: Microsoft.DBforPostgreSQL/servers/write Microsoft.DBforPostgreSQL/servers/read    In addition, the backup vault MSI should be given [these permissions](./backup-azure-database-postgresql-overview.md#set-of-permissions-needed-for-azure-postgresql-database-backup) |
+| On demand backup of PostgreSQL server | Backup Operator | Backup vault | |
 | Validate before restoring a server | Backup Operator | Backup vault | |
-|  | Contributor | Target Azure PostGreSQL server | Alternatively, instead of a built-in-role, you can consider a custom role which has the following permissions: Microsoft.DBforPostgreSQL/servers/write Microsoft.DBforPostgreSQL/servers/read
+|  | Contributor | Target Azure PostgreSQL server | Alternatively, instead of a built-in-role, you can consider a custom role which has the following permissions: Microsoft.DBforPostgreSQL/servers/write Microsoft.DBforPostgreSQL/servers/read
 | Restoring a server | Backup Operator | Backup vault | |
-|  | Contributor | Target Azure PostGreSQL server | Alternatively, instead of a built-in-role, you can consider a custom role which has the following permissions: Microsoft.DBforPostgreSQL/servers/write Microsoft.DBforPostgreSQL/servers/read    In addition, the backup vault MSI should be given [these permissions](./backup-azure-database-postgresql-overview.md#set-of-permissions-needed-for-azure-postgresql-database-restore) |
+|  | Contributor | Target Azure PostgreSQL server | Alternatively, instead of a built-in-role, you can consider a custom role which has the following permissions: Microsoft.DBforPostgreSQL/servers/write Microsoft.DBforPostgreSQL/servers/read    In addition, the backup vault MSI should be given [these permissions](./backup-azure-database-postgresql-overview.md#set-of-permissions-needed-for-azure-postgresql-database-restore) |
 
 ## Next steps
 
diff --git a/articles/backup/manage-backup-vault.md b/articles/backup/manage-backup-vault.md
@@ -154,7 +154,7 @@ The Cross Region Restore option allows you to restore data in a secondary Azur
    :::image type="content" source="./media/backup-vault-overview/monitor-postgresql-restore-to-secondary-region.png" alt-text="Screenshot shows how to monitor the postgresql restore to the secondary region." lightbox="./media/backup-vault-overview/monitor-postgresql-restore-to-secondary-region.png":::
 
 > [!NOTE]
-> Cross Region Restore is currently only available for PostGreSQL servers.
+> Cross Region Restore is currently only available for PostgreSQL servers.
 
 ## Cross Subscription Restore using Azure portal
 
diff --git a/articles/backup/restore-azure-database-postgresql-flex.md b/articles/backup/restore-azure-database-postgresql-flex.md
@@ -28,7 +28,7 @@ Before you restore from Azure Database for PostgreSQL Flexible server backups, r
 
 Follow these steps:
 
-1. Go to **Backup vault** > **Backup Instances**. Select the PostgreSQL-Flex server to be restored and select **Restore**.
+1. Go to **Backup vault** > **Backup Instances**. Select the PostgreSQL - Flexible server to be restored and select **Restore**.
 
    :::image type="content" source="./media/restore-azure-database-postgresql-flex/restore.png" alt-text="Screenshot showing how to restore a database.":::
 
@@ -43,7 +43,7 @@ Follow these steps:
 1. Once the validation is successful, select **Review + restore**.
    :::image type="content" source="./media/restore-azure-database-postgresql-flex/review-restore.png" alt-text="Screenshot showing the restore parameter process.":::
 
-1. After final review of the parameters, select **Restore** to restore the selected PostgreSQL-Flex server backup in target storage account.
+1. After final review of the parameters, select **Restore** to restore the selected PostgreSQL - Flexible server backup in target storage account.
    :::image type="content" source="./media/restore-azure-database-postgresql-flex/review.png" alt-text="Screenshot showing the review process page."::: 
    
 1. Submit the Restore operation and track the triggered job under **Backup jobs**.
diff --git a/articles/backup/restore-postgresql-database-use-rest-api.md b/articles/backup/restore-postgresql-database-use-rest-api.md
@@ -1,6 +1,6 @@
 ---
 title: Restore Azure PostgreSQL databases via Azure data protection REST API
-description: Learn how to restore Azure PostGreSQL databases using Azure Data Protection REST API.
+description: Learn how to restore Azure PostgreSQL databases using Azure Data Protection REST API.
 ms.topic: how-to
 ms.date: 02/09/2025
 ms.service: azure-backup
diff --git a/articles/backup/tutorial-cross-region-restore.md b/articles/backup/tutorial-cross-region-restore.md
@@ -84,5 +84,5 @@ To restore the database to the secondary region, follow these steps:
 
 For more information about backup and restore with Cross Region Restore, see:
 
-- [Cross Region Restore for PostGreSQL Servers](manage-backup-vault.md#perform-cross-region-restore-using-azure-portal).
+- [Cross Region Restore for PostgreSQL Servers](manage-backup-vault.md#perform-cross-region-restore-using-azure-portal).
 - [Restore Azure Database for PostgreSQL backups](./restore-azure-database-postgresql.md).
diff --git a/articles/storage/elastic-san/elastic-san-scale-targets.md b/articles/storage/elastic-san/elastic-san-scale-targets.md
@@ -41,7 +41,7 @@ Different regions have varying levels of base storage capacity available. We bre
 
 ##### Higher available base storage capacity
 
-The following regions are regions with higher base storage capacity available, and the table following the regions outlines their scale targets: Australia East, Brazil South, Canada Central, Germany West, North Europe, West Europe, UK South, East US, East US 2, South Central US, US Central, and West US 2.
+The following regions are regions with higher base storage capacity available, and the table following the regions outlines their scale targets: Australia East, Brazil South, Canada Central, Germany West, North Europe, West Europe, UK South, East US, East US 2, South Central US, US Central, West US 2, Australia Southeast, West Central US, West US, UK West.
 
 
 |Resource  |Values  |
@@ -57,7 +57,7 @@ The following regions are regions with higher base storage capacity available, a
 ##### Lower available base storage capacity
 
 
-The following regions are regions with lower base storage capacity available, and the table following the regions outlines their scale targets: East Asia, Korea Central, South Africa North, France Central, Southeast Asia, West US 3, Sweden Central, Switzerland North.
+The following regions are regions with lower base storage capacity available, and the table following the regions outlines their scale targets: East Asia, Korea Central, South Africa North, France Central, Southeast Asia, West US 3, Sweden Central, Switzerland North, Canada East, Japan West, North Central US, Australia Central, Southeast Brazil, Korea South, UAE Central, Switzerland West, Germany North, France South, Norway West, Sweden South.
 
 
 |Resource  |Values  |
diff --git a/articles/storage/files/storage-files-active-directory-overview.md b/articles/storage/files/storage-files-active-directory-overview.md
@@ -83,7 +83,7 @@ Once you've chosen an identity source, you must enable it on your storage accoun
 
 ### AD DS
 
-For AD DS authentication, you must domain-join your client machines or VMs. You can host your AD domain controllers on Azure VMs or on-premises. Either way, your domain-joined clients must have unimpeded network connectivity to the domain controller, so they must be within the corporate network or virtual network (VNET) of your domain service.
+For AD DS authentication, you can host your AD domain controllers on Azure VMs or on-premises. Either way, your clients must have unimpeded network connectivity to the domain controller, so they must be within the corporate network or virtual network (VNET) of your domain service. We recommend domain-joining your client machines or VMs so that users don't have to provide explicit credentials each time they access the share.
 
 The following diagram depicts on-premises AD DS authentication to Azure file shares over SMB. The on-premises AD DS must be synced to Microsoft Entra ID using Microsoft Entra Connect Sync or Microsoft Entra Connect cloud sync. Only [hybrid user identities](../../active-directory/hybrid/whatis-hybrid-identity.md) that exist in both on-premises AD DS and Microsoft Entra ID can be authenticated and authorized for Azure file share access. This is because the share-level permission is configured against the identity represented in Microsoft Entra ID, whereas the directory/file-level permission is enforced with that in AD DS. Make sure that you configure the permissions correctly against the same hybrid user.
 
