Merge branch 'main' into patch-17

Author: JeffreyWolford

articles/ai-services/speech-service/includes/quickstarts/intent-recognition/javascript.md

@@ -51,7 +51,7 @@ Now we'll add some basic UI for input boxes, reference the Speech SDK's JavaScri
         <td><h1 style="font-weight:500;">Microsoft Azure AI Speech SDK JavaScript Quickstart</h1></td>
       </tr>
       <tr>
-        <td align="right"><a href="https://learn.microsoft.com~/articles/ai-services/speech-service/get-started" target="_blank">Subscription</a>:</td>
+        <td align="right"><a href="https://learn.microsoft.com/azure/ai-services/speech-service/overview" target="_blank">Subscription</a>:</td>
         <td><input id="subscriptionKey" type="text" size="40" value="subscription"></td>
       </tr>
       <tr>

articles/ai-services/speech-service/includes/release-notes/release-notes-stt.md

@@ -14,6 +14,12 @@ Real-time speech to text with diariazation is now generally available.
 
 Check out [Real-time diarization quickstart](../../get-started-stt-diarization.md) to learn more about how to create speech to text applications that use diarization to distinguish between the different speakers who participate in the conversation.
 
+#### Speech to Text model Update
+
+[Real-time Speech to Text](../../how-to-recognize-speech.md) has released new models with bilingual capabilities. The `en-IN` model now support both English and Hindi bilingual scenarios and offers improved accuracy. Arabic locales (`ar-AE`, `ar-BH`, `ar-DZ`, `ar-IL`, `ar-IQ`, `ar-KW`, `ar-LB`, `ar-LY`, `ar-MA`, `ar-OM`, `ar-PS`, `ar-QA`, `ar-SA`, `ar-SY`, `ar-TN`, `ar-YE`) are now equipped with bilingual support for English, enhanced accuracy and call center support. 
+
+[Batch transcription](../../batch-transcription.md) has launched models with new architecture for `es-ES`, `es-MX`, `fr-FR`, `it-IT`, `ja-JP`, `ko-KR`, `pt-BR`, `zh-CN`. These models significantly enhance readability and entity recognition. 
+
 ### March 2024 release
 
 #### Whisper general availability (GA)

articles/azure-monitor/agents/data-collection-syslog.md

@@ -189,6 +189,7 @@ You need:
 - A Log Analytics workspace where you have at least [contributor rights](../logs/manage-access.md#azure-rbac).
 - A [data collection endpoint](../essentials/data-collection-endpoint-overview.md#create-a-data-collection-endpoint).
 - [Permissions to create DCR objects](../essentials/data-collection-rule-create-edit.md#permissions) in the workspace.
+- Syslog messages must follow RFC standards ([RFC5424](https://www.ietf.org/rfc/rfc5424.txt) or [RFC3164](https://www.ietf.org/rfc/rfc3164.txt))
 
 ## Syslog record properties
 

articles/azure-monitor/agents/gateway.md

@@ -81,10 +81,11 @@ The Log Analytics gateway is available in these languages:
 
 ### Supported encryption protocols
 
-The Log Analytics gateway supports only Transport Layer Security (TLS) 1.0, 1.1, and 1.2.  It doesn't support Secure Sockets Layer (SSL).  To ensure the security of data in transit to Log Analytics, configure the gateway to use at least TLS 1.2. Older versions of TLS or SSL are vulnerable. Although they currently allow backward compatibility, avoid using them.  
+The Log Analytics gateway supports only Transport Layer Security (TLS) 1.0, 1.1, 1.2 and 1.3.  It doesn't support Secure Sockets Layer (SSL). To ensure the security of data in transit to Log Analytics, configure the gateway to use at least TLS 1.3. Although they currently allow for backward compatibility, avoid using older versions because they are vunerable.  
 
 For additional information, review [Sending data securely using TLS](../logs/data-security.md#sending-data-securely-using-tls). 
 
+
 >[!NOTE]
 >The gateway is a forwarding proxy that doesn’t store any data. Once the agent establishes connection with Azure Monitor, it follows the same encryption flow with or without the gateway. The data is encrypted between the client and the endpoint. Since the gateway is just a tunnel, it doesn’t have the ability the inspect what is being sent.
 

articles/event-grid/webhook-event-delivery.md

@@ -26,9 +26,9 @@ If you're using any other type of endpoint, such as an HTTP trigger based Azure
 
    Event Grid supports a manual validation handshake. If you're creating an event subscription with an SDK or tool that uses API version 2018-05-01-preview or later, Event Grid sends a `validationUrl` property in the data portion of the subscription validation event. To complete the handshake, find that URL in the event data and do a GET request to it. You can use either a REST client or your web browser.
 
-   The provided URL is valid for **5 minutes**. During that time, the provisioning state of the event subscription is `AwaitingManualAction`. If you don't complete the manual validation within 5 minutes, the provisioning state is set to `Failed`. You have to create the event subscription again before starting the manual validation.
+   The provided URL is valid for **10 minutes**. During that time, the provisioning state of the event subscription is `AwaitingManualAction`. If you don't complete the manual validation within 10 minutes, the provisioning state is set to `Failed`. You have to create the event subscription again before starting the manual validation.
 
-   This authentication mechanism also requires the webhook endpoint to return an HTTP status code of 200 so that it knows that the POST for the validation event was accepted before it can be put in the manual validation mode. In other words, if the endpoint returns 200 but doesn't return back a validation response synchronously, the mode is transitioned to the manual validation mode. If there's a GET on the validation URL within 5 minutes, the validation handshake is considered to be successful.
+   This authentication mechanism also requires the webhook endpoint to return an HTTP status code of 200 so that it knows that the POST for the validation event was accepted before it can be put in the manual validation mode. In other words, if the endpoint returns 200 but doesn't return back a validation response synchronously, the mode is transitioned to the manual validation mode. If there's a GET on the validation URL within 10 minutes, the validation handshake is considered to be successful.
 
 > [!NOTE]
 > Using self-signed certificates for validation isn't supported. Use a signed certificate from a commercial certificate authority (CA) instead.

articles/site-recovery/tutorial-shared-disk.md

@@ -218,6 +218,32 @@ To disable replication of your cluster with Azure Site Recovery, follow these st
     :::image type="content" source="media/tutorial-shared-disk/disable-replication.png" alt-text="Screenshot showing disable replication.":::
 
 
+## Commonly asked questions
+
+
+#### Is PowerShell supported for Azure Site Recovery with shared disks?
+No, PowerShell support for shared disks will be available as part of General Availability.
+
+#### Can we enable replication for only some of the VMs attached to a shared disk?
+No, enable replication can only be enabled successfully when all the VMs attached to a shared disk are selected.
+
+#### Is it possible to exclude shared disks and enable replication for only some of the VMs in a cluster?
+Yes, the first time you don’t select all the VMs in Enable Replication, a warning appears mentioning the unselected VMs attached to the shared disk. If you still proceed, unselect the shared disk replication by selecting ‘No’ for the storage option in Replication Settings tab.
+ 
+
+#### Can new shared disks be added to a protected cluster?
+No, if new shared disks need to be added, disable the replication for the already protected cluster. Enable a new cluster protection with a new cluster name for the modified infrastructure.
+
+#### Can we select both crash-consistent and app-consistent recovery points?
+Yes, both types of recovery points are generated. However, during Public Preview only crash-consistent and the Latest Processed recovery points are supported. App-consistent recovery points and Latest recovery point will be available as part of General Availability.
+
+#### Can we use recovery plans to failover Azure Site Recovery enabled VMs with shared disks?
+No, recovery plans are not supported for shared disks in Azure Site Recovery.
+
+#### Why is there no health status for VMs with shared disks in the monitoring plane, whether test failover is completed or not?
+The health status warning due to test failover will be available as part of General Availability.
+
+
 ## Next steps
 
 Learn more about:

includes/policy/standards/asb/rp-controls/microsoft.sql-dp-3.md

@@ -2,7 +2,7 @@
 author: davidsmatlak
 ms.service: azure-policy
 ms.topic: include
-ms.date: 04/11/2024
+ms.date: 04/17/2024
 ms.author: davidsmatlak
 ms.custom: generated
 ---

includes/policy/standards/asb/rp-controls/microsoft.sql-dp-4.md

@@ -2,7 +2,7 @@
 author: davidsmatlak
 ms.service: azure-policy
 ms.topic: include
-ms.date: 04/11/2024
+ms.date: 04/17/2024
 ms.author: davidsmatlak
 ms.custom: generated
 ---

includes/policy/standards/asb/rp-controls/microsoft.sql-dp-5.md

@@ -2,7 +2,7 @@
 author: davidsmatlak
 ms.service: azure-policy
 ms.topic: include
-ms.date: 04/11/2024
+ms.date: 04/17/2024
 ms.author: davidsmatlak
 ms.custom: generated
 ---

includes/policy/standards/asb/rp-controls/microsoft.sql-im-1.md

@@ -2,7 +2,7 @@
 author: davidsmatlak
 ms.service: azure-policy
 ms.topic: include
-ms.date: 04/11/2024
+ms.date: 04/17/2024
 ms.author: davidsmatlak
 ms.custom: generated
 ---