Daniel Moussa/ Microsoft 365 Engineer

Secure cloud.Intelligentpossibilities.

I build secure Microsoft cloud environments,
purposeful automations, and AI that works
with people in control.

Identity · Security · Azure · Automation · Agentic AI

CONNECTED SYSTEMS
01 / IDENTITY02 / CLOUD03 / AUTOMATION04 / INTELLIGENCE
+Trust at the foundation.+
THE ENGINEERING CONTINUUM
  1. 01Identity
  2. 02Cloud
  3. 03Automation
  4. 04Intelligence
SCROLL TO EXPLORE ↓
01 / SELECTED PROJECTSIDEAS, ENGINEERED.

Complex systems.
Considered solutions.

Architecture, automation, and intelligence.
A closer look at the work behind the systems.

06 PROJECTS
SELECTED ARCHITECTURE & ENGINEERING WORKIDENTITY / CLOUD / AUTOMATION / INTELLIGENCE
02 / TECHNOLOGY ECOSYSTEMCONNECTED, NOT COLLECTED.

The stack is connected.
So is the thinking.

Tools matter. The relationships between them
are where the engineering happens.

IDENTITY / IN PRACTICE

Trust starts here.

Identity-aware access, controlled privilege, and application authentication form the foundation of every connected system.

  • Microsoft Entra ID
  • Entra PIM
  • Conditional Access
  • RBAC
  • App Registrations
  • Enterprise Applications
  • OAuth
  • Managed Identities
  • Identity governance
03 / THE EVERYDAY ENGINEERING

Behind the scenes.
Across the environment.

The migrations, integrations, and operational
work that keep a Microsoft environment moving.

01

Microsoft 365 migrations

MIGRATION

I delivered tenant-to-tenant and Google Workspace to Microsoft 365 migrations with AvePoint Fly, including Gmail to Exchange Online and Google Drive migration. The work covered provisioning, mailbox mapping, migration policies, pilot and full migrations, cutover planning, reporting, validation, and cleanup.

AvePoint Fly · Exchange Online · Google Workspace · Graph authorization
02

Secure Graph mail integration

INTEGRATION

A website-to-Microsoft-365 email solution using Microsoft Graph Mail.Send, OAuth, a dedicated Entra application identity, and scoped Exchange Online mailbox access. Designed to reduce dependency on legacy SMTP authentication.

Microsoft Graph · Entra applications · OAuth · Exchange Online
03

Controlled offboarding archive

DATA LIFECYCLE

A controlled workflow to preserve former-user OneDrive data in a restricted SharePoint archive before access and license cleanup, with administrative access, validation, and deliberate removal of permissions.

OneDrive · SharePoint Online · Access & license lifecycle
04

Microsoft 365 security & governance

GOVERNANCE

Exchange Online and OWA governance, Defender baselines, SMB hardening, lockout policies, ASR controls, sensitivity-label and information-protection planning, Secure Score improvement, tenant reviews, and licensing governance.

Microsoft Defender · Exchange Online · Information protection
04 / THE ENGINEER BEHIND THE SYSTEMS

A systems mindset.
A human perspective.

Daniel MoussaMicrosoft 365 Engineer
CERTIFICATION / SC-300

Microsoft Certified: Identity and Access Administrator Associate

CERTIFICATION / SC-200

Microsoft Certified: Security Operations Analyst Associate

I’m Daniel Moussa, a Microsoft 365 Engineer working across Entra ID, Exchange Online, Teams, SharePoint, OneDrive, Intune, Defender, and Purview. My Microsoft 365 (M365) work connects tenant administration with identity, endpoint management, security, and Azure.

I build automation with PowerShell, Microsoft Graph, Power Automate, and Azure, and develop Copilot Studio agents with human approval at the boundary of consequential actions. Permissions, failure handling, observability, and clear handover are part of the design.

MY FOCUSIDENTITY / SECURITY / AZURE
AUTOMATION / AGENTIC AI
05 / ENGINEERING PRINCIPLESHOW I APPROACH THE WORK

Good systems are
deliberate systems.

01

Security is a starting point.

Least privilege, identity-aware architecture, and safe defaults belong in the first design, not the last review.

02

Automate the repeatable.

Use APIs, scripts, and workflows to make recurring work consistent, inspectable, and easier to operate.

03

Keep people in control.

Let agents reason and propose. Put deliberate approval at the boundary of consequential action.

04

Design for the day after.

Logging, alerts, failure isolation, and clear handover are part of the build. A system needs to be maintainable after delivery.

06 / WHAT’S NEXT

Good work starts
with a conversation.

Have a role, project, or technical challenge to discuss?
Reach out directly.

Daniel MoussaMicrosoft 365 Engineer
Email Me