Merge pull request #192031 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: huypub

articles/active-directory/conditional-access/howto-conditional-access-policy-location.md

@@ -52,7 +52,7 @@ More information about the location condition in Conditional Access can be found
    1. Under **Include**, select **Selected locations**
    1. Select the blocked location you created for your organization.
    1. Click **Select**.
-1. Under **Access controls** > select **Block Access**, and select **Select**.
+1. Under **Access controls** > select **Block Access**, and click **Select**.
 1. Confirm your settings and set **Enable policy** to **Report-only**.
 1. Select **Create** to create to enable your policy.
 

articles/api-management/api-management-advanced-policies.md

@@ -900,7 +900,7 @@ This example shows how to return a 401 response if the authorization token is in
 
 This policy can be used in the following policy [sections](./api-management-howto-policies.md#sections) and [scopes](./api-management-howto-policies.md#scopes).
 
--   **Policy sections:** outbound, backend, on-error
+-   **Policy sections:** inbound, outbound, backend, on-error
 -   **Policy scopes:** all scopes
 
 ## <a name="set-variable"></a> Set variable

articles/azure-resource-manager/management/tag-resources.md

@@ -12,6 +12,8 @@ You apply tags to your Azure resources, resource groups, and subscriptions to lo
 
 For recommendations on how to implement a tagging strategy, see [Resource naming and tagging decision guide](/azure/cloud-adoption-framework/decision-guides/resource-tagging/?toc=/azure/azure-resource-manager/management/toc.json).
 
+Resource tags support all cost-accruing services. You can use Azure Policy to ensure that cost-accruing services are provisioned with a tag by using one of the many different [tag policies](/azure/azure-resource-manager/management/tag-policies).  
+
 > [!WARNING]
 > Tags are stored as plain text. Never add sensitive values to tags. Sensitive values could be exposed through many methods, including cost reports, tag taxonomies, deployment histories, exported templates, and monitoring logs.
 

articles/azure-sql/database/ledger-append-only-ledger-tables.md

@@ -50,7 +50,7 @@ For every append-only ledger table, the system automatically generates a view, c
 | --- | --- | --- |
 | ledger_transaction_id | bigint | The ID of the transaction that created or deleted a row version. |
 | ledger_sequence_number | bigint | The sequence number of a row-level operation within the transaction on the table. |
-| ledger_operation_type_id | tinyint | Contains `0` (**INSERT**) or `1` (**DELETE**). Inserting a row into the ledger table produces a new row in the ledger view that contains `0` in this column. Deleting a row from the ledger table produces a new row in the ledger view that contains `1` in this column. Updating a row in the ledger table produces two new rows in the ledger view. One row contains `1` (**DELETE**), and the other row contains `1` (**INSERT**) in this column. A DELETE shouldn't occur on an append-only ledger table. |
+| ledger_operation_type | tinyint | Contains `1` (**INSERT**) or `2` (**DELETE**). Inserting a row into the ledger table produces a new row in the ledger view that contains `1` in this column. Deleting a row from the ledger table produces a new row in the ledger view that contains `2` in this column. Updating a row in the ledger table produces two new rows in the ledger view. One row contains `2` (**DELETE**), and the other row contains `1` (**INSERT**) in this column. A DELETE shouldn't occur on an append-only ledger table. |
 | ledger_operation_type_desc | nvarchar(128) | Contains `INSERT` or `DELETE`. For more information, see the preceding row. |
 
 ## Next steps

articles/azure-sql/database/ledger-updatable-ledger-tables.md

@@ -75,7 +75,7 @@ The ledger view's schema mirrors the columns defined in the updatable ledger and
 | --- | --- | --- |
 | ledger_transaction_id | bigint | The ID of the transaction that created or deleted a row version. |
 | ledger_sequence_number | bigint | The sequence number of a row-level operation within the transaction on the table. |
-| ledger_operation_type_id | tinyint | Contains `0` (**INSERT**) or `1` (**DELETE**). Inserting a row into the ledger table produces a new row in the ledger view that contains `0` in this column. Deleting a row from the ledger table produces a new row in the ledger view that contains `1` in this column. Updating a row in the ledger table produces two new rows in the ledger view. One row contains `1` (**DELETE**), and the other row contains `1` (**INSERT**) in this column. |
+| ledger_operation_type | tinyint | Contains `1` (**INSERT**) or `2` (**DELETE**). Inserting a row into the ledger table produces a new row in the ledger view that contains `1` in this column. Deleting a row from the ledger table produces a new row in the ledger view that contains `2` in this column. Updating a row in the ledger table produces two new rows in the ledger view. One row contains `2` (**DELETE**), and the other row contains `1` (**INSERT**) in this column. |
 | ledger_operation_type_desc | nvarchar(128) | Contains `INSERT` or `DELETE`. For more information, see the preceding row. |
 
 ## Next steps

articles/machine-learning/how-to-troubleshoot-online-endpoints.md

@@ -88,7 +88,18 @@ By default the logs are pulled from the inference server. Logs include the conso
 
 You can also get logs from the storage initializer container by passing `–-container storage-initializer`. These logs contain information on whether code and model data were successfully downloaded to the container.
 
-Add `--help` and/or `--debug` to commands to see more information. Include the `x-ms-client-request-id` header to help with troubleshooting.
+Add `--help` and/or `--debug` to commands to see more information. 
+
+## Request tracing
+
+There are three supported tracing headers:
+
+- `x-request-id` is reserved for server tracing. We override this header to ensure it's a valid GUID.
+
+   > [!Note]
+   > When you create a support ticket for a failed request, attach the failed request ID to expedite investigation.
+   
+- `x-ms-request-id` and `x-ms-client-request-id` are available for client tracing scenarios. We sanitize these headers to remove non-alphanumeric symbols. These headers are truncated to 72 characters.
 
 ## Common deployment errors
 

articles/postgresql/hyperscale/reference-versions.md

@@ -51,8 +51,8 @@ PostgreSQL - Hyperscale (Citus).
 
 Depending on which version of PostgreSQL is running in a server group,
 different [versions of PostgreSQL extensions](reference-extensions.md)
-will be installed as well. In particular, Postgres versions 12-14 come with
-Citus 10, and earlier Postgres versions come with Citus 9.5.
+will be installed as well. In particular, PostgreSQL versions 12-14 come with
+Citus 10, and earlier PostgreSQL versions come with Citus 9.5.
 
 ## Next steps
 

articles/sentinel/roles.md

@@ -28,7 +28,7 @@ Use Azure RBAC to create and assign roles within your security operations team t
 
 - [Microsoft Sentinel Contributor](../role-based-access-control/built-in-roles.md#microsoft-sentinel-contributor) can, in addition to the above, create and edit workbooks, analytics rules, and other Microsoft Sentinel resources.
 
-- [Microsoft Sentinel Automation Contributor](../role-based-access-control/built-in-roles.md#microsoft-sentinel-contributor) allows Microsoft Sentinel to add playbooks to automation rules. It is not meant for user accounts.
+- [Microsoft Sentinel Automation Contributor](../role-based-access-control/built-in-roles.md#microsoft-sentinel-automation-contributor) allows Microsoft Sentinel to add playbooks to automation rules. It is not meant for user accounts.
 
 > [!NOTE]
 >

includes/key-vault-limits.md

@@ -63,16 +63,6 @@ Key Vault does not restrict the number of keys, secrets or certificates that can
 
 Key Vault does not restrict the number of versions on a secret, key or certificate, but storing a large number of versions (500+) can impact the performance of backup operations. See [Azure Key Vault Backup](../articles/key-vault/general/backup.md).
 
-#### Azure Private Link integration
-
-> [!NOTE]
-> The number of key vaults with private endpoints enabled per subscription is an adjustable limit. The limit shown below is the default limit. If you would like to request a limit increase for your service, please create a support request and it will be assessed on a case by case basis.
-
-| Resource | Limit |
-| -------- | -----:|
-| Private endpoints per key vault or managed HSM| 64 |
-| Key vaults with private endpoints per subscription | 400 |
-
 ### Resource type: Managed HSM
 
 This section describes service limits for resource type `managed HSM`.