A correctly set-up Azure environment is a strategic advantage — secure, predictable on cost, and easy to keep building on. That's what I help Norwegian businesses with.
Landing zones and governance — subscription structure, management groups, policies and budgets set up so your organisation can grow without losing visibility.
Identity and access — Entra ID, Workload Identity, RBAC and fine-grained access control. No shared secrets, no long-lived keys.
Networking — Front Door, Application Gateway, Private Endpoints and hub-and-spoke design. Secure, low-latency paths between services and users.
Data layer — Azure SQL, PostgreSQL, Cosmos DB, Storage Accounts. The right type for the workload, with backup, geo-replication and cost control.
Secrets and config — Key Vault and App Configuration as the primary source for everything sensitive and everything that varies between environments. Never in Git.
Infrastructure as code — Bicep or Terraform, modular, with CI validation and policy checks in the pipeline. No click-through portal configuration.
Cost management — Reserved Instances, Savings Plans, autoshut, right-sizing and a monthly cost report at company, environment and service level.
Reduction in annual infrastructure cost — without compromise on performance or delivery speed.
Read the full storyBoth work. Bicep is simpler if you're 100% Azure and want tight ARM integration. Terraform fits better in environments that have or are planning multi-cloud, or where the team already has HCL experience. I've worked extensively with both and can help you choose.
With a short assessment (2–4 weeks): tagging, cost, security, identity, networking and IaC maturity. The result is a written report with concrete actions, prioritised by impact and effort — usually three to five things drive 80% of the gain.
Yes. In practice, right-sizing, autoshut for non-prod, Reserved Instances and cleaning up unused infrastructure typically yields 20–40% in most installations. The exact number depends on what's already there.
Yes. Norwegian businesses often have clear requirements about where data is stored and processed. I set up architectures that keep data in EU/Norway where required, with documentation showing how the requirements are met.
Whether it's a new deployment or a clean-up of an existing one — get in touch for a no-obligation conversation.