Dataverse

    Dataverse: one data foundation for apps, flows and agents.

    The technician closes the job on the tablet, a flow informs the customer, and the agent answers the follow-up question from the same record. We build your data foundation in Dataverse, so apps, flows and agents work with the same data and roles.

    For teams whose lists in Excel and SharePoint have grown along with the business.

    • Microsoft Dataverse
    • Power Apps
    • Power Automate
    • Copilot Studio
    • Model Context Protocol
    • Microsoft Purview
    In a cheese cellar in the Emmental a cheesemaker records the numbered wheels in Dataverse on a laptop, a case with the CNEXT logo under the table
    01

    SharePoint list or Dataverse

    A SharePoint list carries simple capture with a few fields. Dataverse fits when data has relationships, roles see different records, changes must be traceable or apps, flows and agents use the same data. We decide that from your workflow and the roles that work with it.

    02

    Tables, roles, rules

    We model tables, relationships and choice fields, define security roles and business rules and set up the audit trail. Through solutions, the model moves into test and production in a controlled way. The building blocks:

    • Data modelTables, relationships, choice fields and descriptions in the terms of your business team.Result: apps, reports and agents mean the same thing by an order.
    • SecurityBusiness units, teams and security roles per record, plus column security for confidential fields.Result: every role sees and changes exactly the records it is entitled to.
    • Audit trailChanges with person, time and old and new value, available in Dataverse.Result: you can show who changed what and when.
    • Transfer and connectionData from Excel, SharePoint or the ERP carried over with an inventory comparison, virtual tables for data that stays in the business system.Result: every value has one leading system.
    • Agents through MCPCopilot Studio and approved clients such as GitHub Copilot or Claude reach the tables through the Dataverse MCP server, with the rights of their role.Result: agents read and write under the same rules as your apps.
    03

    Licences, storage, ownership

    Anyone working with Dataverse data needs a premium licence such as Power Apps Premium, and the tables use database, file and log storage in your tenant; we check both before the first step. Bring the terms of your business team: what an order, a customer or an asset is and which details belong to it. We clarify which roles see and change which records, where master data comes from and who owns the data model.

    04

    Checked with real roles

    Test users work in their roles and see exactly the records they are entitled to. We check required fields, business rules, the audit trail and the transfer of legacy data with an inventory comparison, and we let an agent with a restricted role read and write. A documented data model and a person who owns it are part of the handover.

    What you receive from us

    The data model, before anything is built.

    Before the first app is built, you receive the data model for approval: which tables, where the data comes from and who may write what. Shown here as a sample with invented details.

    Data model

    Sample

    Data model, service orders

    Customer
    Muster AG, Bern (fictional)
    Environment
    Muster Service (production), managed environment
    As of
    20 October 2026
    Data sources
    Three SharePoint lists and one Excel file
    • 7tables
    • 4security roles
    • 18’600records migrated
    • 4applications on the same base

    Summary

    Orders, customers, devices and spare parts live today in three SharePoint lists and one Excel file. The model brings them into seven tables; relationships link order, device and customer, so every detail is maintained in one place. The technician app, two flows and the customer question agent work with the same data. Four roles set who sees what: technicians see their own orders, the agent reads orders and devices and only creates questions.

    TableContentSourceWrite access
    OrderService order with status, date and reportSharePoint list OrdersDispatch, technicians (own)
    CustomerCompany, site, service contractSharePoint list CustomersDispatch
    ContactContact person at the customerSharePoint list CustomersDispatch
    DeviceSerial number, model, service intervalSharePoint list DevicesDispatch, technicians
    Spare partItem and stock levelExcel file Spare partsWarehouse
    Parts usedSpare parts per orderNewTechnicians (own)
    QuestionA customer question and the agent's answerNewAgent (create only)

    To settle before building

    • Licences: the twelve technicians need Power Apps Premium; the order runs through your licensing partner.
    • The SharePoint lists stay readable for three months after migration and are then archived.

    Next steps

    After your approval we build the tables in the test environment and check every role with real accounts before any data is migrated.

    Samples with invented details for a fictional Muster AG.

    Sound familiar? Tell us where you stand today.

    Contact

    What's new.

    As of: October 2026

    • As of 5 June 2026

      Agents reach Dataverse through an MCP server.

      For Copilot Studio, the Dataverse MCP server is switched on in every environment; admins enable further clients such as GitHub Copilot or Claude one by one. Since 15 December 2025, the tools are charged in Copilot Credits when agents outside Copilot Studio use them.

      Source: Microsoft Learn: Connect to Dataverse with MCP
    • Since May 2026

      Audit events in Purview no longer contain old and new field values.

      Purview still receives who changed which table and when. The values before and after the change come from the Dataverse audit trail through its own interfaces. We move reports and rules that depend on these values over to Dataverse.

      Source: Microsoft Learn: Important changes coming in Power Platform
    • Since 6 January 2026

      Your own keys run through customer-managed keys.

      Microsoft no longer supports the BYOK feature; environments that were not migrated use Microsoft-managed keys again. With customer-managed keys, the key sits in your Azure Key Vault, and the environment must be a managed environment.

      Source: Microsoft Learn: Manage your customer-managed encryption key

    Data foundations that carry the load today.

    School master data from SAP, Excel and Access in one place for the Canton of Bern, heat-box units with service history at AEW, customers and projects with external partners at AEW myHome and building data at AEW.

    Before your data moves to Dataverse.

    Do our SharePoint lists stay?

    Yes, where they carry simple capture with few relationships, such as a booking list. Data moves to Dataverse when tables are related, roles apply per record, a history is needed or the data volume grows. We decide that per list from the data model of your workflow.

    How is storage counted?

    Dataverse distinguishes database, file and log storage. Licences add storage to a shared tenant pool, and the Power Platform admin centre shows consumption per environment. We estimate the need before the transfer and decide which attachments are better kept in SharePoint.

    Can agents work directly with Dataverse?

    Yes, through the Dataverse MCP server. Agents from Copilot Studio use it without further activation; your admins enable other clients such as GitHub Copilot or Claude per environment, and outside Copilot Studio the access consumes Copilot Credits. Deleting tables or records requires explicit approval.

    Does ERP data have to be copied?

    Not necessarily. Virtual tables show data from the business system in Dataverse without storing it; this fits master data that the ERP leads. Where apps need the data offline or calculate a lot with it, we sync it with a flow. We record per table which system leads.

    How do we prove changes for an audit?

    With the Dataverse audit trail, which records the person, the time and the old and new value. Since May 2026, Microsoft Purview receives only who changed which table and when, without the field values. We agree retention and access to the history with your compliance team.

    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.