Microsoft Cloud Specialist in Copenhagen

Microsoft 365 is the service layer most users actually experience, so it is where support pressure lands first. I have worked with Exchange Online, Teams, SharePoint and OneDrive across organisations from around 50 users up to environments of 5000+. For the IT support side of keeping a tenant running day to day, I have written that up separately.

That includes migrations, tenant clean-up, licence and access review, mailbox and sharing issues, and the everyday reality of keeping a tenant's configuration matching what the business believes it is. Lately that work increasingly includes Copilot adoption — I have written about everyday Microsoft Copilot workflows that actually save time.

On the Azure side my work has been mainly around identity, hybrid connectivity and the infrastructure services that sit underneath a modern workplace, rather than large-scale application platform engineering — I would rather be precise about that than oversell it.

I am AZ-900 certified and comfortable with the cost and architecture conversation: what genuinely belongs in Azure, what is cheaper to keep on-premises, and how to phase a migration safely. My hybrid cloud migration strategy and eight-step plan explains that sequence.

Intune is where endpoint management becomes something a support organisation can actually scale. I have run device compliance policies, app deployment and provisioning so a new hire's machine is usable on day one rather than day five. For a product-focused write-up of that work, see my Microsoft Intune Consultant page.

The largest of these was a migration of around 500 users to Intune, which I have written about in detail — including the parts that did not go smoothly.

Entra ID (formerly Azure Active Directory) has become the real security boundary in most organisations, and a large share of the 2nd and 3rd line tickets I have handled ultimately lived here: sign-in failures, MFA registration, group and role assignment, guest access and hybrid sync. For a deeper, identity-focused write-up, see my Microsoft Entra ID Consultant page.

I have worked with Entra ID in both cloud-only and hybrid setups where on-premises Active Directory still holds the authoritative objects.

Very few Danish organisations are purely cloud or purely on-premises, and the interesting problems live in between: directory sync, legacy applications that expect a domain controller, file shares mid-migration and network paths that assume the office is the centre of the world.

I have supported that in-between state rather than only the finished picture, which is usually what a hiring organisation actually needs.

Conditional Access is the tool I reach for most on the security side, because it lets identity carry the policy instead of the network cable. Done carelessly it locks out the CFO on a Sunday, so I favour staged rollouts, report-only mode and named break-glass accounts.

Alongside that: MFA coverage, privileged access hygiene, device compliance as an access condition, and making sure the security model is documented well enough that someone else can maintain it.