One set of credentials, and correspondence attached to the record it belongs to.
CubeERP and Microsoft 365
Single sign-on with Entra ID, Outlook email and calendar, and documents where your team already keeps them.
- Productivity
- No per-connector licence
- 01234 672 617
Most of the businesses we work with already run Microsoft 365, and the fastest way to make a new system feel unwelcome is to give everybody another password. CubeERP supports single sign-on through Entra ID, sends documents from your own domain, files inbound correspondence against the customer or job it relates to, and puts appointments in the calendars people actually look at.
What moves
Exactly what is synced, and which way
Being specific about this up front avoids the single most common integration disappointment - discovering after go-live that one field never travelled.
- Both ways
Single sign-on
Authentication through Entra ID with your existing conditional access and MFA policies applied - no separate password to manage or leak.
- Out of CubeERP
Quotes, orders and invoices by email
Documents sent from your own domain with correct authentication, logged against the record so everybody can see what was sent and when.
- Into CubeERP
Inbound correspondence
Replies matched back to the quote, order or job by reference, so the conversation is on the record rather than in one person’s inbox.
- Both ways
Calendar
Service visits, installation dates and follow-ups appearing in Outlook calendars, updating when the schedule changes.
How it behaves
The detail that decides whether it is actually useful
Your identity policies
MFA, conditional access and device compliance are enforced by Entra ID, and leavers lose access when their account is disabled - not when somebody remembers.
Email from your domain
Sent through Microsoft 365 with SPF, DKIM and DMARC intact, so documents reach inboxes rather than junk folders.
Documents where they live
Attachments can be stored in SharePoint or OneDrive and referenced from the record, so your document retention arrangements stay as they are.
Exports that open cleanly
Reports export to Excel with formatting and types intact, because a report nobody can use in Excel is a report nobody uses.
Setting it up
Three steps, done during implementation
- 1
Register the application in Entra ID and grant the permissions your IT team is comfortable with - they can be reviewed and revoked at any time.
- 2
Configure email sending from your tenant so documents come from your domain rather than ours.
- 3
Decide where documents live: inside CubeERP or referenced in SharePoint. Either is fine; picking one is important.
Questions
What people ask about this one
Yes. Security is not something we charge extra for - SSO, MFA support and audit logging are part of the platform rather than a premium tier.
Your Entra ID policies apply, including MFA and conditional access. CubeERP does not provide a way around them.
Yes for SSO and email. Microsoft 365 is more common among the businesses we work with, which is why it has its own page.
By default in CubeERP, in UK data centres. Where you would rather they stayed in SharePoint, they can be stored there and referenced instead.
Disabling their Microsoft account removes CubeERP access immediately. That is the main operational reason to use SSO rather than local accounts.
Related
Usually set up at the same time
- Power BI & ReportingDirect, read-only access to your CubeERP data for Power BI, Excel or any other reporting tool you already use.
- CubeERP API & WebhooksA documented REST API and webhooks covering the whole system - the same interface the product itself is built on.
- XeroSales and purchase invoices, credit notes, payments and stock journals posted to Xero automatically, with no rekeying at month end.
Microsoft 365
Check the Microsoft 365 detail before you commit
Send us the specifics - your chart of accounts, your tax treatment, your product structure - and we will tell you exactly how it maps rather than promising it will be fine.