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
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,7 +66,7 @@ Before you can use your app's managed identity, make some changes to the app con
66
66
67
67
Use *one of the following methods* depending on the cloud that your app runs in.
68
68
69
-
***Azure cloud**: If your app runs In *global Azure*, add a setting that identifies an Azure storage account name:
69
+
***Azure cloud**: If your app runs in *public Azure*, add a setting that identifies an Azure storage account name:
70
70
71
71
*`AzureWebJobsStorage__<accountName>`
72
72
@@ -75,7 +75,7 @@ Before you can use your app's managed identity, make some changes to the app con
75
75
***Non-Azure cloud**: If your application runs in a cloud outside of Azure, you must add a specific service URI (endpoint) for the storage account instead of an account name.
76
76
77
77
> [!NOTE]
78
-
> If you're using [Azure Government](../../azure-government/documentation-government-welcome.md) or any other cloud that's separate from global Azure, you must use the option to provide a specific service URL. For more information about using Azure Storage with Azure Government, see [Develop by using the Storage API in Azure Government](../../azure-government/documentation-government-get-started-connect-to-storage.md).
78
+
> If you're using [Azure Government](../../azure-government/documentation-government-welcome.md) or any other cloud that's separate from public Azure, you must use the option to provide a specific service URL. For more information about using Azure Storage with Azure Government, see [Develop by using the Storage API in Azure Government](../../azure-government/documentation-government-get-started-connect-to-storage.md).
79
79
80
80
*`AzureWebJobsStorage__<blobServiceUri>`
81
81
@@ -161,7 +161,7 @@ In the Azure portal, run and test the application. To run and test the app local
161
161
162
162
Use *one of the following methods* depending on the cloud that your app runs in.
163
163
164
-
***Azure cloud**: If your app runs In *global Azure*, add a setting that identifies an Azure storage account name:
164
+
***Azure cloud**: If your app runs in *public Azure*, add a setting that identifies an Azure storage account name:
165
165
166
166
*`AzureWebJobsStorage__<accountName>`
167
167
@@ -170,7 +170,7 @@ In the Azure portal, run and test the application. To run and test the app local
170
170
***Non-Azure cloud**: If your application runs in a cloud outside of Azure, you must add a specific service URI (endpoint) for the storage account instead of an account name.
171
171
172
172
> [!NOTE]
173
-
> If you're using [Azure Government](../../azure-government/documentation-government-welcome.md) or any other cloud that's separate from global Azure, you must use the option to provide a specific service URL. For more information about using Azure Storage with Azure Government, see [Develop by using the Storage API in Azure Government](../../azure-government/documentation-government-get-started-connect-to-storage.md).
173
+
> If you're using [Azure Government](../../azure-government/documentation-government-welcome.md) or any other cloud that's separate from public Azure, you must use the option to provide a specific service URL. For more information about using Azure Storage with Azure Government, see [Develop by using the Storage API in Azure Government](../../azure-government/documentation-government-get-started-connect-to-storage.md).
0 commit comments