SharePoint Connector Documentation
Index

Deployment Options

The SharePoint Connector can be deployed in both cloud (SaaS) and on-premises Business Central environments. This page compares the deployment options and their requirements.

Deployment Comparison

Aspect Business Central Online (SaaS) Business Central On-Premises
Installation AppSource or direct Manual app package install
Updates Automatic via AppSource Manual update required
Authentication OAuth via Microsoft Entra OAuth or Certificate
Maintenance Minimal Requires IT administration
Scaling Automatic Manual infrastructure management

Business Central Online (SaaS)

Advantages

  • Easy Installation: Install directly from Microsoft AppSource
  • Automatic Updates: Receive updates automatically
  • Integrated Authentication: Seamless Microsoft 365 authentication
  • No Infrastructure: Microsoft manages the infrastructure

Requirements

Requirement Details
BC Subscription Business Central Online subscription
SharePoint SharePoint Online (Microsoft 365)
Admin Access Business Central admin permissions for install
Azure AD Access to Microsoft Entra ID for app registration

Installation Path

  1. Find the app in Microsoft AppSource
  2. Install in sandbox for testing
  3. Install in production after validation
  4. Configure SharePoint connection

Business Central On-Premises

Advantages

  • Full Control: Complete control over environment
  • Customization: More flexibility for customizations
  • Offline Capability: Can operate with limited connectivity
  • Data Sovereignty: Data remains in your infrastructure

Requirements

Requirement Details
BC Version Business Central On-Premises 24 (2024 release wave 1) or later
SharePoint SharePoint Online (Microsoft 365)
App Package Download the app package (a single package is produced)
Outbound Internet Required for SharePoint REST API access

Installation Path

  1. Download the app package
  2. Publish the app using Business Central Administration Shell
  3. Install the app in target companies
  4. Configure SharePoint connection

Version Matching

The app declares a minimum platform version of 17.0.0.0 but uses AL runtime 13.0 (app.json), which requires Business Central 24 (2024 release wave 1) or later. A single package is produced; no separate per-version packages exist. If you need a build for a specific platform, contact the publisher.

Hybrid Scenarios

On-Premises BC with SharePoint Online

This is the supported scenario for on-premises:

  • Business Central runs on-premises
  • SharePoint is in Microsoft 365 cloud
  • Authentication via Microsoft Entra ID
  • Requires outbound internet access

Unsupported Configurations

Configuration Status
On-Prem BC + On-Prem SharePoint Not supported
Docker/Container BC May work, not officially supported
Isolated Networks Requires internet for SharePoint

Network Considerations

Required Connectivity

Both deployment types require network access to:

Endpoint Purpose
*.sharepoint.com SharePoint document access (SharePoint REST API)
login.microsoftonline.com OAuth authentication (Public cloud)
login.microsoftonline.us OAuth authentication (US Government cloud)
check.hougaardlicense.com License validation (production activation only)

Firewall Configuration

Ensure your firewall allows outbound HTTPS (port 443) to the above endpoints.

Proxy Servers

If using a proxy server:

  • Ensure the proxy allows access to Microsoft 365 endpoints
  • Authentication proxies may require additional configuration

Multi-Environment Deployment

SaaS Multi-Environment

For organizations with multiple Business Central environments:

  • Each environment is configured independently
  • Sandbox and production can have different settings
  • Consider using the same SharePoint structure across environments

On-Premises Multi-Company

For on-premises with multiple companies:

  • App is installed once per environment
  • Each company can have its own SharePoint configuration
  • Use "Separate Token Per Company" if needed

Deployment Best Practices

Pre-Deployment

  1. Plan SharePoint Structure: Design folder hierarchy before deployment
  2. Verify Permissions: Ensure you have required admin access
  3. Test in Sandbox: Always test in a non-production environment first
  4. Document Configuration: Record settings for future reference

Deployment Checklist

Step SaaS On-Premises
Verify BC version compatibility Yes Yes
Verify SharePoint access Yes Yes
Prepare Azure AD app registration Yes Yes
Download app package No Yes
Install app Via AppSource Via Admin Shell
Configure connection Yes Yes
Test functionality Yes Yes
Activate license Yes Yes

Post-Deployment

  1. Train Users: Provide training on connector features
  2. Monitor Usage: Watch for errors or issues
  3. Plan Updates: Establish update procedures (especially for on-premises)

Updates and Maintenance

SaaS Updates

  • Updates are delivered automatically via AppSource
  • Major updates may require testing in sandbox first
  • Review release notes for changes

On-Premises Updates

  • Updates require manual download and installation
  • Test updates in non-production first
  • May require Business Central service restart
  • Back up before updating