This is the shortest part of the series and the one most likely to save you an afternoon. Pushing an image is three commands — but if you're on an Apple Silicon Mac, one missing flag produces a container that builds perfectly, pushes perfectly, and then refuses to start on Azure.
Your container image is stuck on your laptop, and Azure can't reach your laptop. In this part you'll create the two Azure resources that fix that: a resource group to hold everything, and a container registry to store the image.
Your app works on your machine because your machine happens to have .NET 10 installed. A container removes that "happens to" — it packages the app and the runtime into one box that behaves identically everywhere.
Most "deploy to the cloud" tutorials skip the part where you actually understand what you built. This series does the opposite: six short parts that take you from an empty folder to a real, public URL on Azure, explaining every command along the way.
If you are about to create an Azure OpenAI resource, stop. Microsoft's own guidance is that most use cases should use a Foundry resource instead — it speaks every Azure OpenAI API you already use, and adds the rest of the model catalog, agents and tools on top. This guide creates one from scratch and deploys a model.
Creating an AWS organization takes about thirty seconds and two clicks. Deciding which account you click those two buttons from is permanent. This guide covers both — the decision first, then every screen in order.
Creating an AWS account takes about 10 minutes. This is every screen you will see, in order, with exactly what to enter.
Entity Framework Core maps each database table to an entity class and gives you a DbContext to query them. Most of the time you read from a single DbSet, but sooner or later you need data that lives across two tables — exactly what a SQL JOIN gives you. In EF Core, the lambda-based Join() method does the same job, and it translates into real SQL that runs on the database server.
Everything below targets .NET 10 and EF Core 10, the current Long Term Support releases.
appsettings.json is where an ASP.NET Core app keeps its settings — connection strings, API base URLs, feature flags, timeouts. Reading those values comes down to one service, IConfiguration, which ASP.NET Core registers for you. In a console app you build the same thing yourself in a few lines.
This guide covers both, on .NET 10.
Power Automate is strict about data types. If you try to concatenate a number into a message, save it into a text column, or pass it to a connector that expects text, the flow fails with a type mismatch. The fix is the built-in string() expression, which converts a number or integer into its text or string representation.
