Skip to main content

Microsoft Azure

Azure for the stack you run

We run applications on Microsoft Azure the way a Microsoft-centered team already works: resource groups per environment, Entra ID for access, and App Service, Functions, or AKS chosen for the process.

Illustration for Microsoft Azure development services

What we build on Microsoft Azure

Azure work lines up with identity and with the runtime. .NET is a frequent application stack here. The platform decisions are still about resource groups, access, and how the process runs.

  • Subscriptions, resource groups, and Entra ID

    Environments are resource groups with a naming scheme, or separate subscriptions when the organization already splits that way. Entra ID groups decide who can deploy and who can read production.

    Managed identities call Azure SQL, Storage, or Service Bus. A connection string in an app setting is the fallback, stored as a secret, not as a value in the repository.

  • App Service, Functions, and AKS

    App Service hosts the site or API that should stay up, including the .NET applications OLIANT has long built. Deployment slots are the rollback. Configuration is slot-specific where the environments differ.

    Azure Functions covers a short job or an event: a queue message, a timer, an HTTP call that finishes. AKS is for a team that has chosen Kubernetes and will own the cluster upgrades. A single web app is not a reason to start AKS.

  • Azure SQL, Storage, and Service Bus

    Azure SQL is the relational store when the application speaks SQL Server. Blob Storage holds objects. Service Bus carries commands and events that must be retried independently of the web request.

    Private endpoints or service endpoints keep that data off the public internet when the subscription supports them. The app identity is the principal on the firewall rule.

  • Pipelines you already have

    Azure DevOps Pipelines or GitHub Actions, whichever builds the application today. The pipeline identity can deploy to the resource group and cannot change another environment.

    Bicep or Terraform describes the resources. A portal click is reconciled back into that description or it is reverted.

Typical use cases

Azure fits teams that already sign in with Entra ID and host on Microsoft services, whether the application is .NET or another runtime App Service can run.

  • A .NET site on App Service

    The application is ASP.NET or a similar web stack. App Service runs it, slots carry the new version, and Azure SQL is reached with a managed identity. The publish profile is not the deployment process.

  • A timer or a queue worker on Functions

    A message arrives on Service Bus or a clock fires. The function does one job, writes its outcome, and can be retried. It does not grow into the web application.

  • A container platform with an owner

    AKS when several services share a cluster and a person is named for upgrades. Workload identity and namespaces are part of the first release. App Service or Container Apps stays the recommendation when that owner does not exist.

  • Identity already in Entra ID

    Employees sign in with the tenant you have. The application uses that tenant for users, and a separate app registration or managed identity for itself. Guest accounts and admin roles are not the same group.

How we work

An Azure engagement names the resource group, the identity, and the host before feature work depends on them.

  • Place the environment in a resource group

    One group per environment, tagged, with a budget alert if you use budgets. Resources that share a lifecycle live together. A shared group for everything is the habit we replace.

  • Decide App Service, Functions, or AKS

    Site or API, short job, or cluster. The choice includes who patches the platform. .NET on App Service is the common path for the applications we already build. Another runtime is fine when the host supports it and the team can run it.

  • Use Entra ID for users and for the app

    Users come from the tenant. The app uses a managed identity toward Azure SQL, Storage, and Service Bus. Local development has a documented way to sign in that does not copy production secrets into a laptop file.

  • Deploy with the pipeline that exists

    Azure DevOps or GitHub Actions builds, tests, and deploys to a slot or a staging resource group. Swapping a slot or rerunning the previous release is practiced before production is the only environment.

Tell us the subscription and the runtime

App Service, Functions, or AKS, and whether the application is .NET. We will fit it to Entra ID and a resource group per environment.

Schedule a call

Why OLIANT

Microsoft Azure at OLIANT lines up with Entra ID, with .NET when that is the application, and with a resource group you can audit.

  • Identity is the tenant you have

    Entra ID groups and managed identities replace shared secrets. Admin access and application access are different principals.

  • .NET has a natural host

    App Service and deployment slots suit the .NET applications we build. The platform choice does not force a rewrite of the web stack.

  • The resource group is the environment

    You can see what belongs to staging and what belongs to production. The pipeline deploys into one of them on purpose.

Frequently asked questions

Questions about Azure hosting and how it meets the application.

No. .NET on App Service is a common path because that is a stack we already build. Node, Python, Java, and containers are in scope when Azure is the right host and the team can operate that runtime. The language pages describe the application. This page describes the platform.

Azure in the tenant you already have

Share the subscription model and the application runtime. We will propose the host, the identity, and the pipeline step.

Illustration for the Microsoft Azure closing invitation