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
{{ message }}
This repository was archived by the owner on Sep 10, 2024. It is now read-only.
Both the connection string of the Azure App Configuration and the Azure Service Bus Topic will be needed in the next section, so make sure you have those.
29
27
30
-
## Usage
31
-
Our background job requires both the configuration of Azure App Configuration while setting up the `IConfiguration`,
28
+
## Usage with managed identity
29
+
When connecting to Azure App Configuration using managed identity, you only need to provide the Azure Service Bus topic name and namespace where the Azure App Configuration events are placed:
// Prefix of the Azure Service Bus Topic subscription;
69
+
// this allows the background jobs to support applications that are running multiple instances, processing the same type of events, without conflicting subscription names.
70
+
subscriptionPrefix: "TestSub",
71
+
// The client ID to authenticate for a user assigned managed identity. More information on user assigned managed identities cam be found here:
When using a connection string to connect to Azure App Configuration, our background job requires both the configuration of Azure App Configuration while setting up the `IConfiguration`,
32
80
as well as the [Arcus secret store](https://security.arcus-azure.net/features/secret-store) which will retrieve the connection string of the Azure Service Bus Topic.
0 commit comments