Identity and accounts
Whether you sync from Active Directory or run cloud-only, and how sign-in, MFA and admin roles are set up from day one.
Microsoft 365
Microsoft 365 Setup & Design
Moving to Microsoft 365 is a one-time chance to put the foundations right, and the decisions made in week one are the expensive ones to undo later. We design the licence mix, the identity setup and the file structure before anything moves, so you end up with a setup that stays cheap to run and easy to grow into rather than a rebuild waiting to happen. Whether this is your first move or a tenant somebody else half-built, the design comes first.
What this protects
A decision made once and lived with for years
The tenant you build on day one decides what Microsoft 365 costs you, how well it protects you, and how easily it grows for the next five years.
The licence mix you are stuck with
Wrong tiers agreed at the start are paid for every month until somebody unwinds them. Correct licensing is money straight back into working capital.
A setup your team will actually use
Sensible structure and a short training session mean people adopt the tools instead of working around them, which is where the productivity return lives.
Security built in, not bolted on
A baseline applied before the first sign-in is cheaper and safer than closing gaps after an incident, and it is the evidence an auditor asks to see.
Design first, migrate second
A Microsoft 365 migration is mostly not a technical problem. Moving mailboxes is the easy part. The difficulty is that every decision you make on day one, from the tenant name and the licence mix to the security baseline and which accounts hold admin roles, is expensive to unpick eighteen months later.
So we design before we migrate. You get a written plan covering the licence mix, the identity setup, the security baseline, the file migration and the order of work. You can show it to your board or your auditor before anyone touches a mailbox.
What the design work covers
Licence selection
The right tier for each group of users, so you are not paying for features nobody opens.
Security baseline
A documented set of controls applied before the first user signs in, rather than bolted on after an incident.
File and SharePoint design
A library structure and permission model agreed up front, so you do not inherit eight years of folder sprawl.
Migration planning
Order of work, cutover windows and rollback plans, communicated to staff before the day rather than on it.
Adoption and training
Short, practical sessions for your team so the new tools get used rather than feared.
A migration done badly by a previous provider looks like this
- Two tenants, because nobody noticed the original one still existed
- Everyone dropped onto the same licence tier with no thought to role
- Security defaults switched off during the migration and never turned back on
- SharePoint files dumped into a single library mirroring the old file server
- MFA deferred until after go-live and never revisited
- No documentation, so nobody knows how the tenant was actually built
New setup or rescue job
Some clients come to us before they have moved a single mailbox. We design the tenant, plan the migration and run it, and they arrive in Microsoft 365 with a clean, documented setup.
Others come to us because a previous provider left a mess: duplicated accounts, licences nobody can account for, security features disabled mid-migration. We audit what is there, document it, and fix it in stages without another disruptive move.
What we hand over at the end
- A written record of the tenant design and why it was built that way
- A licence breakdown by user group
- Documentation of the security baseline and any exceptions
- A migration report covering what moved, when, and what did not
Questions we get asked about Microsoft 365 Setup & Design
For most businesses, between two and six weeks, depending on mailbox sizes and how much file data needs moving. The design phase runs first; the actual cutover is usually a weekend.
Yes. We audit the current configuration, document it, and fix it in stages. In most cases you do not need to migrate again. The tenant can be corrected in place.
Yes. Mail, calendars, contacts and files move across, and old addresses keep working. Users notice very little beyond a new sign-in.
Some, usually an hour or two. We run short sessions focused on the tools your team will actually use day to day.
Yes. We migrate from on-premise Exchange, hosted Exchange, Google Workspace and older platforms, including the messy ones.
Not sure whether you need microsoft 365 setup & design?
Book a free 60-minute health check. We will tell you what you actually need, including when the answer is nothing.