Agent Consolidation
One decision per agent across every platform: keep, migrate, merge, rebuild or retire.
See the engagementM&A IT INTEGRATION
Same playbook, every add-on.
Every vendor sells the deal team speed. The deal team needs proof: a Day 1 readiness record, a 100-day plan and a go or no-go in writing before anything connects, including the acquired company's agents, Copilot and shadow AI.
01 Source02 Boundary03 Human decision04 Evidence
HOW IT WORKS
The control path in practice.
- Read-only discovery of the add-on tenant: identities, devices, data, agents.
- A Day 1 readiness record that separates tested from assumed.
- A pilot connection for one group before any wave, rollback written first.
- Your written go or no-go for each wave of the 100-day plan.
WAYS TO START
The fixed engagements behind this page.
Microsoft 365 Security Implementation
Identity and endpoint baselines, piloted on a scoped device group before the wave.
See the engagementView the Microsoft Marketplace listingTHE WOUND
Why does every integration feel like bespoke chaos?
Because nobody wrote the playbook down, so each add-on is a research project with a deadline instead of the same four gates run again.
Every vendor sells speed. The deal team needs proof: a Day 1 readiness record and a 100-day plan with a written go or no-go per wave. The acquired AI estate is part of diligence, not a surprise after close.
THE MICROSOFT INSIGHT
How do acquired people reach your applications on day one without a tenant merge?
Through cross-tenant synchronization in Microsoft Entra ID, which provisions them into the parent tenant as B2B users while their accounts stay managed in their own tenant.
Cross-tenant synchronization in Microsoft Entra ID automates creating, updating and deleting B2B collaboration users and groups across the tenants of one organization, so an acquired company's people can reach the parent's applications from day one while their accounts stay managed in their own tenant. (Microsoft Learn, checked Nov 1, 2026)
Plan the application hub and the acquired team signs in on day one. Plan the merge first and the acquired team waits for the merge.
THE METHOD
What is the playbook?
Read-only discovery of the add-on, a one-page Day 1 record, a pilot connection for one group with rollback written first, and your written go or no-go for each wave of the 100-day plan.
- Read-only discovery of the add-on tenant: identities, devices, data, applications and agents.
- A Day 1 readiness record that separates tested from assumed, one page.
- A pilot connection for one group before any wave, rollback written first.
- Your written go or no-go for each wave of the 100-day plan.
THE AI ESTATE
Is the acquired company's AI part of the integration?
Yes: its agents, its Copilot posture and its shadow AI are inventoried read-only in diligence, through Microsoft Agent 365 and the Purview posture reports, and they enter the Day 1 record.
Microsoft Agent 365 is the control plane that observes, governs and secures agents built on Microsoft platforms or acquired from third parties, through the Microsoft 365 admin center, Microsoft Entra, Microsoft Purview and Microsoft Defender. (Microsoft Learn, checked Oct 31, 2026)
Inventory the add-on's agents before close and they are a line in the deal memo. Inventory them after and they are a line in the incident report.
THE FIRST RUNG
Where does the deal team start on the next add-on?
With the AD to Entra Readiness review, five delivery days, read-only, then M&A IT Integration as the paid program, with Simple Merge as the method shown.
The portfolio CFO gets the go or no-go in writing. Simple Merge is a Simple Intelligence Group product, separate from the service and never required to buy it. Microsoft-funded where you qualify.
AFTER TWO WEEKS
What will be working after two weeks?
- The add-on tenant is inventoried read-only: identities, devices, data, applications, agents.
- The Day 1 readiness record separates tested from assumed on one page.
- The pilot connection for one group is designed with its rollback written first.
- You hold the 100-day plan and its first wave as a written go or no-go.
The work is delivered remotely inside your own Microsoft tenant, wherever your business is, and on site only when the work needs it.
HONEST ABOUT LIMITS
What this does not do yet
It does not give every acquired agent its own governed identity in the first two weeks. Microsoft Entra Agent ID is generally available to every Microsoft Entra customer and gives each AI agent its own identity with owners and sponsors, Conditional Access templates for high-risk, autonomous and on-behalf-of agents, and sponsor lifecycle workflows; extending Entra security features to agents needs a Microsoft Agent 365 license, and the admin center creation wizard and agent user accounts remain in preview. (Microsoft Learn, checked Nov 4, 2026) The acquired agents are inventoried first; each gets its Entra Agent ID, sponsor and Conditional Access in a wave you approve, with the Agent 365 license checked in the acquired tenant.
It does not merge tenants in the first two weeks: a custom domain can live in one tenant at a time, and the merge is a wave you approve.
It does not set the deal timeline: the clock is the deal's, the gates are yours.
THE ONE THING TO REMEMBER
Same playbook, every add-on: a Day 1 record, a 100-day plan and a written go or no-go per wave.
Said another way: integration is a program you run again, not a project you invent again.
Said a third way: the acquired company's AI is part of diligence now.
SHOW YOUR WORK
See the control path on a fictional bank.
The agent action gate
The fictional bank records the exact action and approver.
Coming
See every demonstrationDIRECT ANSWERS
Questions before you decide.
What is in the Day 1 readiness record?
Identities, devices, data, applications and agents of the add-on, each marked tested or assumed, with the rollback for each planned change and the go or no-go for the first wave.
Do the tenants have to merge on day one?
No. Cross-tenant synchronization in Microsoft Entra ID gives acquired people access from day one while the merge is planned as its own wave with its own rollback.
How does AI enter diligence?
Through a read-only inventory of the add-on's agents, owners, identities and data reach in Microsoft Agent 365, plus its Copilot sharing posture, before close.
What is Simple Merge?
A Simple Intelligence Group product that shows the integration control plane. It is the method shown and is never required to buy the program. Simple Intelligence Group lists it as coming soon.
How is it priced?
Quoted after a scoping call. The readiness review is five delivery days, read-only, and scoped separately from the integration program.
NEXT STEP
Start with a boundary you can explain.
Choose a focused check, or speak with the team about the workflow you need to improve.