NServiceBus can automatically provision the necessary infrastructure to run endpoints by using the installers feature. Enabling installers at the endpoint configuration level lets NServiceBus create queues, database tables and schema, and other infrastructure components required to consume and exchange messages successfully when the endpoint is started up. To do so, endpoints must be run with elevated permissions to grant them infrastructure management rights. Alternatively, infrastructure can be provisioned manually without using installers, for example, by using an Infrastructure as Code (IaC) approach.
Currently, NServiceBus provides limited support for infrastructure-as-code tools. If you're using them today, e.g., Azure Bicep, Azure ARM Templates, Terraform, the AWS CDK, or Polumi, tell us what's missing by voicing your interest on the following public issues: