Skip to content

Commit 0485ca6

Browse files
committed
edit pass: how-to-use-managed-identity
1 parent 659c2ef commit 0485ca6

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/energy-data-services/how-to-use-managed-identity.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ This article describes how to access the data plane or control plane of Microsof
1717

1818
There's a need for services such as Azure Functions to be able to consume Microsoft Energy Data Services APIs. This interoperability allows you to use the best capabilities of multiple Azure services.
1919

20-
For example, you can write a script in Azure Functions to ingest data in Microsoft Energy Data Services. In that scenario, you should assume that Azure Functions is the source service while Microsoft Energy Data Services is the target service.
20+
For example, you can write a script in Azure Functions to ingest data in Microsoft Energy Data Services. In that scenario, you should assume that Azure Functions is the source service and Microsoft Energy Data Services is the target service.
2121

2222
This article walks you through the five main steps for configuring Azure Functions to access Microsoft Energy Data Services.
2323

@@ -81,7 +81,7 @@ Retrieve the application ID of the user-assigned identity by using the object ID
8181

8282
## Step 4: Add the application ID to entitlement groups
8383

84-
Next, add the application ID to the appropriate groups that will use the entitlement service to access Microsoft Energy Data Services APIs. The following example adds the Application ID to two groups:
84+
Next, add the application ID to the appropriate groups that will use the entitlement service to access Microsoft Energy Data Services APIs. The following example adds the application ID to two groups:
8585

8686
* users@[partition ID].dataservices.energy
8787
* users.datalake.editors@[partition ID].dataservices.energy
@@ -96,7 +96,7 @@ Next, add the application ID to the appropriate groups that will use the entitle
9696
* [Access token](how-to-manage-users.md#prerequisites)
9797
* Application ID of the managed identity
9898

99-
2. Use the [Add Member API](https://microsoft.github.io/meds-samples/rest-apis/index.html?page=/meds-samples/rest-apis/entitlements_openapi.yaml#/add-member-api/addMemberUsingPOST) to add the application ID of the user-managed identity to the appropriate entitlement groups.
99+
2. Use the [Add Member API](https://microsoft.github.io/meds-samples/rest-apis/index.html?page=/meds-samples/rest-apis/entitlements_openapi.yaml#/add-member-api/addMemberUsingPOST) to add the application ID of the user-assigned managed identity to the appropriate entitlement groups.
100100

101101
> [!NOTE]
102102
> In the following commands, be sure to use the application ID of the managed identity and not the object ID.

0 commit comments

Comments
 (0)