Blog topic
Production Azure architectures for .NET — App Service, Managed Identity, Key Vault, Service Bus, and Azure Functions isolated worker.
Cloud-native .NET on Azure without credential leaks or configuration debt. Start with Managed Identity on Azure or Key Vault secrets in ASP.NET Core.
This page is the article map for deploying and operating ASP.NET Core workloads on Microsoft Azure.
| You want… | Open |
|---|---|
| Passwordless SQL & Storage | Managed Identity on Azure |
| Secure configuration & secrets | Key Vault secrets in ASP.NET Core |
| App Service deployment & slots | Deploy to Azure App Service |
| Enterprise messaging & pub/sub | Azure Service Bus with ASP.NET Core |
| Isolated worker serverless functions | Azure Functions isolated worker |
| Private blob uploads & SAS | Azure Blob Storage uploads |
Each guide provides tested infrastructure configurations and runtime resilience patterns.
Related: API Security · Architecture · DevOps & CI/CD
Use Managed Identity on Azure with DefaultAzureCredential to eliminate connection string credentials.
Configure Azure Key Vault as an IConfiguration provider: Key Vault secrets in ASP.NET Core.
Compare Azure Service Bus messaging with Azure Functions isolated worker.
9 min read
Passwordless Managed Identity for ASP.NET Core on Azure — system vs user-assigned overview, EF Core + Azure SQL, BlobClient with DefaultAzureCredential, Key Vault RBAC, and local dual-mode config. Not a Blob upload UX rewrite.
8 min read
Wire Azure Key Vault into ASP.NET Core configuration — AddAzureKeyVault, secret name mapping, reload/sentinel patterns, leak-prevention with Serilog, Key Vault references vs App Settings, and rotation habits. Pairs with Managed Identity; not a full App Service deploy rewrite.
Updated Published 8 min read
Lessons from shipping ASP.NET Core APIs to Azure App Service in healthcare and SaaS — configuration, deployment slots, secrets, health checks, and the failures that only show up after go-live.
10 min read
Use Azure Service Bus from ASP.NET Core — ServiceBusClient, processors in BackgroundService, queues vs topics vs sessions, JSON pitfalls, peek-lock, and where the transactional outbox fits. Not an outbox theory rewrite.
10 min read
Run Azure Functions isolated worker for .NET beside an ASP.NET Core API — Program.cs DI, HTTP triggers, shared contracts, local Core Tools, and when Functions should not replace App Service.
7 min read
Practical ASP.NET Core patterns for uploading files to Azure Blob Storage — validation, private containers, SAS, metadata, and Angular-friendly APIs.