Skip to main content
Michael P. Goodman

Capability profile · Identity and collaboration Details to be added

Enterprise Microsoft 365 and identity modernization

How I approach moving an organization's identity, mail and device management to Microsoft 365: clean the directory first, migrate in measured waves, and keep a tested way back at every step.

Discuss a Microsoft 365 projectSee IT automation

By Michael P. Goodman · Last reviewed

Focus
Identity, mail and device management
Foundation
Active Directory and Windows Server
Method
Discover, Diagnose, Architect, Build, Harden & Transfer
Engagement
Direct with Michael

Scope outline

This page describes the approach and the technology scope. Project-specific details, screenshots and outcomes are added once they are confirmed.

Enterprise Microsoft 365 overview

Most Microsoft 365 problems are directory problems. Stale accounts, inconsistent group membership, undocumented Group Policy and unclear ownership surface the day a tenant is connected. With more than 28 years of Windows Server and Active Directory work behind me, I start there.

  1. Discover. Inventory users, groups, devices, mail flow, licenses and dependencies in read-only mode.
  2. Diagnose. Audit Active Directory hygiene, DNS, Group Policy and authentication paths before anything moves.
  3. Architect. Design the hybrid identity model, conditional access and wave plan.
  4. Build. Migrate in pilot-first waves with a documented rollback for each.
  5. Harden & Transfer. Lock down, document and hand over to your team.

Enterprise Microsoft 365 screenshots

Annotated, anonymized screenshots will be added when the project record is finalized.

Screenshots are being added

Annotated screenshots of this project will appear here. The architecture diagram below and the linked live or source pages show the current state in the meantime.

Enterprise Microsoft 365 architecture

A typical hybrid identity and migration path.

Hybrid identity and Microsoft 365 migration pathOn-premises Active Directory is cleaned and synchronized to Entra ID. Conditional access and device management with Intune are applied, and mailboxes move to Exchange Online in pilot-first waves with a documented rollback.MIGRATION BOUNDARY: read-only discovery first, rollback documented per waveOn-prem ADclean + auditDirectory synchybrid identityEntra IDconditional accessExchange Onlinepilot-first wavesIntunedevice management
Typical hybrid identity and Microsoft 365 migration path.

Enterprise Microsoft 365 outcomes

Outcomes are listed here once confirmed for a specific engagement.

Clean directory

Stale objects and inconsistent groups resolved before synchronization.

Controlled cutover

Pilot-first waves, each with a tested rollback.

Documented handover

Runbooks and configuration records your team can operate.

Technologies used in Enterprise Microsoft 365

The technology scope of this kind of project.

Identity

  • Active Directory
  • Group Policy
  • Entra ID
  • Conditional access
  • DNS and DHCP

Collaboration and devices

  • Microsoft 365
  • Exchange Online
  • Intune
  • PowerShell

Related to Enterprise Microsoft 365

IT infrastructure automation

PowerShell and API automation with approval gates.

Services

Sovereign IT and AI architecture.

All Michael P. Goodman projects

The full portfolio.

Enterprise Microsoft 365 FAQ

Is this page about a specific client?

No. It is a capability profile that describes the approach and technology scope. No client names or results are implied.

Why start with Active Directory?

Because identity quality determines how clean a Microsoft 365 rollout is. Fixing the directory first avoids carrying problems into the cloud.

Planning a Microsoft 365 or identity project?

Start with a read-only assessment of your directory, mail flow and devices.

Email MichaelSee services