You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-functions/durable/durable-functions-configure-managed-identity.md
+14-18Lines changed: 14 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,43 +91,39 @@ To find your identity resource, select assign access to **Managed identity** and
91
91
92
92
### Add managed identity configuration to your app
93
93
94
-
Before you can use your app's managed identity, make some changes to the app configuration:
94
+
Before you can use your app's managed identity, make some changes to the app settings:
95
95
96
-
1. In the Azure portal, on your function app resource menu under **Settings**, select **Configuration**.
96
+
1. In the Azure portal, on your function app resource menu under **Settings**, select **Environment variables**.
97
97
98
-
1. In the list of settings, select**AzureWebJobsStorage** and select the **Delete** icon.
98
+
1. In the list of settings, find**AzureWebJobsStorage** and select the **Delete** icon.
99
99
[](./media/durable-functions-configure-df-with-credentials/durable-functions-managed-identity-scenario-01.png#lightbox)
100
100
101
101
1. Add a setting to link your Azure storage account to the application.
102
102
103
103
Use *one of the following methods* depending on the cloud that your app runs in:
104
104
105
-
-**Azure cloud**: If your app runs in *public Azure*, add a setting that identifies an Azure storage account name:
105
+
-**Azure cloud**: If your app runs in *public Azure*, add the setting `AzureWebJobsStorage__accountName`that identifies an Azure storage account name. Example value: `mystorageaccount123`
106
106
107
-
-`AzureWebJobsStorage__accountName: < Azure Storage account name >`
107
+
-**Non-Azure cloud**: If your application runs in a cloud outside of Azure, you must add the following three settings to provide specific service URIs (or *endpoints*) of the storage account instead of an account name.
-**Non-Azure cloud**: If your application runs in a cloud outside of Azure, you must add a specific service URI (*an endpoint*) for the storage account instead of an account name.
111
+
Example value: `https://mystorageaccount123.blob.core.windows.net/`
112
112
113
-
-`AzureWebJobsStorage__blobServiceUri: < Service endpoint >`
You can get the values for these URI variables in the storage account information on the Endpoints tab.
121
+
You can get the values for these URI variables in the storage account information from the **Endpoints** tab.
126
122
127
123

128
124
129
125
> [!NOTE]
130
-
> If you are using [Azure Government](../../azure-government/documentation-government-welcome.md) or any other cloud that's separate from public Azure, you must use the option that provides a specific service URI. For more information on using Azure Storage with Azure Government, see the [Develop by using the Storage API in Azure Government](../../azure-government/documentation-government-get-started-connect-to-storage.md).
126
+
> If you are using [Azure Government](../../azure-government/documentation-government-welcome.md) or any other cloud that's separate from public Azure, you must use the option that provides specific service URIs instead of just the storage account name. For more information on using Azure Storage with Azure Government, see the [Develop by using the Storage API in Azure Government](../../azure-government/documentation-government-get-started-connect-to-storage.md).
131
127
132
128
1. Finish your managed identity configuration (remember to click "Apply" after making the setting changes):
133
129
@@ -142,7 +138,7 @@ Before you can use your app's managed identity, make some changes to the app con
142
138

143
139
144
140
> [!NOTE]
145
-
> Durable Functions does *not* support `managedIdentityResourceId` when using user-assigned identity. Use `clientId` instead.
141
+
> Durable Functions does *not* support `managedIdentityResourceId`today when using user-assigned identity. Use `clientId` instead.
0 commit comments