Merge pull request #294994 from MicrosoftDocs/main

2/20/2025 11:00 AM IST Publish

Author: PhilKang0704

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/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.

articles/azure-netapp-files/azacsnap-introduction.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: Phil-Jensen
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 02/01/2025
+ms.date: 02/20/2025
 ms.author: phjensen
 ---
 
@@ -53,6 +53,20 @@ AzAcSnap uses the volume snapshot and replication functionalities in Azure NetAp
 
 AzAcSnap is a single binary. It doesn't need additional agents or plug-ins to interact with the database or the storage (Azure NetApp Files via Azure Resource Manager, and Azure Large Instances via Secure Shell [SSH]).
 
+## Technical articles
+
+The following technical articles describe how to set up AzAcSnap as part of a data protection strategy:
+
+- [Backup and Recovery Guide for SAP HANA on Azure VMs with Azure NetApp Files snapshots by AzAcSnap](https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/manual-recovery-guide-for-sap-hana-on-azure-vms-from-azure/ba-p/3290161)
+- [Backup and Recovery Guide for SAP Oracle 19c on Azure VMs with Azure NetApp Files snapshots by AzAcSnap](https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/manual-recovery-guide-for-sap-oracle-19c-on-azure-vms-from-azure/ba-p/3242408)
+- [Backup and Recovery Guide for SAP Db2 on Azure VMs with Azure NetApp Files snapshots by AzAcSnap](https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/manual-recovery-guide-for-sap-db2-on-azure-vms-from-azure-netapp/ba-p/3865379)
+- [Backup and Recovery Guide for SAP ASE 16.0 on Azure VMs with Azure NetApp Files snapshots by AzAcSnap](https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/sap-ase-16-0-on-azure-netapp-files-for-sap-workloads-on-sles15/ba-p/3729496)
+- [Backup and Recovery Guide for MS SQL Server on Azure VMs with Azure NetApp Files snapshots by AzAcSnap](https://techcommunity.microsoft.com/blog/sapapplications/restoring-an-ms-sql-2022-db-from-a-anf-snapshot/4223716)
+- [Backup and Recovery Guide for SAP HANA on Azure Large Instance from storage snapshots by AzAcSnap](https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/manual-recovery-guide-for-sap-hana-on-azure-large-instance-from/ba-p/3242347)
+- [SAP Oracle 19c System Refresh Guide on Azure VMs using Azure NetApp Files Snapshots with AzAcSnap](https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/sap-oracle-19c-system-refresh-guide-on-azure-vms-using-azure/ba-p/3708172)
+- [Protecting HANA databases configured with HSR on Azure NetApp Files with AzAcSnap](https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/protecting-hana-databases-configured-with-hsr-on-azure-netapp/ba-p/3654620)
+- [Automating SAP system copy operations with Libelle SystemCopy](https://docs.netapp.com/us-en/netapp-solutions-sap/lifecycle/libelle-sc-overview.html)
+
 
 ## Supported databases, operating systems, and Azure platforms
 

articles/backup/azure-file-share-support-matrix.md

@@ -2,7 +2,7 @@
 title: Support Matrix for Azure file share backup by using Azure Backup
 description: Provides a summary of support settings and limitations when backing up Azure file shares.
 ms.topic: reference
-ms.date: 02/03/2025
+ms.date: 02/19/2025
 ms.custom: references_regions, engagement-fy24
 ms.service: azure-backup
 author: jyothisuri
@@ -30,7 +30,7 @@ Azure file shares backup is available in all regions, **except** for Germany Cen
 
 Vaulted backup for Azure Files (preview) is available in the following regions: UK South, UK West, Southeast Asia, East Asia, West Central US, Central US, Central India, North Europe, Australia East, West US, East US, South India, France Central, Canada Central, North Central US, East US 2, Australia Southeast, Germany North, France South, West US 2, Brazil South, Japan West, Germany West Central, Canada East, Korea South, Jio India West, Korea Central, South Africa West, Japan East, Norway East, Switzerland West, Norway West, South Africa North, UAE North, West Europe, Sweden Central, Switzerland North.
 
-Cross Region Restore is currently not supported in Sweden Central, UAE North, Jio India West.
+Cross Region Restore is currently supported in the following regions: Australia East, West US, North Central US, East US, East US2, West US2, South India, Australia Southeast, Brazil South, Canada East, Korea Central, Norway East, South Africa North, Switzerland North, France Central, Germany North, Japan West, Korea South, South Africa West, Switzerland West, Canada Central, France South, Germany West Central,  Japan East, Norway West, West Europe. This feature isn't supported in Sweden Central, UAE North, Jio India West.
 
 Migration of  File shares protected with snapshot backup to vaulted backup is supported in the following regions: UK South, UK West, Southeast Asia, East Asia, West Central US, and India Central.
 

articles/energy-data-services/release-notes.md

@@ -1,8 +1,8 @@
 ---
 title: Release notes for Microsoft Azure Data Manager for Energy
 description: This article provides release notes of Azure Data Manager for Energy releases, improvements, bug fixes, and known issues.
-author: nitinnms
-ms.author: nitindwivedi
+author: bharathim
+ms.author: bselvaraj
 ms.service: azure-data-manager-energy
 ms.topic: conceptual
 ms.date: 09/20/2022
@@ -23,6 +23,26 @@ This page is updated with the details about the upcoming release approximately a
 
 <hr width = 100%>
 
+## February 2025
+### Reservoir DDMS preview 
+Reservoir DDMS (M23 version) is available as a preview feature on Azure Data Manager for Energy Developer tier as a fully integrated offering for customers and partners. See [How to enable Reservoir DDMS (Preview)](how-to-enable-reservoir-ddms.md) for more details.
+
+### Wellbore domain services worker
+Azure Data Manager for Energy now includes support for the Wellbore domain services worker, which enhances Wellbore DDMS performance and scalability when handling large bulk data (> 1 GB). This Python back-end service is used internally by the OSDU&reg; Wellbore Domain Data Management Service (WDDMS). It provides an internal API for accessing wellbore bulk data, facilitating efficient data management and processing. See [ADR: Worker Service for Wellbore Bulk Data Access](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/issues/73) for more details.
+
+### Scale and Performance improvements for seismic workflows
+Azure Data Manager for Energy has implemented performance and scale enhancements to handle ingestion and conversion of seismic datasets with higher number of vertical samples. Additionally, for consuming these datasets via seismic streaming applications, Azure Data Manager for Energy now supports up to 4x higher throughput, allowing a proportional increase in the number of consumers using SDMS APIs.
+
+## November 2024
+### SOC 2 and ISO certification
+Azure Data Manager for Energy is now SOC 2 and ISO compliant, reinforcing our commitment to securely managing sensitive data, building trust, and meeting regulatory requirements. All certifications and compliance reports are available [here](https://servicetrust.microsoft.com/DocumentPage/7adf2d9e-d7b5-4e71-bad8-713e6a183cf3) and will be regularly updated.
+
+### Support for EDS Naturalization DAG (Preview)
+Support for the `eds_naturalization` DAG is now available as a preview feature with the Azure Data Manager for Energy M23 release.
+
+### Create legal tags for restricted COO (Country of Origin)
+OSDU&reg; defines `residencyRisk` for data originating from certain countries in the default configuration [DefaultCountryCode.json](https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/blob/master/legal-core/src/main/resources/DefaultCountryCode.json?ref_type=heads). This configuration can now be edited in an OSDU&reg; compliant manner to allow the creation of legal tags and the ingestion of data from such countries on Azure Data Manager for Energy. These configurations apply at a partition level. See [How to enable legal tag creation for OSDU&reg; restricted COO (Country of Origin) data?](how-to-enable-legal-tags-restricted-country-of-origin.md) for more details.
+
 ## August 2024
 
 ### Compliant with M23 OSDU&reg; release