Understanding How to Configure a SharePoint Data Source in CDEAdminTools

1. Introduction

A SharePoint Data Source in CDEAdminTools allows you to synchronize folders and documents between Autodesk and a SharePoint site.
Before creating synchronization projects, you first need to configure the connection to SharePoint so CDEAdminTools can securely access your documents.

This article explains what each required field means, why it is needed, and provides links to the guided tutorials (Scribe) where users can see exactly how to obtain each value.

This is not a step-by-step guide — it is an overview to help you understand the configuration process.

2. What You Need to Configure a SharePoint Data Source

When adding a new SharePoint Data Source, CDEAdminTools will ask you for the following fields:

1. Name

2. Application (Client) ID

3. Application Secret

4. Tenant ID

5. Site ID

Below you will find an explanation of what each value represents and where it comes from.

3. Field Explanations

1. Name (Custom Identifier)

This is a friendly name chosen by the user.
It helps you identify this Data Source among others you may configure.

Examples:

• “Corporate SharePoint Repository”

• “Client A – SharePoint Files”

• “Engineering Documents Site”

This field is free and fully customizable.

2. Application (Client) ID

This is the unique identifier of your Azure App Registration.
CDEAdminTools uses this ID to know which application is requesting access to SharePoint.

It is required because SharePoint Online (Microsoft Graph) only allows access through a registered Azure AD application.

➡️ How to obtain it:
Follow this Scribe tutorial:
https://scribehow.com/viewer/Registrar_Aplicacion_en_Azure__uDpmroQERya0IOZClstnSw

3. Application Secret

This is the password (secret) associated with your Azure App Registration.
It is used together with the Application ID to authenticate CDEAdminTools when connecting to SharePoint.

Treat it as a credential: keep it secure and private.

➡️ How to obtain it:
Also included in the same Scribe tutorial above:
https://scribehow.com/viewer/Registrar_Aplicacion_en_Azure__uDpmroQERya0IOZClstnSw

4. Tenant ID

This identifies your Microsoft 365 tenant (your organization’s identity on Azure).
SharePoint Online is tied to your tenant, so CDEAdminTools needs this value to authenticate correctly.

➡️ Where to find it:
It is shown in the Azure App Registration tutorial:
https://scribehow.com/viewer/Registrar_Aplicacion_en_Azure__uDpmroQERya0IOZClstnSw

5. Site ID

This identifies the specific SharePoint site you want to synchronize.
A SharePoint tenant may contain many sites — CDEAdminTools needs to know exactly which one to connect to.

You must obtain the Site ID of the root folder or site you intend to use for the Sync Project.

➡️ How to obtain it:
See this Scribe tutorial using Microsoft Graph Explorer:
https://scribehow.com/viewer/Use_Graph_Explorer_to_Get_SharePoint_Site_ID__PxYze0-VQgSdi7NcEsbnKw

4. How These Fields Work Together

Once these fields are provided:

• The Application ID + Secret allow CDEAdminTools to authenticate using Microsoft Graph.

• The Tenant ID ensures authentication happens against your organization’s environment.

• The Site ID indicates which SharePoint site will act as the external source or destination during synchronizations.

In summary, these values:

• Establish a secure communication channel

• Allow CDEAdminTools to locate your SharePoint site

• Enable folder and document synchronization

• Preserve versioning (if your SharePoint library supports it)

5. What Happens After Configuring the Data Source?

After the SharePoint Data Source is created:

1. You will be able to select it inside a Sync Project

2. You can choose a root folder inside the SharePoint site

3. The system will be able to synchronize documents and folders with Autodesk

4. Depending on your Sync Project configuration, synchronization may be:

   • Autodesk ➝ SharePoint

   • SharePoint ➝ Autodesk

   • Bidirectional (mirror mode)

This completes the connection between Autodesk and your SharePoint environment.