Back to Tech landscape

Pulumi

Cloud & DevOps

Infrastructure as code with .NET

Official documentation (opens in a new tab)

Overview

Pulumi appears in template InfrastructureModel projects alongside Bicep. Teams define Azure resources in C# for type-checked, reviewable infrastructure that matches application code.

Microsoft Azure is our primary cloud: Factory templates deploy to App Service, AKS, Container Apps, and managed data services with Bicep or Pulumi, Azure DevOps pipelines, and Application Insights baked in from day one.

When engagements require hybrid or multi-cloud tooling, we adopt it with explicit landing zones, least-privilege identities, and runbooks—while keeping Azure the anchor for ConnectSoft-generated platforms.

From first commit to production dashboards, our DevOps path favors repeatable infrastructure, managed identities, and measurable SLOs—so releases stay boring in the best way.

Why we use it:

  • IaC in the same language as services
  • Azure Native provider for first-class resources
  • Used in SaaS Products Catalog and microservice templates
  • Complements Bicep for different team preferences
  • Infrastructure as code with environment-specific parameters
  • Managed identities and private networking in production paths
  • Integrated CI/CD through Azure DevOps and quality gates

Ready to work with us?

Let's discuss how our team can help achieve your digital goals