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-durable-functions-with-credentials.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ Navigate to your Azure function app’s **Configuration** page and perform the f
51
51
52
52
1. Remove the default value "AzureWebJobsStorage".
53
53
54
-

54
+

55
55
56
56
2. Link your Azure storage account by adding **either one** of the following value settings:
57
57
@@ -66,7 +66,7 @@ Navigate to your Azure function app’s **Configuration** page and perform the f
66
66
> [!NOTE]
67
67
> If you are using [Azure Government](../../azure-government/documentation-government-welcome.md) or any other cloud that's separate from global Azure, then you will need to use this second option to provide specific service URLs. The values for these settings can be found in the storage account under the **Endpoints** tab. For more information on using Azure Storage with Azure Government, see the [Develop with Storage API on Azure Government](../../azure-government/documentation-government-get-started-connect-to-storage.md) documentation.
68
68
69
-

69
+

70
70
71
71
3. Finalize your managed identity configuration:
72
72
@@ -77,7 +77,7 @@ Navigate to your Azure function app’s **Configuration** page and perform the f
77
77
78
78
***AzureWebJobsStorage__clientId**: (This is a GUID value that you obtain from the Azure AD portal)
79
79
80
-

80
+

81
81
82
82
83
83
@@ -104,7 +104,7 @@ In particular, this quickstart assumes that you have already:
104
104
105
105
3. Copy and save the secret value carefully because it will not show up again after you leave the page.
106
106
107
-

107
+

108
108
109
109
### Assign Role-based Access Controls (RBAC) to the client application
110
110
@@ -116,11 +116,11 @@ Assign these three roles to your client application with the following steps.
116
116
117
117
1. Navigate to your function’s storage account **Access Control (IAM)** page and add a new role assignment.
118
118
119
-

119
+

120
120
121
121
2. Choose the required role, click next, then search for your application, review and add.
122
122
123
-

123
+

124
124
125
125
### Add client secret configuration
126
126
@@ -140,7 +140,7 @@ To run and test in Azure, specify the followings in your Azure function app’s
140
140
141
141
The values for these Uri variables can be found in the storage account under the **Endpoints** tab.
142
142
143
-

143
+

144
144
145
145
3. Add a client secret credential by specifying the following values:
146
146
***AzureWebJobsStorage__clientId**: (this is a GUID value found in the Azure AD application page)
@@ -151,5 +151,5 @@ To run and test in Azure, specify the followings in your Azure function app’s
151
151
152
152
The client ID and tenant ID values can be found on your client application’s overview page. The client secret value is the one that was carefully saved in the previous step. It will not be available after the page is refreshed.
153
153
154
-

154
+

0 commit comments