Merge pull request #257581 from MicrosoftDocs/repo_sync_working_branch

Saisang · web-flow · commit e544bd9426a1 · 2023-11-07T13:15:28.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-monitor/logs/manage-logs-tables.md b/articles/azure-monitor/logs/manage-logs-tables.md
@@ -54,6 +54,9 @@ Reduce costs and analysis effort by using data collection rules to [filter out a
 
 ## View table properties
 
+> [!NOTE]
+> The table name is case sensitive.
+
 # [Portal](#tab/azure-portal)
 
 To view and set table properties in the Azure portal:
@@ -137,9 +140,6 @@ To view table properties using PowerShell, run:
 Invoke-AzRestMethod -Path "/subscriptions/ContosoSID/resourcegroups/ContosoRG/providers/microsoft.operationalinsights/workspaces/ContosoWorkspace/tables/Heartbeat?api-version=2021-12-01-preview" -Method GET 
 ```
 
-> [!NOTE]
-> The table name used in the `-Path` parameter is case sensitive.
-
 **Sample response**
 
 ```json
diff --git a/articles/cosmos-db/how-to-develop-emulator.md b/articles/cosmos-db/how-to-develop-emulator.md
@@ -402,7 +402,7 @@ The certificate for the emulator is available in the `_explorer/emulator.pem` pa
     > [!NOTE]
     > You may need to change the host (or IP address) and port number if you have previously modified those values.
 
-1. Install the certificate according to the process typically used for your operating system. For example, in Linux you would copy the certificate to the  `/usr/local/share/ca-certificats/` path.
+1. Install the certificate according to the process typically used for your operating system. For example, in Linux you would copy the certificate to the  `/usr/local/share/ca-certificates/` path.
 
     ```bash
     cp ~/emulatorcert.crt /usr/local/share/ca-certificates/
diff --git a/articles/cosmos-db/introduction.md b/articles/cosmos-db/introduction.md
@@ -1,6 +1,6 @@
 ---
 title: Azure Cosmos DB – Unified AI Database
-titleSuffix: Azure Cosmos DB
+titleSuffix:
 description: Azure Cosmos DB is a global multi-model database and ideal database for AI applications requiring speed, elasticity and availability with native support for NoSQL and relational data.
 author: seesharprun
 ms.author: sidandrews
diff --git a/articles/iot-central/core/concepts-faq-scalability-availability.md b/articles/iot-central/core/concepts-faq-scalability-availability.md
@@ -42,7 +42,7 @@ An incident that requires disaster recovery could range from a subset of service
 
 ### Applications created after April 2023
 
-IoT Central applications created after March 2023 initially have a single IoT hub. If the IoT hub becomes unavailable, the application becomes unavailable. However, IoT Central automatically scales the application and adds a new IoT hub for each 10,000 connected devices. If you require multiple IoT hubs for applications with fewer than 10,000 devices, submit a request to [IoT Central customer support](../../iot/iot-support-help.md?toc=%2Fazure%2Fiot-central%2Ftoc.json&bc=%2Fazure%2Fiot-central%2Fbreadcrumb%2Ftoc.json).
+IoT Central applications created after April 2023 initially have a single IoT hub. If the IoT hub becomes unavailable, the application becomes unavailable. However, IoT Central automatically scales the application and adds a new IoT hub for each 10,000 connected devices. If you require multiple IoT hubs for applications with fewer than 10,000 devices, submit a request to [IoT Central customer support](../../iot/iot-support-help.md?toc=%2Fazure%2Fiot-central%2Ftoc.json&bc=%2Fazure%2Fiot-central%2Fbreadcrumb%2Ftoc.json).
 
 Use the `az iot central device manual-failover` command to check if your application currently uses a single IoT hub. This command returns an error if the application currently has a single IoT hub.
 
diff --git a/articles/logic-apps/create-single-tenant-workflows-visual-studio-code.md b/articles/logic-apps/create-single-tenant-workflows-visual-studio-code.md
@@ -90,7 +90,7 @@ Install the following tools and versions for your specific operating system: Win
 
   * Azure Functions Core Tools - 4.x version
 
-    * [Windows](https://github.com/Azure/azure-functions-core-tools/releases/tag/4.0.4865): Use the Microsoft Installer (MSI) version, which is `func-cli-X.X.XXXX-x*.msi`.
+    * [Windows](https://github.com/Azure/azure-functions-core-tools/releases): Use the Microsoft Installer (MSI) version, which is `func-cli-X.X.XXXX-x*.msi`.
     * [macOS](../azure-functions/functions-run-local.md?tabs=macos#install-the-azure-functions-core-tools)
     * [Linux](../azure-functions/functions-run-local.md?tabs=linux#install-the-azure-functions-core-tools)
 
diff --git a/articles/mariadb/howto-configure-privatelink-cli.md b/articles/mariadb/howto-configure-privatelink-cli.md
@@ -71,7 +71,7 @@ Note the public IP address of the VM. You will use this address to connect to
 
 ## Create an Azure Database for MariaDB server 
 
-Create a Azure Database for MariaDB with the az mariadb server create command. Remember that the name of your MariaDB Server must be unique across Azure, so replace the placeholder value in brackets with your own unique value:
+Create an Azure Database for MariaDB with the az mariadb server create command. Remember that the name of your MariaDB Server must be unique across Azure, so replace the placeholder value in brackets with your own unique value:
 
 ```azurecli-interactive
 # Create a server in the resource group 
diff --git a/articles/mysql/flexible-server/concepts-high-availability.md b/articles/mysql/flexible-server/concepts-high-availability.md
@@ -158,7 +158,7 @@ If there's a database crash or node failure, the Flexible Server VM is restarted
 For zone-redundant HA, while there is no major performance impact for read workloads across availability zones, there might be up to 40 percent drop in write-query latency. The increase in write-latency is due to synchronous replication across Availability zone. The write latency impact is generally twice in zone redundant HA compared to the same zone HA. For same-zone HA, because the primary and the standby replica is in the same zone, the replication latency and consequently the synchronous write latency is lower. In summary, if write-latency is more critical for you compared to availability, you may want to choose same-zone HA but if availability and resiliency of your data is more critical for you at the expense of write-latency drop, you must choose zone-redundant HA. To measure the accurate impact of the latency drop in HA setup, we recommend you to perform performance testing for your workload to take an informed decision.</br>
 
 - **How does maintenance of my HA server happen?**</br>
-Planned events like scaling of compute and minor version upgrades happen on the primary and the standby at the same time. You can set the [scheduled maintenance window](./concepts-maintenance.md) for HA servers as you do for flexible servers. The amount of downtime will be the same as the downtime for the Azure Database for MySQL - Flexible Server when HA is disabled. Using the failover mechanism to reduce downtime for HA servers is on our roadmap and will be available soon. </br>
+Planned events like scaling of compute and minor version upgrades happen on the primary and the standby at the same time. You can set the [scheduled maintenance window](./concepts-maintenance.md) for HA servers as you do for flexible servers. The amount of downtime will be the same as the downtime for the Azure Database for MySQL - Flexible Server when HA is disabled. </br>
 
 - **Can I do a point-in-time restore (PITR) of my HA server?**</br>
 You can do a [PITR](./concepts-backup-restore.md#point-in-time-restore) for an HA-enabled Azure Database for MySQL - Flexible Server to a new Azure Database for MySQL - Flexible Server that has HA disabled. If the source server was created with zone-redundant HA, you can enable zone-redundant HA or same-zone HA on the restored server later. If the source server was created with same-zone HA, you can enable only same-zone HA on the restored server.</br>
diff --git a/articles/mysql/single-server/concepts-connect-to-a-gateway-node.md b/articles/mysql/single-server/concepts-connect-to-a-gateway-node.md
@@ -1,6 +1,6 @@
 ---
 title: Azure Database for MySQL managing updates and upgrades
-description: Learn which versions of the MySQL server are supported in the Azure Database for MySQL service.
+description: Learn which versions of the MySQL server are supported in the Azure Database for MySQL Service.
 author: SudheeshGH
 ms.author: sunaray
 ms.service: mysql
@@ -16,11 +16,11 @@ ms.date: 06/20/2022
 
 [!INCLUDE[azure-database-for-mysql-single-server-deprecation](../includes/azure-database-for-mysql-single-server-deprecation.md)]
 
-In the Single Server deployment option, a gateway is used to redirect the connections to server instances. After the connection is established, the MySQL client displays the version of MySQL set in the gateway, not the actual version running on your MySQL server instance. To determine the version of your MySQL server instance, use the `SELECT VERSION();` command at the MySQL prompt. Review [Connectivity architecture](./concepts-connectivity-architecture.md#connectivity-architecture) to learn more about gateways in Azure Database for MySQL service architecture.
+In the Single Server deployment option, a gateway is used to redirect the connections to server instances. After the connection is established, the MySQL client displays the version of MySQL set in the gateway, not the actual version running on your MySQL server instance. To determine the version of your MySQL server instance, use the `SELECT VERSION();` command at the MySQL prompt. Review [Connectivity architecture](./concepts-connectivity-architecture.md#connectivity-architecture) to learn more about gateways in Azure Database for MySQL Service architecture.
 
 As Azure Database for MySQL supports major version v5.7 and v8.0, the default port 3306 to connect to Azure Database for MySQL runs MySQL client version 5.6 (least common denominator) to support connections to servers of all 2 supported major versions. However, if your application has a requirement to connect to specific major version say v5.7 or v8.0, you can do so by changing the port in your server connection string.
 
-In Azure Database for MySQL service, gateway nodes listens on port 3308 for v5.7 clients and port 3309 for v8.0 clients. In other words, if you would like to connect to v5.7 gateway client, you should use your fully qualified server name and port 3308 to connect to your server from client application. Similarly, if you would like to connect to v8.0 gateway client, you can use your fully qualified server name and port 3309 to connect to your server. Check the following example for further clarity.
+In Azure Database for MySQL Service, gateway nodes listens on port 3308 for v5.7 clients and port 3309 for v8.0 clients. In other words, if you would like to connect to v5.7 gateway client, you should use your fully qualified server name and port 3308 to connect to your server from client application. Similarly, if you would like to connect to v8.0 gateway client, you can use your fully qualified server name and port 3309 to connect to your server. Check the following example for further clarity.
 
 :::image type="content" source="./media/concepts-supported-versions/concepts-supported-versions-gateway.png" alt-text="Example connecting via different gateway mysql versions":::
 
diff --git a/articles/role-based-access-control/includes/resource-provider-operations/databases.md b/articles/role-based-access-control/includes/resource-provider-operations/databases.md
@@ -65,12 +65,6 @@ Azure service: [Azure Cache for Redis](../../../azure-cache-for-redis/index.yml)
 > | Microsoft.Cache/redis/privateEndpointConnections/write | Write a private endpoint connection |
 > | Microsoft.Cache/redis/privateEndpointConnections/delete | Delete a private endpoint connection |
 > | Microsoft.Cache/redis/privateLinkResources/read | Read 'groupId' of redis subresource that a private link can be connected to |
-> | Microsoft.Cache/redis/roleAssignments/read | Read role assignments on a Redis Cache |
-> | Microsoft.Cache/redis/roleAssignments/write | Create or update role assignments on a Redis Cache |
-> | Microsoft.Cache/redis/roleAssignments/delete | Delete All Redis Role Assignments |
-> | Microsoft.Cache/redis/roles/read | Read roles on a Redis Cache |
-> | Microsoft.Cache/redis/roles/write | Create or update role on a Redis Cache |
-> | Microsoft.Cache/redis/roles/delete | Delete role on a Redis Cache |
 > | Microsoft.Cache/redisEnterprise/delete | Delete the entire Redis Enterprise cache |
 > | Microsoft.Cache/redisEnterprise/read | View the Redis Enterprise cache's settings and configuration in the management portal |
 > | Microsoft.Cache/redisEnterprise/write | Modify the Redis Enterprise cache's settings and configuration in the management portal |
