Ask any controller or ops manager running Microsoft Dynamics 365 Business Central where the "real" copy of a signed purchase order lives, and you will usually get a pause before the answer. Sometimes it is an email attachment; sometimes it is a scanned PDF someone dropped in a shared drive three years ago, and nobody's touched since.
SharePoint Business Central integration exists to close that gap, not by adding another tool to manage, but by giving the documents a fixed address that matches the transaction they belong to.
Table of Contents
That sounds simple.
Effectively, most Canadian businesses get partway there and stop that means a folder here, an email rule there, because nobody walked through what "connected" means at the setup level.
This blog does that, with the Canadian details most integration write-ups skip entirely including data residency, CRA recordkeeping, and the bilingual document structure a lot of Quebec-based operations need from day one.
What Is SharePoint Integration in Business Central?
Business Central talks to SharePoint through Microsoft Graph API, using a System Application module Microsoft ship with the product itself. A third-party Business Central SharePoint connector usually sits on top of that same Graph connection and adds a management layer like metadata mapping, factbox links, automatic folder rules, that the native module does not include out of the box.
Once the connection is live, the shift is less about features and more about where friction disappears. Attachments to sales orders, purchase orders, and posted invoices can be saved directly into a SharePoint library instead of Business Central's own database. Customer and vendor cards pick up factbox links straight to the matching SharePoint folder, so nobody's tabbing between two browser windows to confirm a signed contract exists. Quotes and statements generated from templates can land in the right folder automatically at the moment they are created, which matters less for convenience and more because it removes the step where someone forgets.
Business Central 2026 release wave 1 (BC28) pushed this further with external storage support for document attachments that means companies can now move attachment data out of the BC database entirely and into SharePoint or Azure storage instead. Database bloat from years of scanned invoices creeps faster than most finance teams expects, and this is the fix Microsoft finally built in rather than leaving to third-party workarounds.
How to Set Up SharePoint Integration in Business Central
There is no single correct path here. What fits depends on who is going to maintain the connection two years from now, not just what's technically achievable this week.
The native System Application module is the built-in option. It needs an Azure AD app registration with Microsoft Graph permission such as Sites.ReadWrite.All or Files.ReadWrite.All, with admin consent granted before anything works. No extra licensing cost, which is the appeal. The catch is that someone still must configure the API setup correctly in Business Central, and this is exactly where the 403 and 401 errors that flood Microsoft's own community forums come from — permissions scoped too narrowly, or an OAuth token pointed at the wrong audience.
A third-party SharePoint connector trades that configuration risk for a subscription fee. These tools give you screens instead of code: automatic folder structuring by customer or project, bulk document actions, metadata rules you set once. Fine for teams that do not want anyone inside Azure AD, less fine for the budget line if you are already running lean.
Custom development through the Graph API is the third option, and it is only worth it for specific, repeatable workflows means auto-renaming files by document type and customer number before they land in SharePoint, say. It is the most flexible path and the one that needs upkeep, because Graph API permission models shift, and so does Business Central itself, roughly twice a year.
Most small and mid-sized Canadian businesses only need the native module. The remaining gap including bulk automation, approval routing tied to posting events, is usually a Power Automate problem, not a coding one.
Automating Document Management with Power Automate
Power Automate ships with most Business Central licenses, and it earns its keep on anything rule based. A typical flow like a sales invoice post, Power Automate generates the PDF, files it into a dated SharePoint folder, pings finance. No manual export step for anyone to forget at month-end.
Business Central supports two flow types here including automated flows that trigger off record events, and instant flows a user kicks off manually from inside a record. Purchase order approvals route through SharePoint and Teams without a spreadsheet in sight, if it is set up right.
Moreover, the reason for this matter is not abstract. When invoice filing depends on someone remembering to do it before the month closes, mistakes compound quietly. A missing invoice during a GST/HST reconciliation costs a finance team more hours to track down after the fact that the automation would have cost to build in the first place. That's the actual math, not a vague productivity claim.
Common Business Central SharePoint Integration Errors (and How to Fix Them)
The same handful of errors show up over and over on the Dynamics community forums.
A 403 Forbidden error almost always traces back to missing or under-scoped Graph permissions on the app registration, or admin consent that was never actually granted, which happens more than people admit.
A 401 Unauthorized error usually means the OAuth scope was not set to https://graph.microsoft.com/. default, so the token does not match what SharePoint expects. And delegated versus application permissions trips up almost everyone at least once: delegated access only works while a signed-in user has SharePoint rights, while application (app-only) access needs the higher-privilege permissions and, in more advanced setups, certificate-based authentication instead of a plain client secret.
There is also a hard deadline worth knowing if your integration predates 2026. Microsoft retired Azure Access Control Service (ACS) for SharePoint in Microsoft 365 on April 2, 2026. Anything still authenticating through old SharePoint app principals via ACS needs to move to Azure AD app-only authentication. That's not a future nice-to-have, if it has not happened yet, it is already overdue.
The Canadian Context Most Setup Guides Skip
A lot of what's written about this integration is generic and global, which means it misses the parts that change how a Canadian business should build it.
Microsoft runs Canadian data center regions out of Toronto and Quebec City, and businesses with data residency obligations common across finance, healthcare, and public-sector-adjacent work, should confirm their Microsoft 365 tenant is provisioned in the Canadian region before building document workflows on top of it. It is not automatic by default on every tenant, and finding out otherwise after two years of file uploads is not a fun conversation.
Then there is recordkeeping. The CRA requires businesses to hold onto most financial records, invoices and supporting documentation tied to GST/HST filings included, for six years. A Share Point Business Central connection with a consistent folder structure turns that from a scramble into a search. A shared drive with inconsistent naming, which is still how a surprising number of Canadian SMBs handle it, turns it into a multi-day project every time an auditor asks.
Also Read: GST NETFILE
And for companies operating in Quebec, bilingual document libraries, file naming and metadata that work in French and English at once, are a decision worth making during setup, not two years after English-only folders are already the standard everyone's used to.
Note: None of these changes the technical steps above. It changes how the folder structure, retention rules, and access permissions should look before anyone starts uploading anything.
Picking the Right Setup for Your Business
Most companies get this backwards which means they worry about the coding and underestimate the permissions and governance work, when it is almost always the other way around. The native connector plus Power Automate handles most real-world cases without any custom development at all. Where it gets complicated, multi-entity structures, certificate-based service-to-service authentication, migrating off a deprecated ACS connection, is where Dynamics 365 Business Central consulting services earn their cost. Not because the initial setup is hard, but because getting document permissions wrong tends to surface six months later, during an audit or a customer dispute, when it is expensive to fix.
Furthermore, Dynamics Square Canada works through exactly this kind of Microsoft Dynamics 365 configuration with businesses across Ontario, British Columbia, Alberta, and Quebec, scoped to how each business stores and retrieves documents, not sold as a one-size package.
If you are weighing native setup against a third-party connector or custom Graph API work, that's worth talking through before anyone starts provisioning Azure AD permissions.
If you any doubts feel free to contact Dynamics Square via call at +1 778 381 5388 or drop an email at info@dynamicssquare.ca.
