It's 7:10 on Monday morning. The principal opens their phone in the back of the car, and the inbox is right where they left it, with Friday's thread from the estate attorney at the top and Thursday's board dinner on the calendar. Their chief of staff has already accepted two meetings on their behalf. Nobody mentions the migration, because there is nothing to mention.
That quiet morning is the review that matters. The mailbox copies, DNS changes, licensing, and permission work stay invisible to the people at the top unless something goes wrong. Principals judge a move to Microsoft 365 by a short list: email and calendar work on Monday on every device they use, nothing private is exposed to the wrong person, and any training fits their schedule. Plan those three first, and the rest of the project inherits the goodwill.
At a glance
- Design the principal's Monday morning before you design the cutover: their devices, their delegates, and their first sign-in.
- Map who should see what across the family, the entities, and the staff, and build permissions to match before anything moves.
- Pilot with the principal's own office, keep a rollback path, and train in short, private sessions.
Start with the principal's Monday
Before anyone schedules a cutover, sit down with the chief of staff or executive assistant. They usually know the principal's setup better than anyone, including the principal. Write down every device that touches mail and calendar: the phone, the tablet, a laptop at home, a desktop at the office, and anything at a second residence. Note which apps the principal actually uses, whose calendars they look at, and who sends or accepts invitations for them.
Then look for the small things that people notice right away. Email signatures. Contacts built up over twenty years. A folder structure only the principal understands. A shared family calendar. Each of these should arrive intact, and each should be tested on the principal's real devices before the cutover, using a test account set up the same way.
The goal for Monday is simple: the principal picks up the phone and nothing looks different. Everything else on the project plan should support that.
Delegates and shared mailboxes for the people who run the office
In many family offices, the principal's inbox and calendar are worked by two or three people. Microsoft 365 handles that through delegate access and shared mailboxes, and both need deliberate setup.
Outlook lets the principal name delegates who can receive and respond to mail and meeting requests on their behalf. Microsoft describes three permission levels for each folder: Reviewer (read only), Author (read and create), and Editor (read, create, and change items the principal created). Delegate access requires a work or school Microsoft 365 account. Send As permission, where a message appears to come directly from the principal, can only be granted by an administrator, so decide in advance who gets it.
Shared mailboxes suit functions rather than people: a general office inbox, travel requests, or bill pay. Several staff can work from one, and the mail stays with the office when someone leaves.
One practical detail catches assistants off guard. In the new Outlook, shared and delegated calendars may not appear by default. Show the chief of staff where to find them before Monday so their first morning isn't spent hunting.
Permissions around entities and family members
A family office often supports several entities: an operating company, trusts, a foundation, investment partnerships. Each has its own advisors, staff, and confidentiality expectations. Microsoft 365 gives you room to reflect that with separate SharePoint sites or Teams for each entity or function, each with membership limited to the people entitled to it.
The risk sits in the files you bring along. Permissions on an old file server tend to accumulate over years: a former assistant who still has access, a folder opened up for one project and never closed. Moving files as they are tends to carry that old access with them. Review it first, and use the migration as the moment to tighten it.
- Principal
- Typical access: Own mailbox, calendar, and personal files
- Decide before cutover: Which items stay private from delegates
- Chief of staff or executive assistant
- Typical access: Delegate on mail and calendar
- Decide before cutover: Whether they need Send As, and on which folders
- Office and household staff
- Typical access: Shared mailboxes for travel, bills, or requests
- Decide before cutover: Who can send from each one
- Entity advisors and staff
- Typical access: Sites for the entities they serve
- Decide before cutover: Which entity data each person can open
- Family members
- Typical access: Their own accounts, if they are in the tenant at all
- Decide before cutover: Whether they belong in the office's tenant
That last row deserves real thought. Anyone holding administrator rights in the tenant has a path to the data inside it, so what lives there should match who runs it.
The same logic applies to personal and business mail. A principal's personal email account usually stays personal, and the office tenant holds business mail. If something personal is going to move in, the principal should make that call on purpose.
Outlook also lets people mark appointments as private. Confirm with your IT team how private items behave for delegates in the versions of Outlook your office uses, and test it with a sample appointment before the principal relies on it.
Sign-in security principals will accept
Principals will tolerate strong sign-in security when it is quick and set up for them. They will resist anything that interrupts a call or sends them hunting for a code.
Passkeys are often the best fit. They resist phishing, and signing in takes a fingerprint, a face scan, or a PIN. Microsoft Entra ID supports device-bound passkeys in Microsoft Authenticator (on iOS 17 or Android 14 and later) and on FIDO2 security keys. Microsoft recommends security keys for users with elevated privileges and describes synced passkeys, stored in Apple iCloud Keychain or Google Password Manager, as a convenient option for most users.
For a principal whose inbox is a target, a device-bound passkey plus a backup key kept in the office safe is a sensible pairing. Our piece on passwordless sign-in covers the broader options.
Set it up in person, on the principal's own devices. Register two methods so a lost phone doesn't lock anyone out, and agree on a recovery process that never depends on an emailed link. If you want policies that require the stronger method for specific people, Conditional Access requires Microsoft Entra ID P1 licensing, which is included in Microsoft 365 Business Premium.
Training that respects their time
Principals rarely want a class. They want a short, private session in their own office or at home, on their own devices, covering only what changed: where a shared calendar now appears, how to find older mail, and what the new sign-in looks like.
Train the chief of staff and assistants first, and in more depth. They will field most questions in the first week, and their confidence sets the tone. Leave a one-page reference behind, and give the office one named person to call for the first few days. For family members, offer the same short session at a time that suits them.
A quiet cutover with a pilot and a way back
Sequence matters as much as the technical steps.
- Pilot with the principal's office. Move the chief of staff and one or two assistants first, and test delegate access, shared calendars, mobile mail, and sending on the principal's behalf.
- Schedule around the principal's calendar. Avoid board meetings, travel days, closings, and tax deadlines.
- Copy mail ahead of time so the final sync is small and fast.
- Switch mail delivery during a quiet window, often a Friday evening or weekend.
- Keep a way back. Leave the old system readable for an agreed period, write down what would trigger a rollback, and name who makes that call.
- Be there Monday. Have someone on-site or on the phone at the principal's office first thing.
Plan the experience first
A Microsoft 365 move succeeds in a family office when the principal barely notices it happened. That comes from planning their morning, their delegates, and their privacy before the technical work, and from treating training as a personal service.
At CTP, we plan family office migrations from the principal's chair outward, with one named senior advisor, a documented permission map, a pilot, and a tested rollback. Read how we approach Microsoft 365 migration for private companies and family offices, or see our broader work with private companies and family offices.
Sources and further reading
- Microsoft, About delegates: Allow someone to manage your mail and calendar in Outlook
- Microsoft, New Outlook tips for executive admins and delegates
- Microsoft, Passwordless authentication options for Microsoft Entra ID
- Microsoft, Enable passkeys in Microsoft Authenticator
- CTP, Private Companies and Family Offices

