SharePoint, Teams, Power Automate, Power Apps, Copilot. I set them up around how your firm actually works, secure the tenant and the devices, and train your people to run it. Columbia, Maryland.
By Mark Lucas, founder of JamesTech LLC, Columbia, MD. Roughly thirty years on the Microsoft stack, three of them at Microsoft. Artemis program contractor at NASA.
Email moved to Exchange years ago and everything else stayed where it was. The files are on an office server nobody can reach from home, or spread across personal OneDrives. Teams got turned on and never adopted. Copilot got bought for everyone and opened by two people.
Here's what I find in most 5 to 200 person tenants on the first look:
Some of that is a security problem and some of it is a setup problem. I handle both, and the fixes come from one place.
MFA and passkeys on every account, Conditional Access that fits how people actually sign in, admin roles named and reduced, and the shared admin login retired. Microsoft Entra, set up on purpose.
Defender for Office 365 tuned against phishing and malware, laptops and phones enrolled in Intune with Defender for Endpoint, and compliance policies that decide what an unmanaged device can reach. Done with my Microsoft 365 security partner.
Sites and libraries that match how the firm is organized. Metadata instead of nine levels of folders. Permissions by group, not by person. The office server retired, with OneDrive syncing the new structure to every computer.
A few teams and channels that map to real work, not one per whim. Meeting recordings and transcripts landing where people can find them. Guest access decided on purpose.
Approvals, reminders, document routing, status updates, and the hand-offs between systems (payroll, accounting, CRM, forms). One client's 40-hour manual task now runs in minutes.
The tracker that's currently a spreadsheet with six tabs, rebuilt as an app with a proper table behind it, row-level history, and a dashboard for whoever asks for the numbers.
Copilot for the seats where it changes the work, priced at the real per-seat cost, after the documents are organized enough for it to be useful. Copilot Studio agents that answer from your own SharePoint content under your own permissions.
Licensing review, idle seats removed, groups instead of one-off grants, guest accounts audited, retention set, external sharing decided on purpose. Every change documented, so the next person can see what was done and why.
Microsoft 365 backup in place and restore-tested, because Microsoft's retention is not a backup. Security alerts and sign-in risk watched by a person, with a monthly report in plain English.
Most firms this size end up with one vendor for security, another for "the SharePoint stuff," and nobody who sees the whole picture. Identity, devices, email protection, backup, and monitoring are part of the practice, handled with my Microsoft 365 security partner, alongside the workloads your staff use every day.
How this fits with the IT you already have comes down to three lines:
The same holds for AI. Once the documents are organized and the permissions make sense, the agents that read them need an owner too. That's the agentic AI management side of the practice, and this page is usually what comes first.
The tenant keeps getting messier, because every new hire adds a folder and every departure leaves a seat. The person who knows where everything is keeps being the only person who knows. The manual work keeps costing the same hours every week, and the Copilot seats keep billing whether anyone opens them or not.
Then somebody asks the AI a question about the business and it answers like a stranger who met you five seconds ago, because the knowledge it needed was in a drawer, an inbox, and one employee's head. That's the moment most firms call.
I've built this for 5 person nonprofits and for teams inside a global financial-services firm, and the shape is the same at both sizes. Read the case study for the larger one.
Sets up the parts of Microsoft 365 you already pay for around how the firm actually works: SharePoint for documents, Teams for communication, Power Automate for the recurring workflows, Power Apps for the forms and trackers, and Copilot where it earns its seat. I also clean up the tenant and train the team to run it.
Yes, when you want me to. Already have an MSP? Keep them, and I do the part they aren't doing: the fractional CIO or fractional AI officer role, the workloads, the agents. No MSP, or ready for a new one? I do everything: MFA, passkeys, and Conditional Access on the accounts, Defender on mail and devices, Intune on laptops and phones, restore-tested backup, and monitoring a person reads, with my Microsoft 365 security partner.
Yes. A messy file server moved to the cloud is still a messy file server, so the move starts with a structure: which sites, which libraries, who owns each one, what permissions apply. Then the files move in, and OneDrive syncs them to every computer so staff keep working the way they did.
Sometimes, for some seats. Copilot works well when the documents are organized and the permissions are right, and poorly when they aren't. I price it at the real per-seat cost, recommend it for the people whose work it will change, and say so when it won't pay for itself.
A short call, then an assessment scoped to the size of the firm: what you own, what you use, what's exposed, and what to build first. Most firms leave with a ranked list and take on the top two or three items.
A short call to scope a Microsoft 365 assessment. You'll leave with a ranked list of what to fix and build first. Scoped to your team.
Book a scoping call