Microsoft 365 for property management is almost never a technology decision. It is an information architecture decision that happens to be billed per user per month. Most UK letting agents, block managers and managing agents already pay for Microsoft 365 — the licences sit on the direct debit every month — and yet the tenancy files still live on a mapped drive, the maintenance inbox is one negotiator’s personal Outlook folder, and nobody can say with confidence which site holds the current gas safety certificates for a block.
That gap between what is licensed and what is actually built is the subject of this guide, and closing it is what deploying Microsoft 365 for property management actually means in practice. A property business is not a generic small company with thirty desks. It holds client money, it processes special category data about tenants, it works with a rotating cast of contractors who need access to some things and none of the others, and it is now operating under a tenancy regime that changed fundamentally on 1 May 2026. Setting up Microsoft 365 for property management well means designing around those four facts before you assign a single licence.
This guide is written for UK firms of roughly five to three hundred staff. It sits alongside our IT support guide for property management companies, the Microsoft 365 security checklist for property firms and the twenty-control cyber security checklist for managing agents. Those cover the support model, the security baseline and the wider control set. This one covers the build of Microsoft 365 for property management itself: which licences, which sites, which mailboxes, in which order, at what cost. Good cybersecurity is a consequence of that structure rather than a bolt-on to it.
Every price quoted here is the UK list price per user per month on an annual commitment, excluding VAT, taken from Microsoft’s own UK storefront and checked on 16 August 2026.
Table of contents
- What Makes Microsoft 365 for Property Management Different
- Choosing the Licence Mix for Microsoft 365 for Property Management
- Tenant Foundations: Domains, Identity and the Right Setup Order
- SharePoint Architecture for a Property Portfolio
- Teams Structure for Branches, Blocks and Contractors
- Exchange Online, Shared Mailboxes and the Maintenance Inbox
- Devices and Intune Across a Site-Based Workforce
- Compliance Settings Every Microsoft 365 for Property Management Tenant Needs
- Integrating Microsoft 365 for Property Management With Reapit, Alto and Fixflo
- Migrating to Microsoft 365 for Property Management Without Losing Data
- What Microsoft 365 for Property Management Actually Costs
- A 90-Day Rollout Plan for Microsoft 365 for Property Management
- Seven Mistakes That Undermine Microsoft 365 for Property Management
- Frequently Asked Questions About Microsoft 365 for Property Management
- References
What Makes Microsoft 365 for Property Management Different
Generic Microsoft 365 advice assumes a business where everyone does broadly the same job at broadly the same desk. Property firms break that assumption in four specific ways, and every design decision in Microsoft 365 for property management follows from them.
You hold three separate categories of other people’s money and data
A managing agent holds client money in a protected account, personal data about tenants that includes immigration status and sometimes health information, and commercially sensitive landlord information. Client money protection has been mandatory in England since 1 April 2019. Those three categories have different retention rules, different access rules and different breach consequences, and a single shared drive collapses them into one. Structuring Microsoft 365 for property management starts by refusing that collapse.
Your workforce is not all at desks
Property managers do inspections. Maintenance operatives are on site. Block managers attend evening residents’ meetings. Viewings happen on Saturdays from a phone. Any design that assumes a domain-joined desktop in a branch office will fail for a third of the headcount, and that third is often the group handling the most sensitive documents in the least controlled environment. Microsoft 365 for property management has to be designed mobile-first for exactly that reason.
Contractors need access without becoming staff
Every managing agent works with plumbers, roofers, gas engineers, cleaners and surveyors who need a works order, a site plan and a means of returning certificates and photographs. None of them should have a mailbox on your domain or a licence on your bill. Getting external access right is one of the highest-value parts of building Microsoft 365 for property management, and it is the part most often solved badly with a shared password on a file transfer site.
The compliance clock moved in 2026
The Renters’ Rights Act 2025 received Royal Assent on 27 October 2025 and its main provisions commenced on 1 May 2026. Section 21 was abolished, all assured shorthold tenancies converted to assured periodic tenancies, and agents managing on behalf of landlords had to serve the government information sheet on existing tenants by 31 May 2026, with penalties up to £7,000 for failure. Evidence of service is now a document you may need to produce years later, which makes retention a design requirement rather than an afterthought.
| Sector characteristic | Generic SME assumption | Design consequence |
|---|---|---|
| Client money held in trust | One finance folder | Separate site, restricted membership, longest retention |
| Special category tenant data | HR folder only | Sensitivity labels on tenancy files, not just on payroll |
| Site-based and evening working | Everyone has a desktop | Mobile-first licensing, Intune app protection |
| High contractor churn | Suppliers email attachments | Guest access with expiry, never a shared login |
| Property-level record keeping | Folders per client | Metadata per property, not a folder tree per property |
| Statutory retention windows | Keep everything forever | Purview retention labels with defined disposal |
The sector context in numbers
Propertymark’s Housing Insight Report for May 2026 put the average member branch at 12.09 properties available to rent, 8.36 new tenancies agreed and 98 tenant registrations in the month, with 2.39 new fully managed instructions. More than 834,000 homes have left the private rented sector over the past decade.
A survey of 334 agents published on 9 July 2026 found 81% saying the regulatory burden had increased, 77% saying management and new business now need different skills, and 56% naming property manager recruitment as their biggest staffing problem. A tenancy file that a new starter can find without asking anyone is worth real money in that market, and it is the clearest single test of whether Microsoft 365 for property management has been set up properly.
Choosing the Licence Mix for Microsoft 365 for Property Management
The single most common and most expensive mistake in Microsoft 365 for property management is buying one licence type for everyone. Property firms have at least three distinct user profiles, and paying the top rate for all of them wastes money while paying the bottom rate for all of them leaves you without the tools that make the rest of this guide possible.
The plans that matter, and what they actually add
Microsoft 365 Business Basic gives web and mobile apps plus a 100 GB mailbox at £5.40. Business Standard with Copilot adds the installed desktop applications at £18.10. Business Premium with Copilot adds the entire security and management layer at £24.60: Microsoft Intune, Microsoft Entra ID Plan 1 with Conditional Access, Microsoft Defender for Business, Defender for Office 365 Plan 1 and Purview data loss prevention. Microsoft 365 Apps for business is £9.80 and includes no email at all. All three Business plans are capped at 300 users per tenant.
Where the enterprise plans start to matter
Above 300 users the Business plans are unavailable and you move to Microsoft 365 E3 at £33.50 or E5 at £51.60, neither of which has a user cap. A “no Teams” variant of every plan exists at a lower price — E3 at £27.00, Business Premium at £22.10 — which matters only if you have genuinely standardised on another meeting platform. Most property firms under 300 staff never need enterprise plans, and the correct answer for Microsoft 365 for property management at that size is almost always a Business Premium core with cheaper licences around the edges.
Frontline licences for site-based staff
Microsoft 365 F1 at around £2.00 and F3 at roughly £6.30 to £7.20 are built for staff who do not sit at a desk. For a maintenance operative who needs Teams, a works order and a camera roll, an F-plan is the honest fit. Be aware that the frontline SKUs took the largest percentage increases in the July 2026 price round, so the saving is smaller than it was.
The July 2026 pricing change you need to understand
From 1 July 2026 Microsoft raised prices and folded Copilot into the Business Standard and Business Premium bundles. Business Basic rose by roughly 17% and Business Standard by roughly 12%; the underlying Business Premium rate was left alone, with the increase to £24.60 representing the Copilot inclusion rather than a rise in the base plan. New prices apply immediately to new subscriptions and at the next renewal for existing ones. Our Microsoft 365 Copilot cost and ROI analysis works through whether that bundled capability earns its place.
| Plan | UK list, per user/month | Desktop apps | Intune and Entra ID P1 | Best fit in a property firm |
|---|---|---|---|---|
| Business Basic | £5.40 | Web and mobile only | No | Part-time weekend viewing staff |
| Apps for business | £9.80 | Yes | No | Rarely correct — no mailbox |
| Business Standard | £18.10 | Yes | No | Office staff on managed desktops only |
| Business Premium | £24.60 | Yes | Yes | Property managers, finance, directors |
| Microsoft 365 F3 | £6.30 to £7.20 | Web and mobile only | Partial | Maintenance operatives, caretakers |
| Microsoft 365 E3 | £33.50 | Yes | Yes | Only above the 300-user cap |
Matching Microsoft 365 for property management licences to roles
The honest allocation for a typical twenty-five person managing agent is Business Premium for anyone who touches client money, tenancy files or landlord data — which is most of the office — Business Basic for occasional weekend staff, and F3 for site-based maintenance. Resist the temptation to put the directors on Premium and everyone else on Standard: the person most likely to be phished in a property firm is the accounts assistant processing the payment run, not the managing director. Licensing Microsoft 365 for property management by role rather than by seniority is most of the discipline.
Tenant Foundations: Domains, Identity and the Right Setup Order
Order matters more than people expect when you build Microsoft 365 for property management. Almost every painful Microsoft 365 project in this sector went wrong because mailboxes were migrated before identity was designed, and everything afterwards had to be retrofitted around decisions nobody meant to make.
Get the domain and DNS right first
Add and verify your primary domain before creating a single user, and decide early what happens to the trading names you have acquired. Managing agents accumulate domains through acquisition, and each one needs a decision: accept mail as an alias on the main tenant, or leave it parked. Publish SPF, DKIM and DMARC on every domain that sends mail, and on every domain that does not — an unused acquired domain with no DMARC record is a free impersonation platform for anyone targeting your landlords.
Design the naming convention before the first user
Decide once whether people are firstname.lastname or initial.lastname, whether branches appear in the address, and what happens when someone changes name. Then decide the shape of your groups. This sounds trivial and it is the thing you cannot change quietly two years later when it is printed on nine hundred tenancy agreements.
Identity is the real foundation
Business Premium includes Entra ID Plan 1, which is what makes Conditional Access possible. Turn on multi-factor authentication for every account with no exceptions, then move quickly to phishing-resistant methods for finance. Microsoft completed its own enforcement of MFA on the Microsoft 365 admin centre on 9 February 2026, and the Cyber Essentials scheme moved to the Danzell question set effective 26 April 2026, under which missing MFA on cloud services is an automatic fail. If your firm certifies, this is no longer optional.
Identity is the foundation of Microsoft 365 for property management in a literal sense: every other control in this guide assumes you know who is signing in. Our Cyber Essentials guide for property management companies covers that route in full.
The setup order that works for Microsoft 365 for property management
Build in this sequence: domain and DNS, identity and MFA, groups and licensing, SharePoint structure, Teams on top of that structure, mailboxes and shared mailboxes, device enrolment, then data migration, then compliance labels, and only then the integrations with your property software. Doing compliance labels before the site structure exists is the single most common sequencing error, because labels have to be applied to containers that do not exist yet.
| Step | What you configure | Cost of doing it late |
|---|---|---|
| 1. Domains and DNS | Verification, SPF, DKIM, DMARC | Mail delivery failures during cutover |
| 2. Identity and MFA | Entra ID, Conditional Access, break-glass account | Retrofitting MFA onto live users |
| 3. Groups and licensing | Group-based licence assignment | Manual licence admin forever |
| 4. SharePoint structure | Hub, sites, libraries, metadata | A second migration to fix the first |
| 5. Teams and mailboxes | Teams on existing sites, shared mailboxes | Orphaned duplicate document stores |
| 6. Devices | Intune enrolment, app protection | Unmanaged phones holding tenant data |
| 7. Migration | Mail and file movement | Rework if structure is not ready |
| 8. Compliance labels | Retention and sensitivity labels | Relabelling live content at scale |
SharePoint Architecture for a Property Portfolio
This is where most property firms get the least help and lose the most value from Microsoft 365 for property management. The instinct is to recreate the old file server: a folder per property, nested inside a folder per landlord, nested inside a folder per branch. Do not do that.
Why a folder per property fails
A managing agent with 900 units creates 900 folders, and every one of them needs permissions that nobody maintains. Worse, a property changes landlord, a landlord changes agent, a block gains a new managing company — and the folder tree that encoded those relationships is now wrong in a way no search can correct. Property is the classic case where the relationship between records changes more often than the records themselves, so Microsoft 365 for property management should encode as little of that relationship as possible in a folder path.
Use a small number of sites and put the property in the metadata
The structure that holds up over time is a handful of purpose-built sites, each with document libraries whose columns carry the property reference, the landlord, the block, the document type and the expiry date. A gas safety certificate is not filed at a location; it is tagged with a property, a type and a date, and every view you need — expiring this month, missing entirely, by block — becomes a filtered view rather than a folder someone has to remember to open.
A site plan that works for most firms
Six to eight sites cover almost every managing agent: Lettings Operations, Block Management, Client Accounting, Compliance and Certificates, Property Records, Contractors and Procurement, Company and HR, and an intranet home. Each has a clear owner, a clear membership group and a clear retention rule. Connect them with a hub site so search and navigation work across the estate without merging permissions.
| Site | What lives there | Who has access | Retention approach |
|---|---|---|---|
| Lettings Operations | Tenancies, references, inventories | Lettings team | 6 years after tenancy ends |
| Block Management | Leases, Section 20, minutes | Block team | Life of lease plus 6 years |
| Client Accounting | Statements, reconciliations, CMP | Finance only | 6 years minimum, restricted |
| Compliance and Certificates | Gas, electrical, EPC, fire risk | All property staff, read-mostly | Superseded plus statutory period |
| Property Records | Right to Rent, ID, deposits | Named roles only | Tenancy plus 1 year, then delete |
| Contractors and Procurement | Works orders, insurance, quotes | Staff plus expiring guests | 6 years after works complete |
Storage is not the constraint people assume
Every tenant starts with 1 TB of pooled SharePoint storage plus 10 GB per licensed user, so a twenty-five person agency has roughly 1,274 GB before buying anything. A single site can hold up to 25 TB and a single file up to 250 GB. Additional storage runs at about $0.20 per GB per month. Photographs from inspections are what actually consume it, not documents, so agree an image retention rule early rather than buying storage later. Storage is rarely the reason a Microsoft 365 for property management project stalls.
Version history and the accidental archive
SharePoint keeps version history by default, and a firm that migrates fifteen years of files inherits every draft. Set version limits on migration rather than after, and be deliberate about what comes across at all. The cleanest builds of Microsoft 365 for property management move only live and recently closed matters, and leave the historic archive somewhere read-only.
Teams Structure for Branches, Blocks and Contractors
Teams is where good SharePoint architecture goes to die in Microsoft 365 for property management, because every new team silently creates another site. Build Teams onto the structure you designed, not alongside it.
One team per function, channels per branch
Create teams that match the sites above, and use channels for branches or portfolios inside them. A firm with four branches does not need four lettings teams; it needs one Lettings Operations team with four channels and consistent permissions. This keeps the document library single and searchable, which is the entire point.
Use shared channels for landlords and contractors
Shared channels let an external organisation participate in one channel without gaining access to the rest of the team. For a block management company working with a freeholder’s surveyor across a two-year major works project, that is exactly the right tool. It avoids both the guest-in-everything problem and the email-attachment sprawl that follows when people give up on access control. Shared channels are the most underused feature in Microsoft 365 for property management.
Meetings, evening working and recordings
Residents’ meetings recorded in Teams generate transcripts that contain personal data about named leaseholders. Decide whether you keep them, for how long, and who can see them, and apply that as a policy rather than leaving it to whoever pressed record. Retention on meeting recordings is one of the most commonly missed settings in Microsoft 365 for property management.
Exchange Online, Shared Mailboxes and the Maintenance Inbox
Email is where property firms lose the most time and take the most risk, and shared mailboxes are the tool in Microsoft 365 for property management that fixes both — provided you know their limits.
Shared mailboxes are free until they are not
A shared mailbox needs no licence of its own while it stays under 50 GB and has no online archive and no litigation hold. Cross any of those three thresholds and it needs a licence, typically Exchange Online Plan 2, which raises the ceiling to 100 GB. Users still need their own licence to access it. A busy maintenance inbox with photographs attached reaches 50 GB faster than anyone expects, so plan for the licence rather than discovering it when sending stops.
The mailboxes every managing agent should create
Every implementation of Microsoft 365 for property management should create shared mailboxes for maintenance, lettings enquiries, accounts, compliance and complaints. Route them to teams rather than individuals, so that annual leave and staff turnover stop being incidents. Given that 56% of surveyed agents named property manager recruitment as their biggest staffing problem, a mailbox that does not belong to a departing employee is an operational control, not just a tidy one.
Mailbox sizes and archiving
Business Basic and Standard provide a 100 GB primary mailbox with a 50 GB archive; Business Premium provides the same primary with a 1.5 TB archive. For a firm that keeps correspondence for six years after a tenancy ends, that archive difference is a genuine reason to choose Premium beyond the security tooling. It is one of the few places where Microsoft 365 for property management has a storage-driven licensing answer.
Protect the payment path specifically
Payment redirection is the fraud that costs property firms real money, and it arrives by email in a thread that already exists. Enforce a callback on any change of bank details using a number you already hold, and alert on inbox rule creation and external forwarding. Our guide to business email compromise in property management covers that attack in detail.
| Content type | Where it belongs | Where it must not go |
|---|---|---|
| Signed tenancy agreement | Lettings site, tagged to property | A negotiator’s personal mailbox |
| Repair request from tenant | Maintenance shared mailbox | A personal WhatsApp thread |
| Gas safety certificate | Compliance library with expiry date | Folder named “certs new final” |
| Right to Rent document copy | Property Records, restricted | Anywhere with open access |
| Contractor quote | Contractors site, shared channel | Emailed round as an attachment |
| Client account reconciliation | Client Accounting, finance only | The general company drive |
Devices and Intune Across a Site-Based Workforce
A property firm’s riskiest device is a personal phone with a work mailbox on it, standing in an empty flat. Business Premium includes Intune, and using it is the difference between a policy and a control. Device management is also the part of Microsoft 365 for property management that firms postpone longest.
Enrol company devices, protect personal ones
Company laptops and tablets should be fully enrolled so they can be wiped, encrypted and patched. Personal phones rarely need full enrolment; app protection policies are usually the right answer, containing work data inside the Microsoft apps, requiring a PIN, blocking copy-out to personal apps and allowing a selective wipe that removes company data without touching family photographs.
Patch on a clock, not on a whim
The Cyber Essentials Danzell question set requires critical and high-severity updates to be applied within 14 days, and treats failure as an automatic fail. Intune update rings make that measurable. Given that only 5% of UK businesses hold Cyber Essentials certification and 47% use any form of two-factor authentication, a firm that does both is genuinely ahead of its market. Patching on a clock is one of the cheapest wins available in Microsoft 365 for property management.
Lost devices and leavers
Property staff turnover is high, and inspection tablets get left in vans, so offboarding is the most frequently exercised process in Microsoft 365 for property management. Write the sequence down: disable sign-in, revoke sessions, convert the mailbox to shared, reassign the licence, wipe the device. Our guidance on device management covers the operational side of running that estate.
Compliance Settings Every Microsoft 365 for Property Management Tenant Needs
This is the section that separates a tidy Microsoft 365 for property management tenant from a defensible one. Nothing here costs extra on Business Premium; it costs attention.
Retention labels tied to real statutory periods
Right to Rent check copies must be retained for the duration of the tenancy and for at least one year afterwards, then deleted — keeping them forever is its own breach. Tenancy and financial records generally warrant six years. Build those as Purview retention labels applied to libraries, so disposal happens by design rather than by someone’s spring clean.
Sensitivity labels on the documents that matter
Label tenancy files, identity documents and client account records. A sensitivity label travels with the file when it leaves, which is the only control in Microsoft 365 for property management that still works after a document has been emailed to a landlord who forwards it onward.
Data protection duties that changed in 2026
The Data (Use and Access) Act 2025 brought its data protection provisions into force on 5 February 2026, and from 19 June 2026 section 164A of the Data Protection Act 2018 requires organisations to acknowledge a data protection complaint within 30 days. Personal data breaches still go to the ICO within 72 hours, with UK GDPR fines reaching £17.5 million or 4% of global turnover. The ICO has fined a lettings business £80,000 in this sector before, after the personal data of 18,610 tenants and landlords sat exposed for around two years. Our data protection page sets out the wider obligations.
Backup is not the same as retention
Retention labels stop deletion; they do not give you a point-in-time restore. Microsoft 365 Backup is available on a pay-as-you-go meter at roughly $0.15 per GB per month of protected content, with restores free and restore points every ten minutes. For a firm holding client money records, deciding this explicitly is part of building Microsoft 365 for property management properly rather than assuming the cloud handles it.
| Record type | Retention driver | Suggested label | Disposal action |
|---|---|---|---|
| Right to Rent copies | Immigration checks | Tenancy end plus 1 year | Automatic deletion |
| Tenancy agreements | Contract limitation period | Tenancy end plus 6 years | Review then delete |
| Client account records | Client money protection | 6 years minimum | Review, never auto-delete |
| Safety certificates | Statutory duty of care | Superseded plus statutory term | Retain superseded copy |
| Renters’ Rights information sheet | Evidence of service | Tenancy end plus 6 years | Review then delete |
| Meeting recordings | Minimisation | 12 months or less | Automatic deletion |
Integrating Microsoft 365 for Property Management With Reapit, Alto and Fixflo
Nobody runs a property business on one platform alone. Microsoft 365 for property management is the collaboration and compliance layer underneath a property CRM, and the integration points are where the day-to-day time is won or lost.
What the main UK platforms connect to
Reapit’s AgencyCloud offers Outlook integration for filing email against properties and logs Teams calls against records. Alto by Zoopla provides an Outlook add-in for linking email to a property and integrates with SharePoint for document storage. Fixflo, used across more than 1.6 million UK rental units, handles repairs and integrates with Alto through the Alto Marketplace. Arthur suits smaller portfolios. The integration question for Microsoft 365 for property management is always the same: which system is the master record for a document, and which one merely links to it?
Pick one master, always
Storing the tenancy agreement in both the CRM and SharePoint guarantees that within a year they will differ. Decide that the CRM holds the transactional record and SharePoint holds the document of record, or the reverse, and then make the other one link rather than copy. Ambiguity here is the root cause of most “which version is current” arguments in property offices, and the most common reason a Microsoft 365 for property management build gets judged a failure.
Automate the boring joins
Power Automate can move a signed document from an inbox into the right library with the right metadata, notify a channel when a certificate is within thirty days of expiry, and create a task when a compliance field is empty. These are small automations with large returns because they attack exactly the work that gets forgotten when a branch is short-staffed, and they are what makes Microsoft 365 for property management pay for itself.
Where Copilot fits
Copilot Chat is included with any Microsoft 365 subscription and carries enterprise data protection, but it cannot reach your Graph data without a licence. That distinction matters when someone asks whether Copilot can summarise a tenancy file. Our Copilot use cases for property management works through twelve practical workflows for UK firms.
Migrating to Microsoft 365 for Property Management Without Losing Data
Migration is the phase where firms panic and start copying folders manually at eleven at night. Moving to Microsoft 365 for property management does not need to be that.
Know what you are moving from
Most UK property firms are moving from one of four places: an ageing on-premises Exchange or file server, Google Workspace, a hosted IMAP mailbox from a small provider, or an existing but badly structured Microsoft 365 tenant acquired with a business. Each has a different tool and a different trap on the way into Microsoft 365 for property management.
The traps by source
On-premises servers hide permission structures nobody documented. Google Workspace migrations lose shared drive permissions and calendar delegation if you rush them. IMAP migrations bring mail but no calendars or contacts at all. Tenant-to-tenant moves after an acquisition are the hardest of the four and need genuine planning, because two sets of naming conventions, licences and retention policies must reconcile.
Move structure first, content second
Create the sites, libraries, columns and permission groups before a single file moves. Then move content into that structure, mapping old folders to new metadata as you go. Firms that migrate first and organise later almost always end up migrating twice, which is why our migration practice treats structure as the deliverable and file movement as a consequence.
| Moving from | Typical tool | The trap | Mitigation |
|---|---|---|---|
| On-premises Exchange | Hybrid or cutover migration | Undocumented delegate access | Audit permissions before cutover |
| File server | SharePoint Migration Tool | Deep paths and version bloat | Flatten to metadata, cap versions |
| Google Workspace | Migration service | Shared drive permissions lost | Rebuild groups first, then move |
| Hosted IMAP | IMAP migration | No calendars or contacts | Export separately, import manually |
| Acquired tenant | Tenant-to-tenant | Conflicting names and policies | Agree target conventions up front |
What Microsoft 365 for Property Management Actually Costs
Licences are the visible cost of Microsoft 365 for property management and usually the smaller one. Setting a realistic budget means counting the build alongside the subscription.
The licence bill for a twenty-five person agency
Putting all twenty-five staff on Business Premium costs 25 × £24.60 = £615 per month, or £7,380 a year. Putting eighteen on Premium and seven on Basic costs 18 × £24.60 = £442.80 plus 7 × £5.40 = £37.80, giving £480.60 per month. Putting everyone on Business Standard costs 25 × £18.10 = £452.50 per month — barely less than the mixed model, and without Intune, Conditional Access or Defender for Business anywhere in the business.
The build cost nobody budgets for
Design and migration is a project, and for a firm of this size it is normally measured in weeks rather than days. The work that actually takes time is agreeing the site structure with the people who use it, mapping the metadata to how the business really describes a property, and cleaning fifteen years of files enough to decide what moves. Budgeting for Microsoft 365 for property management means counting that work, not just the subscription, and the licence saving from a well-chosen mix typically funds a meaningful share of it within the first year.
Where the return comes from
The measurable returns in Microsoft 365 for property management are consistent: certificates that never expire unnoticed, tenancy files findable by someone who joined last week, a maintenance inbox that survives a resignation, and a compliance position you can evidence rather than assert. Our managed IT services page describes how that estate is run once it is built.
A 90-Day Rollout Plan for Microsoft 365 for Property Management
Ninety days is a realistic timetable for deploying Microsoft 365 for property management in a firm of five to fifty staff that already holds licences. The plan below assumes you are improving an existing tenant as much as building a new one.
Days 1 to 30: foundations and quick wins
Audit what you own and who has it. Verify domains, publish DMARC, enable MFA everywhere and create a break-glass account. Design the site structure on paper with the people who will use it, agree the metadata columns, and fix licence allocation against real roles. Nothing moves yet.
Days 31 to 60: build and pilot the Microsoft 365 for property management structure
Create the sites, libraries, columns and groups. Build the Teams on top of them. Create the shared mailboxes. Enrol company devices in Intune and publish app protection policies for personal phones. Pilot with one branch or one team, move their content, and let them work in it for two weeks before you touch anyone else.
Days 61 to 90: migrate, label and integrate
Migrate the remaining content into the structure. Apply retention and sensitivity labels. Connect the property CRM, build the first two or three Power Automate flows, and run the certificate expiry view for real. Finish with training that shows people the new views rather than the new buttons, because that is what turns Microsoft 365 for property management from a migration into a change of habit.
What to measure at the end
Set a small number of measures before you start: percentage of certificates with a valid expiry date recorded, number of documents held outside the agreed structure, average time to find a named tenancy file, and the proportion of accounts on phishing-resistant multi-factor authentication. A rollout of Microsoft 365 for property management that cannot show movement on those four has not finished.
| Phase | Main activity | Owner | Exit test |
|---|---|---|---|
| Days 1 to 30 | Audit, identity, structure design | Director plus IT partner | MFA at 100%, structure signed off |
| Days 31 to 60 | Build sites, Teams, mailboxes, Intune | IT partner plus pilot team | One branch working live for 2 weeks |
| Days 61 to 90 | Migrate, label, integrate, train | Whole business | No active work on the old drive |
| Ongoing | Review labels, licences, guests | Named owner, quarterly | Quarterly review actually happens |
Seven Mistakes That Undermine Microsoft 365 for Property Management
These are the failures that show up repeatedly when property firms build Microsoft 365 for property management, in rough order of how much they cost.
One: recreating the file server
Lifting a folder tree into SharePoint gives you the old problems in a new place, plus a migration bill. Metadata is the point.
Two: a team for every property
Every team creates a site. A firm that creates one per block ends up with hundreds of unmanaged sites and a search experience that surfaces nothing useful.
Three: giving contractors guest accounts to everything
Guests should land in a shared channel or a single library with an expiry date. Blanket guest access is the access-control equivalent of leaving a key under the mat.
Four: shared logins for the maintenance inbox
A shared password destroys attribution, breaks multi-factor authentication and fails Cyber Essentials. Shared mailboxes with delegated access solve the same problem correctly and cost nothing.
Five: buying one licence type for everyone
Either you pay full rate for weekend staff who barely use the tools, or you leave your property managers without device management. Microsoft 365 for property management is a mixed-licence platform by design, and the mixed model exists for a reason.
Six: treating retention as an archive policy
Keeping everything forever is not caution; for Right to Rent copies it is a compliance failure in its own right. Disposal is part of the design of Microsoft 365 for property management, not an optional extra.
Seven: skipping the structure workshop
The half-day spent agreeing how the business describes a property is the highest-return half-day in the project. Skipping it is why implementations of Microsoft 365 for property management get rebuilt eighteen months later.
Frequently Asked Questions About Microsoft 365 for Property Management
Do we need Business Premium, or is Standard enough?
If anyone in the firm handles client money, tenant identity documents or landlord data on a mobile device, Premium is the correct answer, because Intune, Conditional Access and Defender for Business are only in Premium. Standard is a productivity plan, not a management plan, so Business Premium is the default answer for Microsoft 365 for property management.
Can we mix licence types in one tenant?
Yes, and you should. Assign licences by group so that role changes update entitlements automatically. Mixing Business Premium, Business Basic and F3 in a single tenant is standard practice and is how most well-run implementations of Microsoft 365 for property management are licensed.
What happens when we pass 300 users?
The Business plans stop being available for new assignments and you move affected users to Microsoft 365 E3 or E5, which have no cap. Firms approaching 250 staff should plan that transition rather than meet it during a hiring round; the rest of the Microsoft 365 for property management design is unaffected by it.
Should the tenancy agreement live in the CRM or SharePoint?
Pick one as the document of record and make the other link to it. Both is the wrong answer, because within a year the two copies will disagree and nobody will know which one the tenant signed.
Does Microsoft 365 back up our data?
Not in the sense most people mean. Retention policies prevent deletion; they are not point-in-time restore. Microsoft 365 Backup is a separate pay-as-you-go service at roughly $0.15 per GB per month, and the decision to use it or a third-party product should be explicit.
How long does a full implementation take?
For five to fifty staff, ninety days is realistic when licences already exist and someone senior owns the structure decisions. A Microsoft 365 for property management build rarely fails on timeline; it fails on decisions, because the variable is never the technology but how quickly the business can agree how it describes a property.
Is Copilot worth adding on top?
Copilot Chat comes with the subscription but cannot read your files without a licence. Whether the licensed version pays back depends on how much document-heavy work your team does, which is the question our cost and ROI analysis works through in detail.
References
Compare All Microsoft 365 Business Plans and Pricing
Microsoft 365 Enterprise Plans and Pricing
Microsoft 365 Business Premium Documentation
About Shared Mailboxes in Microsoft 365
Manage Site Storage Limits in SharePoint
Information Architecture in the Modern SharePoint Experience
Shared Channels in Microsoft Teams
Learn About Retention Policies and Retention Labels
Pricing Model for Microsoft 365 Backup
Introducing the SharePoint Migration Tool
Data (Use and Access) Act 2025
Landlords: Immigration Right to Rent Checks
Propertymark Housing Insight Report, May 2026
