---
title: "Azure | Skills We Assign For | Azendo"
description: "Azure in a Microsoft estate — identity, hybrid networking and governance, and the Azendo roles assigned for cloud work."
url: "https://azendo.co/skills/azure/"
---

[Skills](https://azendo.co/skills/) Cloud and infrastructure 

# Azure.

Microsoft Azure is a cloud platform particularly common in organisations already committed to Microsoft — Active Directory, Microsoft 365, SQL Server and .NET. Its integration with that estate is usually why it was chosen.

## Where Azure fits on a long engagement.

Azure work is disproportionately identity work. Entra ID sits under everything, and getting groups, roles and conditional access right determines both security posture and how much friction people meet daily. It is also the part most likely to have been configured once and never revisited.

Hybrid is the other defining feature. Many Azure estates are genuinely half on-premises, and the interesting problems are at the boundary: networking, name resolution, and a migration that has been three-quarters finished for two years. Pretending that boundary is temporary is how it becomes permanent.

## What an assigned team does with Azure.

Azure estates are usually half-migrated, and the half that remains is the difficult half. Treating that boundary as temporary is how it survives another three years; treating it as a permanent architecture until proven otherwise produces better decisions about where to invest.

Identity work underpins everything else and is rarely anybody's explicit job. On an assigned team it sits with platform capacity, commonly alongside .NET application work under [outsource software development services](https://azendo.co/services/software-development/) on one agreement.

## What we use Azure for.

* Finishing a stalled migration The remaining workloads moved or explicitly accepted as staying, so the dual estate stops being an accident.
* Identity and access review Roles and conditional access brought back in line with how the organisation actually works now.
* Governance that holds Policy, tagging and budgets applied so the estate stops accumulating untracked resources.

## How Azure capacity is assigned.

Azure work is assigned under [DevOps as a service](https://azendo.co/services/cloud-and-devops/), alongside .NET capacity on the same agreement where the application and the platform are the same problem.

## Roles we assign Azure for

* [Cloud Engineer Cloud and DevOps](https://azendo.co/services/cloud-and-devops/cloud-engineer/)
* [DevOps Engineer Cloud and DevOps](https://azendo.co/services/cloud-and-devops/devops-engineer/)

## Service lines it sits in

* [Cloud and DevOps](https://azendo.co/services/cloud-and-devops/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in cloud and infrastructure

* [Kubernetes — skill we assign for](https://azendo.co/skills/kubernetes/)
* [Docker — skill we assign for](https://azendo.co/skills/docker/)
* [Terraform — skill we assign for](https://azendo.co/skills/terraform/)
* [AWS — skill we assign for](https://azendo.co/skills/aws/)
* [GCP — skill we assign for](https://azendo.co/skills/gcp/)
* [Terraform modules — skill we assign for](https://azendo.co/skills/terraform-modules/)
* [Pulumi — skill we assign for](https://azendo.co/skills/pulumi/)
* [CloudFormation — skill we assign for](https://azendo.co/skills/cloudformation/)

## Tell us what your roadmap needs Azure for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)