Most construction companies in the Treasure Valley are on Microsoft 365. Far fewer have it configured for an industry that runs files across 40 jobsites, 12 subs, three architects, and a banker who only wants signed PDFs.
The license is fine. The setup is where everything falls apart.
Two things go wrong. First, the company uses Microsoft 365 Business Standard when Business Premium would better fit its field devices and security needs. Second, even companies paying for Premium may not use its device management, sign-in rules, or safer sharing settings. The license is only useful when the features are configured.
Here is how I set up Microsoft 365 for a construction company. The same basic approach works for a 15-person framing company or a 75-person general contractor.
Business Standard vs. Business Premium: When Premium Pays for Itself
Business Premium runs roughly $8 to $10 more per user per month than Business Standard (check Microsoft's current pricing for exact numbers). Staying on Standard looks like savings until you price out what Premium includes that Standard doesn't.
Premium adds:
- Intune : mobile device management for laptops, phones, tablets. Replaces the need for a separate MDM product ($5-15/user/month elsewhere).
- Microsoft Defender for Business : EDR for every endpoint. Replaces standalone antivirus / EDR ($5-10/user/month elsewhere).
- Microsoft Entra ID P1 (formerly Azure AD Premium P1) : conditional access policies, password protection, multi-tenant identity. Worth about $6/user/month standalone.
- Information protection : sensitivity labels for documents, basic DLP. Useful if you handle bid documents or client financials.
- Advanced anti-phishing : better email filtering than Standard's tier.
The math, for a 15-person construction shop:
- Standard plus add-ons: Standard licensing, then add EDR (~$10/user) and MDM (~$8/user) ≈ $270/month more
- Premium: roughly $120 to $150/month more than Standard, all in
Premium is cheaper and it's all under one tenant, one bill, one admin console. The only reason most construction companies are still on Standard is that nobody priced it out properly when they signed up.
The "when Premium doesn't pay" exception: if you're 5 users and your only devices are 5 desktop PCs that never leave the office, you can probably get away with Standard plus standalone EDR. Once you have any field staff, any mobile devices, or any compliance ask from a GC or insurance carrier, Premium is the right answer.
Conditional Access for Field Crew vs. Office
Once you're on Premium, you have Microsoft Entra ID P1 (formerly Azure AD Premium P1). Use it. Conditional access is the single most underutilized feature in M365 for construction.
The principle: different access rules for different user groups, based on what they actually need.
Office staff conditional access policy (typical):
- Require MFA on every sign-in
- Block sign-in from outside the US (most construction companies have no legitimate international users; this kills entire classes of attack)
- Require a compliant device (managed by Intune) for access to financial systems or admin functions
- Force password re-entry on sensitive operations (mailbox rule changes, app consents)
Field crew conditional access policy (typical):
- Require MFA on every sign-in
- Allow sign-in from approved geographies (US states they actually work in)
- Don't require fully managed devices, but require a passcode-locked, encrypted device (Intune compliance check, lighter touch than office staff)
- Block legacy authentication protocols (POP, IMAP, SMTP basic auth). These are the back door attackers use to bypass MFA
A separate "service account" policy:
- For shared logins that integrate with line-of-business apps (the dispatch software, the bookkeeping export, etc.)
- Locked to specific IP addresses (your office, your trusted vendor IPs)
- Use service principals or managed identities instead of shared user logins; avoid app passwords (they bypass MFA and depend on the legacy authentication you just blocked)
The reason this matters: a phishing attempt against a field tech's account looks different from one against an office admin. The field tech's account doesn't have legitimate access to the wire-transfer system. The office admin's account doesn't legitimately sign in from Vietnam. Conditional access lets you encode the rules that match your reality, so anomalies stand out.
For more on what credential attacks actually look like in 2026, see my post on why MFA alone isn't enough anymore .
File Server to OneDrive Migration: Don't Lose the Plan Files
This is where construction companies hurt themselves the most. They've been running a file server (or worse, a Synology in the closet) for plan archives, project folders, daily logs, photos. Sometimes it's a decade of work product. Then someone decides to "go to the cloud" and the migration goes sideways.
These mistakes are common. Here's how it should actually work.
Phase 1: Audit before you migrate
- Inventory every share, every folder, every special permission, every old user with access. The crap you don't see is what bites you on cutover day.
- Identify what's active (current projects) vs. cold (closed jobs you keep for 5-10 years). They go to different places.
- Map out who needs access to what. This becomes your SharePoint / OneDrive permissions structure.
Phase 2: Pick the right destination
For most construction companies:
- Active project files → SharePoint Online sites, one per project or per major client, with permissions for the team on that job (and removable when the job closes).
- Personal work files → OneDrive for Business per user.
- Cold project archives → Azure Blob Storage or a separate "Archive" SharePoint site with read-only permissions and a different retention policy.
- Reference files (price books, standard details, photo libraries) → a shared SharePoint site that everyone can access.
Don't dump everything into one giant "Files" site. The permissions get unmanageable and you lose the ability to scope access.
Phase 3: Migrate carefully, in batches
- Use a real migration tool (Microsoft's SharePoint Migration Tool, or commercial like ShareGate). Don't drag-and-drop in File Explorer. You lose metadata, versions, and you'll corrupt large transfers.
- Migrate cold archives first. Low-risk, builds confidence.
- Migrate one active project at a time, with the team on that job available to test access immediately.
- Keep the old file server running in read-only mode for 60-90 days as a safety net. Don't shut it down on cutover day.
Phase 4: Train and lock down
- Train users on how to find files in the new structure (this is the part that determines whether the migration "works" from their perspective).
- Disable the old shares.
- Lock down permissions per project. Subs and architects get added to the SharePoint site for their job, not given access to the entire file structure.
- Configure retention policies: old projects retained, current projects backed up at the right cadence.
The total project is usually 2-4 weeks of part-time work for a 20-person company. The biggest risk isn't the technology; it's poor planning and impatient owners who try to skip Phase 1.
A Few Microsoft 365 Tips for Construction Companies
A few patterns that work well for Boise construction companies :
- Use Teams channels per project. One Team per major client or division, channels per project. Plan discussions, RFI threads, change-order conversations all live with the files. Beats sifting through email.
- Document libraries with metadata, not deep folders. Tag drawings with revision, discipline, and date. SharePoint can sort and filter on metadata in ways folders can't.
- OneDrive Known Folder Move for field tablets. Desktop, Documents, and Pictures automatically sync to OneDrive. Tablet gets dropped off a scaffold? Issue a new one, sign in, all the files are there. No data loss.
- External sharing locked down. By default, M365 lets users share files with anyone outside the company. For construction, you want this controlled. Allow external sharing only to specific approved domains (your architects, GCs, subs) and require sign-in for access. Open links are how plan sets end up on competitor desks.
The Honest Take
M365 done right is the cheapest, most powerful security and productivity stack a small construction company can run. M365 done wrong is a liability and a frustration. The difference is mostly configuration, not licensing.
If you're paying for Business Standard and stitching together a half-dozen other tools to fill the gaps, you're spending more for worse outcomes. If you're paying for Premium but not using Intune or conditional access, you're leaving the security features on the shelf.
A proper M365 review tells you exactly where you stand. Many shops find they're paying for tools Premium already includes, or for Premium features they never turned on.
For broader cybersecurity context across all the tools you run, see our cybersecurity services page .
Let's Talk
If you want a second set of eyes on your M365 tenant (what license you're on, whether Premium would pay back, whether your conditional access policies actually exist), start with a free 15-minute call.
Request a Free 15-Minute Call →