Skip to content

Commit 0dc7d1b

Browse files
committed
Update release notes for ADME GA as well as updates for month of June
1 parent b7639b1 commit 0dc7d1b

File tree

1 file changed

+18
-7
lines changed

1 file changed

+18
-7
lines changed

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

Lines changed: 18 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -19,18 +19,29 @@ Azure Data Manager for Energy is updated on an ongoing basis. To stay up to date
1919
- Deprecated functionality
2020
- Plans for changes
2121

22-
This page will be updated with the details about the upcoming release approximately a week before the actual deployment.
22+
This page is updated with the details about the upcoming release approximately a week before the actual deployment.
2323

2424
<hr width = 100%>
2525

2626
## June 2023
2727

28-
### Partition names without instance name prefix
29-
July 2023 onwards, all data partitions that you create in Azure Data Manager for Energy will stop having the instance name as a prefix. For example, if your instance is called 'myinstance' and you create a partition called 'mydata', the partition name/ ID will be 'mydata', while previously it used to be 'myinstance-mydata'. This change will not impact the existing data partitions.
28+
### Service Level Agreement (SLA) for Azure Data Manager for Energy
29+
Starting July 2023, Azure Data Manager for Energy offers an uptime SLA for its Standard tier offering. You can find the details of our SLA in the document 'Service Level Agreements for Microsoft Online Services (WW)' published from July 2023 onwards at [Microsoft Licensing Documents & Resource website](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1).
3030

31+
### Developer tier for accelerating innovation with OSDU&trade;
32+
Azure Data Manager for Energy is now available in two tiers; Developer and Standard. All active resources of Azure Data Manager for Energy prior to this release are considered Standard, and now a new Tier option is available called, the 'Developer' tier. Customers can now select their desired tier when creating their Azure Data Manage for Energy resource, using the [Azure portal](https://aka.ms/adme-create). [Learn more](./quickstart-create-microsoft-energy-data-services-instance.md)
3133

32-
### Service Level Agreement (SLA) for Azure Data Manager for Energy
33-
July 2023 onwards, Azure Data Manager for Energy will start offering an uptime SLA for its Standard tier. You can find the details of our SLA in the consolidated Azure services SLA document for the month of July 2023 that will be published at [Microsoft Licensing Documents & Resource website](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1).
34+
### Compliant with M16 OSDU&trade; release
35+
Azure Data Manager for Energy is now compliant with the M16 OSDU&trade; milestone release. With this release, you can take advantage of the latest features and capabilities available in the [OSDU&trade; M16](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/M16-Release-Notes).
36+
37+
### Disaster recovery: cross-region failover
38+
Azure Data Manager for Energy (Standard tier only) now supports cross-region disaster recovery in a multi-region geography (data residency boundary). The service replicates your critical data (in near real time) and infrastructure across another Azure region within the same geography, ensuring data redundancy and enabling swift failover to a secondary region in the event of an outage. [Learn more](./reliability-energy-data-services.md).
39+
40+
### Support for file uploads greater than 5 GB up to 10 GB
41+
Azure Data Manager for Energy now supports uploading dataset files greater than 5 GB using Azcopy. [Learn more](https://learn.microsoft.com/azure/energy-data-services/how-to-upload-large-files-using-file-service)
42+
43+
### Partition names without resource name prefix
44+
July 2023 onwards, all data partitions created in your Azure Data Manager for Energy resource discontinues having the resource name as a prefix. For example, if your resource is called `myadmeresource` and you create a data partition called `mydata`, the partition name/ID will be `mydata`, while previously it used to be `myadmeresource-mydata`. This change won't affect existing data partitions.
3445

3546
<hr width = 100%>
3647

@@ -66,7 +77,7 @@ Azure Data Manager for Energy is now compliant with the M14 OSDU&trade; mileston
6677

6778
### Product Billing enabled
6879

69-
Billing for Azure Data Manager for Energy is enabled. During, 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/pricing/details/energy-data-services/#pricing)
80+
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/pricing/details/energy-data-services/#pricing)
7081

7182

7283
### Available on Azure Marketplace
@@ -98,7 +109,7 @@ Availability Zones are physically separate locations within an Azure region made
98109

99110
### Support for Lockbox
100111

101-
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 provides you with an interface to review, approve or reject data access requests. Azure Data Manager for Energy now supports Lockbox. [Learn more](../security/fundamentals/customer-lockbox-overview.md).
112+
Most operations such as 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 provides you with an interface to review, approve or reject data access requests. Azure Data Manager for Energy now supports Lockbox. [Learn more](../security/fundamentals/customer-lockbox-overview.md).
102113

103114

104115
<hr width=100%>

0 commit comments

Comments
 (0)