Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into nw-flowlogs

Author: halkazwini

.openpublishing.redirection.json

@@ -3874,6 +3874,11 @@
       "redirect_url": "/azure/firewall/ftp-support",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/firewall/long-running-sessions.md",
+      "redirect_url": "/azure/firewall/tcp-session-behavior",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/firewall/diagnostic-logs.md",
       "redirect_url": "/azure/firewall/monitor-firewall",

articles/analysis-services/analysis-services-manage-users.md

@@ -31,6 +31,9 @@ Power BI Desktop, Visual Studio, and SSMS support Active Directory Universal Aut
 
 If signing in to Azure by using a Windows account, and Universal Authentication is not selected or available (Excel), [Active Directory Federation Services (AD FS)](/windows-server/identity/ad-fs/deployment/how-to-connect-fed-azure-adfs) is required. With Federation, Microsoft Entra ID and Microsoft 365 users are authenticated using on-premises credentials and can access Azure resources.
 
+> [!NOTE]
+> When creating a token with custom logic, it must either be a user token or an application service principal and the audience must be set to exactly `https://*.asazure.windows.net`
+
 ### SQL Server Management Studio (SSMS)
 
 Azure Analysis Services servers support connections from [SSMS V17.1](/sql/ssms/download-sql-server-management-studio-ssms) and higher by using Windows Authentication, Active Directory Password Authentication, and Active Directory Universal Authentication. In general, it's recommended you use Active Directory Universal Authentication because:

articles/api-management/api-management-capacity.md

@@ -123,10 +123,6 @@ Access metrics in the portal to understand how much capacity is used over time.
 > [!IMPORTANT]
 > Currently, the **CPU Percentage of Gateway** and **Memory Consumption of Gateway** metrics also appear in the portal for instances in classic tiers. However, they're not supported for use in classic tiers and show a value of 0.
 
-
-
-
-
 > [!NOTE]
 > * You can set a [metric alert](api-management-howto-use-azure-monitor.md#set-up-an-alert-rule) to let you know when something unexpected is happening. For example, get notifications when your API Management instance has exceeded its expected peak capacity for more than 20 minutes.
 > * You can use Azure Monitor [autoscaling](api-management-howto-autoscale.md) to automatically add an Azure API Management unit. Scaling operation can take around 30 minutes, so you should plan your rules accordingly.  
@@ -146,8 +142,11 @@ Use capacity metrics for making decisions whether to scale an API Management ins
 >[!TIP]  
 > If you are able to estimate your traffic beforehand, test your API Management instance on workloads you expect. You can increase the request load on your tenant gradually and monitor the value of the capacity metric that corresponds to your peak load. Follow the steps from the previous section to use Azure portal to understand how much capacity is used at any given time.
 
+> [!IMPORTANT]
+> When defining autoscaling rules, make sure to avoid autoscaling flapping that will cause a scale in/scale out loop. To learn more, we recommend reading [Azure Monitor Autoscale's guidance around flapping](/azure/azure-monitor/autoscale/autoscale-flapping).
+
 ## Related content
 
 - [Upgrade and scale an Azure API Management service instance](upgrade-and-scale.md)
 - [Automatically scale an Azure API Management instance](api-management-howto-autoscale.md)
-- [Plan and manage costs for API Management](plan-manage-costs.md)
+- [Plan and manage costs for API Management](plan-manage-costs.md)

articles/app-service/media/troubleshoot-diagnostic-logs/diagnostic-settings-page.png

@@ -5,7 +5,7 @@ author: Muksvso
 ms.author: mubatra
 ms.service: azure-app-configuration
 ms.topic: how-to 
-ms.date: 11/15/2023
+ms.date: 03/19/2025
 ---
 
 # Manage and use snapshots
@@ -96,8 +96,8 @@ Edit the call to the `AddAzureAppConfiguration` method, which is often found in
 ```csharp
 configurationBuilder.AddAzureAppConfiguration(options =>
 {
-    options.Connect(Environment.GetEnvironmentVariable("ConnectionString"));
-
+    string endpoint = Environment.GetEnvironmentVariable("Endpoint"); 
+    options.Connect(new Uri(endpoint), new DefaultAzureCredential());
     // Select an existing snapshot by name. This will add all of the key-values from the snapshot to this application's configuration.
     options.SelectSnapshot("SnapshotName");
 

articles/app-service/overview-managed-identity.md

@@ -7,13 +7,13 @@ ms.devlang: csharp
 author: maud-lv
 ms.topic: conceptual
 ms.custom: devx-track-csharp
-ms.date: 02/20/2024
+ms.date: 03/19/2025
 ms.author: malev
 
 ---
 # Use labels to provide per-environment configuration values.
 
-Many applications need to use different configurations for different environments. Suppose that an application has a configuration value that defines the connection string to use for its back-end database. The application developers use a different database from the one used in production. The database connection string that the application uses must change as the application moves from development to production.
+Many applications need to use different configurations for different environments. Suppose that an application has a configuration value that defines the endpoint to use for its back-end database. The application developers use a different database from the one used in production. The database endpoint that the application uses must change as the application moves from development to production.
 
 In Azure App Configuration, you can use *labels* to define different values for the same key. For example, you can define a single key with different values for development and production. You can specify which label to load when connecting to App Configuration.
 
@@ -47,17 +47,15 @@ var builder = WebApplication.CreateBuilder(args);
 
 builder.Configuration.AddAzureAppConfiguration(options =>
     {
-            options.Connect(builder.Configuration.GetConnectionString("AppConfig"))
-                // Load configuration values with no label
-                .Select(KeyFilter.Any, LabelFilter.Null)
-                // Override with any configuration values specific to current hosting env
-                .Select(KeyFilter.Any, builder.Environment.EnvironmentName);
+        string endpoint = Environment.GetEnvironmentVariable("Endpoint");
+        options.Connect(new Uri(endpoint), new DefaultAzureCredential())
+               // Load configuration values with no label
+               .Select(KeyFilter.Any, LabelFilter.Null)
+               // Override with any configuration values specific to current hosting env
+               .Select(KeyFilter.Any, builder.Environment.EnvironmentName);
     });
 ```
 
-> [!IMPORTANT]
-> The preceding code snippet uses the Secret Manager tool to load App Configuration connection string. For information storing the connection string using the Secret Manager, see [Quickstart for Azure App Configuration with ASP.NET Core](quickstart-aspnet-core-app.md).
-
 The `Select` method is called twice. The first time, it loads configuration values with no label. Then, it loads configuration values with the label corresponding to the current environment. These environment-specific values override any corresponding values with no label. You don't need to define environment-specific values for every key. If a key doesn't have a value with a label corresponding to the current environment, it uses the value with no label.
 
 ## Test in different environments

articles/app-service/troubleshoot-diagnostic-logs.md

@@ -72,38 +72,17 @@ Install the latest version of the [Microsoft.Azure.Functions.Worker.Extensions.D
 
 ::: zone pivot="other"  
 
-Until the durable task scheduler package is added to the extension bundles, you need to manually install the latest version of these packages using [Azure Functions Core Tools](../../functions-run-local.md#install-the-azure-functions-core-tools):
-  - [Microsoft.Azure.WebJobs.Extensions.DurableTask.AzureManaged](https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Extensions.DurableTask.AzureManaged/)
-  - [Microsoft.Azure.WebJobs.Extensions.DurableTask](https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Extensions.DurableTask)
+In host.json, update the `extensionBundle` property to use the preview version that contains the durable task scheduler package:
 
-For example: 
-```bash
-func extensions install --package Microsoft.Azure.WebJobs.Extensions.DurableTask.AzureManaged --version 0.4.2-alpha
-```
-```bash
-func extensions install --package Microsoft.Azure.WebJobs.Extensions.DurableTask --version 3.0.4
-```
-
-These commands should automatically generate a *extensions.csproj* file. If the package references aren't added to the file, check to ensure that `net8.0` is the target framework and run the commands again. The file should have content similar to the following example:
-
-```xml
-<Project Sdk="Microsoft.NET.Sdk">
-  <PropertyGroup>
-    <TargetFramework>net8.0</TargetFramework>
-	<WarningsAsErrors></WarningsAsErrors>
-	<DefaultItemExcludes>**</DefaultItemExcludes>
-  </PropertyGroup>
-  <ItemGroup>
-    <PackageReference Include="Microsoft.Azure.WebJobs.Extensions.DurableTask" Version="3.0.4" />
-    <PackageReference Include="Microsoft.Azure.WebJobs.Extensions.DurableTask.AzureManaged" Version="0.4.2-alpha" />
-    <PackageReference Include="Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator" Version="1.1.3" />
-  </ItemGroup>
-</Project>
+```json
+{
+  "extensionBundle": {
+    "id": "Microsoft.Azure.Functions.ExtensionBundle.Preview",
+    "version": "[4.29.0, 5.0.0)"
+  }
+}
 ```
 
-> [!NOTE]
-> Remember to remove the reference to extension bundles in `host.json`. 
-
 ::: zone-end 
 
 ## Update host.json
@@ -134,7 +113,7 @@ Add connection information for local development:
   "Values": {
     "FUNCTIONS_WORKER_RUNTIME": "<DEPENDENT ON YOUR PROGRAMMING LANGUAGE>",
     "AzureWebJobsStorage": "UseDevelopmentStorage=true",
-    "DURABLE_TASK_SCHEDULER_CONNECTION_STRING": "Endpoint=http://localhost:<port number>;Authentication=None",
+    "DURABLE_TASK_SCHEDULER_CONNECTION_STRING": "Endpoint=http://localhost:8080;Authentication=None",
     "TASKHUB_NAME": "default"
   }
 }
@@ -153,23 +132,20 @@ Get the durable task scheduler emulator port number in [the next step](#set-up-d
 1. Run the emulator.
 
    ```bash
-   docker run -itP mcr.microsoft.com/dts/dts-emulator:v0.0.5
+   docker run -d -p 8080:8080 -p 8082:8082 mcr.microsoft.com/dts/dts-emulator:v0.0.5
    ```
 
    The following output indicates the emulator started successfully.
 
      :::image type="content" source="media/quickstart-durable-task-scheduler/emulator-started.png" alt-text="Screenshot showing emulator started successfully on terminal.":::
 
-1. Make note of the ports exposed on Docker desktop. These static ports are exposed by the container and mapped dynamically by default. The scheduler exposes multiple ports for different purposes:  
+1. Make note of the ports exposed on Docker desktop. The scheduler exposes multiple ports for different purposes:  
 
    - `8080`: gRPC endpoint that allows an app to connect to the scheduler
    - `8082`: Endpoint for durable task scheduler dashboard
 
    :::image type="content" source="media/quickstart-durable-task-scheduler/docker-ports.png" alt-text="Screenshot of ports on Docker.":::
 
-1. Update the connection string in *local.settings.json* with the gRPC endpoint port number. 
-
-   In the previous example, port `55000` is mapped to the gRPC `8080` endpoint, so the connection string should be `Endpoint=http://localhost:55000;Authentication=None`.
 
 ## Test locally 
 
@@ -210,9 +186,7 @@ Get the durable task scheduler emulator port number in [the next step](#set-up-d
      }
    ```
 
-1. To view more details about the orchestration instance, go to the Docker desktop app and click the `8082` link to access the durable task scheduler dashboard. 
-
-   :::image type="content" source="media/quickstart-durable-task-scheduler/docker-ports.png" alt-text="Screenshot of ports on Docker.":::
+1. To view more details about the orchestration instance, go to **http://localhost:8082/** access the durable task scheduler dashboard. 
 
 1. Click on the *default* task hub to see its dashboard. 
 

articles/azure-app-configuration/howto-create-snapshots.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 03/26/2025
+ms.date: 03/27/2025
 ms.author: anfdocs
 ms.custom: references_regions
 ---
@@ -23,20 +23,16 @@ Creating a capacity pool enables you to create volumes within it.
     >[!IMPORTANT]
     >To create a 1-TiB capacity pool with a tag, you must use API versions `2023-07-01_preview` to `2024-01-01_preview` or stable releases from `2024-01-01`.
 * The Standard, Premium, and Ultra service levels are generally available (GA). No registration is required. 
-* The **Flexible** service level is currently in preview. Before creating a Flexible service level capacity pool, you must first register the feature:  
-
-    1. Register the feature: 
-        ```azurepowershell-interactive
-        Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFFlexibleServiceLevel
-        ```
-    2. Check the status of the feature registration: 
-        > [!NOTE]
-        > The **RegistrationState** may be in the `Registering` state for up to 60 minutes before changing to `Registered`. Wait until the status is **Registered** before continuing.
-        ```azurepowershell-interactive
-        Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFFlexibleServiceLevel
-        ```
-        You can also use [Azure CLI commands](/cli/azure/feature) `az feature register` and `az feature show` to register the feature and display the registration status. 
+* The **Flexible** service level is currently in preview. You must submit a waitlist request to access the Flexible service level by using [the request form](https://aka.ms/ANFFlexibleSLpreviewsignup). After you submit the waitlist request, it can take approximately one week to enable the feature.
+    
+    Check the status of feature registration with the command:
 
+    ```azurepowershell-interactive
+    Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFFlexibleServiceLevel
+    ```
+    
+    You can also use [Azure CLI commands](/cli/azure/feature) `az feature show` to register the feature and display the registration status. 
+    
 ### <a name="regions"></a> Supported regions for the Flexible service level
 
 >[!NOTE]