Calling Database.Migrate() on startup is the demo answer, not the production one. How to actually ship schema changes - idempotent SQL scripts, migration bundles, a least-privilege migration login, and reviewing what EF generated.
You don't need an Azure subscription to put a .NET Web API on the public internet with a real SQL Server database behind it. A free-tier hosting setup, a connection string that actually works remotely, and the limits worth knowing before you rely on it.
Publishing an ASP.NET Core Web API to Azure App Service directly from Visual Studio - creating the App Service plan, choosing the right runtime stack, and the configuration that has to move with the app.
Take an ASP.NET Core Web API from a Dockerfile to a running Kubernetes deployment - multi-stage image build, pushing to a registry, and a Deployment plus Service manifest with three replicas behind a load balancer.
Deploying to IIS is still how a lot of .NET APIs actually ship inside companies with existing Windows Server infrastructure. Installing the Hosting Bundle, the ASP.NET Core Module, and the app pool settings that trip almost everyone up the first time.
.NET Aspire's AppHost orchestrates a multi-project app locally with one F5, then the same model drives an azd deploy straight to Azure. What Aspire actually is, and what "cloud-ready" means in practice.