I work as a Service Desk Specialist and I’m currently building my skills toward Identity and Access Management.
My goal is to move toward an IAM role where I can work more deeply with users, access, permissions, identity processes and Microsoft Entra ID.
Long term, I’m interested in the engineering and architecture side of IAM: how access should be designed, how identity moves through systems and how to build solutions that are secure, clear and practical.
I use GitHub as a portfolio and learning space.
I like writing down what I study, what I build and how my thinking develops over time. Most of my repositories are connected to IT learning, IAM, Microsoft Entra ID, Microsoft 365, PowerShell, documentation and practical problem solving.
This profile is not meant to look perfect. It is meant to show progress, curiosity and hands-on learning.
I’m currently building my skills around:
- Identity and Access Management
- Microsoft Entra ID
- Microsoft 365 administration
- Access lifecycle and user lifecycle processes
- Identity governance
- Privileged access basics
- IAM tools and platforms
- PowerShell for practical administration
- SC-300 certification studies
I’m also building a basic understanding of security, governance and compliance topics, including:
- ISO/IEC 27001
- GDPR
- NIS2 and Finnish cybersecurity regulation
- Risk and compliance thinking
Support work has shown me how quickly access problems turn into real business problems.
Weak processes, unclear ownership, poor documentation and badly planned changes create confusion for users, pressure for support and unnecessary security risk.
That is why IAM interests me.
Access looks simple from the outside. In reality, it becomes messy fast when ownership, lifecycle, roles and documentation are not designed properly.
Good access management is structure, timing, ownership and clean logic — not just adding or removing permissions.
Quiet progress still counts 🌱