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/container-apps/dapr-components.md
+41-11Lines changed: 41 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: hhunter-ms
6
6
ms.service: azure-container-apps
7
7
ms.custom: build-2023
8
8
ms.topic: conceptual
9
-
ms.date: 08/02/2024
9
+
ms.date: 09/23/2024
10
10
---
11
11
12
12
# Dapr components in Azure Container Apps
@@ -154,15 +154,23 @@ scopes:
154
154
155
155
#### Referencing Dapr secret store components
156
156
157
-
Once you [create a Dapr secret store using one of the previous approaches](#creating-a-dapr-secret-store-component), you can reference that secret store from other Dapr components in the same environment. In the following example, the `secretStoreComponent` field is populated with the name of the secret store specified in the previous examples, where the `sb-root-connectionstring` is stored.
157
+
Once you [create a Dapr secret store using one of the previous approaches](#creating-a-dapr-secret-store-component), you can reference that secret store from other Dapr components in the same environment. The following example demonstrates using Entra ID authentication.
0 commit comments