more fixes

Author: mohitp930

articles/azure-government/azure-secure-isolation-guidance.md

@@ -862,7 +862,7 @@ Compared to traditional on-premises hosted systems, Azure provides a greatly **r
 PaaS VMs offer more advanced **protection against persistent malware** infections than traditional physical server solutions, which if compromised by an attacker can be difficult to clean, even after the vulnerability is corrected. The attacker may have left behind modifications to the system that allow re-entry, and it's a challenge to find all such changes. In the extreme case, the system must be reimaged from scratch with all software reinstalled, sometimes resulting in the loss of application data. With PaaS VMs, reimaging is a routine part of operations, and it can help clean out intrusions that haven't even been detected. This approach makes it more difficult for a compromise to persist.
 
 #### Side channel attacks
-Microsoft has been at the forefront of mitigating **speculative execution side channel attacks** that exploit hardware vulnerabilities in modern processors that use hyper-threading. In many ways, these issues are similar to the Spectre (variant 2) side channel attack, which was disclosed in 2018. Multiple new speculative execution side channel issues were disclosed by both Intel and AMD in 2022. To address these vulnerabilities, Microsoft has developed and optimized Hyper-V **[HyperClear](/virtualization/community/team-blog/2018/20180814-hyper-v-hyperclear-mitigation-for-l1-terminal-fault)**, a comprehensive and high performing side channel vulnerability mitigation architecture. HyperClear relies on three main components to ensure strong inter-VM isolation:
+Microsoft has been at the forefront of mitigating **speculative execution side channel attacks** that exploit hardware vulnerabilities in modern processors that use hyper-threading. In many ways, these issues are similar to the Spectre (variant 2) side channel attack, which was disclosed in 2018. Multiple new speculative execution side channel issues were disclosed by both Intel and AMD in 2022. To address these vulnerabilities, Microsoft has developed and optimized Hyper-V **[HyperClear](https://techcommunity.microsoft.com/t5/virtualization/hyper-v-hyperclear-mitigation-for-l1-terminal-fault/ba-p/382429)**, a comprehensive and high performing side channel vulnerability mitigation architecture. HyperClear relies on three main components to ensure strong inter-VM isolation:
 
 - **Core scheduler** to avoid sharing of a CPU core’s private buffers and other resources.
 - **Virtual-processor address space isolation** to avoid speculative access to another virtual machine’s memory or another virtual CPU core’s private state.

articles/defender-for-iot/device-builders/how-to-deploy-agent.md

@@ -10,7 +10,7 @@ ms.date: 03/28/2022
 Defender for IoT provides reference architectures for security agents that monitor and collect data from IoT devices.
 To learn more, see [Security agent reference architecture](security-agent-architecture.md).
 
-Agents are developed as open-source projects, and are available in two flavors: <br> [C](https://aka.ms/iot-security-github-c), and [C#](https://aka.ms/iot-security-github-cs).
+Agents are developed as open-source projects, and are available in two flavors: <br> C, and [C#](https://aka.ms/iot-security-github-cs).
 
 In this article, you learn how to:
 - Compare security agent flavors
@@ -25,7 +25,7 @@ The C-based security agent has a lower memory footprint, and is the ideal choice
 
 |     | C-based security agent | C#-based security agent |
 | --- | ----------- | --------- |
-| **Open-source** | Available under [MIT license](https://en.wikipedia.org/wiki/MIT_License) in [GitHub](https://aka.ms/iot-security-github-c) | Available under [MIT license](https://en.wikipedia.org/wiki/MIT_License) in [GitHub](https://aka.ms/iot-security-github-cs) |
+| **Open-source** | Available under [MIT license](https://en.wikipedia.org/wiki/MIT_License) in GitHub | Available under [MIT license](https://en.wikipedia.org/wiki/MIT_License) in [GitHub](https://aka.ms/iot-security-github-cs) |
 | **Development language**    | C | C# |
 | **Supported Windows platforms?** | No | Yes |
 | **Windows prerequisites** | --- | [WMI](/windows/desktop/wmisdk/) |

articles/defender-for-iot/device-builders/how-to-deploy-linux-c.md

@@ -27,7 +27,7 @@ For other platforms and agent flavors, see [Choose the right security agent](how
 
 To install and deploy the security agent, use the following workflow:
 
-1. Download the most recent version to your machine from [GitHub](https://aka.ms/iot-security-github-c).
+1. Download the most recent version to your machine from GitHub.
 
 1. Extract the contents of the package and navigate to the _/src/installation_ folder.
 

articles/iot-central/core/howto-transform-data.md

@@ -504,7 +504,7 @@ This scenario uses the same Azure Functions deployment as the IoT Central device
 | Scope ID | Use the **ID scope** you made a note of previously. |
 | IoT Central SAS Key | Use the shared access signature primary key for the **SaS-IoT-Devices** enrollment group. You made a note of this value previously. |
 
-[![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fiotc-device-bridge%2Fmaster%2Fazuredeploy.json).
+[![Deploy to Azure]](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fiotc-device-bridge%2Fmaster%2Fazuredeploy.json).
 
 Select **Review + Create**, and then **Create**. It takes a couple of minutes to create the Azure function and related resources in the **egress-scenario** resource group.
 

articles/iot-operations/connect-to-cloud/howto-configure-destination-fabric.md

@@ -30,7 +30,7 @@ To configure and use a Microsoft Fabric destination pipeline stage, you need:
 
 Before you can write to Microsoft Fabric from a data pipeline, you need to grant access to the lakehouse from the pipeline. You can use either a service principal or a managed identity to authenticate the pipeline. The advantage of using a managed identity is that you don't need to manage the lifecycle of the service principal. The managed identity is automatically managed by Azure and is tied to the lifecycle of the resource it's assigned to.
 
-Before you configure either service principal or managed identity access to a lakehouse, enable [service principal authentication](/fabric/onelake/onelake-security#authentication).
+Before you configure either service principal or managed identity access to a lakehouse, enable [service principal authentication](/fabric/onelake/security/get-started-security#authentication).
 
 # [Service principal](#tab/serviceprincipal)
 

articles/sentinel/data-connectors/citrix-waf-web-app-firewall.md

@@ -141,4 +141,4 @@ Make sure to configure the machine's security according to your organization's s
 
 ## Next steps
 
-For more information, go to the [related solution](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/citrix.citrix_waf_mss?tab=Overview) in the Azure Marketplace.
+For more information, go to the [related solution](https://azuremarketplace.microsoft.com/) in the Azure Marketplace.

articles/sentinel/data-connectors/juniper-srx.md

@@ -10,7 +10,7 @@ ms.author: cwatson
 
 # Juniper SRX connector for Microsoft Sentinel
 
-The [Juniper SRX](https://www.juniper.net/us/en/products-services/security/srx-series/) connector allows you to easily connect your Juniper SRX logs with Microsoft Sentinel. This gives you more insight into your organization's network and improves your security operation capabilities.
+The [Juniper SRX](https://www.juniper.net/us/en/products/security/srx-series.html) connector allows you to easily connect your Juniper SRX logs with Microsoft Sentinel. This gives you more insight into your organization's network and improves your security operation capabilities.
 
 ## Connector attributes
 

articles/site-recovery/hyper-v-azure-troubleshoot.md

@@ -176,7 +176,6 @@ All Hyper-V replication events are logged in the Hyper-V-VMMS\Admin log, located
 
 ### Log collection for advanced troubleshooting
 
-These tools can help with advanced troubleshooting:
+This tool can help with advanced troubleshooting:
 
 -	For VMM, perform Site Recovery log collection using the [Support Diagnostics Platform (SDP) tool](https://social.technet.microsoft.com/wiki/contents/articles/28198.asr-data-collection-and-analysis-using-the-vmm-support-diagnostics-platform-sdp-tool.aspx).
--	For Hyper-V without VMM, [download this tool](https://dcupload.microsoft.com/tools/win7files/DIAG_ASRHyperV_global.DiagCab), and run it on the Hyper-V host to collect the logs.

articles/virtual-machine-scale-sets/spot-priority-mix.md

@@ -50,8 +50,6 @@ You can set your Spot Priority Mix by using an ARM template to add the following
 - `baseRegularPriorityCount` – Specifies a base number of VMs that are standard, *Regular* priority; if the Scale Set capacity is at or below this number, all VMs are *Regular* priority.
 - `regularPriorityPercentageAboveBase` – Specifies the percentage split of *Regular* and *Spot* priority VMs that are used when the Scale Set capacity is above the *baseRegularPriorityCount*.
 
-You can refer to this [ARM template example](https://paste.microsoft.com/f84d2f83-f6bf-4d24-aa03-175b0c43da32) for more context.
-
 ### [Portal](#tab/portal)
 
 You can set your Spot Priority Mix in the Spot tab of the Virtual Machine Scale Sets creation process in the Azure portal. The following steps instruct you on how to access this feature during that process.

articles/virtual-machines/extensions/hpccompute-amd-gpu-windows.md

@@ -14,7 +14,7 @@ ms.author: vikancha
 ---
 # AMD GPU Driver Extension for Windows
 
-This article provides an overview of the virtual machine (VM) extension to deploy AMD GPU drivers on Windows N-series VMs. When you install AMD drivers by using this extension, you're accepting and agreeing to the terms of the [AMD End-User License Agreement](https://www.amd.com/en/support/amd-software-eula). During the installation process, the VM might reboot to complete the driver setup.
+This article provides an overview of the virtual machine (VM) extension to deploy AMD GPU drivers on Windows N-series VMs. When you install AMD drivers by using this extension, you're accepting and agreeing to the terms of the [AMD End-User License Agreement](https://www.amd.com/en/legal/eula/amd-software-eula.html). During the installation process, the VM might reboot to complete the driver setup.
 
 Instructions on manual installation of the drivers and the current supported versions are available. For more information, see [Azure N-series AMD GPU driver setup for Windows](../windows/n-series-amd-driver-setup.md).