Merge pull request #207904 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: tfosmark

articles/active-directory/managed-identities-azure-resources/managed-identities-status.md

@@ -50,6 +50,7 @@ The following Azure services support managed identities for Azure resources:
 | Azure Import/Export             | [Use customer-managed keys in Azure Key Vault for Import/Export service](../../import-export/storage-import-export-encryption-key-portal.md)
 | Azure IoT Hub                   | [IoT Hub support for virtual networks with Private Link and Managed Identity](../../iot-hub/virtual-network-support.md)                                                                               |
 | Azure Kubernetes Service (AKS)  | [Use managed identities in Azure Kubernetes Service](../../aks/use-managed-identity.md)                                                                                                                           |
+| Azure Load Testing                | [Use managed identities for Azure Load Testing](../../load-testing/how-to-use-a-managed-identity.md)  |
 | Azure Logic Apps                | [Authenticate access to Azure resources using managed identities in Azure Logic Apps](../../logic-apps/create-managed-service-identity.md)                                                                                                       |
 | Azure Log Analytics cluster     | [Azure Monitor customer-managed key](../../azure-monitor/logs/customer-managed-keys.md)
 | Azure Machine Learning Services | [Use Managed identities with Azure Machine Learning](../../machine-learning/how-to-use-managed-identities.md?tabs=python)                                                                                         |

articles/api-management/api-management-howto-configure-custom-domain-gateway.md

@@ -53,6 +53,8 @@ Add a custom domain certificate (.PFX) file to your API Management instance, or
     > This setting is shared by all domain names configured for the gateway.
 9. Select **Add** to assign the custom domain name to the selected self-hosted gateway.
 
+> [!NOTE]
+> If clients connecting to the self-hosted gateway using the custom domain expect to be presented with all intermediate certificates in the chain, you must upload individual CA certificates to your API Management Service and associate them with the self-hosted gateway. For instructions on how to achieve this, see [Create custom CA for self-hosted gateway](api-management-howto-ca-certificates.md#create-custom-ca-for-self-hosted-gateway) .
 ## Next steps
 
 [Upgrade and scale your service](upgrade-and-scale.md)

articles/availability-zones/migrate-app-service.md

@@ -85,7 +85,7 @@ You can create an App Service with availability zones using the [Azure CLI](/cli
 To enable availability zones using the Azure CLI, include the `--zone-redundant` parameter when you create your App Service plan. You can also include the `--number-of-workers` parameter to specify capacity. If you don't specify a capacity, the platform defaults to three. Capacity should be set based on the workload requirement, but no less than three. A good rule of thumb to choose capacity is to ensure sufficient instances for the application such that losing one zone of instances leaves sufficient capacity to handle expected load.
 
 ```azurecli
-az appservice plan create --resource-group MyResourceGroup --name MyPlan --zone-redundant --number-of-workers 6
+az appservice plan create --resource-group MyResourceGroup --name MyPlan --sku P1v2 --zone-redundant --number-of-workers 6
 ```
 
 > [!TIP]

articles/azure-functions/durable/durable-functions-monitor-python.md

@@ -106,7 +106,7 @@ POST https://{host}/orchestrators/E3_Monitor
 Content-Length: 77
 Content-Type: application/json
 
-{ "repo": "<your github handle>/<a new github repo under your user>", "phone": "+1425XXXXXXX" }
+{ "repo": "<your GitHub handle>/<a new GitHub repo under your user>", "phone": "+1425XXXXXXX" }
 ```
 
 For example, if your GitHub username is `foo` and your repository is `bar` then your value for `"repo"` should be `"foo/bar"`.

articles/azure-functions/functions-bindings-storage-blob-input.md

@@ -22,10 +22,10 @@ For information on setup and configuration details, see the [overview](./functio
 
 # [In-process](#tab/in-process)
 
-```csharp
-
 The following example is a [C# function](functions-dotnet-class-library.md) that uses a queue trigger and an input blob binding. The queue message contains the name of the blob, and the function logs the size of the blob.
 
+```csharp
+
 [FunctionName("BlobInput")]
 public static void Run(
     [QueueTrigger("myqueue-items")] string myQueueItem,

articles/azure-signalr/concept-service-mode.md

@@ -32,13 +32,13 @@ So if you have a SignalR application and want to integrate with SignalR service,
 In default mode, there will be websocket connections between hub server and SignalR service (called server connections). These connections are used to transfer messages between server and client. When a new client is connected, SignalR service will route the client to one hub server (assume you have more than one server) through existing server connections. Then the client connection will stick to the same hub server during its lifetime. When client sends messages, they always go to the same hub server. With this behavior, you can safely maintain some states for individual connections on your hub server. For example, if you want to stream something between server and client, you don't need to consider the case that data packets go to different servers.
 
 > [!IMPORTANT]
-> This also means in default mode client cannot connect without server being connected first. If all your hub servers are disconnected due to network interruption or server reboot, your client connect will get an error telling you no server is connected. So it's your responsibility to make sure at any time there is at least one hub server connected to SignalR service (for example, have multiple hub servers and make sure they won't go offline at the same time for things like maintenance).
+> This also means in default mode a client cannot connect without server being connected first. If all your hub servers are disconnected due to network interruption or server reboot, your client connections will get an error telling you no server is connected. So it's your responsibility to make sure at any time there is at least one hub server connected to SignalR service (for example, have multiple hub servers and make sure they won't go offline at the same time for things like maintenance).
 
 This routing model also means when a hub server goes offline, the connections routed that server will be dropped. So you should expect connection drop when your hub server is offline for maintenance and handle reconnect properly so that it won't have negative impact to your application.
 
 ## Serverless mode
 
-Serverless mode, as its name implies, is a mode that you cannot have any hub server. Comparing to default mode, in this mode client doesn't require hub server to get connected. All connections are connected to service in a "serverless" mode and service is responsible for maintaining client connections like handling client pings (in default mode this is handled by hub servers).
+In Serverless mode, you don't have a hub server. Unlike default mode, the client doesn't require a hub server to be running. All connections are connected in a "serverless" mode and the Azure SignalR service is responsible for maintaining client connections like handling client pings (in default mode this is handled by hub servers).
 
 Also there is no server connection in this mode (if you try to use service SDK to establish server connection, you will get an error). Therefore there is also no connection routing and server-client stickiness (as described in the default mode section). But you can still have server-side application to push messages to clients. This can be done in two ways, use [REST APIs](https://github.com/Azure/azure-signalr/blob/dev/docs/rest-api.md) for one-time send, or through a websocket connection so that you can send multiple messages more efficiently (note this websocket connection is different than server connection).
 
@@ -85,4 +85,4 @@ To learn more about how to use default and serverless mode, read the following a
 
 * [Azure SignalR Service internals](signalr-concept-internals.md)
 
-* [Azure Functions development and configuration with Azure SignalR Service](signalr-concept-serverless-development-config.md)
+* [Azure Functions development and configuration with Azure SignalR Service](signalr-concept-serverless-development-config.md)

articles/cognitive-services/language-service/summarization/includes/quickstarts/nodejs-sdk.md

@@ -127,6 +127,11 @@ summarization_example(textAnalyticsClient).catch((err) => {
 > [!div class="nextstepaction"]
 > <a href="https://microsoft.qualtrics.com/jfe/form/SV_0Cl5zkG3CnDjq6O?PLanguage=JAVASCRIPT&Pillar=Language&Product=Summarization&Page=quickstart&Section=Code-example" target="_target">I ran into an issue</a>
 
+### Command
+
+```console
+node index.js
+```
 ### Output
 
 ```console

articles/defender-for-cloud/defender-for-sql-usage.md

@@ -9,7 +9,7 @@ ms.date: 07/28/2022
 
 # Enable Microsoft Defender for SQL servers on machines 
 
-This Microsoft Defender plan detects anomalous activities indicating unusual and potentially harmful attempts to access or exploit databases.
+This Microsoft Defender plan detects anomalous activities indicating unusual and potentially harmful attempts to access or exploit databases on the SQL server.
 
 You'll see alerts when there are suspicious database activities, potential vulnerabilities, or SQL injection attacks, and anomalous database access and query patterns.
 
@@ -19,7 +19,7 @@ Microsoft Defender for SQL servers on machines extends the protections for your
 
 - On-premises SQL servers:
 
-    - [Azure Arc-enabled SQL Server (preview)](/sql/sql-server/azure-arc/overview)
+    - [Azure Arc-enabled SQL Server](/sql/sql-server/azure-arc/overview)
 
     - [SQL Server running on Windows machines without Azure Arc](../azure-monitor/agents/agent-windows.md)
 

articles/defender-for-cloud/quickstart-enable-database-protections.md

@@ -9,9 +9,9 @@ ms.date: 07/28/2022
 
 # Enable Microsoft Defender for Cloud database plans
 
-This article explains how to enable Microsoft Defender for Cloud's database protections for the most common database types, Azure, hybrid, and multicloud environments.
+This article explains how to enable Microsoft Defender for Cloud's database protections for the most common database types, within Azure, hybrid, and multicloud environments.
 
-Defender for Cloud database protections lets you protect your entire database estate with attack detection and threat response for the most popular database types in Azure. Defender for Cloud provides protection for the database engines and for data types, according to their attack surface and security risks.
+Defender for Cloud database protections let you protect your entire database estate with attack detection and threat response for the most popular database types in Azure. Defender for Cloud provides protection for the database engines and for data types, according to their attack surface and security risks.
 
 Database protection includes:
 

articles/digital-twins/concepts-data-explorer-plugin.md

@@ -82,7 +82,7 @@ The simplest way to ingest IoT data from Azure Digital Twins into Azure Data Exp
 
 ### Direct ingestion
 
-You can also opt to [ingest IoT data directly into your Azure Data Explorer cluster from IoT Hub](/azure/data-explorer/ingest-data-iot-hub), or from other sources. Then, the Azure Digital Twins graph will be used to contextualize the time series data using joint Azure Digital Twins/Azure Data Explorer queries. This option is a good choice for direct-ingestion workloads. For more information about this process, continue through the rest of this section.
+You can also opt to [ingest IoT data directly into your Azure Data Explorer cluster from IoT Hub](/azure/data-explorer/ingest-data-iot-hub), or from other sources. Then, the Azure Digital Twins graph will be used to contextualize the time series data using joint Azure Digital Twins/Azure Data Explorer queries. This option is a good choice for direct-ingestion workloads—however, you won't be able to leverage Azure Digital Twins' event-based architecture to update other twins, trigger downstream services, or emit notifications when twins change state. For more information about this process, continue through the rest of this section.
 
 #### Mapping data across Azure Data Explorer and Azure Digital Twins