Insights

Practical, no-fluff guidance from the engineers who do this work—on Microsoft Identity Manager, Active Directory, and the migrations that connect them.

Identity Lifecycle · IAM Engineering Team

Do You Still Need Microsoft Identity Manager?

Microsoft Identity Manager (MIM) is one of those products that quietly keeps running long after the roadmap conversations move elsewhere. For a lot of organizations, it's still doing real work: provisioning from HR systems, managing group membership, issuing smart card certificates. The question we hear most isn't "should we rip this out tomorrow," it's "do we still need this, and if not, what's the safe way off it?"

Our honest answer: it depends on what you're actually using it for.

  • If MIM is handling certificate management (MIM CM) or complex, custom provisioning logic tied to legacy line-of-business systems, replacing it isn't a weekend project—but it's also not something to leave unmaintained indefinitely.
  • If MIM is mainly syncing HR data into Active Directory and Entra ID, that workload increasingly has a cleaner home in Entra ID Governance and HR-driven provisioning, with less custom code to maintain.
  • If nobody remembers why a specific sync rule exists, that's usually a sign the environment needs a health check before anyone touches the migration conversation.

The organizations that get burned aren't the ones still running MIM—they're the ones who stopped understanding what their MIM deployment actually does. Whether the right move is a support plan, a modernization pass, or a phased migration to Entra ID Governance, the first step is the same: get a clear picture of what's running today before deciding what happens next.

Active Directory Security · IAM Engineering Team

5 Active Directory Misconfigurations We Find in Nearly Every Assessment

Active Directory doesn't usually fail dramatically—it drifts. Years of one-off changes, departed admins, and "temporary" exceptions add up. Here are five issues that show up in nearly every environment we assess, regardless of industry or size.

  1. Oversized privileged groups. Domain Admins and Enterprise Admins memberships grow over time and rarely get pruned. We regularly find service accounts, former employees, or help desk staff with far more access than their role requires.
  2. Unconstrained delegation left enabled. A legacy setting that, once discovered, gives an attacker a fast path to domain compromise—and one of the first things we check in any assessment.
  3. No tiered administration model. Workstation admin credentials with a direct path to domain controller access is one of the most common ways lateral movement turns into full domain compromise.
  4. Stale accounts and orphaned SPNs. Accounts for employees who left years ago, service principal names tied to decommissioned servers—each one is unmonitored attack surface.
  5. Weak or inconsistent password and Kerberos policies. Especially on service accounts, which are often exempt from the password rotation policies applied everywhere else.

None of these are exotic. They're the result of normal operational life in a directory that hasn't had a dedicated security review in a while. A focused AD health check typically surfaces all five—along with a prioritized plan for fixing them without disrupting the business.

Mergers & Acquisitions · IAM Engineering Team

An Identity Checklist for M&A: What to Assess Before Day One

By the time identity shows up as a line item in an M&A integration plan, the deal timeline is usually already set. The organizations that handle this well start assessing identity risk during due diligence—not after close. A few things worth checking early:

  • Directory trust feasibility. Can the two Active Directory forests establish a trust, or does the domain/forest functional level, naming, or security posture rule that out?
  • SID history and UPN collisions. Overlapping UPN suffixes or SAM account names between organizations create migration conflicts that are far easier to plan around than to fix mid-cutover.
  • Entra ID tenant overlap. Shared domains claimed across tenants, conflicting Microsoft 365 licensing, and Conditional Access policies that weren't designed with a second organization in mind.
  • Privileged access inventory. Who has domain admin equivalent rights in the acquired environment, and does that match what the deal team assumes?
  • Timeline-critical dependencies. Payroll, HR systems, and line-of-business apps tied to on-prem AD or a specific tenant often dictate the real migration deadline—regardless of what the integration plan says.

Identity delays are one of the most common reasons post-merger IT integrations slip. Assessing these items early—ideally before the deal closes—turns identity from a surprise blocker into a planned workstream.

Have a question about your own environment?

These patterns are common, but every environment is different. Let's talk about yours.

Contact Us