Merge pull request #273869 from MicrosoftDocs/main

4/30/2024 AM Publish

Author: Taojunshen

.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/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/azure-monitor/agents/azure-monitor-agent-windows-client.md

@@ -291,15 +291,17 @@ DELETE https://management.azure.com/providers/Microsoft.Insights/monitoredObject
 ```PowerShell
 $TenantID = "xxxxxxxxx-xxxx-xxx"  #Your Tenant ID
 $SubscriptionID = "xxxxxx-xxxx-xxxxx" #Your Subscription ID
-$ResourceGroup = "rg-yourResourseGroup" #Your resroucegroup
+$ResourceGroup = "rg-yourResourceGroup" #Your resourcegroup
 
-Connect-AzAccount -Tenant $TenantID
+#If cmdlet below produces an error stating 'Interactive authentication is not supported in this session, please run cmdlet 'Connect-AzAccount -UseDeviceAuthentication
+#uncomment next to -UseDeviceAuthentication below
+Connect-AzAccount -Tenant $TenantID #-UseDeviceAuthentication
 
 #Select the subscription
 Select-AzSubscription -SubscriptionId $SubscriptionID
 
 #Grant Access to User at root scope "/"
-$user = Get-AzADUser -UserPrincipalName (Get-AzContext).Account
+$user = Get-AzADUser -SignedIn
 
 New-AzRoleAssignment -Scope '/' -RoleDefinitionName 'Owner' -ObjectId $user.Id
 
@@ -336,7 +338,7 @@ Invoke-RestMethod -Uri $requestURL -Headers $AuthenticationHeader -Method PUT -B
 #2. Create a monitored object
 
 # "location" property value under the "body" section should be the Azure region where the MO object would be stored. It should be the "same region" where you created the Data Collection Rule. This is the location of the region from where agent communications would happen.
-$Location = "eastus" #Use your own loacation
+$Location = "eastus" #Use your own location
 $requestURL = "https://management.azure.com/providers/Microsoft.Insights/monitoredObjects/$TenantID`?api-version=2021-09-01-preview"
 $body = @"
 {
@@ -368,8 +370,9 @@ $body = @"
 
 Invoke-RestMethod -Uri $requestURL -Headers $AuthenticationHeader -Method PUT -Body $body
 
-#(Optional example). Associate another DCR to monitored object
+#(Optional example). Associate another DCR to monitored object. Remove comments around text below to use.
 #See reference documentation https://learn.microsoft.com/en-us/rest/api/monitor/data-collection-rule-associations/create?tabs=HTTP
+<#
 $associationName = "assoc02" #You must change the association name to a unique name, if you want to associate multiple DCR to monitored object
 $DCRName = "dcr-PAW-WindowsClientOS" #Your Data collection rule name
 
@@ -388,7 +391,7 @@ Invoke-RestMethod -Uri $requestURL -Headers $AuthenticationHeader -Method PUT -B
 #4. (Optional) Get all the associatation.
 $requestURL = "https://management.azure.com$RespondId/providers/microsoft.insights/datacollectionruleassociations?api-version=2021-09-01-preview"
 (Invoke-RestMethod -Uri $requestURL -Headers $AuthenticationHeader -Method get).value
-
+#>
 
 ```
 ## Verify successful setup