Skip to content

Commit 71e1789

Browse files
Merge pull request #222979 from Lakshmisha-KS/main
Implementing suggestions
2 parents c2884cd + 515ed58 commit 71e1789

File tree

1 file changed

+15
-13
lines changed

1 file changed

+15
-13
lines changed

articles/energy-data-services/how-to-manage-legal-tags.md

Lines changed: 15 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -42,14 +42,15 @@ Run the below curl command in Azure Cloud Bash to create a legal tag for a given
4242
```
4343

4444
### Sample request
45+
Consider a Microsoft Energy Data Services instance named "medstest" with a data partition named "dp1"
4546

4647
```bash
47-
curl --location --request POST 'https://<instance>.energy.azure.com/api/legal/v1/legaltags' \
48-
--header 'data-partition-id: <instance>-<data-partition-name>' \
49-
--header 'Authorization: Bearer <access_token>' \
48+
curl --location --request POST 'https://medstest.energy.azure.com/api/legal/v1/legaltags' \
49+
--header 'data-partition-id: medstest-dp1' \
50+
--header 'Authorization: Bearer eyxxxxxxx.........................' \
5051
--header 'Content-Type: application/json' \
5152
--data-raw '{
52-
"name": "<instance>-<data-partition-name>-legal-tag",
53+
"name": "medstest-dp1-legal-tag",
5354
"description": "Microsoft Energy Data Services Preview Legal Tag",
5455
"properties": {
5556
"contractId": "A1234",
@@ -69,7 +70,7 @@ Run the below curl command in Azure Cloud Bash to create a legal tag for a given
6970

7071
```JSON
7172
{
72-
"name": "<instance>-<data-partition-name>-legal-tag",
73+
"name": "medsStest-dp1-legal-tag",
7374
"description": "Microsoft Energy Data Services Preview Legal Tag",
7475
"properties": {
7576
"countryOfOrigin": [
@@ -91,9 +92,9 @@ The country of origin should follow [ISO Alpha2 format](https://www.nationsonlin
9192
The Create Legal Tag api, internally appends data-partition-id to legal tag name if it isn't already present. For instance, if request has name as: ```legal-tag```, then the create legal tag name would be ```<instancename>-<data-partition-id>-legal-tag```
9293

9394
```bash
94-
curl --location --request POST 'https://<instance>.energy.azure.com/api/legal/v1/legaltags' \
95-
--header 'data-partition-id: <instance>-<data-partition-name>' \
96-
--header 'Authorization: Bearer <access_token>' \
95+
curl --location --request POST 'https://medstest.energy.azure.com/api/legal/v1/legaltags' \
96+
--header 'data-partition-id: medstest-dp1' \
97+
--header 'Authorization: Bearer eyxxxxxxx.........................' \
9798
--header 'Content-Type: application/json' \
9899
--data-raw '{
99100
"name": "legal-tag",
@@ -116,7 +117,7 @@ The sample response will have data-partition-id appended to the legal tag name a
116117

117118
```JSON
118119
{
119-
"name": "<instance>-<data-partition-name>-legal-tag",
120+
"name": "medstest-dp1-legal-tag",
120121
"description": "Microsoft Energy Data Services Preview Legal Tag",
121122
"properties": {
122123
"countryOfOrigin": [
@@ -143,18 +144,19 @@ Run the below curl command in Azure Cloud Bash to get the legal tag associated w
143144
```
144145

145146
### Sample request
147+
Consider a Microsoft Energy Data Services instance named "medstest" with a data partition named "dp1"
146148

147149
```bash
148-
curl --location --request GET 'https://<instance>.energy.azure.com/api/legal/v1/legaltags/<instance>-<data-partition-name>-legal-tag' \
149-
--header 'data-partition-id: <instance>-<data-partition-name>' \
150-
--header 'Authorization: Bearer <access_token>'
150+
curl --location --request GET 'https://medstest.energy.azure.com/api/legal/v1/legaltags/medstest-dp1-legal-tag' \
151+
--header 'data-partition-id: medstest-dp1' \
152+
--header 'Authorization: Bearer eyxxxxxxx.........................'
151153
```
152154

153155
### Sample response
154156

155157
```JSON
156158
{
157-
"name": "<instance>-<data-partition-name>-legal-tag",
159+
"name": "medstest-dp1-legal-tag",
158160
"description": "Microsoft Energy Data Services Preview Legal Tag",
159161
"properties": {
160162
"countryOfOrigin": [

0 commit comments

Comments
 (0)