Hosting and releases
ASP.NET Core and Blazor applications on App Service, released from Azure DevOps. A new version goes out without downtime and without copying files by hand, and rolling back is one click.
- App Service
- Azure DevOps
- Deployment slots
Azure for .NET applications
Your .NET application on Azure, in order and cheaper to run
ProCoding is a .NET studio from Split, Croatia (EU). On Azure we work with what most companies actually use: hosting, the database, monitoring, secrets and releases. The goal is an application that runs reliably, problems you hear about before your users do, and a bill that doesn’t grow for no reason.
Vlado Pandžić · Founder · Senior .NET architect
14 years in .NET, and years of applications in production on Azure. Microsoft Certified: Azure Fundamentals, Azure AI Fundamentals and Azure Data Fundamentals. You talk to him directly.
var builder = WebApplication.CreateBuilder(args); builder.Configuration.AddAzureKeyVault( new Uri("https://orders-kv.vault.azure.net/"), new DefaultAzureCredential()); builder.Services.AddOpenTelemetry().UseAzureMonitor();builder.Services.AddHealthChecks() .AddDbContextCheck<OrdersDbContext>(); var app = builder.Build(); app.MapHealthChecks("/health");app.Run();- 14
- years in .NET
- 2013
- working with our longest client since
- CET
- the same working hours as you
- EU
- company, contract and invoices
What we do on Azure
Nothing exotic. The services most business .NET applications run on, set up the way they should be.
Database
Azure SQL that is fast because the queries and indexes are good, not because you pay for the highest tier. The right database size for the real load.
- Azure SQL
- Indexes
- Query Store
Monitoring
Application Insights and alerts that tell you when something goes wrong, before a user calls. You see which screen is slow, which query, and why.
- Application Insights
- Azure Monitor
- Alerts
Security
Passwords and keys in Key Vault instead of in code and configuration. User sign-in through Entra ID, with permissions that match the roles in your company.
- Key Vault
- Entra ID
- Permissions
Background jobs
Imports, exports, notifications and nightly processing in Azure Functions, separate from the web application, so one doesn’t slow the other down.
- Azure Functions
- Scheduled jobs
AI in your application
Azure OpenAI connected to your data and your application, inside your own Azure subscription, instead of people pasting documents into public tools.
- Azure OpenAI
- Your data
- Your subscription
Three ways to start
Each one has a clear result, so you know what you get before we start.
The problems we find most often on Azure
Azure is rarely the problem on its own. It is almost always one of these five.
The bill grows every month
Oversized plans, forgotten environments and logs recorded without any sampling. Most of the savings are found on the first day of looking.
You hear about problems from your users
Application Insights isn’t switched on, or nobody looks at it, and there are no alerts. Once it is set up, you know what broke and where, before anyone calls.
Passwords in configuration and pipelines
Connection strings and API keys in appsettings.json or in pipeline variables. They move to Key Vault, and the application reaches them without a single password in the code.
Releases with downtime, or by hand
A new version means a few minutes of downtime, or someone copying files by hand. A pipeline in Azure DevOps and deployment slots solve both.
Azure SQL slow or too expensive
A higher database tier bought to cover bad queries. Once the queries and indexes are fixed, the database can often go back to a lower tier.
What sorting it out looks like
The order is always the same, because without measuring you don’t know what to fix or how much you saved.
- 01
Measure
Application Insights and a cost review show where the time and the money go.
- 02
Secrets
Every password and key in Key Vault, and access reduced to what is really needed.
- 03
Releases
A pipeline from Azure DevOps and zero-downtime releases, with a one-click rollback.
- 04
Right size
Plans and the database sized for the real load, and unused resources switched off.
When it fits, and when it doesn’t
We are a good fit when
- +You have a .NET application on Azure, or you are moving it there
- +You already use Microsoft 365 and Entra ID
- +You want services maintained by Microsoft, not your own servers
- +You need someone who knows both the application and Azure, not just one of them
We are not a good fit when
- −You need a whole cloud platform for hundreds of services and Kubernetes clusters
- −You have one small application that a plain virtual server runs more cheaply
- −You are looking for someone just for networking, domains and Windows servers
Tools
- Azure App Service
- Azure SQL
- Application Insights
- Azure Monitor
- Key Vault
- Entra ID
- Azure Functions
- Azure DevOps
- Azure OpenAI
Questions
For .NET applications, often yes, because App Service and Azure SQL take server maintenance, patches and backups off your hands. For one small application with few users, a plain virtual server can be cheaper. We will tell you what pays off in your case.
Usually because of oversized plans, environments nobody uses, test systems running around the clock and logs without sampling. A cost review shows exactly where the money goes and how much can be saved.
For most ASP.NET Core and Blazor applications, App Service: no operating system to maintain, simpler releases, and scaling is one click. A virtual machine makes sense when the application needs something App Service doesn’t support.
Yes. We connect Azure OpenAI to your data and your existing .NET application, inside your own Azure subscription, so the data doesn’t go into public tools.
Yes, with .NET applications on AWS too, including Lambda functions. This page is about Azure because most .NET teams use it.
The cost review and the health check are agreed after a free 30-minute call, once we know how big the system is. Development is billed by the hour or as a monthly block of days.
Yes. It is often most useful to work alongside your team: set up monitoring, the pipeline and Key Vault together, so the knowledge stays with you.
Your Azure bill keeps growing and you don’t know why? Or you don’t know what is happening in production?
A free 30-minute call is enough to see where the problem is and what the first step should be.
Book a free 30-minute call →- EU company, Split, Croatia
- Central European hours
- NDA on request
- You talk to the engineer who writes the code
Useful to send with your message
- /Which Azure services you use
- /Rough monthly bill
- /Your .NET version
- /What is bothering you right now