Skip to content

Commit ef663e2

Browse files
Merge pull request #222986 from Lakshmisha-KS/main
Sample Readability
2 parents e6ba62b + a30e50e commit ef663e2

File tree

1 file changed

+23
-15
lines changed

1 file changed

+23
-15
lines changed

articles/energy-data-services/how-to-manage-users.md

Lines changed: 23 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ curl --location --request POST 'https://login.microsoftonline.com/<tenant-id>/oa
8282
"token_type": "Bearer",
8383
"expires_in": 86399,
8484
"ext_expires_in": 86399,
85-
"access_token": abcdefgh123456............."
85+
"access_token": "abcdefgh123456............."
8686
}
8787
```
8888
Copy the `access_token` value from the response. You'll need it to pass as one of the headers in all calls to the Entitlements API of your Microsoft Energy Data Services Preview instance.
@@ -125,10 +125,12 @@ The value to be sent for the param **"email"** is the **Object_ID (OID)** of the
125125

126126
**Sample request**
127127

128+
Consider a Microsoft Energy Data Services instance named "medstest" with a data partition named "dp1"
129+
128130
```bash
129-
curl --location --request POST 'https://<instance>.energy.azure.com/api/entitlements/v2/groups/users@<instance>-<data-partition-name>.dataservices.energy/members' \
130-
--header 'data-partition-id: <instance>-<data-partition-name>' \
131-
--header 'Authorization: Bearer <access_token>' \
131+
curl --location --request POST 'https://medstest.energy.azure.com/api/entitlements/v2/groups/users@medstest-dp1.dataservices.energy/members' \
132+
--header 'data-partition-id: medstest-dp1' \
133+
--header 'Authorization: Bearer abcdefgh123456.............' \
132134
--header 'Content-Type: application/json' \
133135
--data-raw '{
134136
"email": "90e0d063-2f8e-4244-860a-XXXXXXXXXX",
@@ -163,10 +165,12 @@ The value to be sent for the param **"email"** is the **Object_ID (OID)** of the
163165

164166
**Sample request**
165167

168+
Consider a Microsoft Energy Data Services instance named "medstest" with a data partition named "dp1"
169+
166170
```bash
167-
curl --location --request POST 'https://<instance>.energy.azure.com/api/entitlements/v2/groups/service.search.user@<instance>-<data-partition-name>.dataservices.energy/members' \
168-
--header 'data-partition-id: <instance>-<data-partition-name>' \
169-
--header 'Authorization: Bearer <access_token>' \
171+
curl --location --request POST 'https://medstest.energy.azure.com/api/entitlements/v2/groups/service.search.user@medstest-dp1.dataservices.energy/members' \
172+
--header 'data-partition-id: medstest-dp1' \
173+
--header 'Authorization: Bearer abcdefgh123456.............' \
170174
--header 'Content-Type: application/json' \
171175
--data-raw '{
172176
"email": "90e0d063-2f8e-4244-860a-XXXXXXXXXX",
@@ -195,10 +199,12 @@ Run the below curl command in Azure Cloud Bash to get all the groups associated
195199

196200
**Sample request**
197201

202+
Consider a Microsoft Energy Data Services instance named "medstest" with a data partition named "dp1"
203+
198204
```bash
199-
curl --location --request GET 'https://<instance>.energy.azure.com/api/entitlements/v2/members/90e0d063-2f8e-4244-860a-XXXXXXXXXX/groups?type=none' \
200-
--header 'data-partition-id: <instance>-<data-partition-name>' \
201-
--header 'Authorization: Bearer <access_token>'
205+
curl --location --request GET 'https://medstest.energy.azure.com/api/entitlements/v2/members/90e0d063-2f8e-4244-860a-XXXXXXXXXX/groups?type=none' \
206+
--header 'data-partition-id: medstest-dp1' \
207+
--header 'Authorization: Bearer abcdefgh123456.............'
202208
```
203209
**Sample response**
204210

@@ -210,12 +216,12 @@ Run the below curl command in Azure Cloud Bash to get all the groups associated
210216
{
211217
"name": "users",
212218
"description": "Datalake users",
213-
"email": "users@<instance>-<data-partition-name>.dataservices.energy"
219+
"email": "users@medstest-dp1.dataservices.energy"
214220
},
215221
{
216222
"name": "service.search.user",
217223
"description": "Datalake Search users",
218-
"email": "service.search.user@<instance>-<data-partition-name>.dataservices.energy"
224+
"email": "service.search.user@medstest-dp1.dataservices.energy"
219225
}
220226
]
221227
}
@@ -235,10 +241,12 @@ As stated above, **DO NOT** delete the OWNER of a group unless you have another
235241

236242
**Sample request**
237243

244+
Consider a Microsoft Energy Data Services instance named "medstest" with a data partition named "dp1"
245+
238246
```bash
239-
curl --location --request DELETE 'https://<instance>.energy.azure.com/api/entitlements/v2/members/90e0d063-2f8e-4244-860a-XXXXXXXXXX' \
240-
--header 'data-partition-id: <instance>-<data-partition-name>' \
241-
--header 'Authorization: Bearer <access_token>'
247+
curl --location --request DELETE 'https://medstest.energy.azure.com/api/entitlements/v2/members/90e0d063-2f8e-4244-860a-XXXXXXXXXX' \
248+
--header 'data-partition-id: medstest-dp1' \
249+
--header 'Authorization: Bearer abcdefgh123456.............'
242250
```
243251

244252
**Sample response**

0 commit comments

Comments
 (0)