Microsoft Azure (Cloud)
Building and running .NET applications and SQL databases on Microsoft Azure, including the identity, access, and backup settings that come with them.
Azure can be a natural fit for a business that already runs .NET applications and SQL Server. Web apps and APIs move to App Service or containers, scheduled and event-driven work moves to Azure Functions, and databases move to Azure SQL Database or Azure SQL Managed Instance. IKRC plans and carries out those moves, and builds new applications on Azure where it suits the workload.
Settings to check after a migration
- Backup retention. Azure SQL Database keeps point-in-time restore backups for 7 days by default, configurable from 1 to 35 days (1 to 7 on the Basic tier). Keeping backups longer, up to 10 years, needs a long-term retention policy, which is not enabled by default.
- Credentials. A managed identity lets an App Service app or Function authenticate to Azure SQL, Key Vault, or Storage through Microsoft Entra ID, with no password or key in a connection string or configuration file. The identity still has to be granted access, such as a database user or an Azure role assignment, before it can read or change anything.
- Access. The people who can change production resources should be a short, reviewed list of role assignments.
Database work on Azure overlaps with our Microsoft SQL Server service, and application work with .NET development.
Ready to get started?
Describe the system or process you want built or fixed, and we will follow up to talk through the project.
Contact IKRC