Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into sdk-managed-identity

Author: pauljewellmsft

articles/api-management/api-management-authenticate-authorize-azure-openai.md

@@ -5,7 +5,7 @@ description: Options to authenticate and authorize to Azure OpenAI APIs using Az
 author: dlepow
 ms.service: azure-api-management
 ms.topic: article
-ms.date: 02/20/2024
+ms.date: 01/23/2025
 ms.author: danlep
 ms.collection: ce-skilling-ai-copilot
 ---
@@ -78,7 +78,7 @@ In this example, the named value in API Management is *openai-api-key*.
 
 ## Authenticate with managed identity
 
-An alternative way to authenticate to an Azure OpenAI API by using a managed identity in Microsoft Entra ID. For background, see
+An alternative and recommended way to authenticate to an Azure OpenAI API is by using a managed identity in Microsoft Entra ID. For background, see
 [How to configure Azure OpenAI Service with managed identity](/azure/ai-services/openai/how-to/managed-identity).
 
 Following are steps to configure your API Management instance to use a managed identity to authenticate requests to an Azure OpenAI API. 

articles/api-management/azure-openai-api-from-specification.md

@@ -5,7 +5,7 @@ ms.service: azure-api-management
 author: dlepow
 ms.author: danlep
 ms.topic: how-to
-ms.date: 05/10/2024
+ms.date: 01/23/2025
 ms.collection: ce-skilling-ai-copilot
 ms.custom: template-how-to, build-2024
 ---
@@ -16,7 +16,7 @@ ms.custom: template-how-to, build-2024
 
 This article shows two options to import an [Azure OpenAI Service](/azure/ai-services/openai/overview) API into an Azure API Management instance as a REST API:
 
-- [Import an Azure OpenAI API directly from Azure OpenAI Service](#option-1-import-api-from-azure-openai-service)
+- [Import an Azure OpenAI API directly from Azure OpenAI Service](#option-1-import-api-from-azure-openai-service) (recommended)
 - [Download and add the OpenAPI specification](#option-2-add-an-openapi-specification-to-api-management) for Azure OpenAI and add it to API Management as an OpenAPI API.
 
 ## Prerequisites

articles/api-management/azure-openai-token-limit-policy.md

@@ -9,7 +9,7 @@ ms.collection: ce-skilling-ai-copilot
 ms.custom:
   - build-2024
 ms.topic: reference
-ms.date: 06/25/2024
+ms.date: 02/18/2025
 ms.author: danlep
 ---
 

articles/api-management/llm-token-limit-policy.md

@@ -8,7 +8,7 @@ ms.service: azure-api-management
 ms.collection: ce-skilling-ai-copilot
 ms.custom:
 ms.topic: reference
-ms.date: 08/08/2024
+ms.date: 02/18/2025
 ms.author: danlep
 ---
 

articles/app-service/includes/deploy-github-actions/deploy-github-actions-openid-connect.md

@@ -6,7 +6,7 @@ ms.custom: devx-track-azurecli
 ms.date: 01/16/2025
 ---
 
-To deploy with OpenID Connect using the managed identity you configured, use the `azure/login@v1` action with the `client-id`, `tenant-id`, and `subscription-id` keys. Reference the GitHub secrets that you created earlier.
+To deploy with OpenID Connect using the managed identity you configured, use the `azure/login@v2` action with the `client-id`, `tenant-id`, and `subscription-id` keys. Reference the GitHub secrets that you created earlier.
 
 # [ASP.NET Core](#tab/aspnetcore)
 
@@ -31,7 +31,7 @@ jobs:
     steps:
       # Checkout the repo
       - uses: actions/checkout@main
-      - uses: azure/login@v1
+      - uses: azure/login@v2
         with:
           client-id: ${{ secrets.AZURE_CLIENT_ID }}
           tenant-id: ${{ secrets.AZURE_TENANT_ID }}
@@ -89,7 +89,7 @@ jobs:
     # checkout the repo
     - uses: actions/checkout@main
     
-    - uses: azure/login@v1
+    - uses: azure/login@v2
       with:
         client-id: ${{ secrets.AZURE_CLIENT_ID }}
         tenant-id: ${{ secrets.AZURE_TENANT_ID }}
@@ -140,7 +140,7 @@ jobs:
 
     steps:
     - uses: actions/checkout@v4
-    - uses: azure/login@v1
+    - uses: azure/login@v2
       with:
         client-id: ${{ secrets.AZURE_CLIENT_ID }}
         tenant-id: ${{ secrets.AZURE_TENANT_ID }}
@@ -240,7 +240,7 @@ jobs:
     - name: 'Checkout GitHub Action' 
       uses: actions/checkout@main
    
-    - uses: azure/login@v1
+    - uses: azure/login@v2
       with:
         client-id: ${{ secrets.AZURE_CLIENT_ID }}
         tenant-id: ${{ secrets.AZURE_TENANT_ID }}
@@ -292,7 +292,7 @@ jobs:
     steps:
     - uses: actions/checkout@v4
     
-    - uses: azure/login@v1
+    - uses: azure/login@v2
       with:
         client-id: ${{ secrets.AZURE_CLIENT_ID }}
         tenant-id: ${{ secrets.AZURE_TENANT_ID }}

articles/app-service/includes/deploy-github-actions/deploy-github-actions-service-principal.md

@@ -6,7 +6,7 @@ ms.custom: devx-track-azurecli
 ms.date: 01/16/2025
 ---
 
-To deploy with the service principal you configured, use the `azure/login@v1` action with the `creds` key and reference the `AZURE_CREDENTIALS` secret that you created earlier.
+To deploy with the service principal you configured, use the `azure/login@v2` action with the `creds` key and reference the `AZURE_CREDENTIALS` secret that you created earlier.
 
 # [ASP.NET Core](#tab/aspnetcore)
 
@@ -27,7 +27,7 @@ jobs:
     steps:
       # Checkout the repo
       - uses: actions/checkout@main
-      - uses: azure/login@v1
+      - uses: azure/login@v2
         with:
           creds: ${{ secrets.AZURE_CREDENTIALS }}
 
@@ -79,7 +79,7 @@ jobs:
     # checkout the repo
     - uses: actions/checkout@main
     
-    - uses: azure/login@v1
+    - uses: azure/login@v2
       with:
         creds: ${{ secrets.AZURE_CREDENTIALS }}
 
@@ -124,7 +124,7 @@ jobs:
 
     steps:
     - uses: actions/checkout@v4
-    - uses: azure/login@v1
+    - uses: azure/login@v2
       with:
         creds: ${{ secrets.AZURE_CREDENTIALS }}
     - name: Set up JDK 1.8
@@ -219,7 +219,7 @@ jobs:
     - name: 'Checkout GitHub Action' 
       uses: actions/checkout@main
    
-    - uses: azure/login@v1
+    - uses: azure/login@v2
       with:
         creds: ${{ secrets.AZURE_CREDENTIALS }}
         
@@ -267,7 +267,7 @@ jobs:
     steps:
     - uses: actions/checkout@v4
     
-    - uses: azure/login@v1
+    - uses: azure/login@v2
       with:
         creds: ${{ secrets.AZURE_CREDENTIALS }}
 

articles/azure-app-configuration/howto-best-practices.md

@@ -89,7 +89,7 @@ You can also make your App Configuration data accessible to your application as
 
 Excessive requests to App Configuration can result in throttling or overage charges. To reduce the number of requests made:
 
-* Increase the refresh interval, especially if your configuration values do not change frequently. Specify a new refresh interval using the [`SetCacheExpiration` method](/dotnet/api/microsoft.extensions.configuration.azureappconfiguration.azureappconfigurationrefreshoptions.setcacheexpiration).
+* Increase the refresh interval, especially if your configuration values do not change frequently. Specify a new refresh interval using the [`SetRefreshInterval` method](/dotnet/api/microsoft.extensions.configuration.azureappconfiguration.azureappconfigurationrefreshoptions.setrefreshinterval).
 
 * Watch a single *sentinel key*, rather than watching individual keys. Refresh all configuration only if the sentinel key changes. See [Use dynamic configuration in an ASP.NET Core app](enable-dynamic-configuration-aspnet-core.md) for an example.
 

articles/azure-compute-fleet/quickstart-create-portal.md

@@ -7,7 +7,7 @@ ms.topic: how-to
 ms.service: azure-compute-fleet
 ms.custom:
   - build-2024
-ms.date: 11/13/2024
+ms.date: 02/19/2025
 ms.reviewer: jushiman
 ---
 
@@ -16,7 +16,7 @@ ms.reviewer: jushiman
 > [!IMPORTANT]
 > Azure Compute Fleet is currently in preview. Previews are made available to you on the condition that you agree to the [supplemental terms of use](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). Some aspects of this feature may change prior to general availability (GA). 
 
-This article steps through using Azure portal to create a Compute Fleet.
+This article steps through using the Azure portal to create a Compute Fleet.
 
 
 ## Log in to Azure
@@ -28,20 +28,25 @@ Sign in to the [Azure portal](https://portal.azure.com).
 
 You can deploy a Compute Fleet with a Windows Server image or Linux image such as RHEL, CentOS, Ubuntu, or SLES.
 
-1. In the Azure portal search bar, search for **Azure Compute Fleet** and select the result under *Marketplace*.
+1. In the Azure portal search bar, search for **Compute Fleet** and select the result under *Marketplace*.
 1. Select **Create** on the **Compute Fleet** page. 
 
 1. In the **Basics** tab, under **Project details**, make sure the correct subscription is selected and create a new resource group called *myFleetResourceGroup*. 
 1. Under **Instance details**, set *myFleet* for your Compute Fleet name.
 1. Select a **Region** that is close to your area.
-1. Select a marketplace image for **Image**. 
+1. Select an option from **Availability zones** or a qualified availability zone will be automatically picked up for you.
+1. Select a **Security type** that is available for a Virtual Machine (VM).
+1. Select a marketplace image for **Image**.
+1. Select **Architecture** for your VM. Available options are `Arm64` or `x64`.  
 1. For **Virtual machine types**, select whether you're deploying Spot VMs, Standard VMs, or both. In this example, we select both. 
-1. Specify 3 to 15 virtual machine (VM) sizes for **Sizes**.
+1. Specify 3 to 15 VM sizes for **Sizes**.
 1. **For Spot fleet deployment:** Under **VM capacity**, specify your target capacity for Spot VM instance count between 1 and 10,000.
-1. **For Standard fleet deployment:** Under **VM capacity**, specify your target capacity for Standard VM instance count between 1 and 10,000. 
+1. **For Standard fleet deployment:** Under **VM capacity**, specify your target capacity for Standard VM instance count between 1 and 10,000.
+1. Select **Allocation strategy** to what factors you would like to prioritize when procuring VM size.
+1. Enter the **Max hourly price per Spot VM (USD)**. Note that Spot VMs above your maximum hourly price will be evicted. 
 
 1. Under **Administrator account** configure the admin username and set up an associated password or SSH public key.
-   - A **Password** must be at least 12 characters long and meet three out of the four following complexity requirements: one lower case character, one upper case character, one number, and one special character. For more information, see [username and password requirements](/azure/virtual-machines/windows/faq#what-are-the-password-requirements-when-creating-a-vm-).
+   - A **Password** must be at least 12 characters long and meet three out of the four following complexity requirements: one lowercase character, one uppercase character, one number, and one special character. For more information, see [username and password requirements](/azure/virtual-machines/windows/faq#what-are-the-password-requirements-when-creating-a-vm-).
    - If you select a Linux OS disk image, you can instead choose **SSH public key**. You can use an existing key or create a new one. In this example, Azure generates a new key pair for us. For more information on generating key pairs, see [create and use SSH keys](/azure/virtual-machines/linux/mac-create-ssh-keys).
 
 1. Select **Next: Networking** to move the networking configuration options. For this quickstart, leave the default networking configurations.

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

@@ -94,7 +94,7 @@ This guide assumes you're starting with a .NET Durable Functions 2.x project.
 
 ### Update your project
 
-The first step is to update your project to [Azure Functions .NET isolated](../migrate-version-3-version-4.md). Then, update your Durable Functions NuGet package references.
+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.
 
 Old:
 

articles/azure-maps/release-notes-map-control.md

@@ -16,7 +16,7 @@ This document contains information about new features and other changes to the M
 
 ## v3 (latest)
 
-### [3.6.0] (CDN: February 18, 2025, npm: TBA)
+### [3.6.0] (CDN: February 18, 2025, npm: February 20, 2025)
 
 #### New features
 * Add a new option `StyleOptions.styleOverrides` which controls the visibility of various map elements, including `countryRegion`, `adminDistrict`, `adminDistrict2`, `buildingFootprint`, and `roadDetails`.
@@ -29,15 +29,15 @@ This document contains information about new features and other changes to the M
 #### Other changes
 * Disable the telemetry by default.
 
-### [3.5.0] (CDN: November 4, 2024, npm: November 7)
+### [3.5.0] (CDN: November 4, 2024, npm: November 7, 2024)
 
 #### New features
 - Add support for fullscreen control.
 
 #### Bug fixes
 - Expose new type on `PolygonExtrusionLayerOptions.fillPattern` to support `DataDrivenPropertyValueSpecification<string>`.
 
-### [3.4.0] (CDN: September 30, 2024, npm: October 2)
+### [3.4.0] (CDN: September 30, 2024, npm: October 2, 2024)
 
 #### New features
 - Add support for PMTiles.