NServiceBus can automatically provision the required infrastructure to run endpoints by using the installers feature. When installers are enabled at the endpoint configuration level, during startup, NServiceBus creates queues, database tables and schema, and several other infrastructure components required to consume and exchange messages successfully.
To do so, endpoints must run with elevated permissions to grant them infrastructure management rights. The alternative is to manually provision infrastructure without using installers, for example, by using an Infrastructure as Code (IaC) approach.
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: