Microsoft Technologies

Full-stack Microsoft capability — .NET/C#, Azure cloud, Azure DevOps, Azure AI Foundry — for Australian Government.

Overview

Most of our current government work runs on Azure. Not because we are a Microsoft shop, but because that is where the agencies are, and meeting an organisation inside the investment it has already made beats arguing with it.

So: .NET applications on Azure, CI/CD through Azure DevOps, enterprise data through Data Factory and Synapse, AI on Azure AI Foundry. Azure for Australian Government, Protected tenancies included, is ordinary ground for us rather than a special case.

Core Capabilities

.NET & C# Development

Production C# and .NET across web applications, backend services, and game development in Unity.

We are deliberately polyglot, and it pays off here. An engineer who has solved the same problem in three ecosystems recognises which parts of a platform are essential and which are just that platform’s habits.

Azure Cloud Services

Azure carries most of our current government work.

For compute that means Container Apps, App Services and serverless functions. Data work runs through Azure Data Factory and Synapse, with Power BI at the reporting end. Where APIs need governing rather than merely publishing, we use Azure API Management.

Identity and security is Entra ID with RBAC, Key Vault for secrets and Azure Defender watching. Everything is defined in Terraform or Bicep, so an environment can be destroyed and rebuilt from its definition rather than nursed.

Azure DevOps

Not just pipelines. At DEWR this was platform engineering at departmental scale: CI/CD architectures spanning the department, built on Terraform modules written to be reused rather than copied, and a multi-tenanted API Management platform with governance held centrally.

Sprint planning, backlogs and delivery tracking live in the same place, which is less about tooling than about not keeping two versions of the truth.

Azure AI Foundry

AI work on Microsoft platforms sits inside our wider agentic services capability.

Solution design uses Foundry projects, agents and the AI services an agency has approved. Azure OpenAI Service gives model access inside a governed environment. For proving value quickly, Copilot Studio is usually enough to put a conversational prototype in front of someone.

Orchestration is Foundry-native where that fits, and we have run the alternatives too: Temporal.io, LangGraph and LangChain.

Policy Alignment

Azure for Australian Government is where we normally work, so the Essential Eight and the ISM shape how things get built rather than what gets checked afterwards. Security controls arrive with the component.

On APIs there is a more direct connection: GoSource co-authored the first draft of the Australian Government Standard for API Integration for the DTA. What we do on Azure follows the principles we helped write.

Evidence

At DEWR we built department-wide Azure DevOps CI/CD with reusable Terraform modules, an enterprise API Management platform, and AI proofs of concept on Azure AI Foundry.

Two case studies sit on Azure. Medical Cost Finder for the Department of Health runs Azure Data Factory under strict data governance. The DAFF maintenance work includes an Azure API Management deployment alongside the production cloud engineering.

For people: Megan Mirams across C#/.NET, React, Python and TypeScript. Niko Kresic on Azure Synapse and Dataverse integration. Peter Zhao on Azure AD, ADFS and Microsoft 365, with the Azure Data Fundamentals certification. Ashley Harwood on Azure DevOps pipelines.