Merge pull request #274540 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: Taojunshen

articles/ai-services/language-service/conversational-language-understanding/concepts/best-practices.md

@@ -216,3 +216,38 @@ curl --request POST \
 "targetResourceRegion": "<target-region>" 
 }'
 ```
+
+
+## Addressing out of domain utterances
+
+Customers can use the new recipe version '2024-06-01-preview' in case the model has poor AIQ on out of domain utterances. An example of this with the default recipe can be like the below where the model has 3 intents Sports, QueryWeather and Alarm. The test utterances are out of domain utterances and the model classifies them as InDomain with a relatively high confidence score.
+
+| Text |	Predicted intent |	Confidence score |
+|----|----|----|
+| "*Who built the Eiffel Tower?*" |	 `Sports` | 0.90 |
+| "*Do I look good to you today?*" | `QueryWeather` |	1.00 |
+| "*I hope you have a good evening.*" | `Alarm` | 0.80 |
+
+To address this, use the `2024-06-01-preview` configuration version that is built specifically to address this issue while also maintaining reasonably good quality on In Domain utterances.
+
+```console
+curl --location 'https://<your-resource>.cognitiveservices.azure.com/language/authoring/analyze-conversations/projects/<your-project>/:train?api-version=2022-10-01-preview' \
+--header 'Ocp-Apim-Subscription-Key: <your subscription key>' \
+--header 'Content-Type: application/json' \
+--data '{
+      "modelLabel": "<modelLabel>",
+      "trainingMode": "advanced",
+      "trainingConfigVersion": "2024-06-01-preview",
+      "evaluationOptions": {
+            "kind": "percentage",
+            "testingSplitPercentage": 0,
+            "trainingSplitPercentage": 100
+      }
+}
+```
+
+Once the request is sent, you can track the progress of the training job in Language Studio as usual.
+
+Caveats:
+- The None Score threshold for the app (confidence threshold below which the topIntent is marked as None) when using this recipe should be set to 0. This is because this new recipe attributes a certain portion of the in domain probabiliities to out of domain so that the model is not incorrectly overconfident about in domain utterances. As a result, users may see slightly reduced confidence scores for in domain utterances as compared to the prod recipe.
+- This recipe is not recommended for apps with just two (2) intents, such as IntentA and None, for example.

articles/azure-app-configuration/enable-dynamic-configuration-dotnet-core-push-refresh.md

@@ -39,7 +39,7 @@ In this tutorial, you learn how to:
 
 ## Set up Azure Service Bus topic and subscription
 
-This tutorial uses the Service Bus integration for Event Grid to simplify the detection of configuration changes for applications that don't wish to poll App Configuration for changes continuously. The Azure Service Bus SDK provides an API to register a message handler that can be used to update configuration when changes are detected in App Configuration. Follow steps in the [Quickstart: Use the Azure portal to create a Service Bus topic and subscription](../service-bus-messaging/service-bus-quickstart-topics-subscriptions-portal.md) to create a service bus namespace, topic, and subscription.
+This tutorial uses the Service Bus integration for Event Grid to simplify the detection of configuration changes for applications that don't wish to poll App Configuration for changes continuously. The Azure Service Bus SDK provides an API to register a message handler that can be used to update configuration when changes are detected in App Configuration. Follow the steps in the [Quickstart: Use the Azure portal to create a Service Bus topic and subscription](../service-bus-messaging/service-bus-quickstart-topics-subscriptions-portal.md) to create a service bus namespace, topic, and subscription.
 
 Once the resources are created, add the following environment variables. These will be used to register an event handler for configuration changes in the application code.
 
@@ -111,13 +111,14 @@ namespace TestConsole
                     options.ConfigureRefresh(refresh =>
                         refresh
                             .Register("TestApp:Settings:Message")
-                            .SetCacheExpiration(TimeSpan.FromDays(1))  // Important: Reduce poll frequency
+                            // Important: Reduce poll frequency
+                            .SetCacheExpiration(TimeSpan.FromDays(1))  
                     );
 
                     _refresher = options.GetRefresher();
                 }).Build();
 
-            RegisterRefreshEventHandler();
+            await RegisterRefreshEventHandler();
             var message = configuration["TestApp:Settings:Message"];
             Console.WriteLine($"Initial value: {configuration["TestApp:Settings:Message"]}");
 
@@ -135,33 +136,35 @@ namespace TestConsole
             }
         }
 
-        private static void RegisterRefreshEventHandler()
+        private static async Task RegisterRefreshEventHandler()
         {
             string serviceBusConnectionString = Environment.GetEnvironmentVariable(ServiceBusConnectionStringEnvVarName);
             string serviceBusTopic = Environment.GetEnvironmentVariable(ServiceBusTopicEnvVarName);
-            string serviceBusSubscription = Environment.GetEnvironmentVariable(ServiceBusSubscriptionEnvVarName);
+            string serviceBusSubscription = Environment.GetEnvironmentVariable(ServiceBusSubscriptionEnvVarName); 
             ServiceBusClient serviceBusClient = new ServiceBusClient(serviceBusConnectionString);
             ServiceBusProcessor serviceBusProcessor = serviceBusClient.CreateProcessor(serviceBusTopic, serviceBusSubscription);
 
             serviceBusProcessor.ProcessMessageAsync += (processMessageEventArgs) =>
-                {
-                    // Build EventGridEvent from notification message
-                    EventGridEvent eventGridEvent = EventGridEvent.Parse(BinaryData.FromBytes(processMessageEventArgs.Message.Body));
+            {
+                // Build EventGridEvent from notification message
+                EventGridEvent eventGridEvent = EventGridEvent.Parse(BinaryData.FromBytes(processMessageEventArgs.Message.Body));
 
-                    // Create PushNotification from eventGridEvent
-                    eventGridEvent.TryCreatePushNotification(out PushNotification pushNotification);
+                // Create PushNotification from eventGridEvent
+                eventGridEvent.TryCreatePushNotification(out PushNotification pushNotification);
 
-                    // Prompt Configuration Refresh based on the PushNotification
-                    _refresher.ProcessPushNotification(pushNotification);
+                // Prompt Configuration Refresh based on the PushNotification
+                _refresher.ProcessPushNotification(pushNotification);
 
-                    return Task.CompletedTask;
-                };
+                return Task.CompletedTask;
+            };
 
             serviceBusProcessor.ProcessErrorAsync += (exceptionargs) =>
-                {
-                    Console.WriteLine($"{exceptionargs.Exception}");
-                    return Task.CompletedTask;
-                };
+            {
+                Console.WriteLine($"{exceptionargs.Exception}");
+                return Task.CompletedTask;
+            };
+
+            await serviceBusProcessor.StartProcessingAsync();
         }
     }
 }

articles/container-registry/zone-redundancy.md

@@ -24,7 +24,7 @@ Zone redundancy is a  feature of the Premium container registry service tier. Fo
 
     |Americas  |Europe  |Africa  |Asia Pacific  |
     |---------|---------|---------|---------|
-    |Brazil South<br/>Canada Central<br/>Central US<br/>East US<br/>East US 2<br/>East US 2 EUAP<br/>South Central US<br/>US Government Virginia<br/>West US 2<br/>West US 3     |France Central<br/>Germany West Central<br/>North Europe<br/>Norway East<br/>Sweden Central<br/>Switzerland North<br/>UK South<br/>West Europe    |South Africa North<br/>        |Australia East<br/>Central India<br/>China North 3<br/>East Asia<br/>Japan East<br/>Korea Central<br/>Qatar Central<br/>Southeast Asia<br/>UAE North     |
+    |Brazil South<br/>Canada Central<br/>Central US<br/>East US<br/>East US 2<br/>East US 2 EUAP<br/>South Central US<br/>US Government Virginia<br/>West US 2<br/>West US 3     |France Central<br/>Germany West Central<br/>Italy North<br/>North Europe<br/>Norway East<br/>Sweden Central<br/>Switzerland North<br/>UK South<br/>West Europe    |South Africa North<br/>        |Australia East<br/>Central India<br/>China North 3<br/>East Asia<br/>Japan East<br/>Korea Central<br/>Qatar Central<br/>Southeast Asia<br/>UAE North     |
 
 * Region conversions to availability zones aren't currently supported. 
 * To enable availability zone support in a region, create the registry in the desired region with availability zone support enabled, or add a replicated region with availability zone support enabled.

articles/spring-apps/enterprise/how-to-configure-enterprise-spring-cloud-gateway.md

@@ -244,7 +244,7 @@ If you send the `GET` request to the `/scg-logout` endpoint by using `XMLHttpReq
 
 You need to have a route configuration to route the logout request to your application, as shown in the following example. This code makes a gateway-only logout SSO session.
 
-```java
+```javascript
 const req = new XMLHttpRequest();
 req.open("GET", "/scg-logout);
 req.send();

articles/virtual-machines/linux/disk-encryption-sample-scripts.md

@@ -279,7 +279,7 @@ To configure encryption during the distribution installation, do the following s
 
    ![openSUSE 13.2 Setup - Provide passphrase on boot](./media/disk-encryption/opensuse-encrypt-fig2.png)
 
-3. Prepare the VM for uploading to Azure by following the instructions in [Prepare a SLES or openSUSE virtual machine for Azure](./suse-create-upload-vhd.md?toc=/azure/virtual-machines/linux/toc.json#prepare-opensuse-152). Don't run the last step (deprovisioning the VM) yet.
+3. Prepare the VM for uploading to Azure by following the instructions in [Prepare a SLES or openSUSE virtual machine for Azure](./suse-create-upload-vhd.md?toc=/azure/virtual-machines/linux/toc.json#prepare-opensuse-154). Don't run the last step (deprovisioning the VM) yet.
 
 To configure encryption to work with Azure, do the following steps:
 

articles/virtual-machines/linux/suse-create-upload-vhd.md

@@ -7,7 +7,7 @@ ms.subservice: imaging
 ms.collection: linux
 ms.custom: linux-related-content
 ms.topic: how-to
-ms.date: 12/14/2022
+ms.date: 04/28/2024
 ms.author: srijangupta
 ms.reviewer: mattmcinnes
 ---
@@ -221,33 +221,35 @@ As an alternative to building your own VHD, SUSE also publishes BYOS (bring your
     sudo rm -f ~/.bash_history
     ```
 
-## Prepare openSUSE 15.2+
+## Prepare openSUSE 15.4+
 
 1. On the center pane of Hyper-V Manager, select the virtual machine.
-2. Select **Connect** to open the window for the virtual machine.
-3. In a terminal, run the command `zypper lr`. If this command returns output similar to the following example, the repositories are configured as expected and no adjustments are necessary. (Version numbers might vary.)
-
-   | # | Alias                 | Name                  | Enabled | Refresh
-   | - | :-------------------- | :-------------------- | :------ | :------
-   | 1 | Cloud:Tools_15.2      | Cloud:Tools_15.2      | Yes     | Yes
-   | 2 | openSUSE_15.2_OSS     | openSUSE_15.2_OSS     | Yes     | Yes
-   | 3 | openSUSE_15.2_Updates | openSUSE_15.2_Updates | Yes     | Yes
-
-    If the command returns "No repositories defined," use the following commands to add these repos:
-
-    ```bash
-    sudo zypper ar -f http://download.opensuse.org/repositories/Cloud:Tools/openSUSE_15.2 Cloud:Tools_15.2
-    sudo zypper ar -f https://download.opensuse.org/distribution/15.2/repo/oss openSUSE_15.2_OSS
-    sudo zypper ar -f http://download.opensuse.org/update/15.2 openSUSE_15.2_Updates
-    ```
-
-    You can then verify that the repositories have been added by running the command `zypper lr` again. If one of the relevant update repositories isn't enabled, enable it by using the following command:
-
-    ```bash
-    sudo zypper mr -e [NUMBER OF REPOSITORY]
-    ```
-
-4. Update the kernel to the latest available version:
+1. Select **Connect** to open the window for the virtual machine.
+1. In a terminal, run the command `zypper lr`. If this command returns output similar to the following example, the repositories are configured as expected and no adjustments are necessary. (Version numbers might vary.)
+
+   | # | Alias                                                                                      | Name          | Enabled | GPG Check | Refresh
+   | - | :------------------------------------------------------------------------------------------| :-------------| :-------| :---------| :------
+   | 1 | Cloud:Tools_15.4                                                                           | Cloud:Tools-> | Yes     | (r ) Yes  | Yes
+   | 2 | openSUSE_stable_OSS                                                                        | openSUSE_st-> | Yes     | (r ) Yes  | Yes
+   | 3 | openSUSE_stable_Updates                                                                    | openSUSE_st-> | Yes     | (r ) Yes  | Yes 
+   
+   If the the message "___No repositories defined___" appears from the `zypper lr`  the repositories must be added manually.
+   
+   Below are examples of commands for adding these repositories (versions and links may vary):
+   
+   ```bash
+   sudo zypper ar -f https://download.opensuse.org/update/openSUSE-stable openSUSE_stable_Updates
+   sudo zypper ar -f https://download.opensuse.org/repositories/Cloud:/Tools/15.4 Cloud:Tools_15.4
+   sudo zypper ar -f https://download.opensuse.org/distribution/openSUSE-stable/repo/oss openSUSE_stable_OSS
+   ```
+   
+   You can then verify that the repositories have been added by running the command `zypper lr` again. If one of the relevant update repositories isn't enabled, enable it by using the following command:
+   
+   ```bash
+   sudo zypper mr -e [NUMBER OF REPOSITORY]
+   ```
+
+1. Update the kernel to the latest available version:
 
     ```bash
     sudo zypper up kernel-default
@@ -259,16 +261,16 @@ As an alternative to building your own VHD, SUSE also publishes BYOS (bring your
     sudo zypper update
     ```
 
-5. Install the Azure Linux Agent:
+1. Install the Azure Linux Agent:
 
     ```bash
     sudo zypper install WALinuxAgent
     ```
 
-6. Modify the kernel boot line in your GRUB configuration to include other kernel parameters for Azure. To do this, open */boot/grub/menu.lst* in a text editor and ensure that the default kernel includes the following parameters:
+1. Modify the kernel boot line in your GRUB configuration to include other kernel parameters for Azure. To do this, open */boot/grub/menu.lst* in a text editor and ensure that the default kernel includes the following parameters:
 
     ```config-grub
-     console=ttyS0 earlyprintk=ttyS0
+    console=ttyS0 earlyprintk=ttyS0
     ```
 
    This option ensures that all console messages are sent to the first serial port, which can assist Azure support with debugging issues. In addition, remove the following parameters from the kernel boot line if they exist:
@@ -277,21 +279,21 @@ As an alternative to building your own VHD, SUSE also publishes BYOS (bring your
      libata.atapi_enabled=0 reserve=0x1f0,0x8
     ```
 
-7. We recommend that you edit the */etc/sysconfig/network/dhcp* file and change the `DHCLIENT_SET_HOSTNAME` parameter to the following setting:
+1. We recommend that you edit the */etc/sysconfig/network/dhcp* file and change the `DHCLIENT_SET_HOSTNAME` parameter to the following setting:
 
     ```config
      DHCLIENT_SET_HOSTNAME="no"
     ```
 
-8. In the */etc/sudoers* file, comment out or remove the following lines if they exist. This is an important step.
+1. In the */etc/sudoers* file, comment out or remove the following lines if they exist. This is an important step.
 
     ```output
     Defaults targetpw   # ask for the password of the target user i.e. root
     ALL    ALL=(ALL) ALL   # WARNING! Only use this together with 'Defaults targetpw'!
     ```
 
-9. Ensure that the SSH server is installed and configured to start at boot time.
-10. Don't create swap space on the OS disk.
+1. Ensure that the SSH server is installed and configured to start at boot time.
+1. Don't create swap space on the OS disk.
 
     The Azure Linux Agent can automatically configure swap space by using the local resource disk that's attached to the VM after provisioning on Azure. The local resource disk is a *temporary* disk and will be emptied when the VM is deprovisioned.
 
@@ -305,26 +307,26 @@ As an alternative to building your own VHD, SUSE also publishes BYOS (bring your
     ResourceDisk.SwapSizeMB=2048    ## NOTE: set the size to whatever you need it to be.
     ```
 
-11. Ensure that the Azure Linux Agent runs at startup:
+1. Ensure that the Azure Linux Agent runs at startup:
 
     ```bash
     sudo systemctl enable waagent.service
     ```
 
-12. Run the following commands to deprovision the virtual machine and prepare it for provisioning on Azure.
+1. Run the following commands to deprovision the virtual machine and prepare it for provisioning on Azure.
 
     If you're migrating a specific virtual machine and don't want to create a generalized image, skip the deprovisioning step.
 
     ```bash
-        sudo rm -f ~/.bash_history # Remove current user history
-        sudo rm -rf /var/lib/waagent/
-        sudo rm -f /var/log/waagent.log
-        sudo waagent -force -deprovision+user
-        sudo rm -f ~/.bash_history # Remove root user history
-        sudo export HISTSIZE=0
+    sudo rm -f ~/.bash_history # Remove current user history
+    sudo rm -rf /var/lib/waagent/
+    sudo rm -f /var/log/waagent.log
+    sudo waagent -force -deprovision+user
+    sudo rm -f ~/.bash_history # Remove root user history
+    sudo export HISTSIZE=0
     ```
 
-13. Select **Action** > **Shut Down** in Hyper-V Manager.
+1. Select **Action** > **Shut Down** in Hyper-V Manager.
 
 ## Next steps
 

articles/vpn-gateway/tutorial-site-to-site-portal.md

@@ -95,7 +95,10 @@ To see more information about the public IP address object, select the name/IP a
 
 ## <a name="LocalNetworkGateway"></a>Create a local network gateway
 
-The local network gateway is a specific object that represents your on-premises location (the site) for routing purposes. You give the site a name by which Azure can refer to it, and then specify the IP address of the on-premises VPN device to which you create a connection. You also specify the IP address prefixes that are routed through the VPN gateway to the VPN device. The address prefixes you specify are the prefixes located on your on-premises network. If your on-premises network changes or you need to change the public IP address for the VPN device, you can easily update the values later.
+The local network gateway is a specific object that represents your on-premises location (the site) for routing purposes. You give the site a name by which Azure can refer to it, and then specify the IP address of the on-premises VPN device to which you create a connection. You also specify the IP address prefixes that are routed through the VPN gateway to the VPN device. The address prefixes you specify are the prefixes located on your on-premises network. If your on-premises network changes or you need to change the public IP address for the VPN device, you can easily update the values later. 
+
+> [!Note]
+> The local network gateway is deployed in Azure only and not on your on-premises.
 
 Create a local network gateway by using the following values: