Merge pull request #306490 from marielherz/reference-data-values-update

Update reference data values for greenfield ga

Author: prmerger-automator[bot]

articles/energy-data-services/concepts-reference-data-values.md

@@ -1,19 +1,15 @@
 ---
-title: Reference Data Value Syncing in Microsoft Azure Data Manager for Energy
-description: This article describes Reference Values and syncing of Reference Values with Azure Data Manager for Energy data partitions.
-author: bharathim
-ms.author: bselvaraj
+title: Reference Data Value in Microsoft Azure Data Manager for Energy
+description: This article describes Reference Values and how Reference Data Values are automatically loaded in Azure Data Manager.
+author: marielherz
+ms.author: marielherzog
 ms.service: azure-data-manager-energy
 ms.topic: conceptual
-ms.date: 08/28/2024
+ms.date: 10/03/2025
 ms.custom: template-concept
 ---
 
-# Syncing Reference Data Values
-
-> [!IMPORTANT]
-> The feature to sync reference values in your Azure Data Manager for Energy data partition is currently in **Limited Preview**. If you are interested in having this feature enabled for your Azure subscription, then please reach out to either your Microsoft Sales contact or open a support ticket for assistance.
->
+# Reference Data Values Automated Sync in ADME
 
 This article provides an overview of reference data values in OSDU Data Platform, and explains how Azure Data Manager for Energy helps you synchronize them with OSDU community standards. 
 
@@ -32,7 +28,7 @@ For more information about OSDU reference data values and their different types,
 
 ## Configuring value syncing in Azure Data Manager for Energy
 
-To help you maintain data integrity and facilitate interoperability, new Azure Data Manager for Energy instances are automatically created with **FIXED** and **OPEN** reference data values synced per the latest set from the OSDU community for the [current milestone supported by Azure Data Manager for Energy](osdu-services-on-adme.md). You can additionally choose to have new instances create with **LOCAL** values synced as well.
+To help you maintain data integrity and facilitate interoperability, new Azure Data Manager for Energy instances are automatically created with **FIXED** and **OPEN** reference data values synced per the latest set from the OSDU community for the [current milestone supported by Azure Data Manager for Energy](osdu-services-on-adme.md). During provisioning, you can additionally choose to have new instances create with **LOCAL** values synced or opt out.
 
 Later, if you create new data partitions in the Azure Data Manager for Energy instance, they'll also be created with FIXED and OPEN reference values synced. If you had chosen to additionally sync LOCAL values when you first created the instance, new partitions will also sync LOCAL values from the community.
 

articles/energy-data-services/concepts-tier-details.md

@@ -1,11 +1,11 @@
 ---
-title: Microsoft Azure Data Manager for Energy tier concepts
+title: Microsoft Azure Data Manager for Energy tier concepts - Developer and Standard SKU
 description: This article describes tier concepts
-author: bharathim
-ms.author: bselvaraj
+author: marielherz
+ms.author: marielherzog
 ms.service: azure-data-manager-energy
 ms.topic: conceptual
-ms.date: 07/11/2023
+ms.date: 10/03/2025
 ms.custom: template-concept
 ---
 
@@ -14,16 +14,18 @@ Azure Data Manager for Energy is available in two tiers; Standard and Developer.
 
 
 ## Developer tier 
-The Developer tier of Azure Data Manager for Energy is designed for users who want more flexibility and speed in building out new applications and testing their [OSDU®](https://osduforum.org) Data Platform backed solutions. The Developer tier provides users with the same high bar of security features, and application integration services as the Standard tier at a lower cost and with reduced resource capacity. Organizations can isolate and manage their test and production environments more cost-effectively. Use cases for the Developer tier of Azure Data Manager for Energy includes the following:
+The Azure Data Manager for Energy Developer Tier is designed to provide flexibility and speed for users building and testing [OSDU®](https://osduforum.org) Data Platform backed solutions.  It offers the same high standard of security and integration capabilities as the Standard tier, but at a lower cost and with reduced resource capacity.
+
+This tier is best suited for functional testing, evaluation, and early-stage development. It is not recommended for performance benchmarking or production-scale workloads, as its resource limits may lead to suboptimal results in such scenarios. Organizations can use the Developer tier to cost-effectively isolate and manage their test environments, ensuring a clear separation from production operations. Typical use cases include:
 
 * Evaluating and creating data migration strategy
-* Building proof of concepts and business case demonstrations
-* Defining deployment pipeline
+* Building proof of concepts and business case demonstrations of user scenarios
+* Defining deployment pipelines
 * Validating application compatibility
 * Validating security features such as Customer Managed Encryption Keys (CMEK)
 * Implementing sensitive data classification
 * Testing new [OSDU®](https://osduforum.org) Data Platform releases
-* Validating data by ingesting in a safe pre production environment
+* Validating a limited dataset by ingesting in a safe pre production environment
 * Testing new third party or in-house applications 
 * Validating service updates
 * Testing API functionality
@@ -34,6 +36,8 @@ Customers can isolate their test and production environments in a safe and effec
 ## Standard tier 
 The Standard tier of Azure Data Manager for energy is ideal for customers' production ready scenarios. These include the following:
 
+* Large scale data ingestion
+* Production grade performance (including testing)
 * Operationalizing domain workflows (such as seismic or well log)
 * Deploying and testing predictive reservoir models to a production environment on the cloud
 * Running subsurface models

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

@@ -23,6 +23,13 @@ This page is updated with the details about the upcoming release approximately a
 
 <hr width = 100%>
 
+## October 2025
+### Reference Data Values Automatic Sync
+
+With this release, all new Azure Data Manager for Energy instances provisioned automatically includes the latest set of Reference Data Values by default, ensuring out-of-the-box compliance with OSDU® standards and accelerating data onboarding workflows. The update delivers a complete library of reference values synced to the latest OSDU milestone (currently **M25**), improving interoperability, guaranteeing schema consistency, and eliminating manual setup during provisioning.  
+
+For more details on how to work with this feature, see the official documentation: [Reference Data Values in ADME](release-notes.md).
+
 ## September 2025
 ### Rock and Fluid Samples (RAFS) Preview
 The Rock and Fluid Samples (RAFS) DDMS introduces a standardized approach for storing, querying, and analyzing geological and engineering sample data collected from subsurface and surface sites. These samples are critical for workflows such as reservoir modeling, facility design, and drilling planning. RAFS DDMS is now available as a Preview feature on ADME Developer SKU. See [Tutorial: Use Rock and Fluid Samples (RAFS) DDMS APIs](tutorial-rock-and-fluid-samples-ddms.md) on how to use RAFS DDMS APIs.