Merge pull request #309735 from marielherz/rdvBrownfieldGA

ADME: Update Reference Data Values and Release Notes

Author: ttorble

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

@@ -4,31 +4,31 @@ description: This article describes Reference Values and how Reference Data Valu
 author: marielherz
 ms.author: marielherzog
 ms.service: azure-data-manager-energy
-ms.topic: conceptual
-ms.date: 10/03/2025
+ms.topic: article
+ms.date: 12/18/2025
 ms.custom: template-concept
 ---
 
-# Reference Data Values Automated Sync in ADME
+# Reference Data Values Automated Sync in Azure Data Manager for Energy
 
-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. 
+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. 
 
 ## What are reference data values and why are they important?
 
-Within the OSDU Data Platform framework, reference data values play a crucial role in ensuring data consistency and standardization. Reference data refers to the set of permissible values for attributes to be used across various data fields, such as master data or work product components. For example, `degree Celsius` is a permitted `UnitofMeasure`, and `Billing Address` is a permitted `AddressType`.
+Within the OSDU Data Platform® framework, reference data values play a crucial role in ensuring data consistency and standardization. Reference data refers to the set of permissible values for attributes to be used across various data fields, such as master data or work product components. For example, `degree Celsius` is a permitted `UnitofMeasure`, and `Billing Address` is a permitted `AddressType`.
 
-In addition to enabling data interpretation and collaboration, reference data is required for data ingestion via the OSDU manifest ingestion workflow. Manifests provide a specific container for reference data values, which are then used to validate the ingested data and generate metadata for later discovery and use. To learn more about manifest-based ingestion, see [Manifest-based ingestion concepts](concepts-manifest-ingestion.md). 
+In addition to enabling data interpretation and collaboration, reference data is required for data ingestion via the OSDU® manifest ingestion workflow. Manifests provide a specific container for reference data values, which are then used to validate the ingested data and generate metadata for later discovery and use. To learn more about manifest-based ingestion, see [Manifest-based ingestion concepts](concepts-manifest-ingestion.md). 
 
-The OSDU Data Platform categorizes Reference data values into the following three buckets:
-* **FIXED** values: This set of reference values is universally recognized and used across OSDU deployments and the energy sector. These values can't be extended or changed except by OSDU community governance updates
-* **OPEN** values: The OSDU community provides an initial list of OPEN values upon which you can extend but not otherwise change
-* **LOCAL** values: The OSDU community provides an initial list of LOCAL values that you can freely change, extend, or entirely replace
+The OSDU Data Platform® categorizes Reference data values into the following three buckets:
+* **FIXED** values: This set of reference values is universally recognized and used across OSDU® deployments and the energy sector. These values can't be extended or changed except by OSDU® community governance updates
+* **OPEN** values: The OSDU® community provides an initial list of OPEN values upon which you can extend but not otherwise change
+* **LOCAL** values: The OSDU® community provides an initial list of LOCAL values that you can freely change, extend, or entirely replace
 
-For more information about OSDU reference data values and their different types, see [OSDU Data Definitions / Data Definitions / Reference Data](https://community.opengroup.org/osdu/data/data-definitions/-/blob/master/Guides/Chapters/02-GroupType.md#22-reference-data).
+For more information about OSDU® reference data values and their different types, see [OSDU® Data Definitions / Data Definitions / Reference Data](https://community.opengroup.org/osdu/data/data-definitions/-/blob/master/Guides/Chapters/02-GroupType.md#22-reference-data).
 
 ## 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). During provisioning, you can additionally choose to have new instances create with **LOCAL** values synced or opt out.
+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.
 
@@ -55,10 +55,21 @@ If you extend OPEN values after instance creation, we recommend creating and usi
 
 **NameAlias updates** don't require a separate entitlement. Updates to the `NameAlias` field are governed by the same access control mechanisms as updates to any other part of a storage record. In effect, OWNER access confers the entitlement to update the `NameAlias` field.
 
-## Current scope of Azure Data Manager for Energy reference data value syncing
-Currently, Azure Data Manager for Energy syncs reference data values at instance creation and at new partition creation for newly created instances after feature enablement. Reference values are synced to those from the OSDU community, corresponding to the OSDU milestone supported by Azure Data Manager for Energy at the time of instance or partition creation. For information on the current milestone supported by and available OSDU service in Azure Data Manager for Energy, refer [OSDU services available in Azure Data Manager for Energy](osdu-services-on-adme.md).
+## OSDU® Milestone Automated Reference Data Value Upgrades
+
+Azure Data Manager for Energy updates Reference Data Values (RDVs) by automatically applying the latest OSDU®‑aligned FIXED, OPEN, and LOCAL values as part of each instance’s standard upgrade cycle. These updates keep instances aligned with evolving OSDU® definitions while preserving customer‑specific configurations where appropriate. This approach ensures FIXED values remain interoperable across all OSDU®‑based systems, OPEN values continue to support extensibility without losing customer intent, and LOCAL values retain the business‑specific meaning organizations depend on. Updates require no user action and occur seamlessly with no downtime — Azure Data Manager for Energy incorporates new OSDU®‑provided values, updates FIXED values to the latest standards, and preserves customer changes for OPEN and LOCAL. As RDV versioning is decoupled from OSDU® versions, Azure Data Manager for Energy applies RDV updates **only** during the all‑up OSDU® milestone upgrade, ensuring predictable, governed rollout.
+
+### Reference Data Values Update Behavior Summary
+
+| RDV Type | Upgrade Behavior | Rationale |
+|---------|------------------|-----------|
+| **FIXED** | Updated to the latest OSDU® standard; prior versions remain accessible in history. | Ensures global interoperability across OSDU®‑based systems. |
+| **OPEN** | Customer‑extended or modified entries are preserved; new OSDU® baseline entries are added without overwriting user changes. | Balances shared semantics with user‑driven extensibility. |
+| **LOCAL** | Behaviors follow the instance’s provisioning choice; custom values remain unchanged, and new OSDU® suggestions are added only if LOCAL was enabled. | Protects business‑specific meaning and avoids unintended modification. |
+
+For information on the current milestone supported by and available OSDU® services in Azure Data Manager for Energy, refer [OSDU® services available in Azure Data Manager for Energy](osdu-services-on-adme.md).
 
 ## Next steps
 - [Quickstart: Create Azure Data Manager for Energy instance](quickstart-create-microsoft-energy-data-services-instance.md)
 - [Tutorial: Sample steps to perform a manifest-based file ingestion](tutorial-manifest-ingestion.md)
-- [OSDU Operator Data Loading Quick Start Guide](https://community.opengroup.org/groups/osdu/platform/data-flow/data-loading/-/wikis/home#osdu-operator-data-loading-quick-start-guide)
+- [OSDU® Operator Data Loading Quick Start Guide](https://community.opengroup.org/groups/osdu/platform/data-flow/data-loading/-/wikis/home#osdu-operator-data-loading-quick-start-guide)

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

@@ -4,7 +4,7 @@ description: This article provides release notes of Azure Data Manager for Energ
 author: bharathim
 ms.author: bselvaraj
 ms.service: azure-data-manager-energy
-ms.topic: conceptual
+ms.topic: article
 ms.date: 09/20/2022
 ms.custom: template-concept
 ---
@@ -23,6 +23,13 @@ This page is updated with the details about the upcoming release approximately a
 
 <hr width = 100%>
 
+## December 2025
+### Reference Data Values Automatic Sync - Generally Available
+
+Reference Data Values (RDV) Automatic Sync is now Generally Available on all SKUs. As part of each OSDU® milestone upgrade, all Azure Data Manager for Energy instances will be upgraded with the latest Reference Data Values available at that milestone. This ensures consistent, standardized reference data across all instances without requiring manual ingestion.
+
+For more details on how to work with this feature, see the official documentation: [Reference Data Values in ADME](concepts-reference-data-values.md).
+
 ## November 2025
 ### Reservoir DDMS Standard SKU Preview
 
@@ -31,7 +38,7 @@ Reservoir DDMS is now available on the standard SKU as a preview. The standard S
 ## 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.  
+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](concepts-reference-data-values.md).
 
@@ -98,7 +105,7 @@ Azure Data Manager for Energy has now been upgraded with the supported set of se
 We are releasing a Limited Preview for syncing Reference Values with your Azure Data Manager for Energy data partitions. Note that this feature is currently only available for newly created Azure Data Manager for Energy after feature enablement for your Azure subscription. Learn more about [Reference Values on Azure Data Manager for Energy](concepts-reference-data-values.md).
 
 ### CNAME DNS Record Fix
-Previously, each ADME resource had an incorrect privatelink DNS record by default, causing inaccessibility issues for some SLB apps. This release resolves the issue for both new and existing instances, ensuring correct and secure configuration of private endpoints. For more details, see [How to setup private links](how-to-set-up-private-links.md).
+Previously, each ADME resource had an incorrect private link DNS record by default, causing inaccessibility issues for some SLB apps. This release resolves the issue for both new and existing instances, ensuring correct and secure configuration of private endpoints. For more details, see [How to setup private links](how-to-set-up-private-links.md).
 
 ## June 2024
 
@@ -166,7 +173,7 @@ July 2023 onwards, all data partitions created in your Azure Data Manager for En
 
 ### Enriched Airflow Logs
 
-Airflow logs from your Azure Data Manager for Energy Preview resource now include extra fields: Dag Name, Dag Task Name, Run ID or Correlation ID, Code Path, TryNumber, Content, Location, Log Severity Level, and Resource ID. These fields can be utilized in the KQL query editor of your linked Log Analytics Workspace to get more specific logs for your executed workflows/DAGs. Learn more about [how to integrate Airflow logs with Azure Monitor](how-to-integrate-airflow-logs-with-azure-monitor.md). 
+Airflow logs from your Azure Data Manager for Energy Preview resource now include extra fields: DAG Name, DAG Task Name, Run ID or Correlation ID, Code Path, TryNumber, Content, Location, Log Severity Level, and Resource ID. These fields can be utilized in the KQL query editor of your linked Log Analytics Workspace to get more specific logs for your executed workflows/DAGs. Learn more about [how to integrate Airflow logs with Azure Monitor](how-to-integrate-airflow-logs-with-azure-monitor.md). 
 
 <hr width = 100%>