Merge pull request #250539 from JasonWHowell/fixes9

prmerger-automator[bot] · web-flow · commit 555c9628e34c · 2023-09-06T23:48:43.000Z
Bulk fix absolute-links
diff --git a/articles/operator-nexus/howto-use-azure-policy-for-aks-cluster-security.md b/articles/operator-nexus/howto-use-azure-policy-for-aks-cluster-security.md
@@ -19,7 +19,7 @@ This guide provides information on how to apply policy definitions to your clust
 
 If you're new to Azure Policy, here are some helpful resources that you can use to become more familiar with Azure Policy, how it can be used to secure your AKS clusters, and the built-in policy definitions that are available for you to use for AKS resource protection:
 
-- [Azure Policy documentation](https://learn.microsoft.com/azure/governance/policy/)
+- [Azure Policy documentation](/azure/governance/policy/)
 - [Understand Azure Policy for Kubernetes clusters](../governance/policy/concepts/policy-for-kubernetes.md)
 - [Azure Policy Built-in definitions for AKS](../aks/policy-reference.md) 
 
diff --git a/articles/operator-nexus/howto-use-vm-console-service.md b/articles/operator-nexus/howto-use-vm-console-service.md
@@ -15,7 +15,7 @@ The Virtual Machine (VM) console service provides managed access to a VM hosted
 
 :::image type="content" source="media/vm-console-service.png" alt-text="Diagram of VM Console service." lightbox="media/vm-console-service.png":::
 
-For more information about networking resources that enables private connectivity to an Operator Nexus Instance, see [Introduction to Azure Private Link](https://learn.microsoft.com/training/modules/introduction-azure-private-link/).
+For more information about networking resources that enables private connectivity to an Operator Nexus Instance, see [Introduction to Azure Private Link](/training/modules/introduction-azure-private-link/).
 
 This document provides guided instructions of how to use the VM Console service to establish a session with a Virtual Machine in an Operator Nexus Instance.
 
diff --git a/articles/orbital/concepts-contact.md b/articles/orbital/concepts-contact.md
@@ -52,7 +52,7 @@ If you don't know the pass timings, or which sites are available, then you can u
 |Portal| Yes | Yes | Custom pass timings aren't possible. You must use the results from the query. |
 |API | Yes | Yes| Custom pass timings are possible. |
 
-See [how-to schedule a contact](schedule-contact.md) for the Portal method. The API can also be used to create a contact. See the [API docs](https://learn.microsoft.com/rest/api/orbital/) for this method.
+See [how-to schedule a contact](schedule-contact.md) for the Portal method. The API can also be used to create a contact. See the [API docs](/rest/api/orbital/) for this method.
 
 ## Next steps
 
diff --git a/articles/orbital/overview.md b/articles/orbital/overview.md
@@ -39,7 +39,7 @@ For a full end-to-end solution to manage fleet operations and "Telemetry, Tracki
 ## Links to learn more
 - [Overview, features, security, and FAQ](https://azure.microsoft.com/products/orbital/#layout-container-uid189e)
 - [Pricing](https://azure.microsoft.com/pricing/details/orbital/)
-- [Microsoft Learn training session](https://learn.microsoft.com/training/modules/introduction-to-ground-station/)
+- [Microsoft Learn training session](/training/modules/introduction-to-ground-station/)
 - [Azure Space Blog](https://techcommunity.microsoft.com/t5/azure-space-blog/bg-p/AzureSpaceBlog)
 - [General Availability press announcement](https://azure.microsoft.com/blog/new-azure-space-products-enable-digital-resiliency-and-empower-the-industry/)
 
diff --git a/articles/orbital/partner-network-integration.md b/articles/orbital/partner-network-integration.md
@@ -16,7 +16,7 @@ This article describes how to integrate partner network ground stations for cust
 ## Prerequisites
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
-- [Contributor permissions](https://learn.microsoft.com/azure/role-based-access-control/rbac-and-directory-admin-roles#azure-roles) at the subscription level.
+- [Contributor permissions](/azure/role-based-access-control/rbac-and-directory-admin-roles#azure-roles) at the subscription level.
 - A [Basic Support Plan](https://azure.microsoft.com/support/plans/) or higher is required for a spacecraft authorization request.
 - A spacecraft license is required for private spacecraft.
 - An active contract with the partner network(s) you wish to integrate with Azure Orbital Ground Station:
diff --git a/articles/orbital/prepare-network.md b/articles/orbital/prepare-network.md
@@ -43,17 +43,17 @@ Ensure the contact profile properties are set as follows:
 | **Property** | **Setting** |
 |----------|---------|
 | subnetId | Enter the **full ID to the delegated subnet**, which can be found inside the VNET's JSON view. subnetID is found under networkConfiguration. |
-| ipAddress | For each link, enter an **IP for TCP/UDP server mode**. Leave blank for TCP/UDP client mode. See section below for a detailed explanation on configuring this property. |
-| port | For each link, port must be within 49152 and 65535 range and must be unique across all links in the contact profile. |
+| ipAddress | For each link, enter an **IP for TCP/UDP server mode**. Leave blank for TCP/UDP client mode. See the following section for a detailed explanation of configuring this property. |
+| port | For each link, the port must be within the 49152 and 65535 range and must be unique across all links in the contact profile. |
 
 > [!NOTE]
-> You can have multiple links/channels in a contact profile, and you can have multiple IPs. But the combination of port/protocol must be unique. You cannot have two identical ports, even if you have two different destination IPs. 
+> You can have multiple links/channels in a contact profile, and you can have multiple IPs. However the combination of port/protocol must be unique. You cannot have two identical ports, even if you have two different destination IPs. 
 
-For more information, learn about [contact profiles](https://learn.microsoft.com/azure/orbital/concepts-contact-profile) and [how to configure a contact profile](https://learn.microsoft.com/azure/orbital/contact-profile).
+For more information, learn about [contact profiles](/azure/orbital/concepts-contact-profile) and [how to configure a contact profile](/azure/orbital/contact-profile).
 
 ## Schedule the contact
 
-The Azure Orbital Ground Station platform pre-reserves IPs in the subnet when a contact is scheduled. These IPs represent the platform side endpoints for each link. IPs will be unique between contacts, and if multiple concurrent contacts are using the same subnet, Microsoft guarantees those IPs to be distinct. The service will fail to schedule the contact and an error will be returned if the service runs out of IPs or cannot allocate an IP.
+The Azure Orbital Ground Station platform pre-reserves IPs in the subnet when a contact is scheduled. These IPs represent the platform side endpoints for each link. IPs are unique between contacts, and if multiple concurrent contacts are using the same subnet, Microsoft guarantees those IPs to be distinct. The service fails to schedule the contact and an error is returned if the service runs out of IPs or cannot allocate an IP.
 
 When you create a contact, you can find these IPs by viewing the contact properties. Select JSON view in the portal or use the GET contact API call to view the contact properties. Make sure to use the current API version of 2022-03-01. The parameters of interest are below:
 
@@ -71,7 +71,7 @@ You can use this information to set up network policies or to distinguish betwee
 > - Only one destination IP is present. Any link in client mode should connect to this IP and the links are differentiated based on port.
 > - Many source IPs can be present. Links in server mode will connect to your specified IP address in the contact profile. The flows will originate from the source IPs present in this field and target the port as per the link details in the contact profile. There is no fixed assignment of link to source IP so please make sure to allow all IPs in any networking setup or firewalls. 
 
-For more information, learn about [contacts](https://learn.microsoft.com/azure/orbital/concepts-contact) and [how to schedule a contact](https://learn.microsoft.com/azure/orbital/schedule-contact).
+For more information, learn about [contacts](/azure/orbital/concepts-contact) and [how to schedule a contact](/azure/orbital/schedule-contact).
 
 ## Client/Server, TCP/UDP, and link direction
 
diff --git a/articles/postgresql/flexible-server/how-to-create-server-customer-managed-key-azure-api.md b/articles/postgresql/flexible-server/how-to-create-server-customer-managed-key-azure-api.md
@@ -25,7 +25,7 @@ Prerequisites:
 > [!NOTE]  
 > API examples below are based on 2022-12-01 API version 
 
-You can create a PostgreSQL Flexible Server encrypted with Customer Managed Key  by using the [create API](https://learn.microsoft.com/rest/api/postgresql/flexibleserver/servers/create?tabs=HTTP):
+You can create a PostgreSQL Flexible Server encrypted with Customer Managed Key  by using the [create API](/rest/api/postgresql/flexibleserver/servers/create?tabs=HTTP):
 ```rest
 PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBForPostgreSql/flexibleServers/{serverName}?api-version=2022-12-01
 
@@ -54,7 +54,7 @@ PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{
 ```
 Key Vault Uri can be copied from key properties **Key Identifier** field  in Azure Key Vault Portal UI, as shown in image below:
 :::image type="content" source="./media/how-to-create-server-customer-managed-key-azure-api/key-uri-portal.png" alt-text =" Screenshot of  key properties and URI on Azure Key Vault Portal page." :::
-You can also programmatically fetch Key Vault Uri using [Azure REST API](https://learn.microsoft.com/rest/api/keyvault/keyvault/vaults/get?tabs=HTTP)
+You can also programmatically fetch Key Vault Uri using [Azure REST API](/rest/api/keyvault/keyvault/vaults/get?tabs=HTTP)
 
 ## Next steps
 
diff --git a/articles/private-5g-core/delete-resources.md b/articles/private-5g-core/delete-resources.md
@@ -64,13 +64,13 @@ If you are deleting multiple sites, repeat this step for each site.
 
 ## Delete the AKS cluster
 
-The Azure Kubernetes Service (AKS) cluster is an orchestration layer used to manage the packet core software components. To delete the Azure Kubernetes Service (AKS) connected cluster, follow [Remove the Azure Kubernetes service](https://learn.microsoft.com/azure/databox-online/azure-stack-edge-deploy-aks-on-azure-stack-edge#remove-the-azure-kubernetes-service).
+The Azure Kubernetes Service (AKS) cluster is an orchestration layer used to manage the packet core software components. To delete the Azure Kubernetes Service (AKS) connected cluster, follow [Remove the Azure Kubernetes service](/azure/databox-online/azure-stack-edge-deploy-aks-on-azure-stack-edge#remove-the-azure-kubernetes-service).
 
 If you are deleting multiple sites, repeat this step for each site.
 
 ## Reset ASE
 
- Azure Stack Edge (ASE) hardware runs the packet core software at the network edge. To reset your ASE device, follow [Reset and reactivate your Azure Stack Edge device](https://learn.microsoft.com/azure/databox-online/azure-stack-edge-reset-reactivate-device).
+ Azure Stack Edge (ASE) hardware runs the packet core software at the network edge. To reset your ASE device, follow [Reset and reactivate your Azure Stack Edge device](/azure/databox-online/azure-stack-edge-reset-reactivate-device).
 
 If you are deleting multiple sites, repeat this step for each site.
 
diff --git a/articles/reliability/asm-retirement.md b/articles/reliability/asm-retirement.md
@@ -16,11 +16,11 @@ Azure Service Manager (ASM) is the old control plane of Azure responsible for cr
 ## Benefits of migrating to ARM 
 Migrating from the classic resource model to ARM offers several benefits, including: 
 
-- **Simplified management**: ARM provides a [unified platform](https://learn.microsoft.com/azure/azure-resource-manager/management/overview) for managing and deploying resources, allowing for easier provisioning, monitoring, and updating of infrastructure components.
-- **Improved security**: ARM incorporates robust security features, such as [role-based access control (RBAC)](https://learn.microsoft.com/azure/role-based-access-control/overview) and [Managed Identity](https://learn.microsoft.com/azure/active-directory/managed-identities-azure-resources/overview), to help protect resources and provide automatic credential management
-- **High Availability and Resiliency**: [Availability Zones](https://learn.microsoft.com/azure/reliability/availability-zones-overview) allow customers to run mission-critical applications with higher availability and fault tolerance to datacenter failures
-- **High Scalability**: ARM enables [automatic scaling](https://learn.microsoft.com/azure/well-architected/scalability/design-scale) of resources based on demand, ensuring applications can handle increased workloads efficiently.
-- **Cost optimization**: ARM provides features like [cost management](https://learn.microsoft.com/azure/cost-management-billing/) and [resource tagging](https://learn.microsoft.com/azure/azure-resource-manager/management/tag-resources), enabling better visibility and control over resource usage, leading to cost optimization and efficient resource allocation.
+- **Simplified management**: ARM provides a [unified platform](/azure/azure-resource-manager/management/overview) for managing and deploying resources, allowing for easier provisioning, monitoring, and updating of infrastructure components.
+- **Improved security**: ARM incorporates robust security features, such as [role-based access control (RBAC)](/azure/role-based-access-control/overview) and [Managed Identity](/azure/active-directory/managed-identities-azure-resources/overview), to help protect resources and provide automatic credential management
+- **High Availability and Resiliency**: [Availability Zones](/azure/reliability/availability-zones-overview) allow customers to run mission-critical applications with higher availability and fault tolerance to datacenter failures
+- **High Scalability**: ARM enables [automatic scaling](/azure/well-architected/scalability/design-scale) of resources based on demand, ensuring applications can handle increased workloads efficiently.
+- **Cost optimization**: ARM provides features like [cost management](/azure/cost-management-billing/) and [resource tagging](/azure/azure-resource-manager/management/tag-resources), enabling better visibility and control over resource usage, leading to cost optimization and efficient resource allocation.
 
 
 There are many service-related benefits which can be found in the migration guides. 
diff --git a/articles/sap/monitor/provider-netweaver.md b/articles/sap/monitor/provider-netweaver.md
@@ -190,7 +190,7 @@ Ensure all the prerequisites are successfully completed. To add the NetWeaver pr
     3. Ensure the NSG/firewall is not blocking the port – 5XX13 or 5XX14. (XX - SAP Instance Number)
     4. Check if AMS and SAP VMs are in the same vNet or are attached using vNet peering.
 
-       If not attached, see the following [link](https://learn.microsoft.com/azure/virtual-network/tutorial-connect-virtual-networks-portal) to connect vNets:  
+       If not attached, see the following [link](/azure/virtual-network/tutorial-connect-virtual-networks-portal) to connect vNets:  
    
 2. **Check for unprotected updated rules. ErrorCode: SOAPWebMethodsValidationFailed**
 
