Skip to content

New: How We Design Technology - our seven-layer architecture model, explained in full. See the architecture

general

Your IT Provider Does Not Get Discretion. Time to Switch?

10/29/2026

Your chief of staff mentions it almost in passing. The technician who came to fix the scanner last week had the family's estate folder open on screen when she walked back into the room. Nobody thinks he meant any harm. He was probably looking for a driver. Still, someone you have never met has now scrolled past trust documents and a draft of next year's gifts.

Most companies judge an IT provider on how fast tickets get closed. In a family office, the more important question is who touches what, and whether those people behave like the other advisors you trust with private matters. If the honest answer keeps coming back as "we're not sure," your provider may be perfectly competent and still the wrong fit.

At a glance

  • Discretion shows up in small habits: who connects, when, with what access, and whether anyone tells you.
  • A good fit looks like one named senior contact, limited and time-bound access to your Microsoft tenant, logged remote sessions, and confidentiality terms in writing.
  • If you decide to change providers, secure ownership of accounts and credentials first, then run the old and new teams side by side for a short overlap.

Your IT provider may see more than any other advisor

Your attorney sees the estate plan. Your CPA sees the returns. Your wealth manager sees the portfolio. The people who administer your email, file shares, and devices can, in principle, reach all of it, along with travel plans, household staff records, the children's school correspondence, and every note the principal has typed on a phone.

That reach comes with the job. Someone has to be able to restore a deleted folder or reset a locked account. The question is whether your provider treats that access the way your other advisors treat theirs: sparingly, by name, and with a clear reason every time. A firm built for high-volume help desk work often isn't set up to do that, however capable its technicians are.

Signs your provider wasn't built for discretion

Technicians browse while they fix. A support task rarely requires opening the folders where legal, tax, and estate documents live. If staff notice unrelated files open on screen, or hear that someone "just took a look," the provider's habits are set for convenience.

Remote sessions start without warning. You look up from a call and the cursor is moving on its own. Good practice is to ask before connecting, show a clear indicator during the session, and keep a record of who connected and when.

The whole help desk shares one admin login. When every technician uses the same administrator account, nobody can tell you which person made a change. A technician who leaves the firm also leaves with the same key everyone else holds.

A new name answers every ticket. The principal ends up explaining the household's setup to someone different each time, and private context spreads across people you have never met.

No one comes on-site. Some work belongs in the room: a new phone for the principal, the network at a second home, a sensitive file restore, a family member who needs a patient hour of help. A provider that can only offer a remote ticket will struggle with all of it.

Vague answers about access. Ask, "Who at your firm can see our email today?" If the answer takes a week, or comes back as "the team," the provider probably doesn't know either.

What discretion looks like in practice

Discretion can be checked. It shows up in how a provider is organized, how its tools are configured, and what it is willing to put in writing.

One named senior contact

You should have one senior person who knows the family, the entities, and the staff, and who decides who else gets involved. Other technicians can still do the work, under that person's direction and with only the access a given task needs. When something sensitive comes up, you call someone you know.

Limited, time-bound access to your Microsoft tenant

If your office runs on Microsoft 365, ask how the provider reaches your tenant. Microsoft has moved partners away from the older delegated admin model, which granted broad, long-lived access, toward granular delegated admin privileges (GDAP). Under GDAP, a partner requests specific administrative roles for a set period, from one day up to two years, and the relationship takes effect only after someone in your organization approves it. You can see the partner's roles, and remove them yourself, from the Partner relationships page in the Microsoft 365 admin center.

GDAP governs the provider's admin roles in your Microsoft cloud. The remote support agent on each laptop, the backup console, the firewall, and any server at the house each need their own named accounts and their own access review.

Consent and a record for every session

A remote session should begin with a request the person at the keyboard can accept or decline, except for after-hours maintenance you have agreed to in advance. Each session should be logged with the technician's name, the device, and the time. Ask whether sessions can be recorded and who is allowed to watch the recordings.

Confidentiality in writing

The services agreement should cover the provider's employees and subcontractors, require background checks for anyone with administrative access, prohibit browsing data outside the scope of a request, and require prompt notice if something goes wrong. Have your attorney review it the way they would review any other advisor's engagement letter.

Documentation and an exit plan you control

Keep a current list of every administrator account, who uses it, and how it is recovered. The domain registrar, Microsoft tenant, backup service, and key vendor portals should belong to the family office, with the provider added as a user. An exit plan written on a calm day turns any future change into routine work.

Questions to put to your current provider

You can learn a lot from one short meeting. Here are five questions and what a reassuring answer sounds like.

  • Who at your firm can access our email and files today?
    • A reassuring answer: A short list of names and roles, sent within a day or two
  • How do you reach our Microsoft 365 tenant?
    • A reassuring answer: Through GDAP, with specific roles and an end date we can see in our admin center
  • Do technicians use their own named accounts?
    • A reassuring answer: Yes, so every administrative action traces to one person
  • What happens before a remote session starts?
    • A reassuring answer: The user is asked to accept, and the session is logged
  • Who owns our domain, tenant, and backup accounts?
    • A reassuring answer: The family office does, and we can show you the records

If the answers are vague, slow, or defensive, you have learned something important. A provider can fix gaps it is willing to name. It is much harder to work with one that can't tell you where they are.

If you decide to make a change

A transition is a sensitive moment, because the outgoing provider still holds the keys. Keep it calm and orderly.

  1. Secure ownership first. Before you give notice, confirm the family office (or the right entity) owns the domain registrar account, Microsoft tenant, backup service, network equipment accounts, and key vendor portals. Create named administrator accounts for your side and keep emergency access under your control.
  2. Collect a complete access list. Ask the current provider for every administrator account, service account, remote tool, and GDAP relationship. Compare it with what you can see yourself in the admin center.
  3. Overlap the two providers. Bring the new team in before the old one leaves. A useful overlap runs long enough to cover one full monthly cycle of patching, backups, and renewals.
  4. Close out old access deliberately. Remove the outgoing provider's GDAP roles, uninstall their remote support agents, disable their accounts, change any shared credentials they knew, and confirm that backups and monitoring now report to the new team.
  5. Keep the family's experience quiet. Tell staff and family members only what changes for them, such as a new number to call, and have the new contact introduce themselves in person.

Discretion should be part of the service

The right provider feels like another trusted advisor. You know their name, they know the household, and you rarely have to think about who might be looking at what.

That is how we approach family offices at CTP. You work with one named senior advisor who knows the people and the entities, we come on-site when the work belongs in the room, and every account and access path is documented so the office stays in control. If your current arrangement has you wondering, see how we deliver managed IT for private companies and family offices, or schedule a quiet conversation with our team.

Sources and further reading

Ask about something important for you.

Curious about our take on an industry or technology topic? Let us know.

Contact Us