Missing an NDIS claim notification isn't always a process failure. Often it's a configuration failure — something quietly broken inside your Microsoft 365 environment that nobody set up to catch. Here are the five mistakes we see most often in NDIS provider tenants, and what to do about each one.

1. Shared inboxes aren't monitored — they're just there

Many providers set up a shared mailbox like claims@yourorg.com.au during onboarding and never configure who actually monitors it. In Outlook, shared mailboxes don't surface unread counts the same way personal inboxes do. Notifications from the NDIS portal land there and sit unread for days.

Fix this by adding the shared mailbox to the primary view of the relevant staff member's Outlook, and setting up an Outlook rule to flag or forward any email from noreply@ndis.gov.au to a personal inbox as well.

2. Power Automate flows are broken and nobody noticed

If you've built a Power Automate flow to forward or alert on NDIS portal emails, check when it last ran successfully. Flows break silently — a password change, a licence reassignment, or a connector token expiry can disable a flow without any visible error to the end user.

Go to flow.microsoft.com, open the flow, and check the run history. If there are failures or a long gap in activity, it needs to be re-authenticated or rebuilt. Set up a separate flow that sends a weekly confirmation that your notification flow is still alive.

3. Email rules are silently misfiling claim notifications

Outlook rules run in the order they're listed. If an older rule — often something broad like "move all government emails to a subfolder" — fires before your NDIS-specific rule, claim notifications can end up buried in a folder nobody checks. This is especially common when rules are inherited from a previous staff member's setup.

Audit the rules in any mailbox that receives NDIS correspondence. In Outlook desktop: Home > Rules > Manage Rules & Alerts. Make your NDIS-specific rules run first.

4. Microsoft Teams notifications are suppressed organisation-wide

Some IT admins or MSPs turn off email notifications from Teams at the tenant level to reduce noise. If your team uses a Teams channel to triage claim alerts, and notifications are suppressed, staff will only see new messages if they happen to open Teams. Urgent items get missed entirely on busy days.

Check Teams notification settings under Teams Admin Centre > Notifications & feeds. For claim-critical channels, consider configuring channel-level notifications so members receive an email digest for any activity — even if general Teams notifications are off.

5. The wrong person owns the NDIS portal email address

This one is structural. The email address registered with the NDIS myplace provider portal is often set to a staff member's personal work address — not a shared or role-based inbox. When that person leaves, goes on leave, or changes roles, notifications go to an inbox nobody else can access.

Log into the NDIS myplace provider portal and verify what email address is registered for notifications. Update it to a shared mailbox that survives staff turnover. This single change eliminates one of the most common causes of missed claim notifications we see.

What to do right now

Run through each of these five checks this week. Most of them take under ten minutes each. You don't need a new system — you need the system you already have configured to actually work.

If you're not sure what's broken in your Microsoft 365 environment, a focused review can find it quickly. Book a Discovery Call and we'll map it out with you.