Merge pull request #286878 from MicrosoftDocs/JasonWHowell-patch-3

Fix links

Author: prmerger-automator[bot]

articles/batch/tutorial-parallel-dotnet.md

@@ -118,7 +118,7 @@ The following sections break down the sample application into the steps that it
 
 ### Authenticate Blob and Batch clients
 
-To interact with the linked storage account, the app uses the Azure.Storage.Blobs Library for .NET. Using the [BlobServiceClient](/dotnet/api/azure.storage.blobs.blobserviceclient) class which takes a reference to the account Uri and authenticating [Token](/dotnet/api/azure.core.tokencredentia) such as [DefaultAzureCredential](/dotnet/api/azure.identity.defaultazurecredential).
+To interact with the linked storage account, the app uses the Azure.Storage.Blobs Library for .NET. Using the [BlobServiceClient](/dotnet/api/azure.storage.blobs.blobserviceclient) class which takes a reference to the account Uri and authenticating [Token](/dotnet/api/azure.core.tokencredential) such as [DefaultAzureCredential](/dotnet/api/azure.identity.defaultazurecredential).
 
 ```csharp
 // TODO: Replace <storage-account-name> with your actual storage account name

articles/openshift/howto-large-clusters.md

@@ -52,7 +52,7 @@ When deploying a large cluster, you must start with at most 50 worker nodes at c
 > While you can define up to 50 worker nodes at creation time, it's best to start with a small cluster (e.g, three (3) worker nodes) and then scale out to the desired number of worker nodes after the cluster is installed.
 >
 
-Follow the steps provided in [Create an Azure Red Hat OpenShift cluster](https://learn.microsoft.com/azure/openshift/create-cluster?tabs=azure-cli) until the "Create the cluster" steps, then continue as instructed:
+Follow the steps provided in [Create an Azure Red Hat OpenShift cluster](create-cluster.md?tabs=azure-cli) until the "Create the cluster" steps, then continue as instructed:
 
 The sample command below using the Azure CLI can be used to deploy a cluster with Standard_D32s_v5 as the control plane nodes, requesting three public IP addresses, and defining nine worker nodes:
 

articles/update-manager/troubleshoot.md

@@ -264,7 +264,7 @@ If the extension is already present on the machine but the extension status is n
 
 #### Issue
 
-The property [AllowExtensionOperations](https://learn.microsoft.com/dotnet/api/microsoft.azure.management.compute.models.osprofile.allowextensionoperations?view=azure-dotnet-legacy) is set to false in the machine OSProfile.
+The property [AllowExtensionOperations](/dotnet/api/microsoft.azure.management.compute.models.osprofile.allowextensionoperations) is set to false in the machine OSProfile.
 
 #### Resolution
 The property should be set to true to allow extensions to work properly. 
@@ -286,7 +286,7 @@ Proxy is configured on Windows or Linux machines that may block access to endpoi
 
 #### Resolution
 
-For Windows, see [issues related to proxy](https://learn.microsoft.com/troubleshoot/windows-client/installing-updates-features-roles/windows-update-issues-troubleshooting?toc=%2Fwindows%2Fdeployment%2Ftoc.json&bc=%2Fwindows%2Fdeployment%2Fbreadcrumb%2Ftoc.json#issues-related-to-httpproxy). 
+For Windows, see [issues related to proxy](/troubleshoot/windows-client/installing-updates-features-roles/windows-update-issues-troubleshooting#issues-related-to-httpproxy). 
 
 For Linux, ensure proxy setup doesn't block access to repositories that are required for downloading and installing updates.
 
@@ -300,7 +300,7 @@ TLS 1.0 and TLS 1.1 are deprecated.
 
 Use TLS 1.2 or higher.
 
-For Windows, see [Protocols in TLS/SSL Schannel SSP](https://learn.microsoft.com/windows/win32/secauthn/protocols-in-tls-ssl--schannel-ssp-).
+For Windows, see [Protocols in TLS/SSL Schannel SSP](/windows/win32/secauthn/protocols-in-tls-ssl--schannel-ssp-).
 
 For Linux, execute the following command to see the supported versions of TLS for your distro.
 `nmap --script ssl-enum-ciphers -p 443 www.azure.com`