• English icon
  • German icon

Articles

Background pieces and tutorials on .NET, Azure and Dynamics 365: what IT teams on the Microsoft stack need to decide right now, step-by-step walkthroughs with video and code, and video explainers of single Azure topics.

Articles & tutorials

E-invoices need no AI: XRechnung and ZUGFeRD are read exactly, only PDFs and scans go through AI and a check.Article6:15

E-invoices and PDF invoices, processed automatically: read exactly, checked before they are saved

Germany's e-invoicing mandate makes incoming invoices a mix of XRechnung, ZUGFeRD and PDFs for years. How an open-source .NET application reads e-invoices exactly without AI, reads PDFs and scans with AI, and recalculates every invoice before it is stored.

dotnete-invoicingxrechnungzugferdopenaipostgresql
Support ends Nov 10, 2026: .NET 8, .NET 9 and the Azure Functions in-process model lose support on the same day.Article8:15

End of support on November 10, 2026: .NET 8, .NET 9 and Azure Functions in-process — what to do now

On November 10, 2026, .NET 8, .NET 9 and the Azure Functions in-process model reach end of support. Apps keep running, but without security updates. What exactly ends, why it hits energy companies hard, and a five-step upgrade plan.

dotnetazure-functionsazure-app-serviceazure-devopsterraformnis2
Azure OpenAI observability in .NET — token usage, cost and latency with OpenTelemetry and Application InsightsTutorial12:57

Monitor Azure OpenAI in .NET — Token Usage, Cost & Latency with OpenTelemetry and Application Insights

Every chat completion costs money and takes time — and by default neither shows up anywhere. This walkthrough adds real observability to an Azure OpenAI integration in .NET: distributed traces, token usage as queryable metrics, and an estimated cost per request, all in Application Insights.

azure-openaiopentelemetryapplication-insightsdotnetterraformobservability
Azure OpenAI without API keys — Managed Identity with DefaultAzureCredential in .NETTutorial7:20

Azure OpenAI Without API Keys in .NET — Managed Identity on Microsoft Foundry

Calling Azure OpenAI with an API key in your config works — until the security review. This is the pattern enterprises actually accept: keyless authentication with Managed Identity and DefaultAzureCredential in .NET. Same code locally and in Azure, no key anywhere.

azure-openaimanaged-identityentra-iddotnetterraformmicrosoft-foundry

Explainers

One Azure topic per video, explained step by step, with a summary, the code and the transcript on each page. Grouped by topic area.

Containers on Azure18

View all 18
200 OK. Still broken: the Azure Kubernetes Service icon, kubectl port-forward answering 200 and a call from inside the cluster refused.Explainer7:24

How to test a Kubernetes Service on AKS (not with port-forward)

v2 broken. v1 serving: the Azure Kubernetes Service icon, the old pod at 1/1, the new pod at 0/1 with a 404, and 718 calls answered, 0 failed.Explainer7:50

Stuck Kubernetes rollout on AKS: ProgressDeadlineExceeded, no rollback

kubectl logs: NotFound: the Azure Kubernetes Service icon and the error from the server, because the pod is gone and its log with it.Explainer9:04

Kubernetes logs on AKS: kubectl logs vs Log Analytics