Guides · 119
What are you trying to do?
Fix a problem
4The error or symptom in front of you, and the fix.Apps & integration
AKS upgrade failed: fix the pod disruption budget and capacity blockers
When an AKS upgrade failed, the cause is almost always a pod disruption budget that allows zero disruptions, two budgets on one pod, or no capacity for surge nodes. Read the UpgradeFailed message, fix the budget or the surge settings, and reconcile the cluster, with the undrainable-node and automatic-budget options for next time.
Apps & integration
App Service 502 and 503 errors: a diagnosis flow from symptom to fix
App Service 502 and 503 errors nearly always mean the app itself is slow, out of memory or CPU, or crashing on start. This diagnosis flow goes from the first symptom to the fix: check service health, read the metrics, use Diagnose and solve problems and Kudu, then mitigate with scale, auto-heal or a restart.
Apps & integration
Azure Functions .NET in-process model ends on 10 November 2026: the migration checklist
Support for the Azure Functions .NET in-process model ends on 10 November 2026. This migration checklist finds the apps that still use it, converts the project, packages, Program.cs, bindings and logging to the isolated worker model, and deploys through a staging slot without an outage.
Apps & integration
Container Apps deployment failures: ImagePullBackOff, failing probes, the wrong target port and identity 403s
Azure Container Apps deployment failures come from a short list: ImagePullBackOff and registry sign-in, a container that crashes on start, health probes that fail, an ingress target port that doesn't match, empty secrets, and a managed identity without the right role. Here is the symptom table, the fix for each, and the six CLI commands that find the cause.
Choose a tool
2Decide before you build.Apps & integration
Azure Functions hosting plans: Flex Consumption, Premium or Consumption, and leaving Linux Consumption by 2028
Which Azure Functions hosting plan to pick in 2026: Flex Consumption is the serverless default, Premium is for always-warm or long-running apps, Consumption is legacy and its Linux form retires on 30 September 2028. With the limits that decide it, and the migration to Flex Consumption step by step.
Apps & integration
Where should my code run on Azure? App Service vs Functions vs Container Apps vs AKS
App Service vs Functions vs Container Apps vs AKS, decided in four questions: do you have an existing app to move, is the work event-driven, do you ship containers, and do you need the Kubernetes API. With Microsoft's own tables on skills, scale, networking and cost, and the mistakes each choice invites.