Skip to content

Commit 21df5e7

Browse files
committed
Clarity edits
1 parent c23ec4f commit 21df5e7

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

articles/logic-apps/customer-managed-keys-integration-service-environment.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -22,11 +22,11 @@ This topic shows how to set up and specify your own encryption key to use when y
2222

2323
* You can specify a customer-managed key *only when you create your ISE*, not afterwards. You can't disable this key after your ISE is created. Currently, no support exists for rotating a customer-managed key for an ISE.
2424

25-
* To support customer-managed keys, your ISE requires requires having its [system-assigned managed identity](../active-directory/managed-identities-azure-resources/overview.md#how-does-the-managed-identities-for-azure-resources-work) enabled. This identity helps the ISE authenticate access to resources in other Azure Active Directory (Azure AD) tenants so that you don't have to sign in with your own credentials.
25+
* To support customer-managed keys, your ISE requires requires having its [system-assigned managed identity](../active-directory/managed-identities-azure-resources/overview.md#how-does-the-managed-identities-for-azure-resources-work) enabled. This identity lets the ISE authenticate access to resources in other Azure Active Directory (Azure AD) tenants so that you don't have to sign in with your credentials.
2626

27-
* Currently, the only way to create an ISE that supports a customer-managed key and has its system-assigned identity enabled is by calling the Logic Apps REST API with an HTTPS PUT request.
27+
* Currently, to create an ISE that supports customer-managed keys and has its system-assigned identity enabled, you have to call the Logic Apps REST API by using an HTTPS PUT request.
2828

29-
* Within *30 minutes* after you send the HTTPS PUT request that creates your ISE, you must [grant access to your key vault for your ISE's system-assigned identity](#identity-access-to-key-vault). Otherwise, ISE creation fails and throws a permissions error.
29+
* Within *30 minutes* after you send the HTTPS PUT request that creates your ISE, you must [give key vault access to your ISE's system-assigned identity](#identity-access-to-key-vault). Otherwise, ISE creation fails and throws a permissions error.
3030

3131
## Prerequisites
3232

@@ -183,7 +183,9 @@ This example request body shows the sample values:
183183

184184
## Grant access to your key vault
185185

186-
Within *30 minutes* after you send the HTTP PUT request to create your ISE, you must grant access to your key vault for your ISE's system-assigned identity. Otherwise, creation for your ISE fails, and you get a permissions error. For this task, add an access policy to your key vault for your ISE's system-assigned identity. You can use either the Azure PowerShell [Set-AzKeyVaultAccessPolicy](https://docs.microsoft.com/powershell/module/az.keyvault/set-azkeyvaultaccesspolicy) command, or you can follow these steps in the Azure portal:
186+
Within *30 minutes* after you send the HTTP PUT request to create your ISE, you must add an access policy to your key vault for your ISE's system-assigned identity. Otherwise, creation for your ISE fails, and you get a permissions error.
187+
188+
For this task, you can use either the Azure PowerShell [Set-AzKeyVaultAccessPolicy](https://docs.microsoft.com/powershell/module/az.keyvault/set-azkeyvaultaccesspolicy) command, or you can follow these steps in the Azure portal:
187189

188190
1. In the [Azure portal](https://portal.azure.com), open your Azure key vault.
189191

0 commit comments

Comments
 (0)