Common questions about Azure Data Manager for Energy

This article answers commonly asked questions about Azure Data Manager for Energy.

General

What is Azure Data Manager for Energy?

Azure Data Manager for Energy is a fully managed, cloud-based data platform solution for the energy industry. This enterprise-grade service is based on the OSDU® Data Platform. It brings together the security and trust of the Microsoft Azure cloud platform and the domain expertise of SLB.

Access

How can I get access to Azure Data Manager for Energy?

Azure Data Manager for Energy is available to all customers and partners who have a valid Azure subscription. You can create an instance by going to Azure Marketplace and searching for Azure Data Manager for Energy.

Legal tags

Why can't customers update the specific configuration for country of origin?

The OSDU® platform doesn't offer APIs for making country/region-specific configuration changes. These configuration settings are stored in .json files within the legal service container, and any changes require a service restart to take effect. The Azure Data Manager for Energy service architecture also doesn't expose the underlying infrastructure to customers, which prevents them from making these changes directly.

External Data Services

What's the effect of data sharing across tenancy boundaries on security, privacy, and compliance?

Any data transferred across tenancy boundaries by the data provider and data consumer is the responsibility of the data provider and the data consumer. Microsoft doesn't store or process customer data outside the customer-specified geography without your authorization. The data provider and consumer can use customer-managed encryption keys and private links to secure data at rest and during transit.

How are the network bandwidth/data transfer charges handled with External Data Services usage?

The deployment topology decided by the data provider and data consumer determines the network bandwidth/data transfer costs.

Would data integrity be maintained when the data provider deletes source data?

Currently, External Data Services doesn't support reconciling deleted data, so deleting data at the data provider's level might result in inconsistent records at the data consumer's level.

What's the effect of secret key rotation at the data consumer's end?

Key rotation is fully supported, so it doesn't have an effect on External Data Services functionality.

When will External Data Services be generally available on Azure Data Manager for Energy?

External Data Services is a preview feature in Azure Data Manager for Energy. We want to learn from customer implementation of the External Data Services preview feature to ensure that functionality, performance, and scalability needs are met before the feature is generally available.

Data residency

Where does Azure Data Manager for Energy store customer data?

By default, Azure Data Manager for Energy replicates customer data to Azure paired regions for resiliency. The service doesn't replicate or move data outside the geography in which the customer created the instance. In some regions with requirements for data to remain within the single region, the service always keeps customer data within the same region. These regions are documented at Data residency in Azure. For more information on the regions that support disaster recovery and cross-region data replication, see Reliability in Azure Data Manager for Energy.

Pricing and billing

Where can I learn about pricing for Azure Data Manager for Energy?

Go to the Azure Data Manager for Energy pricing page.

How is Azure Data Manager for Energy priced?

Azure Data Manager for Energy includes a fixed instance fee for each base instance and for each data partition after the first one. The fixed instance pricing includes the capacity, which can scale up to allow for peak workloads and the need for a higher number of data partitions.

Does Azure Data Manager for Energy charge even if the instance is idle and not being used?

Yes. The fixed instance fee for Azure Data Manager for Energy applies to all active instances. The fee is charged even if the instance is idle or running with no usage.

Are there any charges for data storage?

Standard Azure Storage rates apply after the free trial period.

Are there any charges for data transfer?

Standard Azure data transfer rates apply after the free trial period.

Will I be charged for Azure Data Manager for Energy separately from the applications that I use on top of the platform?

Pricing for Azure Data Manager for Energy is separate from other applications that you build or use on the platform.

Do prices differ regionally?

Pricing for Azure Data Manager for Energy varies by region. To understand regional differences, select a region and currency by using the pricing filters in the pricing calculator.

Support policies

How do I raise a support request for Azure Data Manager for Energy?

In the Azure portal, search for Support. Select Help + Support > Create a support request. You can select Azure Data Manager for Energy in the service option to raise a bug with Azure Data Manager for Energy.

Service updates

How do I get the latest updates on Azure Data Manager for Energy?

Azure Data Manager for Energy is a fully managed service that's based on the OSDU® Data Platform. Microsoft fully manages the underlying infrastructure, security updates, new features, and upgrades to new OSDU&reg versions.

Can I move an Azure Data Manager for Energy resource from one subscription or resource group to another?

Currently, you can't move an Azure Data Manager for Energy resource from one subscription or resource group to another. Instead, you can delete the existing Azure Data Manager for Energy instance in the current resource group or subscription, and then create a new Azure Data Manager for Energy instance in the target resource group or subscription. Then, reingest the data into the new instance.

Analytics Consumption Zone

How do I get access to Analytics Consumption Zone (ACZ) during the preview?

ACZ access requires the use of allow lists during the preview. Follow the step-by-step guidance in Enable Analytics Consumption Zone, and contact your Microsoft representative to get ACZ enabled on your Azure Data Manager for Energy resource.

Is there a portal experience to create ACZ instances, and how many can I create?

No. During preview, you can't create or manage ACZ instances in the Azure portal. Use the REST APIs instead. You can create up to three ACZ instances per data partition. For more information, see Tutorial: Use ACZ APIs.

Can I change the entity types in an ACZ instance after creation?

No. You can't modify the entity type configuration of an existing ACZ instance. To change the catalog kinds or Wellbore Domain Data Management Service (DDMS) kinds, delete the existing ACZ instance and create a new one with the updated configuration.

Can I modify the ACZ data directly in Azure Data Lake Storage Gen2?

No. ACZ is a one-way, read-only sync from Azure Data Manager for Energy to Data Lake Storage Gen2. Don't modify, delete, or add files directly in the ACZ folders in Data Lake Storage Gen2. Manual changes to ACZ data corrupt the sync and cause data inconsistencies because ACZ manages all Delta Lake operations, including transaction logs, checkpoints, and compaction. For analytics and reporting, treat the exported data as read-only. All data modifications must occur in Azure Data Manager for Energy.

What happens to the data in Data Lake Storage Gen2 if I delete an ACZ instance?

When you delete an ACZ instance, the sync stops and ACZ removes the configuration. Data already in your Data Lake Storage Gen2 storage account stays intact. You keep full ownership and control of the exported data.

Can ACZ sync data from Reservoir DDMS, Seismic Store DDMS, or Rock and Fluid Samples DDMS?

No. During preview, ACZ supports only catalog kinds and Wellbore DDMS kinds. ACZ doesn't yet support Reservoir DDMS, Seismic Store DDMS, or Rock and Fluid Samples DDMS.

Are Azure Data Manager for Energy entitlements carried over to the Data Lake Storage Gen2 storage account?

No. ACZ doesn't carry over Azure Data Manager for Energy entitlements to Data Lake Storage Gen2. ACZ exports all records that match your entity filters. Per-record entitlements don't apply. Use Azure role-based access control and Data Lake Storage Gen2 permissions to secure the exported data.

What telemetry and monitoring capabilities are available during the ACZ preview?

During the ACZ preview, the following status indicators are available through the ACZ API:

• ACZ status: Indicates the overall state of the ACZ instance (for example, ACTIVE).
  
• Historical snapshot status: Indicates the progress of the initial data sync (for example, PROCESSING or COMPLETED). More detailed telemetry and monitoring capabilities, such as sync progress metrics, error diagnostics, and integration with Azure Monitor, are planned for general availability.

What are the known issues in the ACZ preview release?

During preview:

• ACZ prohibits you from creating a new ACZ instance in the same data partition while another ACZ instance has a historical snapshot in the PROCESSING state. Wait for the in-progress snapshot to finish before you create another ACZ in that data partition.
  
• ACZ delete is allowed when a historical snapshot is in the PROCESSING state. This action might lead to data inconsistencies in ACZ data.
  
• ACZ supports a maximum of 100 kinds.
  
• ACZ is available only on Developer tier instances. Standard tier instances aren't supported.

How does ACZ differ from Geospatial Consumption Zone (GCZ)?

ACZ exports Azure Data Manager for Energy entity data to Data Lake Storage Gen2 in Delta Parquet format for analytics and reporting. GCZ provides geospatial map services (GIS) for Azure Data Manager for Energy data by using a transformer and provider setup on Azure Kubernetes Service. Both make Azure Data Manager for Energy data available outside the core platform, but they serve different use cases.

When is ACZ generally available on Azure Data Manager for Energy?

ACZ is in preview. Microsoft uses customer feedback to validate functionality, performance, and scale before general availability.

This article answers commonly asked questions about Azure Data Manager for Energy.

Azure Data Manager for Energy is a fully managed, cloud-based data platform solution for the energy industry. This enterprise-grade service is based on the OSDU® Data Platform. It brings together the security and trust of the Microsoft Azure cloud platform and the domain expertise of SLB.

Azure Data Manager for Energy is available to all customers and partners who have a valid Azure subscription. You can create an instance by going to Azure Marketplace and searching for Azure Data Manager for Energy.

The OSDU® platform doesn't offer APIs for making country/region-specific configuration changes. These configuration settings are stored in .json files within the legal service container, and any changes require a service restart to take effect. The Azure Data Manager for Energy service architecture also doesn't expose the underlying infrastructure to customers, which prevents them from making these changes directly.

Any data transferred across tenancy boundaries by the data provider and data consumer is the responsibility of the data provider and the data consumer. Microsoft doesn't store or process customer data outside the customer-specified geography without your authorization. The data provider and consumer can use customer-managed encryption keys and private links to secure data at rest and during transit.

The deployment topology decided by the data provider and data consumer determines the network bandwidth/data transfer costs.

Currently, External Data Services doesn't support reconciling deleted data, so deleting data at the data provider's level might result in inconsistent records at the data consumer's level.

Key rotation is fully supported, so it doesn't have an effect on External Data Services functionality.

External Data Services is a preview feature in Azure Data Manager for Energy. We want to learn from customer implementation of the External Data Services preview feature to ensure that functionality, performance, and scalability needs are met before the feature is generally available.

By default, Azure Data Manager for Energy replicates customer data to Azure paired regions for resiliency. The service doesn't replicate or move data outside the geography in which the customer created the instance. In some regions with requirements for data to remain within the single region, the service always keeps customer data within the same region. These regions are documented at Data residency in Azure. For more information on the regions that support disaster recovery and cross-region data replication, see Reliability in Azure Data Manager for Energy.

Go to the Azure Data Manager for Energy pricing page.

Azure Data Manager for Energy includes a fixed instance fee for each base instance and for each data partition after the first one. The fixed instance pricing includes the capacity, which can scale up to allow for peak workloads and the need for a higher number of data partitions.

Yes. The fixed instance fee for Azure Data Manager for Energy applies to all active instances. The fee is charged even if the instance is idle or running with no usage.

Standard Azure Storage rates apply after the free trial period.

Standard Azure data transfer rates apply after the free trial period.

Pricing for Azure Data Manager for Energy is separate from other applications that you build or use on the platform.

Pricing for Azure Data Manager for Energy varies by region. To understand regional differences, select a region and currency by using the pricing filters in the pricing calculator.

In the Azure portal, search for Support. Select Help + Support > Create a support request. You can select Azure Data Manager for Energy in the service option to raise a bug with Azure Data Manager for Energy.

Azure Data Manager for Energy is a fully managed service that's based on the OSDU® Data Platform. Microsoft fully manages the underlying infrastructure, security updates, new features, and upgrades to new OSDU&reg versions.

Currently, you can't move an Azure Data Manager for Energy resource from one subscription or resource group to another. Instead, you can delete the existing Azure Data Manager for Energy instance in the current resource group or subscription, and then create a new Azure Data Manager for Energy instance in the target resource group or subscription. Then, reingest the data into the new instance.

ACZ access requires the use of allow lists during the preview. Follow the step-by-step guidance in Enable Analytics Consumption Zone, and contact your Microsoft representative to get ACZ enabled on your Azure Data Manager for Energy resource.

No. During preview, you can't create or manage ACZ instances in the Azure portal. Use the REST APIs instead. You can create up to three ACZ instances per data partition. For more information, see Tutorial: Use ACZ APIs.

No. You can't modify the entity type configuration of an existing ACZ instance. To change the catalog kinds or Wellbore Domain Data Management Service (DDMS) kinds, delete the existing ACZ instance and create a new one with the updated configuration.

No. ACZ is a one-way, read-only sync from Azure Data Manager for Energy to Data Lake Storage Gen2. Don't modify, delete, or add files directly in the ACZ folders in Data Lake Storage Gen2. Manual changes to ACZ data corrupt the sync and cause data inconsistencies because ACZ manages all Delta Lake operations, including transaction logs, checkpoints, and compaction. For analytics and reporting, treat the exported data as read-only. All data modifications must occur in Azure Data Manager for Energy.

When you delete an ACZ instance, the sync stops and ACZ removes the configuration. Data already in your Data Lake Storage Gen2 storage account stays intact. You keep full ownership and control of the exported data.

No. During preview, ACZ supports only catalog kinds and Wellbore DDMS kinds. ACZ doesn't yet support Reservoir DDMS, Seismic Store DDMS, or Rock and Fluid Samples DDMS.

No. ACZ doesn't carry over Azure Data Manager for Energy entitlements to Data Lake Storage Gen2. ACZ exports all records that match your entity filters. Per-record entitlements don't apply. Use Azure role-based access control and Data Lake Storage Gen2 permissions to secure the exported data.

During the ACZ preview, the following status indicators are available through the ACZ API:

• ACZ status: Indicates the overall state of the ACZ instance (for example, ACTIVE).
  
• Historical snapshot status: Indicates the progress of the initial data sync (for example, PROCESSING or COMPLETED). More detailed telemetry and monitoring capabilities, such as sync progress metrics, error diagnostics, and integration with Azure Monitor, are planned for general availability.

During preview:

• ACZ prohibits you from creating a new ACZ instance in the same data partition while another ACZ instance has a historical snapshot in the PROCESSING state. Wait for the in-progress snapshot to finish before you create another ACZ in that data partition.
  
• ACZ delete is allowed when a historical snapshot is in the PROCESSING state. This action might lead to data inconsistencies in ACZ data.
  
• ACZ supports a maximum of 100 kinds.
  
• ACZ is available only on Developer tier instances. Standard tier instances aren't supported.

ACZ exports Azure Data Manager for Energy entity data to Data Lake Storage Gen2 in Delta Parquet format for analytics and reporting. GCZ provides geospatial map services (GIS) for Azure Data Manager for Energy data by using a transformer and provider setup on Azure Kubernetes Service. Both make Azure Data Manager for Energy data available outside the core platform, but they serve different use cases.

ACZ is in preview. Microsoft uses customer feedback to validate functionality, performance, and scale before general availability.