Merge pull request #211712 from nitinnms/add-release-notes

Add release notes

Author: tamarakhader

articles/energy-data-services/index.yml

@@ -42,6 +42,10 @@ landingContent:
             url: concepts-csv-parser-ingestion.md
           - text: Index and search workflows
             url: concepts-index-and-search.md
+      - linkListType: whats-new
+        links:
+          - text: Release notes
+            url: release-notes.md
   - title: About Domain Data Management Services (DDMS)
     linkLists:
       - linkListType: overview
@@ -91,4 +95,4 @@ landingContent:
           - text: How to integrate airflow logs with Azure Monitor
             url: how-to-integrate-airflow-logs-with-azure-monitor.md
           - text: How to integrate elastic logs with Azure Monitor
-            url: how-to-integrate-elastic-logs-with-azure-monitor.md
+            url: how-to-integrate-elastic-logs-with-azure-monitor.md

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

@@ -0,0 +1,67 @@
+---
+title: Release notes for Microsoft Energy Data Services Preview #Required; page title is displayed in search results. Include the brand.
+description: This topic provides release notes of Microsoft Energy Data Services 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.
+ms.topic: conceptual #Required; leave this attribute/value as-is.
+ms.date: 09/20/2022 #Required; mm/dd/yyyy format.
+ms.custom: template-concept #Required; leave this attribute/value as-is.
+---
+
+# Release Notes for Microsoft Energy Data Services Preview
+
+[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
+
+Microsoft Energy Data Services receives improvements on an ongoing basis. To stay up to date with the most recent developments, this article provides you with information about:
+
+- The latest releases
+- Known issues
+- Bug fixes
+- Deprecated functionality
+- Plans for changes
+
+## Microsoft Energy Data Services Preview Release
+
+
+### Key Announcement
+
+Microsoft Energy Data Services is now available as a public preview. 
+
+Microsoft Energy Data Services conforms with the requirements of the Release-3, [Milestone-12](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/M12-Release-Notes) of OSDU™ Technical Standard, Version 1.0.
+
+### Partition & User Management
+
+- You can create [new data partitions](how-to-add-more-data-partitions.md) (up to five) in your existing Microsoft Energy Data Services instance. Earlier, you could create a data partition only while provisioning the instance.
+- The domain name for your entitlement groups for [user management](how-to-manage-users.md) is changed to "dataservices.energy".
+
+### Data Ingestion
+
+- Microsoft Energy Data Services - Enabled support for user context in ingestion ([ADR: Issue 52](https://community.opengroup.org/osdu/platform/data-flow/ingestion/home/-/issues/52)) (not yet supported in the Azure OSDU™ community edition)
+  - In Microsoft Energy Data Services, the User identity is preserved and passed on to all ingestion workflow related services using the newly introduced _x-on-behalf-of_ header.
+  - In Azure OSDU™ community edition, by using elevated SPN permissions, users could call the workflow service and trigger an ingestion job even without appropriate service level entitlements on the underlying dependent services. In Microsoft Energy Data Services, a user needs to have appropriate service level entitlements on all dependent services involved in the ingestion workflow
+  - In Azure OSDU™ community edition, users who weren't part of the same data entitlement group could accidentally modify and corrupt data (using elevated SPN permissions). In Microsoft Energy Data Services, only users belonging to the same data entitlement group can modify data, and the modified user and date information are captured.
+- 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.
+- Microsoft Energy Data Services uses Azure Data Factory (ADF) to run large scale ingestion workloads.
+
+### Search
+
+- Improved security as Elasticsearch images is 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.
+
+### Monitoring
+
+- You can create diagnostic settings to export [Airflow](how-to-integrate-airflow-logs-with-azure-monitor.md) and [Elasticsearch](how-to-integrate-elastic-logs-with-azure-monitor.md) logs from your Microsoft Energy Data Services instance to Azure Monitor.
+
+### Hardware & Software
+
+- Your Microsoft Energy Data Services instance runs on the latest version of Azure Kubernetes Services (AKS) clusters – [version 1.24.](https://kubernetes.io/blog/2022/04/07/upcoming-changes-in-kubernetes-1-24/)
+
+### Region Availability
+
+- In Preview, Availability Zones will be available by default in select regions. All new Microsoft Energy Data Services instances created in these select zones will have Availability Zones redundancy enabled on them upon creation.
+- The selected regions where Availability Zones will be offered on Microsoft Energy Data Services Preview are - South Central US, East US, West Europe, and North Europe.
+
+---
+
+ 

articles/energy-data-services/toc.yml

@@ -8,6 +8,10 @@
     - name: About Domain Data Management Services (DDMS)
       displayName: DDMS overview
       href: overview-ddms.md
+    - name: What's new
+      items:
+        - name: Release notes
+          href: release-notes.md
 - name: Quickstarts
   expanded: true
   items: