Business Applications
Integration of ERP, CRM and core systems with Microsoft 365.
Customers, orders and staff details flow from your ERP, CRM and HR system to where your team works. For every field, we agree which system owns it.
For companies that work with bexio, Abacus, a CRM or industry software and also need that data in Microsoft 365.
- bexio
- Abacus
- Dataverse
- Custom connectors
- Azure Logic Apps
- Azure API Management
- Copilot connectors

From CRM deal to project workspace
Sales wins a new customer in the CRM. In bexio or Abacus the order follows, in SharePoint the project workspace with customer and contacts, and field staff see both in their app. On the same day HR records the new project manager; on her first morning her account is ready, with access to the project workspace. Each detail is entered once, in the system that owns it.
Connections we build
Your ERP, your CRM and your line-of-business applications run the business reliably; where they meet Microsoft 365, the same detail is often typed a second time. Each connection starts with the question which system owns which field and whether data flows one way or both ways, and ends with a pilot on real data. We build with what suits the data flow, from Power Platform connectors to Azure Logic Apps and Azure Functions for integrations that run server-side.
- Project and customer workspaces from the ERPA new order or customer in bexio or Abacus creates a SharePoint site or Teams channel with template, metadata and permissions; quotes and contracts from that workspace are linked to the ERP record.Result: every project has a place to file from day one, and whoever opens the order in the ERP finds its documents.
- Data in apps and DataverseCustomers, contacts, orders and items from the ERP or CRM are available in Power Apps, synchronised into Dataverse or read straight from the source as a virtual table when the data should stay there; only agreed fields such as status or note are written back.Result: field staff see customer, order and item on the phone exactly as they stand in the system of record.
- CRM and line-of-business applicationsWe connect Dynamics 365, Salesforce or industry software through their interfaces, with prebuilt connectors, custom connectors or Azure Logic Apps, depending on what the interface offers. A won opportunity creates the order in the ERP, an enrolment in the school administration system the place on the course.Result: sales keep working in the CRM, and the ERP knows the order as soon as it is won.
- Accounts from the HR systemA new starter in the HR system or business application creates the account in Entra ID, with department, job title and manager, and assigns groups, teams and licences; a leaver's access is blocked on the agreed date. Abacus Copilot prepares payroll changes that HR reviews and approves.Result: new staff have their access on day one, and every change is traceable in Abacus.
- One interface for many applicationsWhen several applications need the same data, we provide a documented API, published through Azure API Management, with sign-in through Entra ID, rate limits and a log of calls. New applications connect there.Result: your team sees in one place which application retrieves which data, and a change at the source is followed up once.
- Data for Copilot and agentsCopilot connectors make records from the CRM, ticketing system or business application findable in Microsoft Copilot, in search and for agents, indexed or queried live from the source, always with the source's permissions.Result: whoever asks Copilot about a customer gets the details from the CRM with a link to the record.
Fields, interfaces, owners
One decision per field: which system owns customer, project, order, contact and person, and what writes back. Interface access: the bexio API, the Abacus REST API or the API of your CRM and business application, with a service account, the licences needed and test data for creation, change, failure and retry. One person for errors: a duplicate customer or missing required field needs a decision from someone who knows the data. Where contact or personnel data flows, we record under the Swiss data protection act which fields are transferred and who can trace the transfer.
Tested in the pilot, monitored in operation
A connection that runs in the pilot with real data: creation, change, failure and retry, checked by your business team and system owners. Documentation of the mapping: which field comes from where, goes where and in which direction. Monitoring, an error log and a responsible person for every connection. Afterwards your team adjusts mappings and resolves errors on its own, or Support & Operations takes over operation, with a procedure for changes to the interfaces.
Sound familiar? Tell us where you stand today.
ContactWhat's new.
As of: 11 October 2026
- As of 25 September 2026
Copilot connectors bring data from other systems into Copilot and search.
Synced connectors index content from external systems into Microsoft Graph; federated connectors query the source in real time through the Model Context Protocol, without indexing. Both show only what the person may see in the source. Microsoft offers more than 100 prebuilt connectors, for example for Salesforce, ServiceNow, Dynamics 365 and SAP; for other systems a custom connector can be built.
Source: Microsoft Learn: Copilot connectors overview - As of 3 June 2026
Custom connectors make any REST API usable in Power Apps, Power Automate and Copilot Studio.
A custom connector describes a REST API with OpenAPI and is then available in Power Apps, Power Automate, Copilot Studio and Logic Apps. It supports OAuth 2.0, API keys and basic authentication, reaches systems on your own network through the on-premises data gateway and can be shared in the tenant or certified by Microsoft.
Source: Microsoft Learn: Custom connectors overview - As of 19 June 2026
bexio API: OpenID Connect, refresh tokens and rate limits.
The public bexio API is a JSON REST interface with sign-in through OpenID Connect on OAuth 2.0, refresh tokens and personal access tokens, and it publishes rate limits in its responses. On 19 June 2026 bexio changed the required scopes for purchase bills, payments and expenses; integrations have to check their permissions.
Source: bexio: API documentation
Connections and tools.
Ready-made connections for bexio and Abacus, the platforms for connections of your own and the workshop where the data flow is defined.
bexio data in SharePoint, Teams and Power Apps.
präziis. PlatformAbacus data in Microsoft 365.
Abacus CopilotQuery HR data and prepare changes.
DataverseSynchronised and virtual tables for data from ERP and CRM.
Power AutomateTriggers, connectors and error handling in the product.
Entra IDAccounts, groups and sign-in for staff and service accounts.
Dynamics 365When the ERP or CRM comes from Microsoft.
WorkshopsDefine data flow, triggers and exceptions in a workshop.
Connections from our projects.
Data from ERP, PIM and CRM for intranet, apps and reports at REV Ritter, HR changes and payroll runs with Abacus at Kwaxx, accounts, teams and Moodle courses from the school administration system at BZ Pflege, and the central API being built there now.

REV Ritter GmbH
Connecting documents, information and business processes at REV Ritter
View project
Kwaxx AG
In progressManaging HR changes and payroll runs together at Kwaxx
View project
BZ Pflege
BZ Pflege: Providing students with the digital access they need
View project
Berner Bildungszentrum Pflege AG
In progressModernising the central BZ Pflege API
View projectProducts from our catalogue.
Three products that connect bexio and Abacus with Microsoft 365.
Related to your task
Apps for capture and workflows that build on the connected data.
Process automationPower Automate flows for business processes that run on these connections.
Reporting & dashboardsPower BI reports on customers, orders and invoices from ERP and CRM.
PeopleProfile card, directory and people search from the HR system's details.
Data & content preparation for AIClean up master data before Copilot and agents answer from it.
Migration to Microsoft 365Carry data over once when a system is replaced.
Support & OperationsHave the connections monitored and supported after the pilot.
Before data flows between your systems.
Which system owns the data?
One per field, and we define that before the build. Usually the ERP owns customer, order and invoice, the CRM opportunities and contacts, the HR system the people and Microsoft 365 the documents and the collaboration. Only what is explicitly agreed is written back, such as a status or a note. That way there are no two truths.
Do we need an API licence from bexio or Abacus?
For bexio the public API can be used with the bexio subscription; for Abacus the REST API has to be enabled and a service user created in the user management. Which licences and permissions your workflow needs, we clarify with your fiduciary or Abacus partner before the start and record in the proposal.
What do you build the connection with?
For bexio we first check bexioLink, for Abacus präziis. Platform and Abacus Copilot; they cover the common workflows and are maintained by us. If your team is to adjust the connection itself later, we build in the Power Platform with prebuilt and custom connectors. Large data volumes, systems on your own network or logic in code belong in Azure Logic Apps or Azure Functions in your Azure.
What happens on errors?
They are logged, retried and reported. A duplicate customer, a missing required field or an interrupted connection triggers a retry and, if that is not enough, a message to the responsible person with the record. Nothing is lost silently, and nothing is overwritten silently.
Who sees the data in Microsoft 365?
Those allowed to, by role. We transfer only the fields the workflow needs, set permissions through groups in Entra ID and check with selected roles who sees what. Copilot connectors follow the permissions of the source; for virtual tables we control access in the source, because Dataverse has no per-record permissions for them. Payroll and personnel data stay with HR.
Can we synchronise in real time?
Where the workflow needs it, yes: a new order triggers the workspace immediately. Much works better in intervals, for example master data several times a day, because rate limits of the interfaces and error handling are then simpler. Direction, trigger and frequency we define per data flow.
Agree on a useful next step
Tell us about your current workflow, the systems involved and the result you need. In our first conversation, we identify what else we need to know to plan a useful next step.
