Merge branch 'main' into release-ga-api-center

Author: v-alje

.openpublishing.publish.config.json

@@ -872,6 +872,12 @@
       "branch": "master",
       "branch_mapping": {}
     },
+    {
+      "path_to_root": "blob-devguide-go",
+      "url": "https://github.com/Azure-Samples/blob-storage-devguide-go",
+      "branch": "main",
+      "branch_mapping": {}
+    },
     {
       "path_to_root": "azure-sdk-for-net",
       "url": "https://github.com/Azure/azure-sdk-for-net/",

.openpublishing.redirection.azure-monitor.json

@@ -5,6 +5,11 @@
             "redirect_url": "/azure/azure-monitor/snapshot-debugger/snapshot-debugger#release-notes-for-microsoftapplicationinsightssnapshotcollector",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/azure-monitor/agents/om-agents.md",
+            "redirect_url": "/azure/azure-monitor/vm/scom-managed-instance-overview",
+            "redirect_document_id": false
+         },
         {
             "source_path_from_root": "/articles/azure-monitor/best-practices.md",
             "redirect_url": "/azure/azure-monitor/getting-started",

articles/ai-services/speech-service/how-to-windows-voice-assistants-get-started.md

@@ -29,7 +29,7 @@ To start developing a voice assistant for Windows, you need to make sure
 Some resources necessary for a customized voice agent on Windows requires resources from Microsoft. The [UWP Voice Assistant Sample](windows-voice-assistants-faq.yml#the-uwp-voice-assistant-sample) provides sample versions of these resources for initial development and testing, so this section is unnecessary for initial development.
 
 - **Keyword model:** Voice activation requires a keyword model from Microsoft in the form of a .bin file. The .bin file provided in the UWP Voice Assistant Sample is trained on the keyword *Contoso*.
-- **Limited Access Feature Token:** Since the ConversationalAgent APIs provide access to microphone audio, they're protected under Limited Access Feature restrictions. To use a Limited Access Feature, you need to obtain a Limited Access Feature token connected to the package identity of your application from Microsoft. For more information about any Limited Access Feature or to request an unlock token, contact [Microsoft Support](https://github.com/MicrosoftDocs/azure-docs-pr).
+- **Limited Access Feature Token:** Since the ConversationalAgent APIs provide access to microphone audio, they're protected under Limited Access Feature restrictions. To use a Limited Access Feature, you need to obtain a Limited Access Feature token connected to the package identity of your application from Microsoft. For more information about any Limited Access Feature or to request an unlock token, contact [Microsoft Support](https://aka.ms/LAFAccessRequests).
 
 
 

articles/ai-services/translator/containers/transliterate-text-parameters.md

@@ -102,29 +102,13 @@ The following limitations apply:
 ]
 ```
 
-## Code samples: transliterate text
-
 > [!NOTE]
 >
 > * Each sample runs on the `localhost` that you specified with the `docker run` command.
 > * While your container is running, `localhost` points to the container itself.
 > * You don't have to use `localhost:5000`. You can use any port that is not already in use in your host environment.
 > To specify a port, use the `-p` option.
 
-### Transliterate with REST API
-
-```rest
-
-  POST https://api.cognitive.microsofttranslator.com/transliterate?api-version=3.0&language=ja&fromScript=Jpan&toScript=Latn HTTP/1.1
-  Ocp-Apim-Subscription-Key: ba6c4278a6c0412da1d8015ef9930d44
-  Content-Type:  application/json
-
-  [
-      {"Text":"こんにちは"},
-      {"Text":"さようなら"}
-  ]
-```
-
 ## Next Steps
 
 > [!div class="nextstepaction"]

articles/aks/egress-outboundtype.md

@@ -1,18 +1,18 @@
 ---
 title: Customize cluster egress with outbound types in Azure Kubernetes Service (AKS)
-description: Learn how to define a custom egress route in Azure Kubernetes Service (AKS)
+description: Learn how to define a custom egress route in Azure Kubernetes Service (AKS).
 author: asudbring
 ms.subservice: aks-networking
 ms.custom:
 ms.author: allensu
 ms.topic: how-to
-ms.date: 02/06/2024
+ms.date: 04/29/2024
 #Customer intent: As a cluster operator, I want to define my own egress paths with user-defined routes. Since I define this up front I do not want AKS provided load balancer configurations.
 ---
 
 # Customize cluster egress with outbound types in Azure Kubernetes Service (AKS)
 
-You can customize egress for an AKS cluster to fit specific scenarios. By default, AKS will provision a standard SKU load balancer to be set up and used for egress. However, the default setup may not meet the requirements of all scenarios if public IPs are disallowed or additional hops are required for egress.
+You can customize egress for an AKS cluster to fit specific scenarios. By default, AKS provisions a standard SKU load balancer to be set up and used for egress. However, the default setup may not meet the requirements of all scenarios if public IPs are disallowed or extra hops are required for egress.
 
 This article covers the various types of outbound connectivity that are available in AKS clusters.
 
@@ -21,7 +21,7 @@ This article covers the various types of outbound connectivity that are availabl
 
 ## Limitations
 
-* Setting `outboundType` requires AKS clusters with a `vm-set-type` of `VirtualMachineScaleSets` and `load-balancer-sku` of `Standard`.
+- Setting `outboundType` requires AKS clusters with a `vm-set-type` of `VirtualMachineScaleSets` and `load-balancer-sku` of `Standard`.
 
 ## Outbound types in AKS
 
@@ -36,9 +36,9 @@ The load balancer is used for egress through an AKS-assigned public IP. An outbo
 
 If `loadBalancer` is set, AKS automatically completes the following configuration:
 
-* A public IP address is provisioned for cluster egress.
-* The public IP address is assigned to the load balancer resource.
-* Backend pools for the load balancer are set up for agent nodes in the cluster.
+- A public IP address is provisioned for cluster egress.
+- The public IP address is assigned to the load balancer resource.
+- Backend pools for the load balancer are set up for agent nodes in the cluster.
 
 ![Diagram shows ingress I P and egress I P, where the ingress I P directs traffic to a load balancer, which directs traffic to and from an internal cluster and other traffic to the egress I P, which directs traffic to the Internet, M C R, Azure required services, and the A K S Control Plane.](media/egress-outboundtype/outboundtype-lb.png)
 
@@ -48,8 +48,8 @@ For more information, see [using a standard load balancer in AKS](load-balancer-
 
 If `managedNatGateway` or `userAssignedNatGateway` are selected for `outboundType`, AKS relies on [Azure Networking NAT gateway](../virtual-network/nat-gateway/manage-nat-gateway.md) for cluster egress.
 
-* Select `managedNatGateway` when using managed virtual networks. AKS will provision a NAT gateway and attach it to the cluster subnet.
-* Select `userAssignedNatGateway` when using bring-your-own virtual networking. This option requires that you have provisioned a NAT gateway before cluster creation.
+- Select `managedNatGateway` when using managed virtual networks. AKS provisions a NAT gateway and attach it to the cluster subnet.
+- Select `userAssignedNatGateway` when using bring-your-own virtual networking. This option requires that you have provisioned a NAT gateway before cluster creation.
 
 For more information, see [using NAT gateway with AKS](nat-gateway.md).
 
@@ -72,10 +72,10 @@ The following tables show the supported migration paths between outbound types f
 
 ### Supported Migration Paths for Managed VNet
 
-| Managed VNet           |loadBalancer   | managedNATGateway | userAssignedNATGateway | userDefinedRouting |
+| Managed VNet           | loadBalancer  | managedNATGateway | userAssignedNATGateway | userDefinedRouting |
 |------------------------|---------------|-------------------|------------------------|--------------------|
-| loadBalancer           | N/A           | Supported         | Not Supported          | Supported          |
-| managedNATGateway      | Supported     | N/A               | Not Supported          | Supported          |
+| loadBalancer           | N/A           | Supported         | Not Supported          | Not Supported      |
+| managedNATGateway      | Supported     | N/A               | Not Supported          | Not Supported      |
 | userAssignedNATGateway | Not Supported | Not Supported     | N/A                    | Not Supported      |
 | userDefinedRouting     | Supported     | Supported         | Not Supported          | N/A                |
 
@@ -131,24 +131,21 @@ az aks update -g <resourceGroup> -n <clusterName> --outbound-type userDefinedRou
 
 ### Update cluster from loadbalancer to userAssignedNATGateway in BYO vnet scenario
 
-- Associate nat gateway with subnet where the workload is associated with. Please refer to [Create a managed or user-assigned NAT gateway](nat-gateway.md)
+- Associate nat gateway with subnet where the workload is associated with. Refer to [Create a managed or user-assigned NAT gateway](nat-gateway.md)
 
 ```azurecli-interactive
 az aks update -g <resourceGroup> -n <clusterName> --outbound-type userAssignedNATGateway
 ```
 
 ## Next steps
 
-* [Configure standard load balancing in an AKS cluster](load-balancer-standard.md)
-* [Configure NAT gateway in an AKS cluster](nat-gateway.md)
-* [Configure user-defined routing in an AKS cluster](egress-udr.md)
-* [NAT gateway documentation](./nat-gateway.md)
-* [Azure networking UDR overview](../virtual-network/virtual-networks-udr-overview.md)
-* [Manage route tables](../virtual-network/manage-route-table.yml)
+- [Configure standard load balancing in an AKS cluster](load-balancer-standard.md)
+- [Configure NAT gateway in an AKS cluster](nat-gateway.md)
+- [Configure user-defined routing in an AKS cluster](egress-udr.md)
+- [NAT gateway documentation](./nat-gateway.md)
+- [Azure networking UDR overview](../virtual-network/virtual-networks-udr-overview.md)
+- [Manage route tables](../virtual-network/manage-route-table.yml)
 
 <!-- LINKS - internal -->
-[az-feature-register]: /cli/azure/feature#az_feature_register
-[az-feature-show]: /cli/azure/feature#az_feature_show
-[az-provider-register]: /cli/azure/provider#az_provider_register
 [az-aks-update]: /cli/azure/aks#az_aks_update
 

articles/aks/load-balancer-standard.md

@@ -139,10 +139,6 @@ Two different pool membership types are available:
 * The AKS cluster must be version 1.23 or newer.
 * The AKS cluster must be using standard load balancers and virtual machine scale sets.
 
-#### Limitations
-
-* Clusters using IP based backend pools are limited to 2500 nodes.
-
 #### Create a new AKS cluster with IP-based inbound pool membership
 
 ```azurecli-interactive

articles/aks/media/supported-kubernetes-versions/kubernetes-versions-gantt.png

@@ -3,7 +3,7 @@ title: Use instance-level public IPs in Azure Kubernetes Service (AKS)
 description: Learn how to manage instance-level public IPs Azure Kubernetes Service (AKS)
 ms.topic: article
 ms.custom: devx-track-azurecli
-ms.date: 01/23/2024
+ms.date: 04/29/2024
 ms.author: pahealy
 author: phealy
 ---
@@ -71,50 +71,13 @@ You can locate the public IPs for your nodes in various ways:
 az vmss list-instance-public-ips -g MC_MyResourceGroup2_MyManagedCluster_eastus -n YourVirtualMachineScaleSetName
 ```
 
-## Use public IP tags on node public IPs (PREVIEW)
+## Use public IP tags on node public IPs
 
 Public IP tags can be utilized on node public IPs to utilize the [Azure Routing Preference](../virtual-network/ip-services/routing-preference-overview.md) feature.
 
-[!INCLUDE [preview features callout](includes/preview/preview-callout.md)]
-
 ### Requirements
 
 * AKS version 1.24 or greater is required.
-* Version 0.5.115 of the aks-preview extension is required.
-
-### Install the aks-preview Azure CLI extension
-
-To install the aks-preview extension, run the following command:
-
-```azurecli
-az extension add --name aks-preview
-```
-
-Run the following command to update to the latest version of the extension released:
-
-```azurecli
-az extension update --name aks-preview
-```
-
-### Register the 'NodePublicIPTagsPreview' feature flag
-
-Register the `NodePublicIPTagsPreview` feature flag by using the [`az feature register`][az-feature-register] command, as shown in the following example:
-
-```azurecli-interactive
-az feature register --namespace "Microsoft.ContainerService" --name "NodePublicIPTagsPreview"
-```
-
-It takes a few minutes for the status to show *Registered*. Verify the registration status by using the [`az feature show`][az-feature-show] command:
-
-```azurecli-interactive
-az feature show --namespace "Microsoft.ContainerService" --name "NodePublicIPTagsPreview"
-```
-
-When the status reflects *Registered*, refresh the registration of the *Microsoft.ContainerService* resource provider by using the [`az provider register`][az-provider-register] command:
-
-```azurecli-interactive
-az provider register --namespace Microsoft.ContainerService
-```
 
 ### Create a new cluster using routing preference internet
 
@@ -152,7 +115,6 @@ Examples:
 ### Requirements
 
 * AKS version 1.24 or greater is required.
-* Version 0.5.110 of the aks-preview extension is required.
 
 ### Create a new cluster with allowed ports and application security groups
 

articles/aks/use-node-public-ips.md

@@ -4,7 +4,7 @@ description: Significant updates to Azure Automation updated each month.
 services: automation
 ms.subservice:
 ms.topic: overview
-ms.date: 01/26/2024
+ms.date: 04/30/2024
 ms.custom: references_regions
 ---
 
@@ -21,6 +21,12 @@ Azure Automation receives improvements on an ongoing basis. To stay up to date w
 
 This page is updated monthly, so revisit it regularly. If you're looking for items older than six months, you can find them in [Archive for What's new in Azure Automation](whats-new-archive.md).
 
+## April 2024
+ 
+### Changes in Process Automation subscription and service limits and quotas
+ 
+Find the changes in Azure Automation limits and quotas [here](../azure-resource-manager/management/azure-subscription-service-limits.md#automation-limits). These changes are aimed towards improving the reliability and performance of the service by ensuring fair access to cloud resources for all users. We recommend to use other regions or other subscriptions within the same Azure geography to create more Automation accounts.
+
 ## January 2024
 
 ### Public Preview: Azure Automation Runtime environment & support for Azure CLI commands in runbooks

articles/automation/whats-new.md

@@ -121,7 +121,7 @@ The most recent version of the Flux v2 extension and the two previous versions (
 > [!NOTE]
 > When a new version of the `microsoft.flux` extension is released, it may take several days for the new version to become available in all regions.
 
-### 1.8.4 (March 2024)
+### 1.8.4 (April 2024)
 
 Flux version: [Release v2.1.2](https://github.com/fluxcd/flux2/releases/tag/v2.1.2)