15.2 SharePoint & OneDrive Document Management Integration

SharePoint & OneDrive Document Management Integration

While Microsoft Dataverse is optimized for relational business data, transactional processes, and process automation, enterprise business records (such as Accounts, Contracts, Proposals, and Support Cases) require robust document management capabilities including version control, co-authoring, large file storage, check-in/check-out workflows, and granular document lifecycle management. Microsoft Dataverse delivers this through Server-based SharePoint Integration and OneDrive for Business Integration. On the PL-200 exam, functional consultants must understand how to enable server-based integration, configure folder hierarchies, navigate the underlying document entity model, embed document grids on model-driven forms, and manage the critical security boundary between Dataverse and SharePoint.

---

1. Architecture of Server-Based SharePoint Integration

Server-based SharePoint Integration establishes a direct, secure server-to-server (S2S) connection between Microsoft Dataverse and SharePoint Online (or SharePoint On-Premises) using Microsoft Entra ID authentication.

+-----------------------------------------------------------------------------------+
|              SERVER-BASED SHAREPOINT INTEGRATION ARCHITECTURE                     |
|                                                                                   |
|  +---------------------------+             +-----------------------------------+  |
|  |    MICROSOFT DATAVERSE    |             |     MICROSOFT SHAREPOINT ONLINE   |  |
|  |                           |  Microsoft  |                                   |  |
|  |  +---------------------+  |  Entra S2S  |  +-----------------------------+  |  |
|  |  | SharePoint Site     |  |    OAuth    |  | SharePoint Site Collection  |  |  |
|  |  | (Base URL & Status) |<==============>|  | (e.g. /sites/CRMDocuments)  |  |  |
|  |  +----------+----------+  |             |  +--------------+--------------+  |  |
|  |             | (1:N)       |             |                 |                 |  |
|  |  +----------v----------+  |             |  +--------------v--------------+  |  |
|  |  | SharePoint Document |  |  REST / CSOM|  | Document Libraries:         |  |  |
|  |  | Location            |<==============>|  | - /account                  |  |  |
|  |  | (Relative URL &     |  |             |  |   - /Contoso_GUID           |  |  |
|  |  |  RegardingObjectId) |  |             |  |     - /opportunity          |  |  |
|  |  +----------+----------+  |             |  |       - /Project_Apollo_GUID|  |  |
|  |             |             |             |  +-----------------------------+  |  |
|  |  +----------v----------+  |             +-----------------------------------+  |
|  |  | Model-Driven App Form| |                               ^                    |
|  |  | - Related -> Docs   | |                               |                    |
|  |  | - Embedded Subgrid  |=================================|                    |
|  +---------------------------+       Office Online / Direct File Access           |
+-----------------------------------------------------------------------------------+

Why Server-Based Integration?

Legacy SharePoint integration relied on client-side authentication and the Microsoft Dynamics CRM List Component (an ActiveX/sandbox solution). Modern Server-based integration provides distinct architectural advantages:

• No Client Footprint: Operates entirely at the cloud server tier; users do not need special browser extensions, ActiveX controls, or local client software.
• Modern Authentication: Authenticates seamlessly via Microsoft Entra S2S tokens, eliminating prompt loops and third-party cookie restrictions.
• Full Device Parity: Delivers identical document management capabilities across web browsers, tablets, and the Power Apps mobile app.
• Office Online Co-Authoring: Enables users to open, view, and co-author Word, Excel, and PowerPoint documents directly inside model-driven apps via Office Online.

The Dual-Security Model (Crucial Exam Concept)

Dataverse and SharePoint maintain completely separate security models:

• Dataverse Security: Governs whether a user can see, create, edit, or delete a Dataverse record (e.g., an Account or Opportunity).
• SharePoint Security: Governs whether a user has permissions (Read, Edit, Full Control) on the underlying SharePoint site, library, or folder.

[!WARNING] Exam Trap - Permissions Synchronization: Dataverse does not synchronize security roles or record ownership to SharePoint folder permissions by default. If a user has Read/Write permissions on an Account record in Dataverse but has no access to the connected SharePoint site, clicking the "Documents" tab will throw a SharePoint Access Denied (403) error. Both Dataverse privileges and SharePoint permissions must be granted to the user independently.

---

2. Configuration Workflow in Power Platform Admin Center

Setting up SharePoint integration involves three sequential configuration stages:

+-----------------------------------------------------------------------------+
|                   SHAREPOINT INTEGRATION CONFIGURATION FLOW                 |
|                                                                             |
|  [1. ENABLE INTEGRATION]     [2. RUN DOC MGMT WIZARD]  [3. FOLDER STRUCTURE]|
|  PPAC -> Settings ->         Select entities to enable  Choose Default flat |
|  Integration -> Document     (Account, Contact, Lead,   structure OR check  |
|  management settings ->      Opportunity, Custom) and   'Based on entity'   |
|  Enable Server-based         specify SharePoint Site    (Account / Contact  |
|  SharePoint Integration.     URL.                       hierarchy).         |
+-----------------------------------------------------------------------------+

Step 1: Enable Server-Based SharePoint Integration

1. In the Power Platform Admin Center (PPAC), navigate to Environments -> [Select Environment] -> Settings -> Integration -> Document management settings.
2. Click Enable Server-based SharePoint Integration.
3. Choose whether SharePoint is Online or On-Premises.
4. Enter the SharePoint Site Collection URL (e.g., https://contoso.sharepoint.com/sites/sales).
5. The system validates the URL and executes a server-to-server handshake via Microsoft Entra ID.

Step 2: Document Management Settings Wizard

Once server-based integration is active, run the Document Management Settings wizard:

1. Select the tables to enable for document management (e.g., Account, Contact, Lead, Opportunity, Incident/Case, and any custom tables).
2. Specify the default SharePoint Site URL.
3. Configure the Folder Structure strategy.

Step 3: Folder Structure Selection (Flat vs. Hierarchical)

The wizard presents a pivotal architectural decision: whether to structure folders flatly per entity or hierarchically based on parent Account or Contact records.

+-----------------------------------------------------------------------------+
|                     FOLDER STRUCTURE STRATEGY COMPARISON                    |
|                                                                             |
|  FLAT (DEFAULT ENTITY-CENTRIC):                                             |
|  /sites/sales/                                                              |
|  ├── /account/                                                              |
|  │   └── /Contoso Corporation_B4E1/ -> [Account Files]                      |
|  ├── /opportunity/                                                          |
|  │   └── /Project Apollo_89F2/      -> [Opportunity Files]                  |
|  └── /incident/                                                             |
|      └── /Case 1042_31C0/           -> [Case Files]                         |
|                                                                             |
|  HIERARCHICAL (ACCOUNT-BASED):                                              |
|  /sites/sales/                                                              |
|  └── /account/                                                              |
|      └── /Contoso Corporation_B4E1/                                         |
|          ├── [Account Direct Files]                                         |
|          ├── /opportunity/                                                  |
|          │   └── /Project Apollo_89F2/ -> [Opportunity Files]               |
|          └── /incident/                                                     |
|              └── /Case 1042_31C0/      -> [Case Files]                      |
+-----------------------------------------------------------------------------+

[!IMPORTANT] Folder Name Format: SharePoint folder names generated by Dataverse follow the naming convention: [Record Name]_[Record GUID without hyphens] (e.g., Contoso Ltd_7a2e8c84d67341e2b5e28a491d904721). The GUID suffix ensures folder names remain globally unique in SharePoint even if two Dataverse records have identical names.

---

3. The Dataverse Document Entity Architecture

Behind the user interface, Dataverse manages SharePoint connections using two core tables:

+-----------------------------------------------------------------------------+
|                   DATAVERSE DOCUMENT MANAGEMENT DATA MODEL                  |
|                                                                             |
|  +-----------------------------------------------------------------------+  |
|  |                       SharePoint Site (`sharepointsite`)              |  |
|  |  - `absoluteurl`: Base URL of SharePoint site collection              |  |
|  |  - `isdefault`: True for primary organization site                     |  |
|  |  - `statuscode`: Validation status (Succeeded / Failed)               |  |
|  +-----------------------------------+-----------------------------------+  |
|                                      | 1:N                                  |
|                                      v                                      |
|  +-----------------------------------------------------------------------+  |
|  |             SharePoint Document Location (`sharepointdocumentlocation`)|
|  |  - `parentsiteorlocation`: Lookup to `sharepointsite` OR parent       |  |
|  |                           `sharepointdocumentlocation`                |  |
|  |  - `relativeurl`: Folder or library path name (e.g., 'account')        |  |
|  |  - `regardingobjectid`: Polymorphic lookup to target record           |  |
|  |                         (e.g., Account, Opportunity, Case)             |  |
|  |  - `locationtype`: General (0) / Dedicated (1)                        |  |
|  +-----------------------------------------------------------------------+  |
+-----------------------------------------------------------------------------+

1. sharepointsite Table

• Stores the base URL and connection parameters for each integrated SharePoint site collection or subsite.
• Contains a Validate action on the command bar that tests server-to-server connectivity and marks the status as Succeeded or Failed.
• Multiple site records can exist (e.g., Sales Site, Legal Site, Support Site).

2. sharepointdocumentlocation Table

• Represents a specific folder or document library in SharePoint linked to a Dataverse record.
• Utilizes a recursive parent-child hierarchy via the parentsiteorlocation lookup:
  • The root location for a table (e.g., account) points to the sharepointsite.
  • An individual record location (e.g., Contoso_B4E1) points to the table root location (account) as its parent.
  • In a hierarchical structure, a child opportunity location points to the parent Contoso_B4E1 document location.
• The regardingobjectid polymorphic lookup establishes the direct relationship to the specific Dataverse row.

On-Demand Folder Provisioning

A vital architectural characteristic tested on the exam is On-Demand Provisioning:

• Creating a new Account or Opportunity record in Dataverse does not immediately create a folder in SharePoint.
• The SharePoint folder and corresponding sharepointdocumentlocation record are created only when a user navigates to the "Related -> Documents" tab or interacts with an embedded document subgrid on that specific record for the very first time.

---

4. Document Management Experience in Model-Driven Apps

Once configured, users interact with SharePoint documents directly within model-driven forms through the Related -> Documents navigation item or an embedded Document subgrid.

+-----------------------------------------------------------------------------+
|                   MODEL-DRIVEN FORM: DOCUMENT COMMAND BAR                   |
|                                                                             |
|  [+ New]  [Upload]  [Check Out]  [Check In]  [Discard Check Out]  [Edit Loc]|
|  -------------------------------------------------------------------------  |
|  NAME                  MODIFIED           MODIFIED BY       VERSION         |
|  Proposal_v2.docx      10 mins ago        Sarah Connor      2.1             |
|  Master_Agreement.pdf  Yesterday          John Doe          1.0             |
|  Cost_Model.xlsx       Aug 14, 2026       Alex Smith        3.0 (Checked Out)|
+-----------------------------------------------------------------------------+

Supported Document Operations

• New: Instantly create a new Word, Excel, PowerPoint, or OneNote notebook directly in the linked SharePoint folder.
• Upload: Upload one or multiple files from the local computer.
• Check Out / Check In: Lock a document in SharePoint to prevent concurrent overwrites by colleagues while editing, and check in a new version with comments when finished.
• Version History: Inspect historical revisions, view previous drafts, and restore earlier versions.
• Open in SharePoint: Launch the native SharePoint document library interface in a new browser tab.
• Edit in Office Online / Desktop: Open documents for real-time collaborative editing in Word/Excel Online or full desktop applications.
• Edit Location / Add Location: Point the record to an existing SharePoint folder or link multiple document locations across different sites to a single Dataverse record.

---

5. OneDrive for Business Integration

In addition to collaborative SharePoint team libraries, Dataverse supports OneDrive for Business Integration.

Architectural Purpose & Mechanics

• Personal Working Space: While SharePoint is designed for shared, collaborative team documentation, OneDrive for Business is designed for private, personal working documents.
• Storage Location: Files uploaded via the OneDrive tab are stored in the user's personal OneDrive for Business storage account under OneDrive/CRM/[EntityName]/[RecordName_GUID].
• Privacy Boundary: By default, files stored in OneDrive for Business are private to the individual user who uploaded them. Other Dataverse users cannot view the file unless the owner explicitly shares it from their OneDrive interface.

Enabling OneDrive for Business

1. In PPAC, navigate to Settings -> Integration -> Document management settings.
2. Click Enable OneDrive for Business.
3. Prerequisite: Server-based SharePoint Integration must be enabled first before OneDrive for Business can be activated.