~/paras-karki · portfolio

Loading portfolio

Skip to content
PK

04

User access: Microsoft 365, Entra ID and AWS

Adding users, granting and removing access, and connecting Microsoft Entra ID sign-in to the platform's services.

Role
Full Stack Developer · Mavericks Tech Solutions
When
Sep 2025 – present
Relevant for
IT SupportCloud & InfrastructureSoftware

01 The person is added in Microsoft 365.

My part

I add users to Microsoft 365 and manage their access in Entra ID, set up IAM users with limited permissions in AWS, and integrated Entra ID and Microsoft Graph into the platform's services.

Problem

A growing team and several services meant access had to be granted, checked and removed reliably, in more than one cloud.

Approach

Users and groups live in Entra ID, and every service checks the same identity through Microsoft Graph. In AWS, each person or service gets an IAM user with only the permissions it needs.

Outcome

One place to add or remove a person in Microsoft's cloud, and limited access in AWS.

What I did

  • Microsoft 365 accounts

    I add new users to Microsoft 365.

    Microsoft 365 admin

  • Access by group

    Users and groups live in Entra ID; group membership decides what each person can open.

    Microsoft Entra ID

  • One sign-in for every service

    Each service validates the same Entra ID identity through Microsoft Graph instead of keeping its own passwords.

    Microsoft GraphOAuth 2.0 / OIDC

  • Least privilege in AWS

    Each person or service gets an IAM user with only the permissions it needs.

    AWS IAM

  • Removal in one place

    Disable the account once, and access ends everywhere.

See also

Stack

  • Microsoft 365 admin
  • Microsoft Entra ID
  • Microsoft Graph
  • AWS IAM
  • OAuth 2.0 / OIDC

Paras Karki · CV

page 1 of 2