DevOps Engineer – Entra External ID & Observability (Azure)
At a glance
Mid-level DevOps & Release role at Digital Forms. Remote, Poland · contract.
Pay not stated DevOps Engineer salary
remoteroles summary, based on the employer's posting.
What you'll do
- Configure customer identity flows, app registrations, authentication extensions and claims in Entra External ID
- Build HTTP or webhook Azure Functions, securing access through managed identity and Key Vault
- Trace OAuth2, OIDC and JWT token issues, including missing claims and On-Behalf-Of flows
- Create monitoring, alerts and dashboards with Application Insights, Log Analytics and OpenTelemetry, keeping logs free of personal data
- Update Terraform and Azure DevOps pipelines while testing and documenting work within the agreed architecture
What you bring
- You have personally set up Entra External ID for customer-facing apps, including custom authentication extensions
- You can follow OAuth2, OIDC and JWT claims through an integration to find where they go wrong
- You have secured Azure Functions with managed identity and Key Vault, and built observability with the named Azure tools
- You bring Azure Terraform and Azure DevOps pipeline experience, plus spoken English at B2 level or higher
Who this fits
This suits a hands-on mid-level engineer who can take ownership of identity and observability tasks and explain a real customer identity setup in an initial conversation. The work is within an architect-led programme and includes regular client technical sessions. It is a remote B2B contract for three months, with a commitment of fifty to one hundred percent FTE and an ASAP start.
From the employer
About the role
At Digital Forms we deliver digital transformation projects for clients in the US, EU and UK. We’re looking for a hands-on DevOps Engineer to take over the identity and observability workstream on a live enterprise Azure programme.
The platform is new and in active delivery, with go-live planned for January 2027. The Azure foundation (landing zones, networking, central logging) is already built. The remaining work covers customer identity, Azure Functions and application observability, and that’s where you come in.
You’ll implement, test and document solutions within the architecture decisions made by our Solution Architect and the client’s architecture governance, and join client technical sessions.
What you’ll do
Configure and extend Entra External ID (CIAM): user flows, app registrations, custom authentication extensions, claims, Microsoft Graph API
Build and secure Azure Functions (HTTP/webhook) with managed identity and Key Vault
Troubleshoot token flows and claims across OAuth2 / OIDC / JWT integrations, including On-Behalf-Of
Set up monitoring, alerting and dashboards with Application Insights, Log Analytics (KQL) and OpenTelemetry, keeping logs free of personal data
Maintain the related Terraform code and Azure DevOps pipelines
Must-have
Hands-on experience configuring Entra External ID for customer-facing applications (CIAM). Azure AD B2C counts as adjacent experience only, and workforce/internal Entra ID (employee access, PIM, Conditional Access) on its own is not enough for this role.
Solid understanding of OAuth2, OIDC and JWT. You can trace a missing or incorrect claim end to end.
Azure Functions secured with managed identity and Key Vault
Application Insights, Log Analytics (KQL), OpenTelemetry, alerts and dashboards, PII-safe logging
Terraform on Azure and Azure DevOps Pipelines
English B2+ (spoken), for regular client technical sessions
Engagement
B2B contract
3 months, 50–100% FTE
Fully remote
Start: ASAP
Before you apply
Please apply only if you have personally configured Entra External ID for customer-facing apps. In the first conversation we’ll ask you to walk us through a concrete setup you built, including any custom authentication extension.