Anyone who tries to honestly connect an ERP world like Abacus with the collaboration platform Microsoft 365 quickly hits the limits of classic point-to-point connectors. Synchronizing lists is not enough. What is needed is a platform that understands business logic and translates it consistently into both worlds — from the first order all the way through to archiving.

In this article we show how präziis. works under the hood: which building blocks play together, how we implement provisioning, synchronization and governance — and which design decisions sit behind them.

The Core Idea: Abacus as the Single Point of Truth

präziis. is built on a simple premise: master data belongs in the ERP. Collaboration belongs in the digital workplace. Both worlds should do what they are best at — not duplicate each other's responsibilities.

Concretely:

• Abacus is the leading source for customers, suppliers, projects, orders, employees, roles and cost centers.
• Microsoft 365 is the leading environment for documents, communication, tasks and day-to-day collaboration.
• präziis. ensures that every relevant change in the ERP automatically results in the corresponding structure, permission and metadata maintenance in the Microsoft tenant — and that selected Microsoft 365 activities flow back to the ERP as signals.

Architecture at a Glance

präziis. consists of five logical layers:

1. 1Connector layer that talks to Abacus (via Abacus AbaConnect web services) and Microsoft 365 (via Microsoft Graph and SharePoint APIs).
2. 2Domain model that brings together Abacus objects (customer, order, project, employee) and Microsoft 365 objects (team, site, channel, library) in a shared data model.
3. 3Orchestrator that translates incoming events into workflows: "New order → create team using template X, site using design Y, permissions from role Z".
4. 4Governance and audit layer for naming conventions, lifecycle, retention, permission reviews and logging.
5. 5Dashboard and API through which IT, business units and third-party systems can query state, intervene or trigger further workflows.

All components run entirely on Microsoft Azure in the Swiss regions — as multi-tenant SaaS or, on request, as a dedicated tenant.

Provisioning: From Abacus Order to Microsoft Team in Seconds

The most important workflow in präziis. is probably the automatic provisioning. Simplified, this is what happens when a new project is created in Abacus:

Abacus trigger (new order/project)
   ↓
präziis. orchestrator
   ├── loads master data via AbaConnect
   ├── selects matching provisioning template
   ├── creates Microsoft 365 Group + Team via Graph
   ├── configures channels, tabs and apps
   ├── provisions SharePoint site with site design
   ├── creates libraries, columns, views, metadata
   ├── applies permissions from Abacus role model
   └── writes link back into Abacus

A single click in the ERP creates a fully prepared workspace — with the right people, the right structure and the right metadata. No wild growth, no forgotten permission, no "we will clean it up next time" debt.

Templates Instead of Snowflakes

To make this work in any organization, präziis. uses provisioning templates that you define per project type, client or business unit. A template covers:

• Team template: channels, tabs, installed apps, tags.
• SharePoint site design: library structure, content types, columns, default views.
• Metadata mapping: which Abacus fields become which site columns?
• Permission model: which Abacus roles map to which Microsoft 365 groups?
• Lifecycle rules: when to archive, delete, freeze?

Templates are managed centrally, versioned, and can be retroactively applied to existing sites — a critical tool for legacy migrations.

Synchronization: Consistency Instead of Drift

Provisioning is only the beginning. The more interesting — and harder — challenge is ongoing synchronization. präziis. keeps master data, memberships and structures continuously consistent. Four mechanisms make that possible:

1. Event-Driven Updates

Changes in Abacus (e.g. a new contact for a customer, a changed project role) are picked up via AbaConnect triggers or periodic delta polling and immediately propagated into Microsoft 365. The other way around, Microsoft Graph change notifications feed signals from the tenant back to präziis.

2. Conflict Resolution with Clear Rules

What if someone manually changes a site title? What if an address is corrected in Abacus while a SharePoint site column was edited in parallel? präziis. uses clearly defined source-of-truth fields per attribute. For each field it is declaratively defined which system wins — and deviations are surfaced in the dashboard instead of being silently overwritten.

3. Soft Reconciliation

At defined intervals (typically nightly), präziis. reconciles the two worlds and corrects deviations that arose between events. These reconciliation reports are a key tool for audits and for the continuous improvement of the data model.

4. Lifecycle Hooks

When a project is closed or archived in Abacus, präziis. triggers the configured lifecycle: reduce access to read-only, apply retention rules, move the site into an archive hub, archive the team. Once the retention period expires, the configured deletion rule kicks in — fully logged and audit-ready.

Permissions: Roles Become Groups

One of the most common compliance weaknesses we see in audits is outdated permissions in SharePoint and Teams. präziis. solves this by never granting permissions manually — they are derived from Abacus roles:

• Project role in Abacus → Microsoft 365 group → team membership / site access.
• When someone leaves the project or the company, permissions disappear automatically — across all derived structures.
• External users (customers, partners) are modeled through separately managed guest roles, with defined expiration dates and re-approval workflows.

Permission hygiene becomes a side effect rather than a permanent project.

Governance, Compliance and Audit

präziis. is not just a provisioning machine, it is also a governance platform. The following capabilities are included from day one:

• Gap-free audit log of all changes — who created, modified, deleted what and when.
• Naming convention enforcement: forbidden characters, length limits, tenant prefixes — all declarative.
• Template versioning: templates can be versioned, with migration paths for existing sites.
• Permission reviews: periodic, automatically generated reviews for site owners and compliance teams.
• Integration with Microsoft Purview: sensitivity labels, retention policies and DLP rules are automatically applied to provisioned structures.

For regulated industries — trustees, banking, healthcare, public sector — these are the building blocks that distinguish "we use Microsoft 365" from "we use Microsoft 365 in an audit-proof way".

Security and Swiss Data Hosting

The entire platform runs on Microsoft Azure in the Swiss regions Switzerland North and West. We consistently apply:

• Zero-trust principles for all service access (managed identities, conditional access, privileged identity management).
• Encryption at rest and in transit, with customer-managed keys on request.
• Tenant separation at the database, storage and configuration layer.
• Penetration tests and security reviews by independent Swiss providers.

Compliance with the revised Swiss FADP, GDPR and sector-specific requirements is part of our standard process — not an afterthought.

Extensibility: präziis. as a Platform

präziis. is deliberately built to fit into your existing IT landscape — not the other way around. Three extension mechanisms are particularly relevant:

1. 1Webhooks and REST API to integrate custom workflows or third-party systems (CRM, time tracking, BI).
2. 2Custom templates, defined through configuration rather than code — business units can model new project types themselves.
3. 3Pluggable connectors: in addition to Abacus, we can hook up further ERPs, CRMs or industry systems as data sources on request.

In this way präziis. evolves from an Abacus-↔-M365 connector into the data and provisioning backbone of your digital workplace.

Where to Start

If any of the following sounds familiar, it is worth a conversation:

• More than half an hour of effort per new project setup in Microsoft 365.
• Recurring discussions about "where do we put this" and "what should we call this folder".
• Audits that uncover permission gaps or outdated memberships.
• Reporting overhead caused by inconsistencies between Abacus and Microsoft 365.
• Growth where your IT can no longer keep up with manual structure creation.

You will find a live demo, a tour through the dashboard and a detailed feature list at praeziis.ch. For a technical deep-dive demo, an architecture discussion or a free initial analysis of your Abacus / Microsoft 365 landscape, simply reach out — we will take the time.