Merge branch 'main' into release-migrate-new-structure

Author: v-alje

.openpublishing.redirection.json

@@ -6740,7 +6740,7 @@
       "redirect_document_id": false
     },
     {
-      "source_path": "articles/work-with-styx-objects-and-indicators.md",
+      "source_path": "articles/sentinel/work-with-styx-objects-and-indicators.md",
       "redirect_url": "/azure/sentinel/work-with-styx-objects-indicators",
       "redirect_document_id": false
     },

articles/app-service/tutorial-sidecar-local-small-language-model.md

@@ -75,6 +75,7 @@ This section assumes that you already built a Phi-3 Docker image and uploaded it
     - **Image type**: **Public**
     - **Registry server URL**: *mcr.microsoft.com*
     - **Image and tag**: *appsvc/docs/sidecars/sample-experiment:phi3-python-1.0*
+    - **Port**: *8000*
 1. Select **Apply**.
 
 ## 4. Verify the running app
@@ -144,4 +145,4 @@ To upload the built image to Azure Container Registry, see [Push your first imag
 
 ## More resources
 
-- [Try out sidecars in this guided lab](https://mslabs.cloudguides.com/guides/Sidecars%20in%20Azure%20App%20Service)
+- [Try out sidecars in this guided lab](https://mslabs.cloudguides.com/guides/Sidecars%20in%20Azure%20App%20Service)

articles/application-gateway/ingress-controller-install-existing.md

@@ -6,7 +6,7 @@ author: greg-lindsay
 ms.service: azure-application-gateway
 ms.custom: devx-track-arm-template, devx-track-azurecli
 ms.topic: how-to
-ms.date: 2/28/2025
+ms.date: 4/4/2025
 ms.author: greglin
 ---
 
@@ -264,15 +264,15 @@ Use [Cloud Shell](https://shell.azure.com/) to install the AGIC Helm package:
 1. Install the Helm chart with the `helm-config.yaml` configuration from the previous step:
 
     ```bash
-    helm install agic-controller oci://mcr.microsoft.com/azure-application-gateway/charts/ingress-azure --version 1.8.0 -f helm-config.yaml
+    helm install agic-controller oci://mcr.microsoft.com/azure-application-gateway/charts/ingress-azure --version 1.8.1 -f helm-config.yaml
     ```
 
     Alternatively, you can combine `helm-config.yaml` and the Helm command in one step:
 
     ```bash
     helm install oci://mcr.microsoft.com/azure-application-gateway/charts/ingress-azure \
          --name agic-controller \
-         --version 1.8.0 \
+         --version 1.8.1 \
          --namespace default \
          --debug \
          --set appgw.name=applicationgatewayABCD \

articles/application-gateway/ingress-controller-install-new.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: azure-application-gateway
 ms.topic: how-to
-ms.date: 10/15/2024
+ms.date: 4/4/2025
 ms.author: greglin
 ---
 
@@ -288,7 +288,7 @@ If you use [Cloud Shell](https://shell.azure.com/), you don't need to install He
 1. Install the AGIC package:
 
     ```bash
-    helm install agic-controller oci://mcr.microsoft.com/azure-application-gateway/charts/ingress-azure --version 1.8.0 -f helm-config.yaml
+    helm install agic-controller oci://mcr.microsoft.com/azure-application-gateway/charts/ingress-azure --version 1.8.1 -f helm-config.yaml
     ```
 
 ## Install a sample app

articles/application-gateway/ingress-controller-update-ingress-controller.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: azure-application-gateway
 ms.topic: how-to
-ms.date: 2/28/2025
+ms.date: 4/4/2025
 ms.author: greglin
 ---
 
@@ -39,7 +39,7 @@ You can upgrade the Azure Application Gateway Ingress Controller (AGIC) for Kube
     helm upgrade \
         odd-billygoat \
         oci://mcr.microsoft.com/azure-application-gateway/charts/ingress-azure \
-        --version 1.8.0
+        --version 1.8.1
     ```
 
 ## Roll back

articles/automation/automation-linux-hrw-install.md

@@ -4,7 +4,7 @@ description: This article tells how to install an agent-based  Hybrid Runbook Wo
 services: automation
 ms.subservice: process-automation
 ms.custom: linux-related-content
-ms.date: 09/09/2024
+ms.date: 04/07/2025
 ms.topic: how-to
 ms.service: azure-automation
 ---
@@ -73,7 +73,7 @@ The minimum requirements for a Linux system and user Hybrid Runbook Worker are:
 | **Required package** | **Description** | **Minimum version**|
 |--------------------- | --------------------- | -------------------|
 |Glibc |GNU C Library| 2.5-12 |
-|Openssl| OpenSSL Libraries | 1.0 (TLS 1.1 and TLS 1.2 are supported)|
+|OpenSSL| OpenSSL Libraries | 1.0 (TLS 1.1 and TLS 1.2 are supported)|
 |Curl | cURL web client | 7.15.5|
 |Python-ctypes | Foreign function library for Python| Python 2.x or Python 3.x are required |
 |PAM | Pluggable Authentication Modules|

articles/automation/extension-based-hybrid-runbook-worker-install.md

@@ -4,7 +4,7 @@ description: This article provides information about deploying the extension-bas
 services: automation
 ms.subservice: process-automation
 ms.custom: devx-track-azurepowershell, devx-track-azurecli, devx-track-bicep, linux-related-content
-ms.date: 02/27/2025
+ms.date: 04/07/2025
 ms.topic: how-to
 #Customer intent: As a developer, I want to learn about extension so that I can efficiently deploy Hybrid Runbook Workers.
 ms.service: azure-automation
@@ -52,7 +52,7 @@ Azure Automation stores and manages runbooks and then delivers them to one or mo
 | Required package | Description | Minimum version |
 |--------------------- | --------------------- | ------------------- |
 | Glibc |GNU C Library | 2.5-12 |
-| Openssl | OpenSSL Libraries | 1.0 (TLS 1.1 and TLS 1.2 are supported) |
+| OpenSSL | OpenSSL Libraries | 1.0 (TLS 1.1 and TLS 1.2 are supported) |
 | Curl | cURL web client | 7.15.5 |
 | Python-ctypes | Foreign function library for Python | Python 2.x or Python 3.x are required |
 | PAM | Pluggable Authentication Modules |       |

articles/automation/migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md

@@ -3,7 +3,7 @@ title: Migrate an existing agent-based hybrid workers to extension-based-workers
 description: This article provides information on how to migrate an existing agent-based hybrid worker to extension based workers.
 services: automation
 ms.subservice: process-automation
-ms.date: 02/27/2025
+ms.date: 04/07/2025
 ms.custom: devx-track-azurecli, devx-track-bicep, devx-track-azurepowershell
 ms.topic: how-to
 #Customer intent: As a developer, I want to learn about extension so that I can efficiently migrate agent based hybrid workers to extension based workers.
@@ -69,7 +69,7 @@ The purpose of the Extension-based approach is to simplify the installation and
 | Required package | Description | Minimum version |
 |--------------------- | --------------------- | ------------------- |
 | Glibc |GNU C Library | 2.5-12 |
-| Openssl | OpenSSL Libraries | 1.0 (TLS 1.1 and TLS 1.2 are supported) |
+| OpenSSL | OpenSSL Libraries | 1.0 (TLS 1.1 and TLS 1.2 are supported) |
 | Curl | cURL web client | 7.15.5 |
 | Python-ctypes | Foreign function library for Python | Python 2.x or Python 3.x are required |
 | PAM | Pluggable Authentication Modules |       |

articles/azure-app-configuration/feature-management-javascript-reference.md

@@ -9,7 +9,7 @@ ms.service: azure-app-configuration
 ms.devlang: javascript
 ms.custom: devx-track-javascript
 ms.topic: tutorial
-ms.date: 01/20/2025
+ms.date: 04/06/2025
 zone_pivot_groups: feature-management
 #Customer intent: I want to control feature availability in my app by using the Feature Management library.
 ---
@@ -125,11 +125,40 @@ import { load } from "@azure/app-configuration-provider";
 import { ConfigurationMapFeatureFlagProvider, FeatureManager } from "@microsoft/feature-management";
 const appConfig = await load("YOUR_APP-CONFIG-ENDPOINT",
                              new DefaultAzureCredential(), // For more information: https://learn.microsoft.com/javascript/api/overview/azure/identity-readme
-                             {featureFlagOptions: { enabled: true }}); // load feature flags from Azure App Configuration service
+                             { featureFlagOptions: { enabled: true } }); // load feature flags from Azure App Configuration service
 const featureProvider = new ConfigurationMapFeatureFlagProvider(appConfig);
 const featureManager = new FeatureManager(featureProvider);
 ```
 
+#### Use Azure App Configuration to dynamically control the state of the feature flag
+
+Azure App Configuration is not only a solution to externalize storage and centralized management of your feature flags, but also it allows to dynamically turn on/off the feature flags.
+
+To enable the dynamic refresh for feature flags, you need to configure the `refresh` property of `featureFlagOptions` when loading feature flags from Azure App Configuration.
+
+``` typescript
+const appConfig = await load("YOUR_APP-CONFIG-ENDPOINT",  new DefaultAzureCredential(),  { 
+    featureFlagOptions: { 
+        enabled: true,
+        refresh: {
+            enabled: true, // enable the dynamic refresh for feature flags
+            refreshIntervalInMs: 30_000
+        }
+    } 
+});
+
+const featureProvider = new ConfigurationMapFeatureFlagProvider(appConfig);
+const featureManager = new FeatureManager(featureProvider);
+```
+
+You need to call the `refresh` method to get the latest feature flag state.
+
+```typescript
+await appConfig.refresh(); // Refresh to get the latest feature flags
+const isBetaEnabled = await featureManager.isEnabled("Beta");
+console.log(`Beta is enabled: ${isBetaEnabled}`);
+```
+
 > [!NOTE]
 > For more information about how to use feature management library with Azure App Configuration, please go to the [quickstart](./quickstart-javascript.md).
 
@@ -276,10 +305,14 @@ The following snippet demonstrates how to implement a customized feature filter
     }
 ```
 
-You need to register the custom filter when creating the `FeatureManager`.
+You need to register the custom filter under the `customFilters` property of the `FeatureManagerOptions` object passed to the `FeatureManager` constructor.
 
 ```typescript
-const featureManager = new FeatureManager(ffProvider, {customFilters: [new MyCriteriaFilter()]});
+const featureManager = new FeatureManager(ffProvider, {
+    customFilters: [
+        new MyCriteriaFilter() // add custom feature filters under FeatureManagerOptions.customFilters
+    ]
+});
 ```
 
 ### Parameterized feature filters
@@ -307,7 +340,7 @@ The feature filter can take advantage of the context that is passed in when `isE
 
 ## Built-in feature filters
 
-There are two feature filters that come with the `FeatureManagement` package: `TimeWindowFilter`, and `TargetingFilter`.
+There are two feature filters that come with the `FeatureManagement` package: `TimeWindowFilter` and `TargetingFilter`. All built-in feature filters will be added by default when constructing `FeatureManager`.
 
 Each of the built-in feature filters has its own parameters. Here's the list of feature filters along with examples.
 

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

@@ -86,15 +86,20 @@ public class MyOrchestration : TaskOrchestrator<string, string>
 ```
 
 ## Durable entities
-Durable entities are supported in the .NET isolated worker. See [developer's guide](./durable-functions-dotnet-entities.md).
+
+Durable entities are supported in the .NET isolated worker. For more information, see the [developer's guide](./durable-functions-dotnet-entities.md).
 
 ## Migration guide
 
-This guide assumes you're starting with a .NET Durable Functions 2.x project.
+This process assumes you're starting with a .NET Durable Functions 2.x project running in-process with the Functions host. 
+
+### Migrate your project
+
+The first step is to [migrate your .NET project to the isolated worker process](../migrate-dotnet-to-isolated-model.md). 
 
-### Update your project
+### Update package reference 
 
-The first step is to update your project to [Azure Functions .NET isolated](../migrate-dotnet-to-isolated-model.md). Then, update your Durable Functions NuGet package references.
+After you've migrated your app to use the isolate worker process, you must update your Durable Functions NuGet package to reference the isolated worker-specific package, like in this example:
 
 Old: