February release notes

Author: sandeepchadda

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

@@ -1,6 +1,6 @@
 ---
 title: Release notes for Microsoft Azure Data Manager for Energy Preview #Required; page title is displayed in search results. Include the brand.
-description: This topic provides release notes of Azure Data Manager for Energy Preview releases, improvements, bug fixes, and known issues. #Required; article description that is displayed in search results. 
+description: This article provides release notes of Azure Data Manager for Energy Preview releases, improvements, bug fixes, and known issues. #Required; article description that is displayed in search results. 
 author: nitinnms #Required; your GitHub user alias, with correct capitalization.
 ms.author: nitindwivedi #Required; microsoft alias of author; optional team alias.
 ms.service: energy-data-services #Required; service per approved list. slug assigned by ACOM.
@@ -25,23 +25,23 @@ Azure Data Manager for Energy Preview is updated on an ongoing basis. To stay up
 
 ## February 2023
 
-### Product Access Update
+### Compliant with M14 OSDU™ release
 
-Beginning on February 15, 2023, customers of Microsoft Energy Data Services can search for and provision their instances of the product without a request for access. Customers can go directly to the Azure Marketplace to create an instance under their selected subscription.
+Azure Data Manager for Energy Preview is now compliant with the M14 OSDU™ milestone release. With this release, you can take advantage of the latest features and capabilities available in the [OSDU™ M14](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/M14-Release-Notes).
 
+### Product Billing Enabled
 
-### Product Billing Update
+Billing for Azure Data Manager for Energy is enabled. During Preview, the price for each instance is based on a fixed per-hour consumption. [Pricing information for Azure Data Manager for Energy.](https://azure.microsoft.com/en-gb/pricing/details/energy-data-services/#pricing)
 
-Microsoft Energy Data Services will begin billing February 15, 2023. Prices will be based on a fixed per-hour consumption rate at a 50 percent discount during preview. 
-- No upfront costs or termination fees—pay only for what you use.
-- No charges for storage, data transfers or compute overage during preview.
 
-### OSDU™ Milestone Upgrade
+### Available on Azure Marketplace
+
+You can go directly to the [Azure Marketplace](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/Microsoft.MicrosoftEnergyDataServices?tab=Overview) to create an Azure Data Manager for Energy Preview instance in your subscription. You don't need to raise a support ticket with Microsoft to provision an instance anymore. 
 
-Azure Data Manager for Energy Preview is now compliant with the M14 OSDU™ milestone release. With this release you can take advantage of the latest features and capabilities available in the [OSDU™ M14](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/M14-Release-Notes).
 
 ### Enable Resource sharing (CORS)
-CORS provides a secure way to allow one origin (the origin domain) to call APIs in another origin. With this feature you can set CORS rules for each Azure Data Manager for Energy instance. When you set CORS rules for the instance it gets applied automatically across all the services and storage accounts linked with Microsoft Energy Data services.[Learn more.]( ../energy-data-services/how-to-enable-CORS.md)
+
+CORS provides a secure way to allow one origin (the origin domain) to call APIs in another origin. You can set CORS rules for each Azure Data Manager for Energy instance. When you set CORS rules for the instance they get applied automatically across all the services and storage accounts linked with Azure Data Manager for Energy Preview. [How to enable CORS.]( ../energy-data-services/how-to-enable-CORS.md)
 
 ## January 2023
 
@@ -57,9 +57,9 @@ Availability Zones are physically separate locations within an Azure region made
 
 ## December 2022
 
-### Lockbox
+### Support for Lockbox
 
-Most operations, support, and troubleshooting performed by Microsoft personnel do not require access to customer data. In those rare circumstances where such access is required, Customer Lockbox for Azure Data Manager for Energy Preview provides you an interface to review and approve or reject data access requests. Azure Data Manager for Energy Preview now supports Lockbox. [Learn more](../security/fundamentals/customer-lockbox-overview.md).
+Most operations, support, and troubleshooting performed by Microsoft personnel don't require access to customer data. In those rare circumstances where such access is required, Customer Lockbox for Azure Data Manager for Energy Preview provides you an interface to review, approve or reject data access requests. Azure Data Manager for Energy Preview now supports Lockbox. [Learn more](../security/fundamentals/customer-lockbox-overview.md).
 
 
 <hr width=100%>
@@ -68,9 +68,10 @@ Most operations, support, and troubleshooting performed by Microsoft personnel d
 
 ### Support for Private Links
 
-Azure Private Link on Azure Data Manager for Energy Preview provides private access to the service. This means traffic between your private network and Azure Data Manager for Energy Preview travels over the Microsoft backbone network therefore limiting any exposure over the internet. By using Azure Private Link, you can connect to an Azure Data Manager for Energy Preview instance from your virtual network via a private endpoint, which is a set of private IP addresses in a subnet within the virtual network. You can then limit access to your Azure Data Manager for Energy Preview instance over these private IP addresses. [Create a private endpoint for Azure Data Manager for Energy Preview](how-to-set-up-private-links.md).
+Azure Private Link on Azure Data Manager for Energy Preview provides private access to the service. With Azure Private Link traffic between your private network and Azure Data Manager for Energy Preview travels over the Microsoft backbone network therefore, limiting any exposure over the internet. By using Azure Private Link, you can connect to an Azure Data Manager for Energy Preview instance from your virtual network via a private endpoint. You can limit access to your Azure Data Manager for Energy Preview instance over these private IP addresses. [Create a private endpoint for Azure Data Manager for Energy Preview](how-to-set-up-private-links.md).
 
 ### Encryption at Rest using Customer Managed Keys
+
 Azure Data Manager for Energy Preview supports customer managed encryption keys (CMK). All data in Azure Data Manager for Energy Preview is encrypted with Microsoft-managed keys by default. In addition to Microsoft-managed key, you can use your own encryption key to protect the data in Azure Data Manager for Energy Preview. When you specify a customer-managed key, that key is used to protect and control access to the Microsoft-managed key that encrypts your data. [Data security and encryption in Azure Data Manager for Energy Preview](how-to-manage-data-security-and-encryption.md).
 
 
@@ -81,34 +82,33 @@ Azure Data Manager for Energy Preview supports customer managed encryption keys
 
 ### Key Announcement: Preview Release
 
-Azure Data Manager for Energy Preview is now available in public preview. Information on latest releases, bug fixes, & deprecated functionality for Azure Data Manager for Energy Preview will be updated monthly. Keep tracking this page. 
+Azure Data Manager for Energy Preview is now available in public preview. Information on latest releases, bug fixes, & deprecated functionality for Azure Data Manager for Energy Preview will be updated monthly.
 
-Azure Data Manager for Energy Preview is developed in alignment with the emerging requirements of the OSDU™ Technical Standard, Version 1.0. and is currently aligned with Mercury Release(R3), [Milestone-12](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/M12-Release-Notes).
+Azure Data Manager for Energy Preview is developed in alignment with the emerging requirements of the OSDU™ technical standard, version 1.0. and is currently aligned with Mercury Release(R3), [Milestone-12](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/M12-Release-Notes).
 
 ### Partition & User Management
 
-- New data partitions can be [created dynamically](how-to-add-more-data-partitions.md) as needed post provisioning of the platform (up to five). Earlier, data partitions could only be created when provisioning a new instance.
+- New data partitions can be [created after provisioning an Azure Data Manager for Energy Preview instance](how-to-add-more-data-partitions.md). Earlier, data partitions could only be created when provisioning a new instance.
 - The domain name for entitlement groups for [user management](how-to-manage-users.md) has been changed to "dataservices.energy".
 
 ### Data Ingestion
 
-- Enabled support for user context in ingestion ([ADR: Issue 52](https://community.opengroup.org/osdu/platform/data-flow/ingestion/home/-/issues/52)) 
-  - User identity is preserved and passed on to all ingestion workflow related services using the newly introduced _x-on-behalf-of_ header. A user needs to have appropriate service level entitlements on all dependent services involved in the ingestion workflow and only users with appropriate data level entitlements can modify data.
-- Workflow service payload is restricted to a maximum of 2 MB. If it exceeds, the service will throw an HTTP 413 error. This restriction is placed to prevent workflow requests from overwhelming the server.
+- Azure Data Manager for Energy Preview supports user context in ingestion ([ADR: Issue 52](https://community.opengroup.org/osdu/platform/data-flow/ingestion/home/-/issues/52)) 
+  - User identity is preserved and passed on to all ingestion workflow related services using the newly introduced _x-on-behalf-of_ header. You need to have appropriate service level entitlements on all dependent services involved in the ingestion workflow to modify data.
+- Workflow service payload is restricted to a maximum of 2 MB. If it exceeds, the service throws an HTTP 413 error. This restriction is placed to prevent workflow requests from overwhelming the server.
 - Azure Data Manager for Energy Preview uses Azure Data Factory (ADF) to run large scale ingestion workloads.
 
 ### Search
 
-- Improved security as Elasticsearch images are now pulled from Microsoft's internal Azure Container Registry instead of public repositories.
-- Improved security by enabling encryption in transit for Elasticsearch, Registration, and Notification services.
+Azure Data Manager for Energy Preview is more secure as Elasticsearch images are now pulled from Microsoft's internal Azure Container Registry instead of public repositories. In addition, Elastic search, registration, and notification services are now encrypted in transit further enhancing the security of the product.
 
 ### Monitoring
 
-- Diagnostic settings can be exported from [Airflow](how-to-integrate-airflow-logs-with-azure-monitor.md) and [Elasticsearch](how-to-integrate-elastic-logs-with-azure-monitor.md) to Azure Monitor.
+Azure Data Manager for Energy Preview supports diagnostic settings for [Airflow logs](how-to-integrate-airflow-logs-with-azure-monitor.md) and [Elasticsearch logs](how-to-integrate-elastic-logs-with-azure-monitor.md). You can configure Azure Monitor to view these logs in the storage location of your choice.
 
 ### Region Availability
 
-- Currently, Azure Data Manager for Energy Preview is being offered in the following regions - South Central US, East US, West Europe, and North Europe.
+Currently, Azure Data Manager for Energy Preview is available in the following regions - South Central US, East US, West Europe, and North Europe.
 
 ---