# Migrating from Legacy to Enhanced Collaborative Authoring Configuration


<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: This article describes the process for customers who configured collaborative authoring prior to 25R1 to migrate from the legacy configuration to the enhanced configuration. To configure collaborative authoring in a new Vault, see <a href="/en/gr/56840/">Configuring Collaborative Authoring</a>.</p>
    </div>
  </div>
</div>



Beginning with 25R1, the collaborative authoring configuration is enhanced to allow Admins to configure collaborative authoring without requiring a Microsoft 365 service account. We recommend that customers with collaborative authoring configured prior to 25R1 migrate from the legacy configuration to the enhanced configuration. Beginning with 26R1, the legacy collaborative authoring configuration is no longer supported.

## Configuration Migration Overview

Migrating from the legacy configuration to the enhanced configuration follows this process in order:

1. [Update Entra ID Application Permissions][1]
2. [Grant Owner Role on the Existing SharePoint Team Site][2]
3. [Grant Access to the SharePoint Team Site using PowerShell][3]
4. [Update the Connection in Vault][4]

We have provided a <a href="/en/gr/56840/#powershell-script">PowerShell script</a> (`collab_auth_setup_script.ps1`) that can perform Step 3 above to simplify the process of granting permissions for your Entra ID application to manage the SharePoint team site. When running the script to migrate from the legacy configuration to the enhanced configuration, the script asks if you already have an Entra ID application and a SharePoint site. For these questions, enter **Y** and provide the requested information.

See <a class="download-link " href="https://platform.veevavault.help/assets/downloads/CollaborativeAuthoring_PowerShell_Script_Inputs_Apr2026.pdf" target="_blank" rel="noopener">this document<i class="fa fa-download" aria-hidden="true"></i></a> for details and screenshots about what information the PowerShell script prompts for.

## Updating Entra ID Application Permissions {#updating-permissions}

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: Complete this configuration in Entra ID as a SharePoint global admin.</p>
    </div>
  </div>
</div>



Update the below Entra ID application permissions. All new permissions need admin consent granted in Entra ID.

* Update your Entra ID application permissions to include the _Sites.Selected_ Application permission.
* If you are using the automatic invitation functionality for external users, add the _Directory.ReadWrite.All_ and _User.Invite.All_ Application permissions.
* If you are using automatic mentioning through collaborative authoring workflows, add the _User.Read.All_ Application permission.

## Granting the Owner Role on the Existing SharePoint Team Site {#granting-owner-role}

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: Complete this configuration in Entra ID as a SharePoint global admin.</p>
    </div>
  </div>
</div>



Add the SharePoint admin who will run the PowerShell script (`collab_auth_setup_script.ps1`) as an _Owner_ on the SharePoint team site.

## Granting Access to the SharePoint Team Site using PowerShell {#granting-sharepoint-access}

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: Complete this configuration in Entra ID as the SharePoint team site <em>Owner</em>.</p>
    </div>
  </div>
</div>



Download and run the provided PowerShell script (`collab_auth_setup_script.ps1`) to grant permissions for your Entra ID application to manage the SharePoint team site.

## Updating the Connection in Vault {#updating-vault-connection}

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: Complete this configuration in Vault as a <em>System Administrator</em> or <em>Vault Owner</em>.</p>
    </div>
  </div>
</div>



Update the connection between Vault and Microsoft 365:

1. Navigate to **Settings > General Settings > Checkout Settings**.
2. Click **Edit** in the _Collaborative Authoring with Microsoft Office_ section.
3. Select the **Remove Service Account from Collaborative Authoring** checkbox. The _Collaborative User_ field is removed from the configuration settings.
4. Enter the **Client Secret**. The _Integration Status_ changes to _Not Authorized_.
5. Click **Authorize** to reauthorize the collaborative authoring configuration. The _Integration Status_ changes to _Verified_.
6. Click **Save**.


### Demo: Migrating from Legacy to Enhanced Collaborative Authoring Configuration {#demo-migrating-from-legacy-to-enhanced-collaborative-authoring-configuration}


The following video demonstrates how to migrate from the legacy configuration to the enhanced collaborative authoring configuration:
<video controls width=860 height =504 poster="https://platform.veevavault.help/assets/images/posters/2025-migrating-legacy-enhanced-collab-authoring.png" preload="metadata">
    <source src="https://platform.veevavault.help/108e9b1d-559c-4d48-918b-1e4c5b5a533c/b0c67292-cc7d-45b6-b923-937134fd1798/b0c67292-cc7d-45b6-b923-937134fd1798_source__v.mp4" type="video/mp4" >
    
    <track
    label="English"
    kind="subtitles"
    srclang="en"
    src="/en/gr/assets/captions/25r3-updating-collaborative-authoring-legacy-v3.vtt"
    default />
    </video>

<a href="/en/gr/676811/">Details</a>


[1]: #updating-permissions
[2]: #granting-owner-role
[3]: #granting-sharepoint-access
[4]: #updating-vault-connection