Absolute links -> Relative links to MDs

Author: spelluru

articles/event-grid/availability-zones-disaster-recovery.md

@@ -60,7 +60,7 @@ Event Grid’s automatic failover has different RPOs and RTOs for your metadata
 
 > [!IMPORTANT]
 > - In case of server-side disaster recovery, if the paired region has no extra capacity to take on the additional traffic, Event Grid cannot initiate failover. The recovery is done on a best-effort basis.
-> - The cost for using this feature  is: $0.
+> - There is not charge for using this feature.
 > - Geo-disaster recovery is not supported for partner namespaces and partner topics. 
 
 ## Next steps

articles/event-grid/mqtt-automotive-connectivity-and-data-solution.md

@@ -53,7 +53,7 @@ The *vehicle to cloud* dataflow is used to process telemetry data from the vehic
 1. The **Event Grid** routes messages to different subscribers based on the topic and message attributes.
     1. Low priority messages that don't require immediate processing (for example, analytics messages) are routed directly to storage using an Event Hubs instance for buffering.
     1. High priority messages that require immediate processing (for example, status changes that must be visualized in a user-facing application) are routed to an Azure Function using an Event Hubs instance for buffering.
-1. Low priority messages are stored directly in the **data lake** using [event capture](/azure/stream-analytics/event-hubs-parquet-capture-tutorial). These messages can use [batch decoding and processing](#data-analytics) for optimum costs.
+1. Low priority messages are stored directly in the **data lake** using [event capture](../stream-analytics/event-hubs-parquet-capture-tutorial.md). These messages can use [batch decoding and processing](#data-analytics) for optimum costs.
 1. High priority messages are processed with an **Azure function**. The function reads the vehicle, device and user consent settings from the **Device Registry** and performs the following steps:
     1. Verifies that the vehicle and device are registered and active.
     2. Verifies that the user has given consent for the message topic.
@@ -157,26 +157,26 @@ Each *vehicle messaging scale unit* supports a defined vehicle population (for e
 
 #### Connectivity
 
-* [Azure Event Grid](/azure/event-grid/) allows for device onboarding, AuthN/Z and pub-sub via MQTT v5.
-* [Azure Functions](/azure/azure-functions/) processes the vehicle messages. It can also be used to implement management APIs that require short-lived execution.
-* [Azure Kubernetes Service (AKS)](/azure/aks/) is an alternative when the functionality behind the Managed APIs consists of complex workloads deployed as containerized applications.
-* [Azure Cosmos DB](/azure/cosmos-db) stores the vehicle, device and user consent settings.
-* [Azure API Management](/azure/api-management/) provides a managed API gateway to existing back-end services such as vehicle lifecycle management (including OTA) and user consent management.
-* [Azure Batch](/azure/batch/) runs large compute-intensive tasks efficiently, such as vehicle communication trace ingestion.
+* [Azure Event Grid](overview.md) allows for device onboarding, AuthN/Z and pub-sub via MQTT v5.
+* [Azure Functions](../azure-functions/functions-overview.md) processes the vehicle messages. It can also be used to implement management APIs that require short-lived execution.
+* [Azure Kubernetes Service (AKS)](../aks/intro-kubernetes.md) is an alternative when the functionality behind the Managed APIs consists of complex workloads deployed as containerized applications.
+* [Azure Cosmos DB](../cosmos-db/introduction.md) stores the vehicle, device and user consent settings.
+* [Azure API Management](../azure/api-management/api-management-key-concepts.md) provides a managed API gateway to existing back-end services such as vehicle lifecycle management (including OTA) and user consent management.
+* [Azure Batch](../batch/batch-technical-overview.md) runs large compute-intensive tasks efficiently, such as vehicle communication trace ingestion.
 
 #### Data and Analytics
 
-* [Azure Event Hubs](/azure/event-hubs/) enables processing and ingesting massive amounts of telemetry data.
+* [Azure Event Hubs](../event-hubs/event-hubs-about.md) enables processing and ingesting massive amounts of telemetry data.
 * [Azure Data Explorer](/azure/data-explorer/data-explorer-overview) provides exploration, curation and analytics of time-series based vehicle telemetry data.
-* [Azure Blob Storage](/azure/storage/blobs) stores large documents (such as videos and can traces) and curated vehicle data.
+* [Azure Blob Storage](../storage/blobs/storage-blobs-overview.md) stores large documents (such as videos and can traces) and curated vehicle data.
 * [Azure Databricks](/azure/databricks/) provides a set of tool to maintain enterprise-grade data solutions at scale. Required for long-running operations on large amounts of vehicle data.
 
 #### Backend Integration
 
-* [Azure Logic Apps](/azure/logic-apps/) runs automated workflows for business integration based on vehicle data.
-* [Azure App Service](/azure/app-service/) provides user-facing web apps and mobile back ends, such as the companion app.
-* [Azure Cache for Redis](/azure/azure-cache-for-redis/) provides in-memory caching of data often used by user-facing applications.
-* [Azure Service Bus](/azure/service-bus-messaging/) provides brokering that decouples vehicle connectivity from digital services and business integration.
+* [Azure Logic Apps](../logic-apps/logic-apps-overview.md) runs automated workflows for business integration based on vehicle data.
+* [Azure App Service](../app-service/overview.md) provides user-facing web apps and mobile back ends, such as the companion app.
+* [Azure Cache for Redis](../azure-cache-for-redis/cache-overview.md) provides in-memory caching of data often used by user-facing applications.
+* [Azure Service Bus](../service-bus-messaging/service-bus-messaging-overview.md) provides brokering that decouples vehicle connectivity from digital services and business integration.
 
 ### Alternatives
 
@@ -188,7 +188,7 @@ Examples:
 * **Azure Batch** for High-Performance Computing tasks such as decoding large CAN Trace / Video Files
 * **Azure Kubernetes Service** for managed, full fledge orchestration of complex logic such as command & control workflow management.
 
-As an alternative to event-based data sharing, it's also possible to use [Azure Data Share](/azure/data-share/) if the objective is to perform batch synchronization at the data lake level.
+As an alternative to event-based data sharing, it's also possible to use [Azure Data Share](../data-share/overview.md) if the objective is to perform batch synchronization at the data lake level.
 
 ## Scenario details
 
@@ -238,7 +238,7 @@ Reliability ensures your application can meet the commitments you make to your c
 
 Security provides assurances against deliberate attacks and the abuse of your valuable data and systems. For more information, see [Overview of the security pillar](/azure/architecture/framework/security/overview).
 
-* Securing vehicle connection: See the section on [certificate management](/azure/event-grid/) to understand how to use X.509 certificates to establish secure vehicle communications.
+* Securing vehicle connection: See the section on [certificate management](../event-grid/overview.md) to understand how to use X.509 certificates to establish secure vehicle communications.
 
 ### Cost optimization
 
@@ -309,4 +309,4 @@ The following articles cover some of the concepts used in the architecture:
 The following articles describe interactions between components in the architecture:
 
 * [Configure streaming ingestion on your Azure Data Explorer cluster](/azure/data-explorer/ingest-data-streaming)
-* [Capture Event Hubs data in parquet format and analyze with Azure Synapse Analytics](/azure/stream-analytics/event-hubs-parquet-capture-tutorial)
+* [Capture Event Hubs data in parquet format and analyze with Azure Synapse Analytics](../stream-analytics/event-hubs-parquet-capture-tutorial.md)

articles/event-grid/mqtt-publish-and-subscribe-cli.md

@@ -27,10 +27,10 @@ If you don't have an [Azure subscription](/azure/guides/developer/azure-develope
 
 ## Prerequisites
 
-- If you're new to Event Grid, read through the [Event Grid overview](/azure/event-grid/overview) before you start this tutorial.
-- Register the Event Grid resource provider according to the steps in [Register the Event Grid resource provider](/azure/event-grid/custom-event-quickstart-portal#register-the-event-grid-resource-provider).
+- If you're new to Event Grid, read through the [Event Grid overview](../event-grid/overview.md) before you start this tutorial.
+- Register the Event Grid resource provider according to the steps in [Register the Event Grid resource provider](../event-grid/custom-event-quickstart-portal.md#register-the-event-grid-resource-provider).
 - Make sure that port 8883 is open in your firewall. The sample in this tutorial uses the MQTT protocol, which communicates over port 8883. This port might be blocked in some corporate and educational network environments.
-- Use the Bash environment in [Azure Cloud Shell](/azure/cloud-shell/overview). For more information, see [Quickstart for Bash in Azure Cloud Shell](/azure/cloud-shell/quickstart).
+- Use the Bash environment in [Azure Cloud Shell](../cloud-shell/overview.md). For more information, see [Quickstart for Bash in Azure Cloud Shell](../cloud-shell/quickstart.md).
 - If you prefer to run CLI reference commands locally, [install](/cli/azure/install-azure-cli) the Azure CLI. If you're running on Windows or macOS, consider running the Azure CLI in a Docker container. For more information, see [Run the Azure CLI in a Docker container](/cli/azure/run-azure-cli-docker).
 - If you're using a local installation, sign in to the Azure CLI by using the [az login](/cli/azure/reference-index#az-login) command. To finish the authentication process, follow the steps that appear in your terminal. For other sign-in options, see [Sign in with the Azure CLI](/cli/azure/authenticate-azure-cli).
 - When you're prompted, install the Azure CLI extension on first use. For more information about extensions, see [Use extensions with the Azure CLI](/cli/azure/azure-cli-extensions-overview).

articles/event-grid/mqtt-routing-to-azure-functions-portal.md

@@ -51,7 +51,7 @@ You use this Azure function as an event handler for a topic's subscription later
 > - This tutorial has been tested with an Azure function that uses .NET 8.0 (isolated) runtime stack.
 
 ## Create an Event Grid topic (custom topic)
-Create an Event Grid topic. See [Create a custom topic using the portal](/azure/event-grid/custom-event-quickstart-portal). When you create the Event Grid topic, on the **Advanced** tab, for **Event Schema**, select **Cloud Event Schema v1.0**.
+Create an Event Grid topic. See [Create a custom topic using the portal](custom-event-quickstart-portal.md). When you create the Event Grid topic, on the **Advanced** tab, for **Event Schema**, select **Cloud Event Schema v1.0**.
 
 :::image type="content" source="./media/mqtt-routing-to-azure-functions-portal/create-topic-cloud-event-schema.png" alt-text="Screenshot that shows the Advanced page of the Create Topic wizard.":::
 

articles/event-grid/mqtt-routing-to-event-hubs-cli-namespace-topics.md

@@ -15,8 +15,8 @@ In this tutorial, you learn how to use a namespace topic to route data from MQTT
 ## Prerequisites
 
 - If you don't have an Azure subscription, create an [Azure free account](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio) before you begin.
-- If you're new to Event Grid, read the [Event Grid overview](/azure/event-grid/overview) before you start this tutorial.
-- Register the Event Grid resource provider according to the steps in [Register the Event Grid resource provider](/azure/event-grid/custom-event-quickstart-portal#register-the-event-grid-resource-provider).
+- If you're new to Event Grid, read the [Event Grid overview](overview.md) before you start this tutorial.
+- Register the Event Grid resource provider according to the steps in [Register the Event Grid resource provider](custom-event-quickstart-portal.md#register-the-event-grid-resource-provider).
 - Make sure that port **8883** is open in your firewall. The sample in this tutorial uses the MQTT protocol, which communicates over port 8883. This port might be blocked in some corporate and educational network environments.
 
 ## Launch Cloud Shell 
@@ -146,7 +146,7 @@ Verify that the event hub received those messages on the **Overview** page for y
 
 ## View routed MQTT messages in Event Hubs by using a Stream Analytics query
 
-Navigate to the Event Hubs instance (event hub) within your event subscription in the Azure portal. Process data from your event hub by using Stream Analytics. For more information, see [Process data from Azure Event Hubs using Stream Analytics - Azure Event Hubs | Microsoft Learn](/azure/event-hubs/process-data-azure-stream-analytics). You can see the MQTT messages in the query.
+Navigate to the Event Hubs instance (event hub) within your event subscription in the Azure portal. Process data from your event hub by using Stream Analytics. For more information, see [Process data from Azure Event Hubs using Stream Analytics - Azure Event Hubs | Microsoft Learn](../event-hubs/process-data-azure-stream-analytics.md). You can see the MQTT messages in the query.
 
 :::image type="content" source="./media/mqtt-routing-to-event-hubs-portal/view-data-in-event-hub-instance-using-azure-stream-analytics-query.png" alt-text="Screenshot that shows the MQTT messages data in Event Hubs by using the Stream Analytics query tool.":::
 

articles/event-grid/mqtt-routing-to-event-hubs-portal-namespace-topics.md

@@ -18,8 +18,8 @@ In this tutorial, you learn how to use a namespace topic to route data from MQTT
 ## Prerequisites
 
 - If you don't have an Azure subscription, create an [Azure free account](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio) before you begin.
-- If you're new to Event Grid, read the [Event Grid overview](/azure/event-grid/overview) before you start this tutorial.
-- Register the Event Grid resource provider according to the steps in [Register the Event Grid resource provider](/azure/event-grid/custom-event-quickstart-portal#register-the-event-grid-resource-provider).
+- If you're new to Event Grid, read the [Event Grid overview](../event-grid/overview.md) before you start this tutorial.
+- Register the Event Grid resource provider according to the steps in [Register the Event Grid resource provider](custom-event-quickstart-portal.md#register-the-event-grid-resource-provider).
 - Make sure that port **8883** is open in your firewall. The sample in this tutorial uses the MQTT protocol, which communicates over port 8883. This port might be blocked in some corporate and educational network environments.
 
 [!INCLUDE [event-grid-create-namespace-portal](./includes/event-grid-create-namespace-portal.md)]
@@ -117,7 +117,7 @@ Follow steps in the quickstart: [Publish and subscribe on an MQTT topic](./mqtt-
 
 ## View routed MQTT messages in Event Hubs by using a Stream Analytics query
 
-Navigate to the Event Hubs instance (event hub) within your event subscription in the Azure portal. Process data from your event hub by using Stream Analytics. For more information, see [Process data from Azure Event Hubs using Stream Analytics - Azure Event Hubs | Microsoft Learn](/azure/event-hubs/process-data-azure-stream-analytics). You can see the MQTT messages in the query.
+Navigate to the Event Hubs instance (event hub) within your event subscription in the Azure portal. Process data from your event hub by using Stream Analytics. For more information, see [Process data from Azure Event Hubs using Stream Analytics - Azure Event Hubs | Microsoft Learn](../event-hubs/process-data-azure-stream-analytics.md). You can see the MQTT messages in the query.
 
 :::image type="content" source="./media/mqtt-routing-to-event-hubs-portal/view-data-in-event-hub-instance-using-azure-stream-analytics-query.png" alt-text="Screenshot that shows the MQTT messages data in Event Hubs by using the Stream Analytics query tool.":::
 

articles/event-grid/publish-deliver-events-with-namespace-topics.md

@@ -21,7 +21,7 @@ The article provides step-by-step instructions to publish events to Azure Event
 
 ## Prerequisites
 
-- Use the Bash environment in [Azure Cloud Shell](/azure/cloud-shell/overview). For more information, see [Quickstart for Bash in Azure Cloud Shell](/azure/cloud-shell/quickstart).
+- Use the Bash environment in [Azure Cloud Shell](../cloud-shell/overview.md). For more information, see [Quickstart for Bash in Azure Cloud Shell](../cloud-shell/quickstart.md).
 
    [:::image type="icon" source="~/reusable-content/ce-skilling/azure/media/cloud-shell/launch-cloud-shell-button.png" alt-text="Launch Azure Cloud Shell" :::](https://shell.azure.com)
 

articles/event-hubs/authenticate-shared-access-signature.md

@@ -218,9 +218,9 @@ $SASToken
 
 ```bash
 get_sas_token() {
-    local EVENTHUB_URI=$1
-    local SHARED_ACCESS_KEY_NAME=$2
-    local SHARED_ACCESS_KEY=$3
+    local EVENTHUB_URI='EVENTHUBURI'
+    local SHARED_ACCESS_KEY_NAME='SHAREDACCESSKEYNAME'
+    local SHARED_ACCESS_KEY='SHAREDACCESSKEYVALUE'
     local EXPIRY=${EXPIRY:=$((60 * 60 * 24))} # Default token expiry is 1 day
 
     local ENCODED_URI=$(echo -n $EVENTHUB_URI | jq -s -R -r @uri)

articles/event-hubs/azure-event-hubs-kafka-overview.md

@@ -150,7 +150,7 @@ Standalone and without ksqlDB, Kafka Streams has fewer capabilities than many al
 - [Apache Storm](event-hubs-storm-getstarted-receive.md)
 - [Apache Spark](event-hubs-kafka-spark-tutorial.md)
 - [Apache Flink](event-hubs-kafka-flink-tutorial.md)
-- [Apache Flink on HDInsight on AKS](/azure/hdinsight-aks/flink/flink-overview)
+- [Apache Flink on HDInsight on AKS](../hdinsight-aks/flink/flink-overview.md)
 - [Akka Streams](event-hubs-kafka-akka-streams-tutorial.md)
 
 The listed services and frameworks can generally acquire event streams and reference data directly from a diverse set of sources through adapters. Kafka Streams can only acquire data from Apache Kafka and your analytics projects are therefore locked into Apache Kafka. To use data from other sources, you're required to first import data into Apache Kafka with the Kafka Connect framework.