Add coo details to toc and index

Author: Bharathi Selvaraj

articles/energy-data-services/how-to-enable-legal-tags-restricted-country-of-origin.md

@@ -10,10 +10,10 @@ ms.date: 02/08/2025
 #customer intent: As a data manager, I need an ability to create legal tag definitions for restricted country of origin data.
 
 ---
-# How to enable legal tag creation for OSDU® restricted country of origin data?
-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](how-to-manage-legal-tags.md).
+# How to enable legal tag creation for OSDU® restricted COO(Country of Origin) data?
+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](how-to-manage-legal-tags.md).
 
+## 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](https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/blob/master/legal-core/src/main/resources/DefaultCountryCode.json?ref_type=heads). 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:
 
 ```json
@@ -28,7 +28,7 @@ The creation of legal tags is governed by a configuration hosted on each Azure D
 
 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 country of origins. As an example, Brazil’s default status doesn't allow the creation of legal tags for data ingestion with Brazil as the country of origin:
+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:
 
 ```json
 {

articles/energy-data-services/index.yml

@@ -86,6 +86,8 @@ landingContent:
             url: how-to-enable-external-data-sources.md
           - text: How to register External Data Sources (EDS)
             url: how-to-register-external-data-sources.md
+          - text: How to enable legal tags restricted COO (Country of Origin)
+            url: how-to-enable-legal-tags-restricted-country-of-origin.md
   - title: Administration
     linkLists:
       - linkListType: how-to-guide

articles/energy-data-services/toc.yml

@@ -81,6 +81,8 @@ items:
           href: how-to-enable-external-data-sources.md
         - name: How to register External Data Sources (EDS)
           href: how-to-register-external-data-sources.md
+        - name: How to enable legal tags restricted COO (Country of Origin)
+          href: how-to-enable-legal-tags-restricted-country-of-origin.md
     - name: Monitoring
       items:
         - name: Airflow task logs integration with Azure Monitor