Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Learn Build Service GitHub App

.openpublishing.redirection.json

@@ -1,5 +1,10 @@
 {
     "redirections": [
+    {
+      "source_path": "articles/germany/index.yml",
+      "redirect_url": "/previous-versions/azure/germany/index",
+      "redirect_document_id": false
+    },
         {
             "source_path_from_root": "/articles/internet-analyzer/internet-analyzer-cli.md",
             "redirect_url": "/previous-versions/azure/internet-analyzer/internet-analyzer-cli",

articles/application-gateway/application-gateway-autoscaling-zone-redundant.md

@@ -15,6 +15,11 @@ ms.custom: fasttrack-edit, references_regions
 Application Gateway and WAF can be configured to scale in two modes:
 
 - **Autoscaling** - With autoscaling enabled, the Application Gateway and WAF v2 SKUs scale out or in based on application traffic requirements. This mode offers better elasticity to your application and eliminates the need to guess the application gateway size or instance count. This mode also allows you to save cost by not requiring the gateway to run at peak-provisioned capacity for expected maximum traffic load. You must specify a minimum and optionally maximum instance count. Minimum capacity ensures that Application Gateway and WAF v2 don't fall below the minimum instance count specified, even without traffic. Each instance is roughly equivalent to 10 more reserved Capacity Units. Zero signifies no reserved capacity and is purely autoscaling in nature. You can also optionally specify a maximum instance count, which ensures that the Application Gateway doesn't scale beyond the specified number of instances. You are only billed for the amount of traffic served by the Gateway. The instance counts can range from 0 to 125. The default value for maximum instance count is 10 if not specified.
+
+
+> [!NOTE]
+> If the maximum instance count is updated to a value less than the current instance count, the new setting will not take immediate effect. The newly updated maximum will only be enforced after a scale-in operation brings  the  current count below newly updated maximum count. If the scale-in operation does not occur because the autoscaling  scale in thresholds are not met, the new maximum setting will not be applied.
+
 - **Manual** - You can also choose Manual mode where the gateway doesn't autoscale. In this mode, if there's more traffic than what Application Gateway or WAF can handle, it could result in traffic loss. With manual mode, specifying instance count is mandatory. Instance count can vary from 1 to 125 instances.
 
 ## Autoscaling and High Availability

articles/application-gateway/configuration-infrastructure.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: application-gateway
 ms.topic: conceptual
-ms.date: 04/25/2024
+ms.date: 05/01/2024
 ms.author: greglin
 ---
 
@@ -63,6 +63,8 @@ It's possible to change the subnet of an existing Application Gateway instance w
 
 The virtual network resource supports [DNS server](../virtual-network/manage-virtual-network.yml#view-virtual-networks-and-settings-using-the-azure-portal) configuration, which allows you to choose between Azure-provided default or custom DNS servers. The instances of your application gateway also honor this DNS configuration for any name resolution. After you change this setting, you must restart ([Stop](/powershell/module/az.network/Stop-AzApplicationGateway) and [Start](/powershell/module/az.network/start-azapplicationgateway)) your application gateway for these changes to take effect on the instances.
 
+When an instance of your Application Gateway issues a DNS query, it uses the value from the server that responds first.
+
 > [!NOTE]
 > If you use custom DNS servers in the Application Gateway virtual network, the DNS server must be able to resolve public internet names. Application Gateway requires this capability.
 

articles/application-gateway/how-application-gateway-works.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: application-gateway
 ms.topic: conceptual
-ms.date: 8/22/2023
+ms.date: 05/01/2024
 ms.author: greglin
 ---
 
@@ -58,8 +58,8 @@ When a backend pool's server is configured with a Fully Qualified Domain Name (F
 The Application Gateway retains this cached information for the period equivalent to that DNS record's TTL (time to live) and performs a fresh DNS lookup once the TTL expires. If a gateway detects a change in IP address for its subsequent DNS query, it will start routing the traffic to this updated destination. In case of problems such as the DNS lookup failing to receive a response or the record no longer exists, the gateway continues to use the last-known-good IP address(es). This ensures minimal impact on the data path.
 
 > [!IMPORTANT]
->  * When using custom DNS servers with Application Gateway's Virtual Network, it is crucial that all servers are identical and respond consistently with the same DNS values.
->  * Users of on-premises custom DNS servers must ensure connectivity to Azure DNS through [Azure DNS Private Resolver](../dns/private-resolver-hybrid-dns.md) (recommended) or DNS forwarder VM when using a Private DNS zone for Private endpoint.
+>  * When using custom DNS servers with Application Gateway's Virtual Network, it is important that all servers respond consistently with the same DNS values. When an instance of your Application Gateway issues a DNS query, it uses the value from the server that responds first.
+>  * Users of on-premises custom DNS servers must ensure connectivity to Azure DNS through [Azure DNS Private Resolver](../dns/private-resolver-hybrid-dns.md) (recommended) or a DNS forwarder VM when using a Private DNS zone for Private endpoint.
 
 ### Modifications to the request
 

articles/azure-arc/data/create-data-controller-direct-prerequisites.md

@@ -155,4 +155,4 @@ For instructions, see [Create a log analytics workspace](upload-logs.md#create-a
 
 ## Create Azure Arc data services
 
-After you have completed these prerequisites, you can [Deploy Azure Arc data controller | Direct connect mode](create-data-controller-direct-azure-portal.md).
+After you have completed these prerequisites, you can [Deploy Azure Arc data controller | Direct connect mode - Azure Portal](create-data-controller-direct-azure-portal.md) or [using the Azure CLI](create-data-controller-direct-cli.md).

articles/azure-arc/data/validation-program.md

@@ -129,9 +129,7 @@ The conformance tests run as part of the Azure Arc-enabled Data services validat
 
 These tests verify that the product is compliant with the requirements of running and operating data services. This process helps assess if the product is enterprise ready for deployments.
 
-The tests for data services cover the following in indirectly connected mode
-
-1. Deploy data controller in indirect mode
+1. Deploy data controller in both indirect and direct connect modes (learn more about [connectivity modes](/azure/azure-arc/data/connectivity))
 2. Deploy [SQL Managed Instance enabled by Azure Arc](create-sql-managed-instance.md)
 3. Deploy [Azure Arc-enabled PostgreSQL server](create-postgresql-server.md)
 

articles/azure-functions/durable/TOC.yml

@@ -12,6 +12,8 @@
     href: durable-functions-versions.md
   - name: Durable Functions for .NET isolated
     href: durable-functions-dotnet-isolated-overview.md
+  - name: Durable Functions packages
+    href: durable-functions-packages.md
 - name: Quickstarts
   expanded: true
   items:

articles/azure-functions/durable/durable-functions-isolated-create-first-csharp.md

@@ -154,8 +154,11 @@ Azure Functions Core Tools lets you run an Azure Functions project locally. You'
 
 1. To test your function, set a breakpoint in the `SayHello` activity function code and press <kbd>F5</kbd> to start the function app project. Output from Core Tools is displayed in the **Terminal** panel.
 
-    > [!NOTE]
-    > For more information on debugging, see [Durable Functions Diagnostics](durable-functions-diagnostics.md#debugging).
+> [!NOTE]
+> For more information on debugging, see [Durable Functions Diagnostics](durable-functions-diagnostics.md#debugging).
+
+> [!NOTE]
+> If you encounter a "No job functions found" error, please [update your Azure Functions Core Tools installation to the latest version](./../functions-core-tools-reference.md). Older versions of core tools do not support .NET isolated.
 
 1. In the **Terminal** panel, copy the URL endpoint of your HTTP-triggered function.
 

articles/azure-functions/durable/durable-functions-overview.md

@@ -13,7 +13,7 @@ zone_pivot_groups: df-languages
 
 # What are Durable Functions?
 
-*Durable Functions* is an extension of [Azure Functions](../functions-overview.md) that lets you write stateful functions in a serverless compute environment. The extension lets you define stateful workflows by writing [*orchestrator functions*](durable-functions-orchestrations.md) and stateful entities by writing [*entity functions*](durable-functions-entities.md) using the Azure Functions programming model. Behind the scenes, the extension manages state, checkpoints, and restarts for you, allowing you to focus on your business logic.
+*Durable Functions* is a feature of [Azure Functions](../functions-overview.md) that lets you write stateful functions in a serverless compute environment. The extension lets you define stateful workflows by writing [*orchestrator functions*](durable-functions-orchestrations.md) and stateful entities by writing [*entity functions*](durable-functions-entities.md) using the Azure Functions programming model. Behind the scenes, the extension manages state, checkpoints, and restarts for you, allowing you to focus on your business logic.
 
 ## <a name="language-support"></a>Supported languages
 

articles/azure-functions/durable/durable-functions-packages.md

@@ -0,0 +1,71 @@
+---
+title: Durable Functions packages
+description: Introduction to the Durable Functions packages, extensions, and SDKs.
+author: davidmrdavid
+ms.topic: overview
+ms.date: 04/09/2024
+ms.author: dajusto
+ms.custom: devdivchpfy22, devx-track-extended-java, devx-track-js, devx-track-python
+ms.reviewer: azfuncdf
+#Customer intent: As a < type of user >, I want < what? > so that < why? >.
+---
+
+# The Durable Functions packages
+
+[Durable Functions](./durable-functions-overview.md) is available in all first-party Azure Functions runtime environments (e.g. .NET, Node, Python, etc.). As such, there are multiple Durable Functions SDKs and packages for each language runtime supported. This guide provides a description of each Durable Functions package from the perspective of each runtime supported.
+
+## .NET in-process
+
+.NET in-process users need to reference the [Microsoft.Azure.WebJobs.Extensions.DurableTask](https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Extensions.DurableTask/) package in their `.csproj` file to use Durable Functions. This package is known as the "WebJobs extension" for Durable Functions.
+
+### The storage providers packages
+
+By default, Durable Functions uses Azure Storage as it's backing store. However, alternative [storage providers](./durable-functions-storage-providers.md) are available as well. To use them, you need to reference their packages _in addition to_ the WebJobs extension in your `.csproj`. Those packages are:
+
+* The Netherite storage provider: [Microsoft.Azure.DurableTask.Netherite.AzureFunctions](https://www.nuget.org/packages/Microsoft.Azure.DurableTask.Netherite.AzureFunctions).
+* The MSSQL storage provider: [Microsoft.DurableTask.SqlServer.AzureFunctions](https://www.nuget.org/packages/Microsoft.DurableTask.SqlServer.AzureFunctions)
+
+> [!TIP]
+> See the [storage providers guide](./durable-functions-storage-providers.md) for complete instructions on how to configure each backend.
+
+> [!NOTE]
+> These are the same packages that non-.NET customers [manually upgrading their extensions](./durable-functions-extension-upgrade.md#manually-upgrade-the-durable-functions-extension) need to manage in their `.csproj`.
+
+## .NET isolated
+
+.NET isolated users need to reference the [Microsoft.Azure.Functions.Worker.Extensions.DurableTask](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.DurableTask/) package in their `.csproj` file to use Durable Functions. This replaces the "WebJobs" extension used in .NET in-process as .NET isolated projects can't directly reference WebJobs packages. This package is known as the "worker extension" for Durable Functions.
+
+### The storage providers packages
+
+In .NET isolated, the alternative [storage providers](./durable-functions-storage-providers.md) are available as well under "worker extension" packages of their own. You need to reference their packages _in addition to_ the worker extension in your `.csproj`. Those packages are:
+
+* The Netherite storage provider: [Microsoft.Azure.Functions.Worker.Extensions.DurableTask.Netherite](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.DurableTask.Netherite).
+* The MSSQL storage provider: [Microsoft.Azure.Functions.Worker.Extensions.DurableTask.SqlServer](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.DurableTask.SqlServer)
+
+> [!TIP]
+> See the [storage providers guide](./durable-functions-storage-providers.md) for complete the instructions on how to configure each backend.
+
+## Extension Bundles users
+
+Users of [Extension Bundles](../functions-bindings-register.md#extension-bundles) (the recommended Azure Functions extension management mechanism for non-.NET users) simply need to install their language runtime's Durable Functions SDK. The SDKs for each first-party language are listed in the table below:
+
+* Node (JavaScript / TypeScript): The [durable-functions](https://www.npmjs.com/package/durable-functions) npm package.
+* Python: The [azure-functions-durable](https://pypi.org/project/azure-functions-durable/) PyPI package.
+* Java: The [durabletask-azure-functions](https://mvnrepository.com/artifact/com.microsoft/durabletask-azure-functions) Maven package.
+* PowerShell: The current GA SDK is built-in to Azure Functions PowerShell language worker, so no installation is needed. See the following _note_ for details.
+
+> [!NOTE]
+> For PowerShell users: we have a [_preview_ SDK standalone package](./durable-functions-powershell-v2-sdk-migration-guide.md) under [AzureFunctions.PowerShell.Durable.SDK](https://www.powershellgallery.com/packages/AzureFunctions.PowerShell.Durable.SDK) in the PowerShell gallery. The latter will be preferred in the future.
+
+## GitHub repositories
+
+Durable Functions is developed in the open as OSS. Users are welcome to contribute to it's development, request features, and to report issues in the appropiate repositories:
+
+* [azure-functions-durable-extension](https://github.com/Azure/azure-functions-durable-extension): For .NET in-process and the Azure Storage storage provider.
+* [durabletask-dotnet](https://github.com/microsoft/durabletask-dotnet): For .NET isolated.
+* [azure-functions-durable-js](https://github.com/Azure/azure-functions-durable-js): For the Node.js SDK.
+* [azure-functions-durable-python](https://github.com/Azure/azure-functions-durable-python): For the Python SDK.
+* [durabletask-java](https://github.com/Microsoft/durabletask-java): For the Java SDK.
+* [azure-functions-durable-powershel](https://github.com/Azure/azure-functions-durable-powershell): For the PowerShell SDK.
+* [durabletask-netherite](https://github.com/microsoft/durabletask-netherite): For the Netherite storage provider.
+* [durabletask-mssql](https://github.com/microsoft/durabletask-mssql): For the MSSQL storage provider.