fix links

Signed-off-by: Hannah Hunter <[email protected]>

Author: hhunter-ms

articles/azure-functions/durable/durable-functions-storage-providers.md

@@ -27,11 +27,11 @@ The durable task scheduler is a fully managed, high performance backend provider
 The key benefits of the durable task scheduler include:
 
 * Lower management and operation overhead compared to BYO backend providers
-* First-class observability and management [dashboard](../durable-task-scheduler/durable-task-scheduler-dashboard.md) provided out-of-the-box. 
+* First-class observability and management [dashboard](./durable-task-scheduler/durable-task-scheduler-dashboard.md) provided out-of-the-box. 
 * Supports the highest throughput of all backends today.
 * Support for authentication using managed identity.
 
-Existing Durable Functions users can leverage the scheduler with no code changes. Learn more about the [durable task scheduler](../durable-task-scheduler/durable-task-scheduler.md), and [how to get started](../durable-task-scheduler/quickstart-durable-task-scheduler.md). 
+Existing Durable Functions users can leverage the scheduler with no code changes. Learn more about the [durable task scheduler](./durable-task-scheduler/durable-task-scheduler.md), and [how to get started](./durable-task-scheduler/quickstart-durable-task-scheduler.md). 
 
 Samples for durable task scheduler can be found on [GitHub](https://github.com/Azure-Samples/Durable-Task-Scheduler/).
 
@@ -123,7 +123,7 @@ Configuring alternate storage providers is generally a two-step process:
 If no storage provider is explicitly configured in host.json, the Azure Storage provider will be enabled by default.
 
 ### Configuring durable task scheduler (preview)
-See the [durable task scheduler getting started documentation](../durable-task-scheduler/quickstart-durable-task-scheduler.md).
+See the [durable task scheduler getting started documentation](./durable-task-scheduler/quickstart-durable-task-scheduler.md).
 
 ### Configuring the Netherite storage provider
 
@@ -204,7 +204,7 @@ There are many significant tradeoffs between the various supported storage provi
 |- |-              |-          |-      |- |
 | Official support status | ✅ Generally available (GA) | ✅ Generally available (GA) | ✅ Generally available (GA) | Public preview|
 | External dependencies | Azure Storage account (general purpose v1) | Azure Event Hubs<br/>Azure Storage account (general purpose) | [SQL Server 2019](https://www.microsoft.com/sql-server/sql-server-2019) or Azure SQL Database | N/A | 
-| Local development and emulation options | [Azurite v3.12+](../../storage/common/storage-use-azurite.md) (cross platform) | Supports in-memory emulation of task hubs ([more information](https://microsoft.github.io/durabletask-netherite/#/emulation)) | SQL Server Developer Edition (supports [Windows](/sql/database-engine/install-windows/install-sql-server), [Linux](/sql/linux/sql-server-linux-setup), and [Docker containers](/sql/linux/sql-server-linux-docker-container-deployment)) | [Durable task scheduler emulator](../durable-task-scheduler/durable-task-scheduler.md#emulator-for-local-development) | 
+| Local development and emulation options | [Azurite v3.12+](../../storage/common/storage-use-azurite.md) (cross platform) | Supports in-memory emulation of task hubs ([more information](https://microsoft.github.io/durabletask-netherite/#/emulation)) | SQL Server Developer Edition (supports [Windows](/sql/database-engine/install-windows/install-sql-server), [Linux](/sql/linux/sql-server-linux-setup), and [Docker containers](/sql/linux/sql-server-linux-docker-container-deployment)) | [Durable task scheduler emulator](./durable-task-scheduler/durable-task-scheduler.md#emulator-for-local-development) | 
 | Task hub configuration | Explicit | Explicit | Implicit by default ([more information](https://microsoft.github.io/durabletask-mssql/#/taskhubs)) | Explicit | 
 | Maximum throughput | Moderate | Very high | Moderate | Very high | 
 | Maximum orchestration/entity scale-out (nodes) | 16 | 32 | N/A | N/A | 

articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-framework.md

@@ -32,7 +32,7 @@ The following table provides some considerations when choosing a framework.
 
 ## Durable Task Scheduler for Durable Functions
 
-When used with Durable Functions, a feature of Azure Functions, the Durable Task Scheduler works as a fully managed backend provider, persisting state data as your app runs. While [other backend providers are supported](../durable/durable-functions-storage-providers.md), the Durable Task Scheduler offers a fully managed experience, which removes operational overhead. The scheduler offers exceptional performance, reliability, and the ease of monitoring orchestrations.
+When used with Durable Functions, a feature of Azure Functions, the Durable Task Scheduler works as a fully managed backend provider, persisting state data as your app runs. While [other backend providers are supported](../durable-functions-storage-providers.md), the Durable Task Scheduler offers a fully managed experience, which removes operational overhead. The scheduler offers exceptional performance, reliability, and the ease of monitoring orchestrations.
 
 The Durable Task Scheduler plays a similar role in the Durable Task Framework as in Durable Functions.
 

articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler.md

@@ -2,7 +2,7 @@
 title: Azure Functions Durable Task Scheduler (preview)
 description: Learn about the characteristics of the Azure Functions Durable Task Scheduler backend.
 ms.topic: conceptual
-ms.date: 04/11/2025
+ms.date: 04/24/2025
 ---
 
 # Azure Functions Durable Task Scheduler (preview)
@@ -13,7 +13,7 @@ The Durable Task Scheduler provides durable execution in Azure. Durable executio
 - Data processing
 - Infrastructure management, and others. 
 
-The Durable Task Scheduler, coupled with a developer orchestration framework like [Durable Functions](../durable/durable-functions-overview.md) or the [Durable Task SDKs][todo], enables you to author stateful apps that run on any compute environment without the need to architect for fault tolerance.
+The Durable Task Scheduler, coupled with a developer orchestration framework like [Durable Functions](../durable-functions-overview.md) or the [Durable Task SDKs][todo], enables you to author stateful apps that run on any compute environment without the need to architect for fault tolerance.
 
 ## Orchestration frameworks
 
@@ -33,7 +33,7 @@ For all Durable Task Scheduler orchestration frameworks, you can create instance
 - Storing and querying history at scale with minimal latency
 - Providing a rich monitoring experience through [the Durable Task Scheduler dashboard](./durable-task-scheduler-dashboard.md)
 
-Unlike [the BYO storage providers](../durable/durable-functions-storage-providers.md), the Durable Task Scheduler provider is a purpose-built backend-as-a-service optimized for the specific needs of the [Durable Task Framework](https://github.com/Azure/durabletask).
+Unlike [the BYO storage providers](../durable-functions-storage-providers.md), the Durable Task Scheduler provider is a purpose-built backend-as-a-service optimized for the specific needs of the [Durable Task Framework](https://github.com/Azure/durabletask).
 
 The following diagram shows the architecture of the Durable Task Scheduler backend and its interaction with connected apps.
 
@@ -86,7 +86,7 @@ Access to the dashboard is secured by identity and role-based access controls.
 
 ### Multiple task hubs
 
-State is durably persisted in a *task hub*. A [task hub](../durable/durable-functions-task-hubs.md) is a logical container for orchestration and entity instances and provides a way to partition the state store. With one scheduler instance, you can create multiple task hubs that can be used by different apps. To access a task hub, the caller's identity *must* have the required role-based access control (RBAC) permissions.
+State is durably persisted in a *task hub*. A [task hub](../durable-functions-task-hubs.md) is a logical container for orchestration and entity instances and provides a way to partition the state store. With one scheduler instance, you can create multiple task hubs that can be used by different apps. To access a task hub, the caller's identity *must* have the required role-based access control (RBAC) permissions.
 
 Creating multiple task hubs isolates different workloads that can be managed independently. For example, you can create a task hub for each environment (dev, test, prod) or for different teams within your organization. 
 
@@ -138,9 +138,9 @@ curl -s https://mcr.microsoft.com/v2/dts/dts-emulator/tags/list
 
 - **Feature parity:** Some features might not be available in the Durable Task Scheduler backend yet. For example, at the time of writing, the Durable Task Scheduler doesn't support the following features:
 
-    - [Orchestration rewind](../durable/durable-functions-instance-management.md#rewind-instances-preview)
-    - [Extended sessions](../durable/durable-functions-azure-storage-provider.md#extended-sessions)
-    - [Management operations using the Azure Functions Core Tools](../durable/durable-functions-instance-management.md#azure-functions-core-tools)
+    - [Orchestration rewind](../durable-functions-instance-management.md#rewind-instances-preview)
+    - [Extended sessions](../durable-functions-azure-storage-provider.md#extended-sessions)
+    - [Management operations using the Azure Functions Core Tools](../durable-functions-instance-management.md#azure-functions-core-tools)
 
     > [!NOTE]
     > Feature availability is subject to change as the Durable Task Scheduler backend approaches general availability. To report problems or request new features, submit an issue in the [Durable Task Scheduler samples GitHub repository](https://github.com/Azure-Samples/Durable-Task-Scheduler/).

articles/azure-functions/durable/durable-task-scheduler/quickstart-durable-task-scheduler.md

@@ -2,55 +2,55 @@
 title: "Quickstart: Set a durable functions app to use Azure Functions durable task scheduler (preview)"
 description: Learn how to configure an existing durable functions app to use Azure Functions durable task scheduler.
 ms.topic: how-to
-ms.date: 04/10/2025
+ms.date: 04/24/2025
 zone_pivot_groups: dts-runtime
 ---
 
 # Quickstart: Set a durable functions app to use Azure Functions durable task scheduler (preview)
 
-Write stateful functions in a serverless environment using durable functions, a feature of [Azure Functions](../functions-overview.md). Scenarios where durable functions is useful include orchestrating microservices and workflows, stateful patterns like fan-out/fan-in, and long-running tasks.  
+Write stateful functions in a serverless environment using durable functions, a feature of [Azure Functions](../../functions-overview.md). Scenarios where durable functions is useful include orchestrating microservices and workflows, stateful patterns like fan-out/fan-in, and long-running tasks.  
 
-Durable functions supports several [storage providers](../durable/durable-functions-storage-providers.md), also known as *backends*, for storing orchestration and entity runtime state. 
+Durable functions supports several [storage providers](../durable-functions-storage-providers.md), also known as *backends*, for storing orchestration and entity runtime state. 
 
-In this quickstart, you configure a durable functions app to use the [durable task scheduler](../durable/durable-functions-storage-providers.md#dts) as the backend and deploy the app to Azure using **Visual Studio Code**. 
+In this quickstart, you configure a durable functions app to use the [durable task scheduler](../durable-functions-storage-providers.md#dts) as the backend and deploy the app to Azure using **Visual Studio Code**. 
 
 > [!NOTE]
 >
-> - To learn more about the benefit of using durable task scheduler, see [durable functions backend providers overview](../durable/durable-functions-storage-providers.md).
+> - To learn more about the benefit of using durable task scheduler, see [durable functions backend providers overview](../durable-functions-storage-providers.md).
 >
-> - Migrating [task hub data](../durable/durable-functions-task-hubs.md) across backend providers currently isn't supported. Function apps that have existing runtime data need to start with a fresh, empty task hub after they switch to the durable task scheduler. Similarly, the task hub contents that are created by using the scheduler resource can't be preserved if you switch to a different backend provider.
+> - Migrating [task hub data](../durable-functions-task-hubs.md) across backend providers currently isn't supported. Function apps that have existing runtime data need to start with a fresh, empty task hub after they switch to the durable task scheduler. Similarly, the task hub contents that are created by using the scheduler resource can't be preserved if you switch to a different backend provider.
 >
 > - Durable task scheduler currently only supports durable functions running on **Functions Premium** and **App Service** plans. 
 
 ## Prerequisites
 
 This quickstart assumes you already have an Azure Functions project on your local computer with:
 - Durable functions added to your project including:
-  - An [orchestrator function](../durable/durable-functions-bindings.md#orchestration-trigger). 
-  - A [client function](../durable/durable-functions-bindings.md#orchestration-client) that triggers the durable functions app.
+  - An [orchestrator function](../durable-functions-bindings.md#orchestration-trigger). 
+  - A [client function](../durable-functions-bindings.md#orchestration-client) that triggers the durable functions app.
 - The project configured for local debugging.
 
 If you don't meet these prerequisites, we recommend that you begin with one of the following quickstarts to set up a local Functions project:
 
 ::: zone pivot="csharp"  
 
-- [Create a durable functions app - C#](../durable/durable-functions-isolated-create-first-csharp.md)
+- [Create a durable functions app - C#](../durable-functions-isolated-create-first-csharp.md)
 
 ::: zone-end 
 
 ::: zone pivot="other"  
 
-- [Create a durable functions app - JavaScript](../durable/quickstart-js-vscode.md)
-- [Create a durable functions app - Python](../durable/quickstart-python-vscode.md)
-- [Create a durable functions app - PowerShell](../durable/quickstart-powershell-vscode.md)
-- [Create a durable functions app - Java](../durable/quickstart-java.md)
+- [Create a durable functions app - JavaScript](../quickstart-js-vscode.md)
+- [Create a durable functions app - Python](../quickstart-python-vscode.md)
+- [Create a durable functions app - PowerShell](../quickstart-powershell-vscode.md)
+- [Create a durable functions app - Java](../quickstart-java.md)
 
 ::: zone-end 
 
 You also need:
 - [Docker](https://docs.docker.com/engine/install/) installed to run the durable task scheduler emulator. 
-- [Azurite](../../storage/common/storage-use-azurite.md#run-azurite) installed.
-- An [HTTP test tool](../functions-develop-local.md#http-test-tools) that keeps your data secure.
+- [Azurite](../../../storage/common/storage-use-azurite.md#run-azurite) installed.
+- An [HTTP test tool](../../functions-develop-local.md#http-test-tools) that keeps your data secure.
 
 ## Add the durable task scheduler package
 
@@ -162,7 +162,7 @@ Get the durable task scheduler emulator port number in [the next step](#set-up-d
 
    :::image type="content" source="media/quickstart-durable-task-scheduler/function-list.png" alt-text="Screenshot of functions listed when running app locally.":::
 
-1. Start an orchestration instance by sending an HTTP `POST` request to the URL endpoint using the [HTTP test tool](../functions-develop-local.md#http-test-tools) you chose. 
+1. Start an orchestration instance by sending an HTTP `POST` request to the URL endpoint using the [HTTP test tool](../../functions-develop-local.md#http-test-tools) you chose. 
 
 1. Copy the URL value for `statusQueryGetUri` and paste it in your browser's address bar. You should see the status on the orchestration instance:
 
@@ -206,7 +206,7 @@ Resource deployment could take around 15 to 20 minutes. Once that is finished, y
 
 ### Deploy your function app to Azure
 
-[!INCLUDE [functions-publish-project-vscode](../../../includes/functions-deploy-project-vs-code.md)]
+[!INCLUDE [functions-publish-project-vscode](../../../../includes/functions-deploy-project-vs-code.md)]
 
 #### Apps on Functions Premium plan