D. Directory Migration (DM_*)
Eight adapter interfaces for every infrastructure service AD was holding together
D. Directory Migration (DM_*)
Active Directory was the implicit governance anchor for eleven categories of infrastructure objects. When AD goes away, each must be migrated to a modern equivalent with governance preserved. DM_* adapters define the interface; vendor implementations plug in underneath.
Leaves
| ID | Adapter | Status |
|---|---|---|
| D.1 | IPAM Adapter — DM_010 | Source present |
| D.2 | DNS Adapter — DM_015 | ⚠ gap — not in registry |
| D.3 | DHCP Adapter — DM_016 | ⚠ gap |
| D.4 | PKI / ADCS Adapter — DM_020 | Source present |
| D.5 | RADIUS / NPS Adapter — DM_030 | Source present |
| D.6 | LDAP Proxy Adapter — DM_040 | Source present |
| D.7 | Sync Engine Adapter — DM_050 | Source present |
| D.8 | Device Management Adapter — DM_060 | Source present |
| D.9 | NTP Adapter — DM_070 | Source present |
| D.10 | DFS Adapter — DM_080 | Source present |
| D.11 | SPN / App Registration — DM_085 | ⚠ gap |
| D.12 | Trust Relationship — DM_090 | ⚠ gap |
Canon surface: modernization/directory-migration.qmd
Canon Phase Mapping Requirement (the program decision)
Every leaf in this subcategory — DNS, PKI, RADIUS, LDAP, DHCP, Sync Engine, Device Management, NTP, DFS, and the SPN / Trust gap-fillers — MUST publish a Canon Phase Mapping table at the top of its operational guide, mapping the guide’s phases to the canonical six-phase Directory Migration model (Discover → Normalize → Map → Migrate → Validate → Decommission). Per [the program decision], this requirement applies to every existing and future adapter guide in this taxonomy.
Reference implementations: DNS Modernization (11→6 mapping) and PKI Modernization (6→6 mapping). Contributor guidance is in [src/fmp/modernization/directory-migration/README.md] under “Adding a New Adapter Migration Guide”.