Skip to content

Azure consulting services

Azure for the application, not a diagram

We put .NET APIs and web apps on Azure when that is where they should run: App Service or containers, a managed database, storage, and secrets kept out of the repo. AWS is the same kind of job when that is the cloud you already use.

Hosting, database, and deploy

For a .NET or web application, the usual pieces are App Service, a database the app already speaks, storage, and a pipeline. GitHub Actions or Azure DevOps builds and deploys it.

The warehouse application sat on SQL and can stay on the desk. A product we run uses Postgres. The database choice follows the application.

What belongs in Key Vault

Carrier tokens and application secrets belong in a vault, not in loose config. On the UPS integration, credentials and carrier tokens were kept out of loose config and logs.

What done means for a first deploy

The repo builds, the app is on App Service, secrets are in the vault, and the pipeline can deploy again. AWS is the same kind of job when that is the cloud you already use.

What this includes

  • App Service, Azure SQL or Postgres, storage, and Key Vault for secrets.
  • GitHub Actions or Azure DevOps to build, test, and deploy.
  • A product we run ourselves uses this pattern on Azure.

Work you can open

Book a project call

Frequently asked questions

Does the warehouse desktop app have to move to Azure?

No. The floor application can stay on the desk. Move the parts that need hosting, such as an API or a web product.

Where should API tokens live?

In Key Vault, or the equivalent secret store. On the UPS integration, credentials and carrier tokens were kept out of loose config and logs.

Which database do you deploy?

The one the application already speaks. The warehouse system used SQL. A product we run uses Postgres.

Related services