Merge pull request #250503 from JasonWHowell/fixes1

Bulk fix build suggestions

Author: v-dirichards

articles/azure-monitor/autoscale/autoscale-multiprofile.md

@@ -58,7 +58,7 @@ When creating multiple profiles using templates, the CLI, and PowerShell, follow
 
 ## [ARM templates](#tab/templates)
 
-See the autoscale section of the [ARM template resource definition](https://learn.microsoft.com/azure/templates/microsoft.insights/autoscalesettings) for a full template reference.
+See the autoscale section of the [ARM template resource definition](/azure/templates/microsoft.insights/autoscalesettings) for a full template reference.
 
 There is no specification in the template for end time. A profile will remain active until the next profile's start time.  
 
@@ -68,7 +68,7 @@ There is no specification in the template for end time. A profile will remain ac
 The example below shows how to create two recurring profiles. One profile for weekends from 00:01 on Saturday morning and a second Weekday profile starting on Mondays at 04:00. That means that the weekend profile will start on Saturday morning at one minute passed midnight and end on Monday morning at 04:00. The Weekday profile will start at 4am on Monday and end just after midnight on Saturday morning.
 
 Use the following command to deploy the template:
-` az deployment group create --name VMSS1-Autoscale-607 --resource-group rg-vmss1 --template-file VMSS1-autoscale.json`
+`az deployment group create --name VMSS1-Autoscale-607 --resource-group rg-vmss1 --template-file VMSS1-autoscale.json`
 where *VMSS1-autoscale.json* is the the file containing the JSON object below.
 
 ``` JSON
@@ -192,7 +192,7 @@ where *VMSS1-autoscale.json* is the the file containing the JSON object below.
 
 The CLI can be used to create multiple profiles in your autoscale settings.
 
-See the [Autoscale CLI reference](https://learn.microsoft.com/cli/azure/monitor/autoscale?view=azure-cli-latest) for the full set of autoscale CLI commands.
+See the [Autoscale CLI reference](/cli/azure/monitor/autoscale) for the full set of autoscale CLI commands.
 
 The following steps show how to create a recurring autoscale profile using the CLI.
 
@@ -267,7 +267,7 @@ az monitor autoscale rule create -g rg-vmss1--autoscale-name VMSS1-Autoscale-607
 
 PowerShell can be used to create multiple profiles in your autoscale settings.
 
-See the [PowerShell Az.Monitor Reference ](https://learn.microsoft.com/powershell/module/az.monitor/#monitor) for the full set of autoscale PowerShell commands.
+See the [PowerShell Az.Monitor Reference](/powershell/module/az.monitor/#monitor) for the full set of autoscale PowerShell commands.
 
 The following steps show how to create an autoscale profile using PowerShell.
 
@@ -415,10 +415,10 @@ $DefaultProfileThursdayProfile = New-AzAutoscaleProfile -DefaultCapacity "1" -Ma
 
 ## Next steps
 
-* [Autoscale CLI reference](https://learn.microsoft.com/cli/azure/monitor/autoscale?view=azure-cli-latest)
-* [ARM template resource definition](https://learn.microsoft.com/azure/templates/microsoft.insights/autoscalesettings)
-* [PowerShell Az PowerShell module.Monitor Reference](https://learn.microsoft.com/powershell/module/az.monitor/#monitor)
-* [REST API reference. Autoscale Settings](https://learn.microsoft.com/rest/api/monitor/autoscale-settings).
-* [Tutorial: Automatically scale a Virtual Machine Scale Set with an Azure template](https://learn.microsoft.com/azure/virtual-machine-scale-sets/tutorial-autoscale-template)
-* [Tutorial: Automatically scale a Virtual Machine Scale Set with the Azure CLI](https://learn.microsoft.com/azure/virtual-machine-scale-sets/tutorial-autoscale-cli)
-* [Tutorial: Automatically scale a Virtual Machine Scale Set with an Azure template](https://learn.microsoft.com/azure/virtual-machine-scale-sets/tutorial-autoscale-powershell)
+* [Autoscale CLI reference](/cli/azure/monitor/autoscale)
+* [ARM template resource definition](/azure/templates/microsoft.insights/autoscalesettings)
+* [PowerShell Az PowerShell module.Monitor Reference](/powershell/module/az.monitor/#monitor)
+* [REST API reference. Autoscale Settings](/rest/api/monitor/autoscale-settings).
+* [Tutorial: Automatically scale a Virtual Machine Scale Set with an Azure template](/azure/virtual-machine-scale-sets/tutorial-autoscale-template)
+* [Tutorial: Automatically scale a Virtual Machine Scale Set with the Azure CLI](/azure/virtual-machine-scale-sets/tutorial-autoscale-cli)
+* [Tutorial: Automatically scale a Virtual Machine Scale Set with an Azure template](/azure/virtual-machine-scale-sets/tutorial-autoscale-powershell)

articles/azure-monitor/autoscale/autoscale-using-powershell.md

@@ -74,7 +74,7 @@ To create autoscale setting using PowerShell, follow the sequence below:
 ### Create rules
 
 Create scale in and scale out rules then associated them with a profile.
-Rules are created using the [`New-AzAutoscaleScaleRuleObject`](https://learn.microsoft.com/powershell/module/az.monitor/new-azautoscalescaleruleobject).
+Rules are created using the [`New-AzAutoscaleScaleRuleObject`](/powershell/module/az.monitor/new-azautoscalescaleruleobject).
 
 The following PowerShell script creates two rules.
 
@@ -134,7 +134,7 @@ The table below describes the parameters used in the `New-AzAutoscaleScaleRuleOb
 
 ### Create a default autoscale profile and associate the rules
 
-After defining the scale rules, create a profile. The profile specifies the default, upper, and lower instance count limits, and the times that the associated rules can be applied. Use the [`New-AzAutoscaleProfileObject`](https://learn.microsoft.com/powershell/module/az.monitor/new-azautoscaleprofileobject) cmdlet to create a new autoscale profile. As this is a default profile, it doesn't have any schedule parameters. The default profile is active at times that no other profiles are active
+After defining the scale rules, create a profile. The profile specifies the default, upper, and lower instance count limits, and the times that the associated rules can be applied. Use the [`New-AzAutoscaleProfileObject`](/powershell/module/az.monitor/new-azautoscaleprofileobject) cmdlet to create a new autoscale profile. As this is a default profile, it doesn't have any schedule parameters. The default profile is active at times that no other profiles are active
 
 ```azurepowershell
 $defaultProfile=New-AzAutoscaleProfileObject `
@@ -163,7 +163,7 @@ The table below describes the parameters used in the `New-AzAutoscaleProfileObje
 
 ### Apply the autoscale settings
 
-After fining the rules and profile, apply the autoscale settings using  [`New-AzAutoscaleSetting`](https://learn.microsoft.com/powershell/module/az.monitor/new-azautoscalesetting). To update existing autoscale setting use [`Update-AzAutoscaleSetting`](https://learn.microsoft.com/powershell/module/az.monitor/add-azautoscalesetting)
+After fining the rules and profile, apply the autoscale settings using  [`New-AzAutoscaleSetting`](/powershell/module/az.monitor/new-azautoscalesetting). To update existing autoscale setting use [`Update-AzAutoscaleSetting`](/powershell/module/az.monitor/add-azautoscalesetting)
 
 ```azurepowershell
 New-AzAutoscaleSetting `
@@ -179,15 +179,15 @@ New-AzAutoscaleSetting `
 ### Add notifications to your autoscale settings  
 
 Add notifications to your sale setting to trigger a webhook or send email notifications when a scale event occurs.
-For more information on webhook notifications, see [`New-AzAutoscaleWebhookNotificationObject`](https://learn.microsoft.com/powershell/module/az.monitor/new-azautoscalewebhooknotificationobject)
+For more information on webhook notifications, see [`New-AzAutoscaleWebhookNotificationObject`](/powershell/module/az.monitor/new-azautoscalewebhooknotificationobject)
 
 Set a webhook using the following cmdlet;
 ```azurepowershell
 
   $webhook1=New-AzAutoscaleWebhookNotificationObject -Property @{} -ServiceUri "http://contoso.com/webhook1"
 ```
 
-Configure the notification using the webhook and set up email notification using the [`New-AzAutoscaleNotificationObject`](https://learn.microsoft.com/powershell/module/az.monitor/new-azautoscalenotificationobject) cmdlet:
+Configure the notification using the webhook and set up email notification using the [`New-AzAutoscaleNotificationObject`](/powershell/module/az.monitor/new-azautoscalenotificationobject) cmdlet:
 
 ```azurepowershell
 
@@ -302,7 +302,7 @@ For more information on scheduled profiles, see [Autoscale with multiple profile
 
 ## Other autoscale commands
 
-For a complete list of PowerShell cmdlets for autoscale, see the [PowerShell Module Browser](https://learn.microsoft.com/powershell/module/?term=azautoscale)
+For a complete list of PowerShell cmdlets for autoscale, see the [PowerShell Module Browser](/powershell/module/?term=azautoscale)
 
 ## Clean up resources
 

articles/azure-monitor/autoscale/autoscale-webhook-email.md

@@ -63,7 +63,7 @@ For example, the following command adds an email notification and a webhook noti
 > You can add mote than one email or webhook notification by using the `--add-action` parameter multiple times. While multiple webhook notifications are supported and can be seen in the JSON, the portal only shows the first webhook.
 
 
-For more information, see [az monitor autoscale](https://learn.microsoft.com/cli/azure/monitor/autoscale?view=azure-cli-latest).
+For more information, see [az monitor autoscale](/cli/azure/monitor/autoscale).
 
 
 
@@ -105,7 +105,7 @@ New-AzAutoscaleSetting -Name autoscalesetting2 `
 
 ### Use Resource Manager templates to configure notifications.
 
-When you use the Resource Manager templates or REST API, include the `notifications` element in your [autoscale settings](https://learn.microsoft.com/azure/templates/microsoft.insights/autoscalesettings?pivots=deployment-language-arm-template#resource-format-1), for example:
+When you use the Resource Manager templates or REST API, include the `notifications` element in your [autoscale settings](/azure/templates/microsoft.insights/autoscalesettings?pivots=deployment-language-arm-template#resource-format-1), for example:
 
 ```JSON
 "notifications": [

articles/azure-monitor/containers/container-insights-syslog.md

@@ -18,8 +18,8 @@ Container Insights offers the ability to collect Syslog events from Linux nodes
 - You need to have managed identity authentication enabled on your cluster. To enable, see [migrate your AKS cluster to managed identity authentication](container-insights-enable-existing-clusters.md?tabs=azure-cli#migrate-to-managed-identity-authentication). Note: Enabling Managed Identity will create a new Data Collection Rule (DCR) named `MSCI-<WorkspaceRegion>-<ClusterName>` 
 - Minimum versions of Azure components
   - **Azure CLI**: Minimum version required for Azure CLI is [2.45.0 (link to release notes)](/cli/azure/release-notes-azure-cli#february-07-2023). See [How to update the Azure CLI](/cli/azure/update-azure-cli) for upgrade instructions. 
-  - **Azure CLI AKS-Preview Extension**: Minimum version required for AKS-Preview Azure CLI extension is [ 0.5.125 (link to release notes)](https://github.com/Azure/azure-cli-extensions/blob/main/src/aks-preview/HISTORY.rst#05125). See [How to update extensions](/cli/azure/azure-cli-extensions-overview#how-to-update-extensions) for upgrade guidance. 
-  - **Linux image version**: Minimum version for AKS node linux image is 2022.11.01. See [Upgrade Azure Kubernetes Service (AKS) node images](https://learn.microsoft.com/azure/aks/node-image-upgrade) for upgrade help. 
+  - **Azure CLI AKS-Preview Extension**: Minimum version required for AKS-Preview Azure CLI extension is [0.5.125 (link to release notes)](https://github.com/Azure/azure-cli-extensions/blob/main/src/aks-preview/HISTORY.rst#05125). See [How to update extensions](/cli/azure/azure-cli-extensions-overview#how-to-update-extensions) for upgrade guidance. 
+  - **Linux image version**: Minimum version for AKS node linux image is 2022.11.01. See [Upgrade Azure Kubernetes Service (AKS) node images](/azure/aks/node-image-upgrade) for upgrade help. 
 
 ## How to enable Syslog
 
@@ -158,8 +158,8 @@ Select the minimum log level for each facility that you want to collect.
 ## Next steps
 
 Once setup customers can start sending Syslog data to the tools of their choice
-- Send Syslog to Microsoft Sentinel: https://learn.microsoft.com/azure/sentinel/connect-syslog  
-- Export data from Log Analytics: https://learn.microsoft.com/azure/azure-monitor/logs/logs-data-export?tabs=portal 
+- [Send Syslog to Microsoft Sentinel](/azure/sentinel/connect-syslog)
+- [Export data from Log Analytics](/azure/azure-monitor/logs/logs-data-export?tabs=portal)
 
 Read more  
 - [Syslog record properties](/azure/azure-monitor/reference/tables/syslog)

articles/azure-monitor/essentials/diagnostics-settings-policies-deployifnotexists.md

@@ -48,7 +48,7 @@ The following steps show how to apply the policy to send audit logs to for key v
 ### [CLI](#tab/cli)
 To apply a policy using the CLI, use the following commands:
 
-1. Create a policy assignment using [`az policy assignment create`](https://learn.microsoft.com/cli/azure/policy/assignment?view=azure-cli-latest#az-policy-assignment-create).
+1. Create a policy assignment using [`az policy assignment create`](/cli/azure/policy/assignment#az-policy-assignment-create).
     ```azurecli
       az policy assignment create --name <policy assignment name>  --policy "6b359d8f-f88d-4052-aa7c-32015963ecc1"  --scope <scope> --params "{\"logAnalytics\": {\"value\": \"<log analytics workspace resource ID"}}" --mi-system-assigned --location <location>
     ```
@@ -69,7 +69,7 @@ Find the role in the policy definition by searching for *roleDefinitionIds*
           "deployment": {
             "properties": {...
     ```
-    Assign the required role using [`az policy assignment identity assign`](https://learn.microsoft.com/cli/azure/policy/assignment/identity?view=azure-cli-latest):
+    Assign the required role using [`az policy assignment identity assign`](/cli/azure/policy/assignment/identity):
     ```azurecli
     az policy assignment identity assign --system-assigned --resource-group <resource group name> --role <role name or ID> --identity-scope </scope> --name <policy assignment name>
     ```
@@ -78,13 +78,13 @@ Find the role in the policy definition by searching for *roleDefinitionIds*
     az policy assignment identity assign --system-assigned --resource-group rg-001  --role 92aaf0da-9dab-42b6-94a3-d43ce8d16293 --identity-scope /subscriptions/12345678-aaaa-bbbb-cccc-1234567890ab/resourceGroups/rg001 --name policy-assignment-1
     ```
 
-1. Trigger a scan to find existing resources using [`az policy state trigger-scan`](https://learn.microsoft.com/cli/azure/policy/state?view=azure-cli-latest#az-policy-state-trigger-scan).
+1. Trigger a scan to find existing resources using [`az policy state trigger-scan`](/cli/azure/policy/state#az-policy-state-trigger-scan).
 
     ```azurecli
     az policy state trigger-scan --resource-group rg-001
     ```
 
-1. Create a remediation task to apply the policy to existing resources using [`az policy remediation create`](https://learn.microsoft.com/cli/azure/policy/remediation?view=azure-cli-latest#az-policy-remediation-create).
+1. Create a remediation task to apply the policy to existing resources using [`az policy remediation create`](/cli/azure/policy/remediation#az-policy-remediation-create).
 
     ```azurecli
     az policy remediation create -g <resource group name> --policy-assignment <policy assignment name> --name <remediation name> 
@@ -95,7 +95,7 @@ Find the role in the policy definition by searching for *roleDefinitionIds*
     az policy remediation create -g rg-001 -n remediation-001 --policy-assignment  policy-assignment-1
     ```
 
-For more information on policy assignment using CLI, see [Azure CLI reference - az policy assignment](https://learn.microsoft.com/cli/azure/policy/assignment?view=azure-cli-latest#az-policy-assignment-create)
+For more information on policy assignment using CLI, see [Azure CLI reference - az policy assignment](/cli/azure/policy/assignment#az-policy-assignment-create)
 
 ### [PowerShell](#tab/Powershell)
 
@@ -284,7 +284,7 @@ You can get your policy assignment details using the following command:
 
 1. Select the subscription where you want to apply the policy initiative using the `az account set` command.
 
-1. Assign the initiative using [`az policy assignment create`](https://learn.microsoft.com/cli/azure/policy/assignment?view=azure-cli-latest#az-policy-assignment-create).
+1. Assign the initiative using [`az policy assignment create`](/cli/azure/policy/assignment#az-policy-assignment-create).
 
     ```azurecli
     az policy assignment create --name <assignment name> --resource-group <resource group name> --policy-set-definition <initiative name> --params <parameters object> --mi-system-assigned --location <location>
@@ -306,7 +306,7 @@ You can get your policy assignment details using the following command:
           "deployment": {
             "properties": {...
     ```
-    Assign the required role using [`az policy assignment identity assign`](https://learn.microsoft.com/cli/azure/policy/assignment/identity?view=azure-cli-latest):
+    Assign the required role using [`az policy assignment identity assign`](/cli/azure/policy/assignment/identity):
     ```azurecli
     az policy assignment identity assign --system-assigned --resource-group <resource group name> --role <role name or ID> --identity-scope <scope> --name <policy assignment name>
     ```
@@ -322,7 +322,7 @@ You can get your policy assignment details using the following command:
     ```azurecli
     az policy set-definition show --name f5b29bc4-feca-4cc6-a58a-772dd5e290a5 |grep policyDefinitionReferenceId
     ```
-    Remediate the resources using [`az policy remediation create`](https://learn.microsoft.com/cli/azure/policy/remediation?view=azure-cli-latest#az-policy-remediation-create)
+    Remediate the resources using [`az policy remediation create`](/cli/azure/policy/remediation#az-policy-remediation-create)
 
     ```azurecli
     az policy remediation create --resource-group <resource group name> --policy-assignment <assignment name> --name <remediation task name> --definition-reference-id  "policy specific reference ID"  --resource-discovery-mode ReEvaluateCompliance