Uredi

Dijelite putem

How to enable legal tag creation for OSDU® restricted COO (Country of Origin) data?

  • Članak

Legal tag definitions represent the legal status of the data hosted on an Azure Data Manager for Energy resource. A valid legal tag is required for data ingestion and retrieval stored on the resource. See How to manage legal tags.

COO (Country of Origin) configuration

The creation of legal tags is governed by a configuration hosted on each Azure Data Manager for Energy resource, defined in OSDU® as the legal service default configuration. This is a JSON configuration that defines data residency risk for data originating from these countries using the parameter residencyRisk and the data types to which this risk status doesn't apply using the parameter typesNotApplyDataResidency. Below is a sample configuration for data originating from Australia as an example:

{
    "name": "Australia",
    "alpha2": "AU",
    "numeric": 36,
    "residencyRisk": "No restriction",
    "typesNotApplyDataResidency": ["Transferred Data"]
}

The residencyRisk can take the values default, Not Assigned, Embargoed, and No restriction. For countries configured as No restriction, creating legal tags and later data ingestion is allowed. However, for all other statuses, an attempt to create legal tags would fail.

For countries with status as default and Not Assigned, the default configuration can be overridden by changing the residencyRisk to client consent required in a legal service configuration maintained in Legal_COO.json. This change in configuration is the recommended method to enable legal tags for restricted COO. As an example, Brazil’s default status doesn't allow the creation of legal tags for data ingestion with Brazil as the COO:

{
  "name": "Brazil",
  "alpha2": "BR",
  "numeric": 76,
  "residencyRisk": "Default",
  "typesNotApplyDataResidency": ["Transferred Data"]
}

However, the configuration can be changed as below in the Legal_COO.json for the partition to allow the creation of legal tags:

{
  "name": "Brazil",
  "alpha2": "BR",
  "numeric": 76,
  "residencyRisk": "Client consent required",
  "typesNotApplyDataResidency": ["Transferred Data"]
}

Note

The configuration change is specific to the data partition in which the configuration is applied. Hence, these change requests require the reference of the data partition.

To enable this change, you should raise a support ticket on the Azure portal using the following information:

  • Subscription ID
  • Region in which the instance is deployed
  • Azure Data Manager for Energy developer tier resource name
  • Data partition name on which the configuration is to be changed.
  • List of country-specific configurations with new values to be applied (as shown above).

Tip

Multiple partition configuration changes can be submitted in the same request by clearly specifying the partition name and the associated country-specific configuration changes.

Note

The country-specific configuration can also be reversed to the original state of 'default' or 'Not Assigned' if the customer chooses.

Important

Microsoft isn't responsible for, and consults not or recommends changes to the residencyRisk status of country-specific configurations. The customer, by making such a request to allow data from these countries of origin by changing the configuration, is doing so at their own risk and understanding.

Related content