Logo
  • English icon
  • German icon

Articles

Background pieces and tutorials on .NET, Azure and Dynamics 365: what IT teams in the energy sector need to decide right now, plus step-by-step walkthroughs with video and code.

E-invoices need no AI. PDFs: AI + a check. XRechnung, ZUGFeRD, PDFArticle6: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
End of support on November 10, 2026: .NET 8, .NET 9 and Azure FunctionsArticle8: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