Skip to content

Commit 7a84f9f

Browse files
committed
updating per review feedback
1 parent 9ee12fe commit 7a84f9f

File tree

2 files changed

+19
-19
lines changed

2 files changed

+19
-19
lines changed

articles/healthcare-apis/deidentification/manage-access-rbac.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ To assign an Azure role to a security principal with PowerShell, call the [New-A
5353

5454
The format of the command can differ based on the scope of the assignment, but `ObjectId` and `RoleDefinitionName` are required parameters. While the `Scope` parameter is optional, you should set it to retain the principle of least privilege. By limiting roles and scopes, you limit the resources that are at risk if the security principal is ever compromised.
5555

56-
The scope for a de-identification service (preview) is in the form `/subscriptions/<Subscription ID>/resourceGroups/<Resource Group Name>/providers/Microsoft.HealthDataAIServices/deidServices/<Deidentification Service Name>`
56+
The scope for a de-identification service (preview) is in the form `/subscriptions/<Subscription ID>/resourceGroups/<Resource Group Name>/providers/Microsoft.HealthDataAIServices/deidServices/<De-identification Service Name>`
5757

5858
The example assigns the **DeID Data Owner** built-in role to a user, scoped to a specific de-identification service. Make sure to replace the placeholder values
5959
in angle brackets `<>` with your own values:
@@ -62,15 +62,15 @@ in angle brackets `<>` with your own values:
6262
New-AzRoleAssignment
6363
-SignInName <Email> `
6464
-RoleDefinitionName "DeID Data Owner" `
65-
-Scope "/subscriptions/<Subscription ID>/resourceGroups/<Resource Group Name>/providers/Microsoft.HealthDataAIServices/deidServices/<Deidentification Service Name>"
65+
-Scope "/subscriptions/<Subscription ID>/resourceGroups/<Resource Group Name>/providers/Microsoft.HealthDataAIServices/deidServices/<De-identification Service Name>"
6666
```
6767

6868
A successful response should look like:
6969

7070
```
7171
console
72-
RoleAssignmentId : /subscriptions/<Subscription ID>/resourceGroups/<Resource Group Name>/providers/Microsoft.HealthDataAIServices/deidServices/<Deidentification Service Name>/providers/Microsoft.Authorization/roleAssignments/<Role Assignment ID>
73-
Scope : /subscriptions/<Subscription ID>/resourceGroups/<Resource Group Name>/providers/Microsoft.HealthDataAIServices/deidServices/<Deidentification Service Name>
72+
RoleAssignmentId : /subscriptions/<Subscription ID>/resourceGroups/<Resource Group Name>/providers/Microsoft.HealthDataAIServices/deidServices/<De-identification Service Name>/providers/Microsoft.Authorization/roleAssignments/<Role Assignment ID>
73+
Scope : /subscriptions/<Subscription ID>/resourceGroups/<Resource Group Name>/providers/Microsoft.HealthDataAIServices/deidServices/<De-identification Service Name>
7474
DisplayName : Mark Patrick
7575
SignInName : [email protected]
7676
RoleDefinitionName : DeID Data Owner
@@ -88,15 +88,15 @@ To assign an Azure role to a security principal with Azure CLI, use the [az role
8888

8989
The format of the command can differ based on the type of security principal, but `role` and `scope` are required parameters.
9090

91-
The scope for a de-identification service (preview) is in the form `/subscriptions/<Subscription ID>/resourceGroups/<Resource Group Name>/providers/Microsoft.HealthDataAIServices/deidServices/<Deidentification Service Name>`
91+
The scope for a de-identification service (preview) is in the form `/subscriptions/<Subscription ID>/resourceGroups/<Resource Group Name>/providers/Microsoft.HealthDataAIServices/deidServices/<De-identification Service Name>`
9292

9393
The following example assigns the **DeID Data Owner** built-in role to a user, scoped to a specific de-identification service. Make sure to replace the placeholder values in angle brackets `<>` with your own values:
9494

9595
```azurecli
9696
az role assignment create \
9797
--assignee <Email> \
9898
--role "DeID Data Owner" \
99-
--scope "/subscriptions/<Subscription ID>/resourceGroups/<Resource Group Name>/providers/Microsoft.HealthDataAIServices/deidServices/<Deidentification Service Name>"
99+
--scope "/subscriptions/<Subscription ID>/resourceGroups/<Resource Group Name>/providers/Microsoft.HealthDataAIServices/deidServices/<De-identification Service Name>"
100100
```
101101

102102
For more information, see [Assign Azure roles using Azure PowerShell](/azure/role-based-access-control/role-assignments-cli).

articles/healthcare-apis/deidentification/quickstart-sdk-net.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.date: 08/05/2024
1010
---
1111

1212

13-
# Quickstart: Azure Health Deidentification client library for .NET
13+
# Quickstart: Azure Health De-identification client library for .NET
1414

1515
Get started with the Azure Health De-identification client library for .NET to de-identify your health data. Follow these steps to install the package and try out example code for basic tasks.
1616

@@ -23,7 +23,7 @@ Get started with the Azure Health De-identification client library for .NET to d
2323

2424
## Setting up
2525

26-
### Create a deidentification service (preview)
26+
### Create a de-identification service (preview)
2727

2828
A de-identification service (preview) provides you with an endpoint URL. This endpoint url can be utilized as a Rest API or with an SDK.
2929

@@ -47,7 +47,7 @@ A de-identification service (preview) provides you with an endpoint URL. This en
4747
az storage account create --name $STORAGE_ACCOUNT_NAME --resource-group $RESOURCE_GROUP_NAME --location $REGION
4848
```
4949

50-
### Authorize deidentification service (preview) on the Azure Storage account
50+
### Authorize de-identification service (preview) on the Azure Storage account
5151

5252
- Give the de-identification service (preview) access to your storage account
5353

@@ -82,13 +82,13 @@ The client library is available through NuGet, as the `Azure.Health.Deidentifica
8282

8383

8484
## Code examples
85-
- [Create a Deidentification Client](#create-a-deidentification-client)
85+
- [Create a de-identification Client](#create-a-de-identification-client)
8686
- [De-identify a string](#de-identify-a-string)
8787
- [Tag a string](#tag-a-string)
88-
- [Create a Deidentification Job](#create-a-deidentification-job)
89-
- [Get the status of a Deidentification Job](#get-the-status-of-a-deidentification-job)
88+
- [Create a de-identification Job](#create-a-de-identification-job)
89+
- [Get the status of a de-identification Job](#get-the-status-of-a-de-identification-job)
9090

91-
### Create a deidentification client
91+
### Create a de-identification client
9292

9393
Before you can create the client, you need to find your **de-identification service (preview) endpoint URL**.
9494

@@ -131,7 +131,7 @@ content.Operation = OperationType.Tag;
131131
DeidentificationResult result = await client.DeidentifyAsync(content);
132132
```
133133

134-
### Create a deidentification job
134+
### Create a de-identification job
135135

136136
This function allows you to de-identify all files, filtered via prefix, within an Azure Blob Storage Account.
137137

@@ -156,7 +156,7 @@ DeidentificationJob job = new(
156156
job = client.CreateJob(WaitUntil.Started, "my-job-1", job).Value;
157157
```
158158

159-
### Get the status of a deidentification job
159+
### Get the status of a de-identification job
160160

161161
Once a job is created, you can view the status and other details of the job.
162162

@@ -175,13 +175,13 @@ dotnet run
175175

176176
## Clean up resources
177177

178-
### Delete deidentification service
178+
### Delete de-identification service
179179

180180
```bash
181181
az resource delete -n $DEID_SERVICE_NAME -g $RESOURCE_GROUP_NAME --resource-type microsoft.healthdataaiservices/deidservices
182182
```
183183

184-
### Delete Azure Storage Account
184+
### Delete Azure Storage account
185185

186186
```bash
187187
az resource show -n $STORAGE_ACCOUNT_NAME -g $RESOURCE_GROUP_NAME --resource-type Microsoft.Storage/storageAccounts
@@ -200,7 +200,7 @@ az role assignment delete --assignee $DEID_SERVICE_PRINCIPAL_ID --role "Storage
200200

201201
Ensure the permissions are given, and the Managed Identity for the de-identification service (preview) is set up properly.
202202

203-
See [Authorize deidentification service on Storage Account](#authorize-deidentification-service-preview-on-the-azure-storage-account)
203+
See [Authorize de-identification service (preview) on the Azure Storage account](#authorize-de-identification-service-preview-on-the-azure-storage-account)
204204

205205
### Job failed with status PartialFailed
206206

@@ -213,7 +213,7 @@ See [Sample](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/healthdata
213213

214214
In this quickstart, you learned:
215215
- How to create a de-identification service (preview) and assign a role on a storage account.
216-
- How to create a deidentification client
216+
- How to create a de-identification client
217217
- How to de-identify strings and create jobs on documents within a storage account.
218218

219219
> [!div class="nextstepaction"]

0 commit comments

Comments
 (0)