Building a SharePoint Intranet Your Staff Will Actually Use

A SharePoint intranet is a set of SharePoint Online sites — built on the licence you already pay for in Microsoft 365 — that gives staff one place for news, policies, documents and people. Build it around how people actually work and they use it daily. Build it as a digital filing cabinet and it dies.

Most Melbourne businesses already own SharePoint and don’t realise it. If you have Microsoft 365 Business Standard or Business Premium, the intranet platform is sitting there, unused, while staff email each other PDFs and hunt through a network drive nobody has tidied since 2019. The technology is rarely the problem. The decisions you make before you build it are.

What a modern SharePoint Online intranet actually is

Forget the old picture of a clunky 2010-era SharePoint server. The modern version runs entirely in the cloud, looks like a clean website, works on a phone, and is made of three building blocks: communication sites, team sites and hub sites. You assemble those into an intranet rather than installing a single “intranet product”.

The point of the thing is to answer the questions staff ask all day: where’s the current leave policy, who do I call in accounts, what’s the new client onboarding process, has anything changed this week. When those answers live in one searchable place that people trust, you stop losing hours to “do you know where the…” messages.

Communication sites versus team sites

This is the first decision that trips people up, so get it straight early. The two site types do different jobs.

In plain terms: your intranet’s front door and its polished, company-wide pages are communication sites. The messy day-to-day work — drafts, working documents, a project’s files — happens in team sites, which are the same thing that gets created every time someone makes a new team in Microsoft Teams. Most organisations need a handful of communication sites and a growing number of team sites.

Hub sites tie it together

On their own, a dozen separate sites are just a dozen separate sites. A hub site is what makes them feel like one intranet. You designate a site as a hub, then associate other sites with it, and they inherit shared navigation, a consistent look, and rolled-up news and search across everything connected.

A practical structure for a mid-sized business: one hub as the company intranet home, with the HR, IT, Operations and Sales sites associated to it. Staff get one top navigation bar across the lot, news from any connected site surfaces on the home page, and search spans the whole hub. You can re-associate sites later, so the structure isn’t a one-way door — but planning it up front saves a painful reorganisation six months in.

The pieces staff care about

An intranet earns its keep through a few core features. None of them are exotic; the difference is whether they’re set up deliberately or thrown together.

• News — SharePoint News posts are how you communicate. A short post about a policy change or a new starter beats an all-staff email nobody reads, and it stays findable afterwards.
• Document libraries — where files live, with version history, check-out, and metadata so you can filter and sort rather than scroll. This is what replaces the network drive.
• Policies — a single authoritative home for the employee handbook, the leave policy, the WHS documents. One current version, not eleven copies in eleven inboxes.
• Staff directory — pulled from your Microsoft 365 user accounts, so people can find who does what and how to reach them.

Integration with Teams and Viva Connections

This is where SharePoint stops being a website you have to remember to visit. Every Microsoft Teams team is already backed by a SharePoint team site — the Files tab in any channel is a SharePoint document library. So your collaboration sites are reachable without leaving Teams, where most staff already spend their day.

Viva Connections takes it further: it surfaces your intranet home page, news and resources directly inside Teams as an app, on desktop and mobile. For frontline and on-the-go staff who never open a browser, that’s often the difference between an intranet they see and one they forget exists. If you’re already invested in the Microsoft stack, our Microsoft 365 support covers wiring these pieces together so the intranet meets staff where they work rather than asking them to come to it. For a fuller picture of what the platform includes, our rundown of what Microsoft 365 support covers is a useful companion read.

The decisions that make or break adoption

Information architecture is the unglamorous part everyone skips, and it’s the part that decides whether the intranet works. Information architecture means how you structure and name things so people find them without thinking.

The mistakes are predictable. Folder structures fifteen levels deep that mirror the old network drive. Navigation built around your org chart instead of around tasks — staff don’t think “I need the People & Culture division’s content”, they think “where’s the leave form”. Twenty different document libraries with no naming convention. Search left to fend for itself with no metadata to work with.

Get the architecture right and the platform does the rest. The questions worth arguing about before you build anything are: what are the ten things staff look for most, what should the top navigation be, what’s a hub and what’s associated to it, and how do you name and tag documents consistently. An hour of disagreement in a planning meeting saves a rebuild later.

Permissions and governance

The fastest way to ruin a SharePoint intranet is to let permissions sprawl. Out of the box it’s easy to share a file or site with one person, then another, until nobody can tell who can see what — and a staff directory or HR site with leaky permissions is a privacy problem, not just a tidiness one.

The disciplined approach is to manage access through Microsoft 365 Groups and security groups rather than one-off shares, keep company-wide content readable by everyone and editable by few, and set a clear policy on who can create new sites. Left unchecked, “anyone can spin up a team” produces hundreds of orphaned sites within a year. Governance also means deciding retention, external sharing rules, and a content owner for each site so pages don’t go stale. Conditional access policies sit underneath all of this, controlling who can reach the intranet, from which devices, and under what conditions — important when the same platform holds your policies and your client files. This kind of structure is part of broader cybersecurity hygiene, not an optional extra.

Migrating off file servers and network drives

Most intranet projects are also a migration off an ageing file server or a mapped network drive, and that’s where the real effort lives. You don’t just copy files across — you decide what comes, what gets archived, and how it’s structured on the other side.

A law firm in Hawthorn we work with had a 600GB shared drive built up over a decade, with matter folders, duplicates, and files three people swore were the master copy. The temptation is to lift-and-shift the whole thing into SharePoint and call it done. That just moves the mess to a new address. We sorted what was still live, archived closed matters, agreed a folder and metadata structure that matched how the firm actually worked, then migrated in stages so nobody lost access mid-week. The migration tooling matters — SharePoint has document size and path-length limits the old drive didn’t — and so does timing it around the firm’s quieter periods.

If your file server is also your backup and disaster-recovery weak point, moving to SharePoint changes that equation too — though “it’s in the cloud” still isn’t a backup strategy, which is why our backup and recovery approach covers Microsoft 365 data as well.

Why “build it and they won’t come” happens

The most common SharePoint outcome in Australian SMEs is an intranet that was built with enthusiasm, launched with an email, and abandoned within two months. It happens for clear reasons: nobody owned the content so it went stale, the structure mirrored the org chart instead of staff tasks, the launch was a one-off announcement with no follow-through, and leadership didn’t use it themselves.

Driving adoption is mostly non-technical. Put the things people need daily — the leave form, the phone list, this week’s news — on the front page so there’s a reason to visit. Move a real workflow onto it, like leave requests or IT support requests, so people have to use it. Surface it in Teams via Viva Connections so they don’t have to remember a URL. Name content owners who keep their corner current. And get the leadership team posting news, because staff follow what management actually uses. An intranet that’s the easiest path to the answer wins; one that’s a chore loses.

Realistic effort

Setting up a basic intranet — a home site, a few hub-connected sites, news and document libraries — is days, not months, for someone who knows the platform. The work that takes time is the thinking: the information architecture, the permissions model, the migration off the old drive, and the change management to get people using it. A sensible mid-sized rollout runs over several weeks, with a planning phase, a build, a staged migration, and a launch backed by training rather than an email. Trying to compress all of that into a weekend is exactly how you end up with the abandoned version.

Frequently asked questions

Do we need extra licences to build a SharePoint intranet?

Usually no. SharePoint Online is included in Microsoft 365 Business Standard, Business Premium and most enterprise plans, and Viva Connections is included as well. If you already run Microsoft 365 for email and Teams, you almost certainly have everything you need to build the intranet on your existing licences.

What’s the difference between SharePoint and Teams?

They’re two views of the same data. Teams is where you chat and meet; SharePoint stores the files and pages behind it. Every Teams team has a SharePoint site underneath, and the Files tab in a channel is a SharePoint document library. An intranet adds the company-wide communication sites and hubs on top.

How do we stop the intranet becoming a mess of duplicate files?

Agree a structure and naming convention before you migrate, use metadata and search rather than deep folders, manage permissions through groups, and control who can create new sites. The discipline is in governance and information architecture, not in the platform itself.

Can staff access the intranet on their phones?

Yes. SharePoint sites are mobile-responsive, and Viva Connections puts your intranet home page, news and resources inside the Teams mobile app — which is how frontline and on-the-go staff actually reach it, since most never open a browser at work.

Getting it built properly

A SharePoint intranet is one of the best-value things you can do with Microsoft 365, because the licence is already paid for and the payoff — less time hunting for documents, one source of truth for policies, cleaner communication — compounds. The risk is doing it without the architecture, permissions and adoption work, and ending up with abandoned space. TechAssist is a Melbourne-based MSP, founded in 2014, with 13 Australian-employed engineers — no offshore helpdesk — and per-user fixed pricing, so a project like this is scoped properly rather than billed by the hour. If you’d like to turn the SharePoint you already own into something staff actually use, explore our cloud services or get in touch for a straight conversation about it.

Power BI is Microsoft’s business intelligence tool — it pulls data out of the systems you already run, like Xero or Excel, and turns it into live dashboards. A small business can build genuinely useful reporting with it without hiring a data analyst, provided you start narrow and keep one set of numbers honest.

Most Melbourne SMEs we work with are drowning in spreadsheets. Sales lives in one workbook, the job costing in another, the helpdesk numbers in a portal nobody logs into, and the cashflow forecast in a file the bookkeeper updates monthly. Power BI’s pitch is simple: connect those sources once, and the dashboard refreshes itself. The trap is treating it as a magic spreadsheet. It is not. Used badly it just creates prettier confusion. Used well it gives a director a single screen that answers “how are we actually going?” before the morning coffee.

What Power BI actually is

Power BI is three things wearing one name. Power BI Desktop is a free Windows application where you build reports — connect data, shape it, write the odd calculation, design the visuals. The Power BI Service is the cloud side (app.powerbi.com) where you publish those reports, share them, and let them refresh on a schedule. Power BI Mobile is the phone app for viewing dashboards on the road.

If your business runs Microsoft 365 — and most Melbourne SMEs do — Power BI sits in the same tenant, uses the same logins, and respects the same security. That integration is the main reason it wins over standalone tools for a small business already inside the Microsoft ecosystem. We cover the broader 365 picture in our Microsoft 365 service.

Licensing: Desktop, Pro and Premium Per User

This is where people get confused and overspend, so be clear about it. Building reports is free. Sharing them with other people is what costs money. Pricing below is per user per month and subject to change by Microsoft — treat it as the shape of the decision, not a quote.

For a typical small business the answer is nearly always Pro. Everyone who needs to view a shared dashboard needs a Pro licence (or PPU), not just the person who built it — that is the line item people forget. Premium Per User only earns its keep once your data models get large or you need refreshes every few minutes. There is also a capacity-based tier (Fabric/Premium capacity) priced for larger organisations; if you are a 25-person firm in Hawthorn, you do not need it.

Connecting your data

Power BI ships with hundreds of connectors. The ones that matter for an Australian SME:

• Xero and MYOB — both connect, though the path differs. Xero has a native connector and also publishes its own pre-built Power BI reports; MYOB is typically reached through its API or a third-party connector. For deep accounting analysis, many firms export to a database or use a connector tool rather than hitting the accounting platform directly every refresh.
• Excel and CSV — the workhorse. Point Power BI at a workbook in SharePoint or OneDrive and it refreshes when the file changes. This alone replaces a lot of manual copy-paste.
• SQL Server and other databases — if you run a line-of-business app (job management, ERP, a practice system) on SQL, Power BI reads it directly. This is where the richest reporting comes from.
• Dataverse — the data layer behind Microsoft Dynamics and Power Apps. If you have built anything on the Power Platform, Power BI reads it natively.
• Web and SaaS APIs — helpdesk tools, CRMs and marketing platforms often expose data Power BI can pull.

One practical note: cloud sources (Xero, SharePoint, SaaS) refresh straight from the Service. On-premises sources like a local SQL server need the on-premises data gateway installed — a small piece of software that lets the cloud Service reach back into your network to refresh. It is a five-minute install but easy to forget, and it is usually the reason a dashboard “stopped updating”.

Building your first dashboard

The mistake is starting with the whole business. Start with one question someone actually asks every week. The build then goes:

1. Connect the source in Power BI Desktop using Get Data.
2. Clean and shape it in Power Query — rename columns, fix date formats, filter out junk. This step is 70% of real BI work and the part people skip.
3. Model the data — link tables together so, for example, every invoice knows which customer and which month it belongs to.
4. Visualise — drop in a few cards for the headline numbers, a line chart for the trend, a table for the detail. Resist the urge to add forty visuals.
5. Publish to a workspace in the Service and set a refresh schedule.

A clean dashboard answering one question beats a cluttered one trying to answer ten. You can always add a second page.

Sharing, workspaces and row-level security

You do not email a Power BI file around — that defeats the point. You publish a report into a workspace (a shared container in the Service), and people with the right licence and permission view it live. Workspaces are how you separate, say, the finance dashboards from the operations ones, and control who sees which.

For anything sensitive, learn row-level security (RLS) early. RLS filters the data by who is looking. The classic case: a sales manager in South Yarra should see only their own team’s pipeline, not the whole company’s, even though everyone opens the same report. You define roles in Power BI Desktop, assign people to them in the Service, and the data filters itself per viewer. Without RLS, “sharing the dashboard” means sharing everything in it — which is how payroll numbers end up in front of the wrong person.

Dashboards that earn their keep in an SME

The reporting that genuinely pays for itself in a small business is unglamorous:

• Cashflow — a live view of receivables ageing, upcoming payables and bank position, pulled from Xero or MYOB. This is the one most directors check daily once it exists.
• Sales pipeline — deals by stage, expected value, conversion rates, from your CRM. Replaces the weekly “where are we at” spreadsheet.
• Job profitability — quoted versus actual cost per job, margin by job type or client, from your job management or accounting system. For construction, trades and professional services this is the dashboard that changes behaviour.
• Helpdesk and operations metrics — ticket volumes, response times, recurring issues. We use Power BI on our own helpdesk data for exactly this.

None of these require a data team. They require someone who knows the business, a few hours in Power Query, and the discipline to keep the inputs clean.

One source of truth and the governance that protects it

This is the part that separates BI that helps from BI that causes arguments. The whole value of a dashboard is that everyone trusts the number. The moment two reports disagree on last month’s revenue, people stop trusting both and go back to their own spreadsheets.

One source of truth means the definitions live in one place — what counts as revenue, when a job is “complete”, how margin is calculated — and every dashboard inherits them. In practice that means a curated dataset (a shared, governed data model) that reports draw from, rather than ten people each connecting to Xero and each calculating “profit” their own way. It also means controlling who can publish, keeping a sensible folder structure of workspaces, and not letting a sprawl of half-finished reports accumulate. For a regulated firm — a financial planner under ASIC, a clinic under AHPRA — that governance discipline is also part of keeping client data handled properly. This is the kind of thing we help with under our virtual CIO services, where the question is less “which chart” and more “what should the business be measuring at all”.

When a spreadsheet is still fine

Plenty of times. If a number lives in one place, one or two people use it, and a fortnightly manual update is no burden, Excel is the right tool and Power BI is overkill. The honest test is whether you have a data assembly problem — the same figures stitched together from several systems, by hand, again and again, with someone always asking “is this current?”. That repetitive consolidation is exactly what Power BI removes. A one-off analysis is a spreadsheet job. A report you rebuild every Monday for the rest of your working life is a Power BI job.

A Melbourne example

A commercial fit-out company in Box Hill we work with — around 30 staff — was running its whole management view off three spreadsheets that the office manager rebuilt every Monday morning from Xero exports and the job management system. It took her half a day, and by Wednesday the numbers were stale. Worse, the director’s “job profitability” sheet and the accountant’s margin figures never quite matched, so every management meeting started with an argument about whose numbers were right.

We connected Power BI to Xero and their job system, built one governed model with agreed definitions of cost and margin, and produced three pages: cashflow, job profitability and a simple pipeline view. It refreshes overnight. The Monday rebuild is gone, the two sets of numbers now agree because they come from one model, and the director checks the dashboard on his phone from site. Nothing exotic — just the same data, assembled once and trusted.

Frequently asked questions

Do I need to be a developer to use Power BI?

No. Building a useful dashboard from Xero or Excel is closer to advanced spreadsheet work than programming. The harder calculations use a formula language called DAX, but a competent finance person picks up the basics, and you only need DAX once you go beyond simple sums and trends. Most SMEs get a long way without writing any.

Is the free version enough for a small business?

Power BI Desktop is free and fine if one person builds and views reports alone. The moment you want to share a live dashboard with colleagues, each person needs a Pro licence. For most SMEs the real cost is a handful of Pro seats, not the build.

Can Power BI connect to Xero and MYOB at the same time?

Yes. A single Power BI model can combine multiple sources — Xero, a SQL database, an Excel file and a SaaS API in one report. Combining sources into one trusted view is exactly the problem it is built to solve, though messy accounting data still needs cleaning in Power Query first.

How do we stop dashboards showing the wrong people sensitive numbers?

Use workspaces to separate reporting by audience, and row-level security to filter data by viewer within a report. Combined, they let a manager see only their team’s figures while everyone opens the same dashboard. Get this set up before you share anything financial.

Getting reporting that people actually trust

Power BI is one of the better value tools a small business can adopt, but only if it is set up with clean sources, sensible licensing and the governance to keep one set of numbers honest. Done wrong it is just another spreadsheet nobody believes. TechAssist is a Melbourne-based MSP, founded in 2014, with 13 Australian-employed engineers — not an offshore call centre — and we run Power BI across our own helpdesk and on client data every week. If your management reporting is a Monday-morning spreadsheet rebuild, get in touch and we will help you turn it into something that refreshes itself.

Power Automate is Microsoft’s workflow automation tool, bundled into most Microsoft 365 plans, that lets you build flows to handle repetitive admin — routing emails, saving attachments, chasing approvals — without writing code. For Melbourne SMEs already paying for Microsoft 365, much of it costs nothing extra. The catch is knowing where the free use rights stop.

Every business runs on small, dull tasks done by hand: copying form responses into a spreadsheet, filing invoices, pinging the team when a particular email lands. Power Automate takes that work off your staff. This post covers what it does, the licensing reality nobody warns you about, cloud flows versus desktop automation, the governance traps that bite when staff leave, and when you are better off hiring a developer instead.

What Power Automate actually is

Power Automate is part of the Microsoft Power Platform, alongside Power Apps and Power BI. At its core it is a trigger-and-action engine: something happens (a trigger), and it carries out a sequence of steps (actions) in response. “When an email arrives from a client with an attachment, save it to SharePoint and post a message in Teams” is a complete, useful flow — built by clicking through a designer, not by writing code.

It connects to hundreds of services through connectors. Outlook, Teams, SharePoint, OneDrive, Excel, Forms and Planner are the Microsoft ones most SMEs use, but there are connectors for Dropbox, Salesforce, SQL databases and more. The connector lets a flow read and write data in each service on your behalf.

The licensing reality

This is where most advice online falls apart, because it either pretends everything is free or scares you off entirely. The truth sits in between.

Most Microsoft 365 business and enterprise plans include seeded Power Automate use rights. That means you can build and run cloud flows using standard connectors — the Microsoft services you already pay for: Outlook, Teams, SharePoint, OneDrive, Excel, Forms, Planner. For a large share of genuinely useful SME automations, that included entitlement is all you need, at no extra cost.

You start paying extra the moment you cross one of three lines:

• Premium connectors. Connecting to a SQL database, Salesforce, an HTTP API or many third-party systems requires a premium licence. The designer marks these “Premium”, so you find out before you build.
• Per-flow plans. Licence a single business-critical flow that many people rely on, rather than every user. Sensible when one flow serves a whole department.
• Per-user plans. Licence specific staff who build and run many premium flows. Sensible for a power user or a small automation team.

The practical rule: scope early automations to standard Microsoft connectors and you will likely stay inside what you already pay for. Microsoft reshuffles plan names and inclusions regularly, so confirm the current entitlements against your specific subscription before assuming a flow is free. Our Microsoft 365 team checks this before building anything that might trip a licence.

Cloud flows versus desktop flows (RPA)

Power Automate comes in two flavours, and confusing them leads to building the wrong thing.

Cloud flows are what most SMEs should reach for first; they are reliable because they talk to applications through proper interfaces. Desktop flows — Microsoft’s robotic process automation, or RPA — automate the screen itself, mimicking a human clicking through a Windows program. They are useful for old line-of-business software that has no API, but they are brittle: change a button’s position or a field’s name and the flow breaks. Treat RPA as a last resort for systems you cannot reach any other way, not a default.

Common SME automations worth building

These flows deliver real time savings without exotic licensing, and none need a developer to maintain once set up properly.

• Email-to-Teams alerts. When an email lands in a shared mailbox from a key client, or with a matching subject, post a card in the relevant Teams channel. Stops important messages drowning in an inbox.
• Approval workflows. Leave requests, purchase orders, expense sign-offs. The requester fills a form, the approver gets a Teams or email prompt with Approve and Reject buttons, and the outcome is logged. No more chasing managers for a yes.
• Save attachments to SharePoint. When invoices or signed documents arrive by email, file the attachment in the correct SharePoint library automatically and consistently named. Ends the “where did that PDF go” hunt.
• Form-to-spreadsheet. A Microsoft Forms submission drops straight into an Excel table or SharePoint list — bookings, incident reports, supplier details — with no manual re-keying.
• New-client onboarding. One trigger kicks off a sequence: create the SharePoint folders, generate a Planner task list, send the welcome email, notify the account manager in Teams. A checklist people forgot half of becomes one reliable flow.

A construction firm in Box Hill we work with was losing supplier invoices that arrived in a shared mailbox and got buried. We built a cloud flow that saved every invoice attachment to a dated SharePoint library and posted a notification to their accounts channel. It used only standard connectors, so it ran inside their existing licensing, and it removed a recurring source of disputes with subbies over unpaid invoices. That is the shape of a good first automation: narrow, boring, previously done by hand.

The governance and security angle

This is the part MSPs care about and most “just build a flow” tutorials ignore. A flow runs with someone’s permissions, often unattended, sometimes touching sensitive data. Left ungoverned, it becomes a liability.

Flow ownership when staff leave

Here is the scenario that catches businesses out. A capable staffer builds a dozen flows under their own account, then resigns. You disable their account during offboarding, and every flow they owned silently stops — invoices stop being filed, approvals stop routing, and nobody knows why. Critical flows should be owned by a shared service account or have co-owners, never tied to one person’s personal login. Offboarding should include checking what a leaver automated.

Data loss prevention policies

Power Automate moves data between services, which means it can also move data out of places it should stay. Microsoft’s data loss prevention (DLP) policies in the Power Platform admin centre classify connectors as business or non-business and block flows from combining the two — stopping, say, a flow that quietly copies SharePoint data to a personal Dropbox. Setting sensible DLP policies before staff start building is far easier than unwinding a mess later. Under the Privacy Act 1988 and the Australian Privacy Principles, you remain accountable for personal information your automations handle, so this is a compliance control, not just IT hygiene.

Service accounts and sprawl

Without guardrails, every department builds undocumented flows, and within a year nobody can tell you what automation is running across the business or what it touches. Govern it like any other production system: shared ownership for anything important, a naming convention, an inventory, and DLP policies set centrally. This is the same discipline behind our cybersecurity services work — who can build what, and where the data can flow.

When to use Power Automate versus hiring a developer

Power Automate is brilliant for connecting Microsoft 365 services and orchestrating standard business processes. It is not a replacement for proper software development, and pushing it past its comfort zone produces flows that are slow, hard to debug and impossible to hand over.

The honest limits: flows can be slow on large data sets, error handling is clunky compared to real code, and a flow with fifty steps and nested conditions is a maintenance nightmare that one staff departure can orphan. If you are fighting the tool to force complex logic into it, that is the signal to step back. A well-scoped flow that saves an hour a day is a win; a sprawling flow only its author understands is a future incident. Where that line sits for your business is exactly what our virtual CIO conversations are built to answer.

Frequently asked questions

Is Power Automate free with Microsoft 365?

Largely, yes — most business and enterprise Microsoft 365 plans include seeded use rights to build and run cloud flows using standard Microsoft connectors such as Outlook, Teams, SharePoint and Forms. You pay extra only for premium connectors, or per-flow or per-user plans. Confirm current entitlements against your subscription, as Microsoft adjusts inclusions regularly.

What is the difference between a cloud flow and a desktop flow?

Cloud flows run on Microsoft’s infrastructure and talk to apps through connectors and APIs — reliable, and the right default. Desktop flows are robotic process automation (RPA): they run on a Windows machine and mimic a human clicking through software, which suits legacy systems with no API but is fragile and breaks when screens change.

Do I need a developer to build flows?

For standard automations — approvals, alerts, filing attachments, form-to-spreadsheet — no. A capable staff member or your MSP can build them in the designer. You need a developer when the logic gets genuinely complex, performance on large volumes matters, or you are integrating a system with no connector.

What happens to flows when a staff member leaves?

If a flow is owned by an individual’s account and you disable that account during offboarding, the flow stops. Business-critical flows should be owned by a shared service account or have co-owners so they survive staff changes. Reviewing what a leaver automated should be a standard offboarding step.

Where TechAssist fits

We are a Melbourne MSP, founded in 2014, with thirteen Australian-employed engineers — not an offshore queue. We help SMEs identify which manual tasks are worth automating, build the flows inside your existing licensing where possible, and set the DLP policies and ownership rules so automation does not become a security hole or a single point of failure when someone resigns. If you are paying staff to do work a flow could handle, or you have a tangle of flows nobody owns properly, get in touch and we will map the quick wins before you spend a dollar on premium licences you may not need.

Microsoft Planner is the shared task tool for small teams: visual boards, buckets and assignments that live inside Teams. Microsoft To Do is for your personal list. Project is for proper project management with dependencies and Gantt charts. Most small teams need the first two and rarely the third.

If your team has outgrown email-and-spreadsheets but isn’t running multi-month projects with critical paths, Microsoft Planner and To Do are almost certainly already in your Microsoft 365 licence — you just aren’t using them properly. Here’s what each tool is for, how the 2024-2025 unification changed things, and how to roll it out without creating a sprawling mess.

Planner vs To Do vs Project: what each is actually for

These three tools overlap enough to confuse people, but they solve different problems. The simplest framing is scope: To Do is one person, Planner is one team, Project is one complex programme of work.

The practical test: if a job has a deadline and an owner but no real dependency chain, it belongs in Planner. If you genuinely need “task B can’t start until task A finishes, and that shifts the whole timeline”, that’s where Project earns its licence. Most Melbourne SMEs we work with never cross that line.

The 2024-2025 unification: one Planner app in Teams

Microsoft spent 2024 and into 2025 folding three separate experiences into one. The old “Tasks by Planner and To Do” app in Teams, the classic Planner web app, and the Project web experience have been consolidated into a single product called Planner, surfaced inside Microsoft Teams and on the web.

In practice, the new Planner app brings your personal To Do tasks, your shared team plans, and — if you hold a Project licence — your Project for the web plans into one place, so you stop hopping between apps. The basic features (buckets, boards, assignments, due dates) stay free with your normal Microsoft 365 licence; the Premium layer — goals, sprints, dependencies, timeline and Copilot — only lights up with a Project/Planner Plan licence. To Do still exists standalone, but its tasks now also appear in the My Tasks view inside the new Planner.

How Planner is structured: boards, buckets, assignments and charts

Planner uses a Kanban-style board, which is why teams pick it up quickly. The building blocks are worth understanding first, because the structure you choose on day one is the one you live with.

Plans and buckets

A plan is the container for a piece of shared work — usually tied to a team or a recurring function. Inside a plan, buckets are columns you define however you like: by stage (To Do / Doing / Done), by client, by team member, or by work type. A logistics operator might bucket by “Awaiting pickup”, “In transit” and “Delivered”. Pick one logic per plan and keep to it.

Tasks, assignments and labels

Each card is a task with an assignee (or several), a due date, a priority, a checklist of sub-steps, attachments, and coloured labels for filtering. The discipline that separates a useful board from an abandoned one is simple: every task has an owner and a due date. Unassigned, undated cards are where boards go to die.

Board, Grid, Schedule and Charts views

The same tasks can be viewed several ways without re-entering anything. Board is the Kanban columns; Grid is a spreadsheet-style list for fast editing; Schedule drops tasks onto a calendar by due date. Charts gives a status dashboard — how many tasks are not started, in progress, late or complete, split across people and buckets. For a team lead it answers “are we on top of this?” in three seconds, and it’s the most underused feature here.

Using Planner inside Teams channels

Planner is at its best when it lives where the work conversation already happens. Add a Planner tab to any Teams channel and the team discusses the work in the Posts tab and tracks it on the Planner tab beside it — no separate tool and no “where did we agree that was due?”.

Create the plan from inside the channel so it’s owned by that team’s Microsoft 365 Group — membership and permissions then follow the team automatically, so people who join get the board and people who leave lose it. Use one plan per channel rather than one giant plan for everything. Assignments notify people in their Teams activity feed and roll up into their My Tasks view, so nobody has to remember to “check the board”.

This is also why Planner suits teams already standardised on Microsoft 365. Our Microsoft 365 services page covers what’s included, and our post on what Microsoft 365 support in Melbourne actually covers goes deeper.

To Do, flagged emails and how tasks roll up

To Do is the personal counterpart — where an individual manages their own day with a “My Day” list, custom lists, reminders and recurring tasks. Two integrations make it more than a notepad. First, flagged emails: flag an email in Outlook and it appears automatically as a task in To Do’s “Flagged email” list, linked back to the message, turning the inbox-as-task-list habit into something you can plan around. Second, assigned tasks roll up: any Planner task assigned to you appears in To Do (and the My Tasks view) under “Assigned to me”.

So an individual sees their reminders, flagged emails and their share of the team’s boards in one consolidated list — the quiet benefit of staying inside the Microsoft stack.

When a small team has outgrown email and spreadsheets

The signal that you’ve outgrown email-and-spreadsheets is usually one of these: work falls through the cracks because it only lived in someone’s inbox; the shared spreadsheet has six versions and no one trusts it; or “who’s doing what by when” takes a meeting to answer. That’s Planner’s sweet spot — structured enough to give visibility, light enough that people will actually use it.

It’s equally important to know when you haven’t crossed into Project territory. You don’t need Project just because the work matters — you need it when timelines genuinely cascade or a client wants a formal Gantt chart. Short of that, Planner plus disciplined ownership does the job.

A Ringwood example

A construction fit-out business in Ringwood we work with was running its job pipeline across a shared Excel file on a network drive and a tangle of email threads. Site supervisors couldn’t see updates from the office, the spreadsheet was routinely locked because someone had it open, and a couple of jobs slipped because a task lived only in one estimator’s inbox. They needed a single source of truth their team would actually open.

We set them up with one Planner board per active project, surfaced as a tab in each job’s Teams channel, with buckets for site stages and every task assigned to a named person with a date. The Charts view became the Monday status check. Supervisors get their tasks in the Teams app on their phones and the office sees the same board live — all already in their Microsoft 365 plan, so no new licence cost.

Governance: don’t let plans sprawl

The failure mode with Planner isn’t the tool — it’s letting it breed. Because anyone can spin up a plan (and creating one quietly creates a Microsoft 365 Group behind it), you can end up with forty half-used boards, three plans called “Projects”, and no idea which is current — worse than the spreadsheet you replaced.

A few governance rules keep it sane:

• One plan per team or function, not per whim. Tie plans to existing Teams channels so they inherit a clear owner and membership.
• Name plans consistently and archive dead ones. A retired plan left lying around is clutter and a data-hygiene issue.
• Control who can create Microsoft 365 Groups. Because each new plan spawns a Group, ungoverned plan creation inflates your Group count and your security surface. Most SMEs should restrict Group creation and govern it centrally.

We bake Planner and Microsoft 365 Group governance into our managed IT services so the collaboration tools stay useful rather than turning into digital landfill.

Frequently asked questions

Is Microsoft Planner free with Microsoft 365?

The core Planner features — boards, buckets, task assignments, due dates, labels and the Charts view — are included with Microsoft 365 Business and Enterprise plans at no extra cost. The Premium layer (goals, sprints, dependencies, timeline and Copilot) requires a separate Project Plan licence that most small teams never need.

What’s the difference between Planner and To Do?

To Do is for one person — your private list, flagged emails and reminders. Planner is for a team — shared boards several people work from, with tasks assigned to named owners. They connect: any Planner task assigned to you appears in your To Do “Assigned to me” list, so you get one personal view of everything on your plate.

Do I still need Microsoft Project?

Only if your work has real task dependencies — where finishing one task is meant to shift the timeline of others — or you need formal Gantt charts and resource levelling. For tracking shared work with owners and due dates, Planner is enough and is already in your licence. Don’t pay for Project to manage a to-do list.

Getting it set up properly

Planner and To Do are quietly capable tools most Melbourne businesses already pay for and barely touch. The value isn’t in the software — it’s in setting it up with sensible structure, keeping tasks owned and dated, and governing plan creation so it doesn’t sprawl. TechAssist is a Melbourne-based MSP, founded in 2014, with 13 Australian-employed engineers and a 24/7 NOC in Tecoma, and we help teams across Melbourne metro get real value out of the Microsoft 365 they already own on per-user fixed monthly pricing. If your team has outgrown the shared spreadsheet, get in touch and we’ll set the boards up to fit how you work.

Microsoft Bookings is the online scheduling app built into most business Microsoft 365 plans. It gives you a public booking page where customers pick a service, choose a time, and book themselves in — with reminders, Teams meeting links and two-way calendar sync handled automatically. If you already pay for Microsoft 365, you almost certainly already own it.

Plenty of Melbourne SMEs pay a separate monthly subscription to Calendly or Acuity while a perfectly capable scheduling tool sits unused inside their existing Microsoft 365 licence. This post explains what Bookings does, which plans include it, how to set it up sensibly, how it stacks up against the standalone tools, and where the privacy and admin pitfalls are.

What Microsoft Bookings actually is

Bookings is a self-service appointment scheduling app. You define your services and your staff, publish a booking page, and customers book themselves into available slots without a single email back-and-forth. Behind the scenes it writes the appointment into the relevant staff calendar in Outlook, sends confirmation and reminder emails to the customer, and — if you want — spins up a Microsoft Teams meeting link for virtual appointments.

It lives at bookings.microsoft.com and inside the Microsoft 365 app launcher. There is also a Bookings mobile app for managing appointments on the move. The whole thing runs on the same identity, calendar and mail infrastructure you already use, which is the main reason it is worth a look before you sign up for anything else.

Which Microsoft 365 plans include it

Bookings is included in the common business and enterprise subscriptions, not the cheapest tiers. As a rule of thumb:

• Included: Microsoft 365 Business Standard, Business Premium, and the Office 365 / Microsoft 365 E3 and E5 enterprise plans.
• Not included: Microsoft 365 Business Basic does not include the Bookings app, and Microsoft 365 Apps for business (the apps-only plan with no hosted services) does not either.

Licensing details shift over time, so confirm against your own tenant rather than taking a blog’s word for it. An admin can check whether Bookings is switched on, and which users can create booking pages, in the Microsoft 365 admin centre. If you want a hand auditing what your current licences actually entitle you to, that is bread-and-butter work for our Microsoft 365 support team.

How a booking page is built

A booking page — Microsoft calls it a “booking calendar” or “booking mailbox” — is the customer-facing front end. You can run more than one, which matters if different parts of the business need separate pages. Each one is assembled from a few building blocks.

Services

A service is whatever a customer can book: a 30-minute consultation, a 60-minute strategy session, a product demo, a support call. For each service you set the duration, the price (or leave it blank), a description, and which staff can deliver it. You can add buffer times before and after — say ten minutes after every appointment to write notes or reset a room — and Bookings blocks that time out automatically so back-to-back bookings do not run you into the ground.

Staff

Staff are the people who deliver services. You add them, set their role, and — this is the important part — connect their Outlook calendar so Bookings can see when they are genuinely free. Staff do not all need a Bookings licence themselves; they can be added as guests, though licensed staff get the full calendar-sync behaviour. Each staff member can have their own working hours, so a part-timer who only works Tuesdays and Thursdays will never be offered for a Wednesday slot.

Business hours and availability

You set business hours at the page level and can override them per service or per staff member. This is where Bookings earns its keep: it cross-references your published hours, each staff member’s working hours, their existing Outlook calendar, and the buffer times, then only offers slots that survive all four filters. A customer can never book you into a slot you are already busy in, because the calendar sync is live.

Customer self-service, reminders and confirmations

From the customer’s side the experience is simple. They open your booking page link, choose a service, see real availability, pick a slot, enter their details, and confirm. They immediately receive a confirmation email with the appointment details and, for virtual appointments, the meeting join link. Bookings then sends automated reminder emails ahead of the appointment — you control how far in advance — which is the single biggest lever on reducing no-shows. Customers can reschedule or cancel through links in those emails without phoning you, which keeps your inbox clear.

Teams meeting integration for virtual appointments

If a service is flagged as an online meeting, Bookings automatically generates a Microsoft Teams meeting link and includes it in the confirmation and reminder emails for both the customer and the staff member. Nobody has to create a meeting, copy a link, or chase it up. For a Melbourne business running consultations or demos with clients across the metro area — or interstate — this removes the most tedious step in scheduling a virtual meeting. The customer joins through the link in their browser or the Teams app; they do not need a Microsoft 365 account of their own.

Calendar sync that actually works

The calendar sync is two-way and this is the feature that separates Bookings from a bolt-on tool. When a customer books, the appointment lands in the staff member’s Outlook calendar. When a staff member blocks out time in Outlook — a dentist appointment, a site visit, annual leave — Bookings sees it and stops offering that slot. There is no manual blocking, no double data entry, and no risk of someone booking a slot you quietly filled an hour ago. Because it is all the same Microsoft 365 calendar, it works across Outlook on the desktop, the web and the phone without any extra configuration.

Use cases for Melbourne SMEs

Bookings suits any business where customers or staff need to lock in a time. The patterns we see most across Melbourne metro clients:

• Professional services consultations — accountants, financial advisers and law firms offering an initial 30-minute call without the email tennis.
• Product demos and sales calls — a software or equipment supplier letting prospects self-book a demo straight off the website.
• Support sessions — booking a customer into a troubleshooting or onboarding slot with the right specialist.
• Recruitment interviews — sending a shortlist of candidates a link and letting them pick an interview slot that suits, with a Teams link auto-attached.

A Hawthorn accounting practice we work with switched their “book a tax appointment” flow over to Bookings during the run-up to end of financial year. Clients self-book consultations against each accountant’s real availability, get an SMS-style reminder by email two days out, and a Teams link if they would rather not drive into the office. The practice manager stopped spending the first hour of every morning playing calendar Tetris, and the no-show rate dropped because the reminders do the chasing.

How it compares to Calendly and Acuity

Calendly and Acuity Scheduling are polished, popular standalone scheduling tools. They are genuinely good products with slicker public pages and deeper integrations into third-party CRMs and payment processors. The honest comparison comes down to what you already pay for and how much scheduling sophistication you actually need.

The cost angle is the one most Melbourne SMEs overlook. If you are running Business Standard or Business Premium across your team, Bookings is already paid for. Paying a second per-seat subscription for scheduling, when the tool you own does the job, is money leaking out the side of the IT budget. We see this constantly when we review a new client’s software spend — the standalone scheduler is often the easiest line to cut. Where Calendly or Acuity earn their fee is deep CRM and payment integration, or a sales team that lives and dies by routing logic. If your needs are “let customers book a time and put it in Outlook with a Teams link,” Bookings covers it.

Privacy of customer data

Because Bookings runs inside your Microsoft 365 tenant, the personal information customers enter — name, email, phone, the reason for the appointment — is stored in your environment under the same data protection, retention and access controls as the rest of your Microsoft 365 data, rather than handed to a separate third-party platform. For an Australian business, that is a meaningful point in its favour. Under the Privacy Act 1988 and the Australian Privacy Principles you are responsible for personal information you collect, and keeping booking data inside a tenant you already govern is simpler to reason about than spreading it across an extra vendor.

That said, a public booking page is exactly that — public. Be deliberate about which fields you make mandatory, do not ask for more than the appointment needs, and decide who in the business can see booking details. If you handle sensitive information, fold the booking page into your broader access and retention thinking. This is the kind of detail our cybersecurity services team looks at when hardening a Microsoft 365 environment.

Admin and setup tips

A few things worth getting right before you publish a page to the world:

• Decide who can create booking pages. An admin can restrict Bookings creation to specific users in the Microsoft 365 admin centre, so you do not end up with a dozen unmanaged public pages.
• Connect every staff member’s calendar. The whole value proposition depends on live availability. A staff member whose calendar is not connected will be offered for slots they are not actually free in.
• Set realistic buffer times and minimum lead time. Stop customers booking a slot for ten minutes from now, and give yourself breathing room between appointments.
• Use a custom domain on the page where possible so the booking link reflects your brand rather than a generic Microsoft URL.
• Test the full customer journey yourself — book a slot, check the confirmation, the reminder timing and the Teams link — before you put the link on your website.

None of this is hard, but it benefits from being set up once, properly, by someone who understands how it interacts with the rest of your tenant. Getting the licensing, the permissions and the calendar connections right is exactly the sort of thing we handle for clients as part of managed IT services, alongside the rest of their Microsoft 365 environment.

Frequently asked questions

Is Microsoft Bookings free?

It is not a separate paid product — it is included in Microsoft 365 Business Standard, Business Premium, and the E3 and E5 enterprise plans at no extra cost. It is not included in Business Basic or the apps-only plans. So it is “free” in the sense that if you have the right plan, you already own it.

Does Bookings work with Microsoft Teams?

Yes. If you mark a service as an online meeting, Bookings automatically creates a Microsoft Teams meeting link and includes it in the confirmation and reminder emails for both the customer and staff. Customers can join through a browser without needing their own Microsoft 365 account.

Where is customer booking data stored?

Inside your own Microsoft 365 tenant, under the same controls as your other Microsoft 365 data. That keeps the personal information customers enter within an environment you already govern, rather than in a separate third-party scheduling platform — which is simpler to manage against your Privacy Act obligations.

Can multiple staff share one booking page?

Yes. You add multiple staff to a booking page, assign them to the relevant services, and connect each person’s Outlook calendar. Bookings then offers customers whichever staff are genuinely available for the service and time they choose, and you can run several separate booking pages if different teams need their own.

Where TechAssist fits

We are a Melbourne MSP, founded in 2014, with thirteen Australian-employed engineers — not an offshore queue. Helping clients get full value out of the Microsoft 365 licences they already pay for is a routine part of what we do, and Bookings is a textbook example: a capable tool sitting unused while a separate subscription does the same job. If you want someone to set Bookings up properly, audit your Microsoft 365 spend for duplication, or sort out the permissions and calendar plumbing behind it, get in touch and we will take a look.

Microsoft Forms is the lightweight survey, quiz and data-capture tool included with virtually every Microsoft 365 Business plan. If you pay for Business Basic, Standard or Premium, you already have it — no extra licence. For most Melbourne SMEs it handles client intake, staff feedback and event RSVPs without touching SurveyMonkey or Typeform.

It is not a heavyweight platform, and it is not trying to be. The value is that it is already in your tenant, lands responses straight into Excel, and keeps data inside your Microsoft 365 environment rather than scattered across a free third-party account nobody owns.

What Microsoft Forms is, and what you already pay for

Forms is a browser-based tool for building online forms, surveys and quizzes. You build it at forms.office.com or in the Forms app, share a link, and responses flow back in real time. It works on any device with a browser, and respondents do not need a Microsoft account to fill in a public form.

Beyond the Business plans, it is bundled into the Microsoft 365 Enterprise (E) plans and most education and non-profit plans. If you are unsure what your subscription includes, our breakdown of what is included with Microsoft 365 support in Melbourne lays it out. The practical point: you are almost certainly already paying for Forms and not using it.

Form versus quiz: pick the right type

When you create something new, Forms asks whether you want a form or a quiz, and the difference matters.

• Form — for collecting information where there are no right or wrong answers: client intake, feedback surveys, RSVPs, incident reports, booking requests. This is what most businesses need.
• Quiz — for assessment. You set correct answers and point values, and Forms marks responses automatically and shows scores. Useful for staff training checks, onboarding tests, or compliance refreshers where you need to prove someone passed.

You cannot cleanly convert one to the other afterwards, so choose deliberately. If in doubt, a form is the safer default.

Question types and branching logic

Forms gives you a sensible spread of question types: choice (single or multiple), text (short or long), rating, date, ranking, Likert scales, file upload, and Net Promoter Score. Each question can be marked required, and text questions can enforce validation such as number ranges or email format.

Branching logic

The feature that lifts Forms above a flat questionnaire is branching. You can route a respondent to different questions based on their answers — answer “yes” to “Have you used our service before?” and they skip the new-client section entirely. To set it up, build all your questions first, then open the question menu, choose Add branching, and map each answer to the question it should jump to. Branching keeps forms short and relevant, the single biggest driver of completion rates.

A short how-to: building a client intake form

The end-to-end for a typical intake form:

1. Go to forms.office.com, sign in, and select New Form.
2. Give it a clear title and short description — respondents see both.
3. Add your questions. Use Choice for fixed options, Text for free responses, and mark essentials as Required.
4. Add branching where questions only apply to certain answers.
5. Click Settings (the three dots) to control who can respond, whether responses are anonymous, and whether to send a receipt.
6. Hit Preview to test it on desktop and mobile, then Collect responses, choose your sharing method, and copy the link.
7. Watch responses arrive under the Responses tab, and click Open in Excel to export.

The whole thing takes ten minutes once you know the layout.

Sharing: internal, external and the tenant setting that controls it

This is where businesses get caught out. How you share a form decides who can fill it in, and whether their data is captured securely.

The critical detail: the “Anyone can respond” option is controlled at the tenant level by your administrators. In the Microsoft 365 admin centre, under the Forms settings, there is a toggle for external sharing. If it is switched off — and in security-conscious tenants it often is — staff will not see the “Anyone” option at all, and every form is locked to internal-only.

That is a sensible default, but it bites when someone genuinely needs to collect responses from clients or the public and cannot work out why the option has vanished. Enabling external collection is a deliberate decision, weighing convenience against the fact that an open link can be forwarded to anyone. We treat it as part of broader tenant hardening, alongside our work on conditional access policies for Microsoft 365.

Collecting responses into Excel

Every form has a Responses tab with a live summary — charts for choice questions, individual responses, aggregate counts. For real analysis, click Open in Excel.

For forms created inside a SharePoint or Teams group — which is how business forms should be set up — you get a live workbook in the group’s SharePoint library that updates as responses arrive. The data lives in a shared, owned location rather than tied to one person’s profile, so it survives that person leaving. Getting Forms created in the right place is a small governance decision we set up as part of a managed Microsoft 365 environment.

Real SME use cases

A few patterns we see work well:

• Client intake — a new-client form capturing contact details, requirements and consent before the first meeting, replacing the email chase.
• Staff feedback — anonymous internal pulse surveys where honesty depends on people trusting it is genuinely anonymous (set “Record name” to off and tell them).
• Event RSVPs — a public link for a client function or open day, with branching for dietary needs and plus-ones.
• Incident reporting — an internal form for staff to log near-misses, IT issues or workplace incidents into a tracked Excel list someone reviews.

A professional services firm in Hawthorn we work with replaced a tangle of Word-document intake sheets with a single branching Forms intake. New enquiries now land structured and complete in a SharePoint-backed spreadsheet their reception team works from each morning — no retyping, no chasing missing fields, no cost beyond licences they already held.

Data residency and privacy

Because Forms is part of Microsoft 365, response data sits within your tenant’s cloud storage, governed by the same agreements as the rest of your environment. Commercial tenants provisioned for Australia store core customer data in Australian data centres, which matters where clients or regulators have data residency expectations.

That said, a tool being inside Microsoft 365 does not make your collection compliant by itself. If you are gathering personal information, the Privacy Act and the Australian Privacy Principles still apply — you need a lawful reason to collect it, you should tell people what you are collecting and why, and you must store and dispose of it responsibly. For health information the OAIC’s expectations are stricter again. Keep forms to the minimum data you need.

Limits, and when to step up

Forms is deliberately simple, and you will hit its ceiling if you push it. Worth knowing the edges:

• It is built for straightforward surveys and capture, not multi-stage workflows, approvals, or apps with stored logic and dashboards.
• Styling and branding are limited — you get themes, not full design control.
• No built-in payment collection, no complex conditional calculations, no relational data model.
• Response and question counts are generous for SME use but capped; very high-volume surveys can hit limits.

When you outgrow it, the upgrade path is clear. Microsoft Dynamics 365 Customer Voice (the successor to the old “Forms Pro”) adds richer survey distribution, follow-up automation and CRM integration. Power Apps is the answer when you need a genuine application — stored data, business logic, role-based access, dashboards — rather than a flat survey, often paired with Power Automate to trigger workflows off submissions. Both are bigger commitments, so use Forms until it genuinely stops fitting.

Frequently asked questions

Is Microsoft Forms free?

It is included at no extra cost with Microsoft 365 Business Basic, Standard and Premium, the Enterprise plans, and most education and non-profit plans. There is a limited version tied to free personal accounts, but business use should run through your paid tenant so data stays governed and owned.

Can people outside my organisation fill in a form?

Yes, if you share it with the “Anyone can respond” option — but that option is controlled at the tenant level by your administrators. If external sharing is switched off in your admin settings, staff can only share forms internally. Enabling external responses is a deliberate administrative decision.

Are responses to a Microsoft Form really anonymous?

Only if you set them up that way. Internal forms can record the respondent’s name unless you turn that off. Public forms are anonymous by default unless you add a question asking for identifying details. If you promise staff anonymity on a feedback survey, confirm the “Record name” setting is off first.

When should we move off Forms?

When you need workflows, approvals, stored business logic, payments or a proper application rather than a survey. At that point Dynamics 365 Customer Voice or Power Apps with Power Automate is the right step up — both bigger commitments worth scoping properly.

Getting it set up right

Forms is one of the most under-used tools in a typical Microsoft 365 subscription. The setup that matters is the bit most businesses skip: forms created in shared SharePoint-backed locations so data is owned not orphaned, the external-sharing and anonymity settings configured correctly, and collection kept within your privacy obligations. We are a Melbourne-based MSP with 13 Australian-employed engineers, and getting clients full value from the Microsoft 365 they already pay for is core to what we do. If you want your tenant configured so tools like Forms are safe and useful out of the box, get in touch and we will sort it.