fixing validation error

paulth1 · paulth1 · commit 757f19ba554b · 2024-01-11T15:21:36.000-08:00
diff --git a/articles/energy-data-services/how-to-manage-users.md b/articles/energy-data-services/how-to-manage-users.md
@@ -1,5 +1,5 @@
 ---
-title: Manage users in Microsoft Azure Data Manager for Energy
+title: Manage users in Azure Data Manager for Energy
 description: This article describes how to manage users in Azure Data Manager for Energy.
 author: shikhagarg1
 ms.author: shikhagarg
@@ -9,7 +9,7 @@ ms.date: 08/19/2022
 ms.custom: template-how-to
 ---
 
-# Manage users
+# Manage users in Azure Data Manager for Energy
 
 In this article, you learn how to manage users and their memberships in OSDU groups in Azure Data Manager for Energy. [Entitlements APIs](https://community.opengroup.org/osdu/platform/security-and-compliance/entitlements/-/tree/master/) are used to add or remove users to OSDU groups and to check the entitlements when the user tries to access the OSDU services or data. For more information about OSDU groups, see [Entitlement services](concepts-entitlements.md).
 
@@ -34,14 +34,14 @@ The object ID (OID) is the Microsoft Entra user OID.
 ## First-time addition of users in a new data partition
 
 1. To add the first admin to a new data partition of an Azure Data Manager for Energy instance, use the access token of the OID that was used to provision the instance.
-1. Get the `client-id` access token by using [Generate client-id access token](how-to-generate-auth-token.md#generate-client-id-auth-token).
+1. Get the `client-id` access token by using [Generate client-id access token](how-to-generate-auth-token.md#generate-the-client-id-auth-token).
 
    If you try to directly use your own access token for adding entitlements, it results in a 401 error. The `client-id` access token must be used to add the first set of users in the system. Those users (with admin access) can then manage more users with their own access token.
 1. Use the `client-id` access token to do the following steps by using the commands outlined in the following sections:
    1. Add the user to the `users@<data-partition-id>.<domain>` OSDU group.
    2. Add the user to the `users.datalake.ops@<data-partition-id>.<domain>` OSDU group.
 1. The user becomes the admin of the data partition. The admin can then add or remove more users to the required entitlement groups:
-   1. Get the admin's auth token by using [Generate user access token](how-to-generate-auth-token.md#generate-user-auth-token) and by using the same `client-id` and `client-secret` values.
+   1. Get the admin's auth token by using [Generate user access token](how-to-generate-auth-token.md#generate-the-user-auth-token) and by using the same `client-id` and `client-secret` values.
    1. Get the OSDU group, such as `service.legal.editor@<data-partition-id>.<domain>`, to which you want to add more users by using the admin's access token.
    1. Add more users to that OSDU group by using the admin's access token.
 
@@ -60,53 +60,53 @@ Run the following curl command in Azure Cloud Bash to get all the groups that ar
 1. Run the following curl command in Azure Cloud Bash to add the users to the users group by using the entitlement service.
 1. The value to be sent for the parameter `email` is the OID of the user and not the user's email address.
 
-```bash
-    curl --location --request POST 'https://<URI>/api/entitlements/v2/groups/<group-name>@<data-partition-id>.dataservices.energy/members' \
-    --header 'data-partition-id: <data-partition-id>' \
-    --header 'Authorization: Bearer <access_token>' \
-    --header 'Content-Type: application/json' \
-    --data-raw '{
-                    "email": "<Object_ID>",
-                    "role": "MEMBER"
-                }'
-```
-
-**Sample request for users OSDU group**
-
-Consider an Azure Data Manager for Energy instance named `medstest` with a data partition named `dp1`.
-
-```bash
-    curl --location --request POST 'https://medstest.energy.azure.com/api/entitlements/v2/groups/users@medstest-dp1.dataservices.energy/members' \
-    --header 'data-partition-id: medstest-dp1' \
-    --header 'Authorization: Bearer abcdefgh123456.............' \
-    --header 'Content-Type: application/json' \
-    --data-raw '{
-                    "email": "90e0d063-2f8e-4244-860a-XXXXXXXXXX",
-                    "role": "MEMBER"
-                }'
-```
-
-**Sample response**
-
-```JSON
-    {
-        "email": "90e0d063-2f8e-4244-860a-XXXXXXXXXX",
-        "role": "MEMBER"
-    }
-```
-
-**Sample request for legal service editor OSDU group**
-
-```bash
-    curl --location --request POST 'https://medstest.energy.azure.com/api/entitlements/v2/groups/service.legal.editor@medstest-dp1.dataservices.energy/members' \
-    --header 'data-partition-id: medstest-dp1' \
-    --header 'Authorization: Bearer abcdefgh123456.............' \
-    --header 'Content-Type: application/json' \
-    --data-raw '{
-                    "email": "90e0d063-2f8e-4244-860a-XXXXXXXXXX",
-                    "role": "MEMBER"
-                }'
-```
+    ```bash
+        curl --location --request POST 'https://<URI>/api/entitlements/v2/groups/<group-name>@<data-partition-id>.dataservices.energy/members' \
+        --header 'data-partition-id: <data-partition-id>' \
+        --header 'Authorization: Bearer <access_token>' \
+        --header 'Content-Type: application/json' \
+        --data-raw '{
+                        "email": "<Object_ID>",
+                        "role": "MEMBER"
+                    }'
+    ```
+
+    **Sample request for users OSDU group**
+    
+    Consider an Azure Data Manager for Energy instance named `medstest` with a data partition named `dp1`.
+    
+    ```bash
+        curl --location --request POST 'https://medstest.energy.azure.com/api/entitlements/v2/groups/users@medstest-dp1.dataservices.energy/members' \
+        --header 'data-partition-id: medstest-dp1' \
+        --header 'Authorization: Bearer abcdefgh123456.............' \
+        --header 'Content-Type: application/json' \
+        --data-raw '{
+                        "email": "90e0d063-2f8e-4244-860a-XXXXXXXXXX",
+                        "role": "MEMBER"
+                    }'
+    ```
+    
+    **Sample response**
+    
+    ```JSON
+        {
+            "email": "90e0d063-2f8e-4244-860a-XXXXXXXXXX",
+            "role": "MEMBER"
+        }
+    ```
+    
+    **Sample request for legal service editor OSDU group**
+    
+    ```bash
+        curl --location --request POST 'https://medstest.energy.azure.com/api/entitlements/v2/groups/service.legal.editor@medstest-dp1.dataservices.energy/members' \
+        --header 'data-partition-id: medstest-dp1' \
+        --header 'Authorization: Bearer abcdefgh123456.............' \
+        --header 'Content-Type: application/json' \
+        --data-raw '{
+                        "email": "90e0d063-2f8e-4244-860a-XXXXXXXXXX",
+                        "role": "MEMBER"
+                    }'
+    ```
 
 > [!IMPORTANT]
 > The app ID is the default OWNER of all the groups.
@@ -116,68 +116,68 @@ Consider an Azure Data Manager for Energy instance named `medstest` with a data
 
 1. Run the following curl command in Azure Cloud Bash to get all the groups associated with the user.
 
-```bash
-    curl --location --request GET 'https://<URI>/api/entitlements/v2/members/<OBJECT_ID>/groups?type=none' \
-    --header 'data-partition-id: <data-partition-id>' \
-    --header 'Authorization: Bearer <access_token>'
-```
-
-**Sample request**
-
-Consider an Azure Data Manager for Energy instance named `medstest` with a data partition named `dp1`.
-
-```bash
-    curl --location --request GET 'https://medstest.energy.azure.com/api/entitlements/v2/members/90e0d063-2f8e-4244-860a-XXXXXXXXXX/groups?type=none' \
-    --header 'data-partition-id: medstest-dp1' \
-    --header 'Authorization: Bearer abcdefgh123456.............'
-```
-
-**Sample response**
-
-```JSON
-    {
-    "desId": "90e0d063-2f8e-4244-860a-XXXXXXXXXX",
-    "memberEmail": "90e0d063-2f8e-4244-860a-XXXXXXXXXX",
-    "groups": [
-        {
-        "name": "users",
-        "description": "Datalake users",
-        "email": "users@medstest-dp1.dataservices.energy"
-        },
+    ```bash
+        curl --location --request GET 'https://<URI>/api/entitlements/v2/members/<OBJECT_ID>/groups?type=none' \
+        --header 'data-partition-id: <data-partition-id>' \
+        --header 'Authorization: Bearer <access_token>'
+    ```
+    
+    **Sample request**
+    
+    Consider an Azure Data Manager for Energy instance named `medstest` with a data partition named `dp1`.
+    
+    ```bash
+        curl --location --request GET 'https://medstest.energy.azure.com/api/entitlements/v2/members/90e0d063-2f8e-4244-860a-XXXXXXXXXX/groups?type=none' \
+        --header 'data-partition-id: medstest-dp1' \
+        --header 'Authorization: Bearer abcdefgh123456.............'
+    ```
+
+    **Sample response**
+    
+    ```JSON
         {
-        "name": "service.search.user",
-        "description": "Datalake Search users",
-        "email": "service.search.user@medstest-dp1.dataservices.energy"
+        "desId": "90e0d063-2f8e-4244-860a-XXXXXXXXXX",
+        "memberEmail": "90e0d063-2f8e-4244-860a-XXXXXXXXXX",
+        "groups": [
+            {
+            "name": "users",
+            "description": "Datalake users",
+            "email": "users@medstest-dp1.dataservices.energy"
+            },
+            {
+            "name": "service.search.user",
+            "description": "Datalake Search users",
+            "email": "service.search.user@medstest-dp1.dataservices.energy"
+            }
+        ]
         }
-    ]
-    }
-```
+    ```
 
 ## Delete OSDU groups of a specific user in a data partition
 
 1. Run the following curl command in Azure Cloud Bash to delete a specific user from a specific data partition.
 1. *Do not* delete the OWNER of a group unless you have another OWNER who can manage users in that group.
-
-```bash
-    curl --location --request DELETE 'https://<URI>/api/entitlements/v2/members/<OBJECT_ID>' \
-    --header 'data-partition-id: <data-partition-id>' \
-    --header 'Authorization: Bearer <access_token>'
-```
-
-**Sample request**
-
-Consider an Azure Data Manager for Energy instance named `medstest` with a data partition named `dp1`.
-
-```bash
-    curl --location --request DELETE 'https://medstest.energy.azure.com/api/entitlements/v2/members/90e0d063-2f8e-4244-860a-XXXXXXXXXX' \
-    --header 'data-partition-id: medstest-dp1' \
-    --header 'Authorization: Bearer abcdefgh123456.............'
-```
-
-**Sample response**
-
-No output for a successful response.
-
+    
+    ```bash
+        curl --location --request DELETE 'https://<URI>/api/entitlements/v2/members/<OBJECT_ID>' \
+        --header 'data-partition-id: <data-partition-id>' \
+        --header 'Authorization: Bearer <access_token>'
+    ```
+    
+    **Sample request**
+    
+    Consider an Azure Data Manager for Energy instance named `medstest` with a data partition named `dp1`.
+    
+    ```bash
+        curl --location --request DELETE 'https://medstest.energy.azure.com/api/entitlements/v2/members/90e0d063-2f8e-4244-860a-XXXXXXXXXX' \
+        --header 'data-partition-id: medstest-dp1' \
+        --header 'Authorization: Bearer abcdefgh123456.............'
+    ```
+    
+    **Sample response**
+    
+    No output for a successful response.
+    
 ## Next steps
 
 After you add users to the groups, you can:
