Can we add a ARM parameter and logic to allow the deployment to select an existing Azure storage account? My understanding is that the EventHubForwarder ARM template deployment always creates a new Azure Storage Account, and is not configurable. This may be redundant as some organizations already have provisioned Storage Accounts.
Desired Behaviour
Add a new ARM parameter to accept the name of the existing Azure Storage account to be used.
Add logic to resources section that will only create a new storage account if no storage account name is provided.
Summary
Can we add a ARM parameter and logic to allow the deployment to select an existing Azure storage account? My understanding is that the EventHubForwarder ARM template deployment always creates a new Azure Storage Account, and is not configurable. This may be redundant as some organizations already have provisioned Storage Accounts.
Desired Behaviour
parameter
to accept the name of the existing Azure Storage account to be used.resources
section that will only create a new storage account if no storage account name is provided.