Back to Blog

    Microsoft 365

    Featured

    How präziis. builds Teams and SharePoint from Abacus data

    The präziis. architecture: provisioning via AbaConnect and Graph, per-field conflict rules, nightly reconciliation and permissions from Abacus roles.

    April 17, 20267 min read
    Marcel Haas

    Marcel Haas

    Solution Architect, CEO

    marcel.haas@cnext.ch
    CNEXT
    In this article

    präziis. automatically builds Teams, SharePoint sites and permissions from Abacus master data and keeps them in sync with Microsoft 365. Abacus remains the authoritative source for master data and Microsoft 365 the environment for collaboration; in between, an orchestrator translates events in the ERP into structures, permissions and metadata in the tenant.

    The basic idea: Abacus as the authoritative source

    Syncing lists is not enough: the business logic has to be carried consistently into both systems, from the first order through to archiving. The principle is therefore: master data belongs in the ERP; collaboration belongs in the digital workplace. Each system should do what it does best rather than copy the other's tasks:

    • Abacus is the authoritative source for customers, suppliers, projects, orders, employees, roles and cost centres.
    • Microsoft 365 is the leading environment for documents, communication, tasks and day-to-day collaboration.
    • präziis. ensures that relevant changes in the ERP lead to the right structure, permissions and metadata in the Microsoft tenant. In the other direction, selected Microsoft 365 activities flow back into the ERP as signals.

    A five-layer architecture

    1. 1Connector layer: connects Abacus through the AbaConnect web services and Microsoft 365 through Microsoft Graph and the SharePoint APIs.
    2. 2Domain model: brings Abacus objects (customer, order, project, employee) and Microsoft 365 objects (team, site, channel, library) together in a shared data model.
    3. 3Orchestrator: translates incoming events into workflows, such as ‘New order → team from template X, site with design Y, permissions from role Z’.
    4. 4Governance and audit layer: naming conventions, lifecycle, retention, permission reviews and logging.
    5. 5Dashboard and API: IT, business departments and third-party systems use it to query the status, intervene or trigger further workflows.

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

    Provisioning: from Abacus project to Microsoft team

    The most important workflow is automatic provisioning. In simplified form, 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 the matching provisioning template
       ├── creates Microsoft 365 group + team via Graph
       ├── configures channels, tabs and apps
       ├── sets up SharePoint site with site design
       ├── creates libraries, columns, views, metadata
       ├── sets permissions from the Abacus role model
       └── writes the link back to Abacus

    The new project in the ERP thus becomes a prepared workspace with the right people, the appropriate structure and the metadata from Abacus.

    Provisioning templates

    To make this work in any organisation, präziis. uses provisioning templates that you define per project type, client entity or business area. 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 become which Microsoft 365 groups
    • Lifecycle rules: when content is archived, deleted or frozen

    Templates are managed and versioned centrally and can be assigned to existing sites retrospectively. This matters when existing structures are brought in.

    Synchronisation: consistency in day-to-day operation

    Provisioning is only the start; ongoing synchronisation is the harder part. präziis. keeps master data, memberships and structures consistent with four mechanisms.

    1. Event-driven updates

    Changes in Abacus, such as a new contact person for a customer or a changed project role, are picked up through AbaConnect triggers or periodic delta polling and applied in Microsoft 365. In the other direction, Microsoft Graph change notifications send signals back from the tenant.

    2. Conflict rules per field

    What if someone changes a site title by hand? Or an address is corrected in Abacus while a site column was being maintained in SharePoint? präziis. declares for each attribute which system wins. Discrepancies are shown in the dashboard instead of being silently overwritten.

    3. Nightly reconciliation

    At defined intervals, typically nightly, präziis. compares the two systems and corrects discrepancies that have arisen between events. The reconciliation reports support audits and the further development of the data model.

    4. Lifecycle hooks

    When a project is closed or archived in Abacus, präziis. triggers the stored lifecycle: reduce access to read-only, apply the retention rule, move the site to an archive hub, archive the team. Once the retention period has expired, the defined deletion rule applies, and the step is logged.

    Permissions from Abacus roles

    Keeping permissions in SharePoint and Teams up to date is an ongoing task in growing environments. präziis. therefore does not assign permissions by hand but derives them from Abacus roles:

    • Project role in Abacus → Microsoft 365 group → team membership and site access.
    • When someone leaves the project or the company, their permissions are removed automatically across all derived structures.
    • External users such as customers and partners are modelled through separately managed guest roles, with expiry dates and re-approval workflows.

    Permissions are thus maintained along with the master data rather than in a separate project.

    Governance and audit

    präziis. is not just a provisioning tool but also a governance platform:

    • Audit log: who created, changed or deleted what, and when
    • Naming conventions: prohibited characters, length limits and client prefixes, defined declaratively
    • Versioned templates with migration paths for existing sites
    • Permission reviews: periodic, automatically generated reviews for site owners and compliance
    • Integration with Microsoft Purview: sensitivity labels, retention policies and DLP rules are applied automatically to the provisioned structures

    These building blocks are particularly relevant for regulated sectors such as fiduciary services, banking, healthcare and the public sector.

    Security and hosting in Switzerland

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

    • Zero Trust principles for all service access: managed identities, Conditional Access and Privileged Identity Management
    • Encryption at rest and in transit
    • Tenant separation at database, storage and configuration level

    Extensibility

    präziis. fits into your existing IT landscape. Three extension mechanisms are particularly relevant:

    1. 1Webhooks and a REST API to connect your own workflows or third-party systems such as CRM, time tracking or BI.
    2. 2Custom templates defined through configuration rather than code, so business departments can model new project types themselves.
    3. 3Additional connectors: besides Abacus, we can connect further ERPs, CRMs or industry systems as data sources where needed.

    What to settle before rollout

    An integration between an ERP and Microsoft 365 needs clear decisions. Before going live, these points should be settled:

    • Authoritative source: defined for each entity and field
    • Identity: stable keys, user mapping and rules for leavers or role changes
    • Synchronisation: direction, triggers, delay, conflict resolution, retries and manual correction
    • Operations: logs, monitoring, recovery, version compatibility and support boundaries
    • Data protection: transferred data, hosting, logs, backups, subprocessors, and contract and deletion rules under the Swiss Federal Act on Data Protection (FADP)

    Test the workflow first in an isolated environment with synthetic or approved data, and compare expected and actual permissions. A successful demo does not yet prove production operation.

    When präziis. is a good fit

    A conversation is worthwhile if one of these points applies to you:

    • Setting up a new project in Microsoft 365 takes more than half an hour of manual work.
    • Questions such as ‘Where do we store this?’ and ‘What is the folder called?’ keep coming up.
    • Permissions and memberships need to be current and traceable for audits.
    • Differences between Abacus and Microsoft 365 create reporting effort.
    • Your organisation is growing faster than structures can be built by hand.

    You can find out more about the product at praeziis.ch.

    Industry: Healthcare & Life Sciences

    CNEXT solutions for healthcare

    Compliance, digital QM and präziis intranet — explore all CNEXT reference projects in healthcare.

    Open healthcare hub
    CNEXT Products

    Explore all CNEXT products

    präziis is one of several CNEXT products. Explore our full product range — from healthcare intranets to AI-powered business tools.

    All products
    SchweizHealthcareTeamsMicrosoft 365GovernanceSharePoint
    Teilen:

    AI tools may have supported the creation of this article. CNEXT is responsible for the published content. Product features and prices can change; check the linked primary sources for current details.

    Marcel Haas

    Marcel Haas

    Solution Architect, CEO

    6x Microsoft Applied Skills

    Request a technical präziis. demo

    We show you präziis. and discuss the architecture for your Abacus and Microsoft 365 environment.