IAM and CIAM architect and developer · Azure AD B2C, Entra External ID
Authentication that holds up in production
I design identity platforms on Azure AD B2C and Entra External ID, then build and ship them myself: custom policies, federation, OpenFGA authorization and the .NET applications that use them. I help teams with anything from one specific problem or a review of their setup to a complete implementation.
Open to new work. Remote. Small jobs close quickly, for larger ones we agree the schedule up front.
header
{ "alg": "EdDSA", "typ": "JWT", "kid": "edgarus-sample" }payload
{"iss": "https://edgarus.eu","sub": "przemyslaw-gawdzik","name": "Przemysław Gawdzik","role": "Senior Identity Management Engineer","scp": "entra-id azure-ad-b2c oauth2 oidc dotnet","azure_since": 2010,"dotnet_years": 17,"degree": "Engineer (inż.), computer networks and distributed systems"}
signature
sy1q4sT8n1AlO6T-lyig0B0mOe8_xoBZkINHNDmEVjddwNRmhHuwXhFhfi7IQi4CRf00zP2QOEuqWPgaEciUCQ
signature verifiedsignature check failed
This token is really signed. Change one field and the signature stops matching.
What I work on
Backend, access and deployment overlap in practice, so I usually own all three on a project.
Authentication and access
How users sign in, what they are allowed to do and how applications talk to each other. Day to day that means Microsoft Entra ID, External ID, Azure AD B2C, OAuth 2.0 and OpenID Connect, with SSO and MFA where they make sense. In OpenFGA I describe permissions as relationships between users and resources, as in the example model.
model
schema 1.1
type user
type tenant
relations
define member: [user]
define admin: [user]
type document
relations
define org: [tenant]
define viewer: [user] or member from org
define editor: [user] or admin from orgEntra ID, Azure AD B2C, External ID, OAuth 2.0, OIDC, OpenFGA, CIAM
Secure .NET applications
Identity does not end with Entra ID configuration. I also build the applications in C# and ASP.NET Core: APIs that validate identity, enforce authorization and carry the business logic.
C#, ASP.NET Core, authorization policies, DDD, TDD
From code to production
Azure, containers and CI/CD, so every deployment follows the same tested path. Infrastructure lives in code and configuration in the repository, and after a release I read the logs, metrics and traces, because I want to know what is really happening.
Azure, CI/CD, containers, OpenTelemetry
Typical problems I solve
Smaller jobs I close in a few days or a week or two. Larger ones, a complete implementation included, start with a shared plan and schedule.
- A plan for moving to External ID
- Which of your custom policies, federations and claims carry over, what has to be rebuilt and in what order, while B2C is still supported.
- A configuration review
- B2C or External ID: app registrations, policies, consents and permissions. You get a list of issues in order of priority.
- One specific problem
- A claim missing from the token, MFA behaving oddly, a federation that fails, ASP.NET Core authorization letting too much through. I find the cause and show the fix.
- Integrating an application with the identity provider
- Connecting your application to B2C, External ID or Entra ID: OAuth and OpenID Connect flows, tokens and claims, sign-out and session refresh, so the app team does not learn it all on production.
- A permission model
- An OpenFGA model for your domain: types, relations and tests that make sure nobody sees more than they should.
- A complete implementation
- B2C or External ID from scratch, with federation, permissions and infrastructure as code. We start with a plan and a schedule.
What I design and build
Custom policies with home realm discovery, federation with many identity providers without growing the policies, authorization outside the token with OpenFGA, profile data kept outside the identity provider, self-service app registration for development teams, and the infrastructure behind it as code.
Open source
Published as Edgarus79 in edgarus-labs on GitHub
Code Janitor
Cleans up and modernizes C# in Visual Studio and VS Code, so nobody has to do it by hand.
VS 2026, VS Code · C# · LGPL-3.0
Project pageClaude Code VS
Claude Code inside Visual Studio, without leaving the IDE.
VS 2022, 2026 · Agent Client Protocol · MIT
Project pageoh-my-pi
The oh-my-pi coding agent in Visual Studio and VS Code, with native diffs and control over the editor.
VS 2022, 2026, VS Code · OMP JSONL RPC · MIT
Project page
About
I design and build identity solutions on Azure, including CIAM systems, and I cover the whole of it: architecture, code, automation, infrastructure and running production.
The identity provider is only part of it: what surrounds it matters just as much, meaning federation, authorization, profile data and the tools that spare teams from asking for every app registration.
I also support application teams with the technical integration of their systems with the identity provider, which is often no smaller a challenge than designing and rolling out the IAM or CIAM platform itself.
I have worked with .NET for 17 years and with Azure since 2010, when I started as a Windows Azure trainer.
I hold an engineer’s degree (inż.) in computer networks and distributed systems from WSPA in Lublin.
experience
- 2024-nowSenior Identity Management Engineer
- 2022-2024Senior .NET Developer, Cloud Infrastructure ConsultantPredica (now SoftwareOne)
- 2019-2022Senior Software Developer, ConsultantCloudTeam
- 2011-2019Software Developer, ConsultantAction Centrum Edukacyjne
- 2010-2011Windows Azure Trainer, Consultant, DeveloperABC Data Centrum Edukacyjne