DevOps Engineer – Entra External ID, Observability, Azure

This is a fully remote position, open to applicants in Poland.

📋 Description

• Assume responsibility for the identity and observability workstream within a live enterprise Azure program.

• Configure and enhance Entra External ID (CIAM), which includes user flows, application registrations, custom authentication extensions, and claims.

• Develop and secure Azure Functions for webhook/HTTP workloads utilizing managed identity and Key Vault.

• Establish monitoring, alerting, and dashboards using Application Insights, Log Analytics, and OpenTelemetry.

• Maintain associated Terraform code and Azure DevOps pipelines.

• Diagnose token flows and claims across OAuth2/OIDC integrations.

• Implement, test, and document solutions in accordance with established architectural decisions and client governance.

• Engage in technical sessions with clients.

⛳️ Requirements

• Practical experience with Entra External ID (CIAM), including user flows, app registrations, custom authentication extensions, claims, and Microsoft Graph API.

• Azure AD B2C experience is advantageous but not mandatory.

• Strong knowledge of OAuth2, OIDC, JWT, and On-Behalf-Of flows, along with the ability to troubleshoot claims.

• Experience with Azure Functions, managed identity, and Key Vault.

• Familiarity with Application Insights, Log Analytics (KQL), OpenTelemetry, alerts, dashboards, and PII-safe logging.

• Proficiency with Terraform on Azure and Azure DevOps Pipelines.

• Proficient in English at a C1 level.

• Polish business entity capable of invoicing B2B, or a willingness to establish one prior to commencement.

• Capability to work on your own computer.

• Availability to work during a 3–7 pm overlap when necessary.

• Practical experience configuring Entra External ID, not solely Azure AD B2C.

• Experience in developing custom authentication extensions using Azure Functions.

🏝️ Benefits

• Fully remote position, with no travel required.

• Flexible working hours (no fixed overlap is necessary).

• Initial 3-month project with potential for extension.

• Engagement level ranging from 50% to 100%.

• Involvement in a modern Azure program for an enterprise client, featuring a well-defined architecture already established.