Recent Territory work.

The Challenge

The agency needed a multi-environment application platform inside its own Azure estate. The vendor's prescribed Kubernetes model did not fit the organisation's landing zone or access controls, and the corporate data centre could not host the required container platform.

What we did

We designed and built the Azure foundation in the organisation's landing zone. Non-production and production Azure Kubernetes Service clusters, private networking, Azure Container Registry, secrets management, and monitoring were delivered with infrastructure as code, fitted to the agency's subscription and access model. Application teams deploy onto the platform through GitOps.

The Outcome

Workloads now run in the organisation's subscriptions on a platform the agency owns and controls, without forcing a vendor-shaped cluster onto the landing zone.

The Challenge

Core biodiversity websites and internal tools needed a secure home in the organisation's Azure landing zone, including a public-facing site that still had to reach data left on-premises.

What we did

We stood up non-production and production environments in the landing zone and onboarded the applications onto shared Azure App Service, Azure SQL, storage, and private networking. Public entry uses Azure Front Door; internal apps stay on the private network. Further applications were added on the same pattern rather than as one-off builds.

The Outcome

The web estate runs in the organisation's subscriptions on a repeatable platform, with room to bring more systems across without redesigning the foundation.

The Challenge

A container-based collection-management system did not fit the existing web-app pattern. The agency needed a proof of value inside the same landing zone before committing to a full cutover.

What we did

We designed an Azure Container Apps platform in the existing biodiversity subscriptions: private networking, managed database and cache, Azure Container Registry, secrets, and Entra ID. Application components stay stateless; data and cache sit on managed services.

The Outcome

The agency can trial the workload in its own estate, on the same guardrails as the rest of the biodiversity platform, without standing up a separate hosting model.

The Challenge

Billing and cost-recovery data sat in a vendor-hosted environment. Replication into the utility's on-premises estate was slow, so finance and operations could not run business intelligence reporting against a current copy of the data.

What we did

We designed and built a production reporting platform in the organisation's Azure landing zone. Vendor database backups land in a utility-owned storage account over private networking. Azure Data Factory restores each new backup into Azure SQL Managed Instance. An on-premises data gateway keeps Power BI connected to the managed instance and remaining on-premises sources. The estate uses private networking, identity-based access, encryption in transit and at rest, and infrastructure as code.

The Outcome

A single production reporting environment is live. Daily billing data is available in Azure without the old replication delay, and the utility's teams can run reporting against current data inside the organisation's security guardrails.