DDM HelpOneDrive
With the OneDrive system type, DDM fetches the files from one particular person's OneDrive for Business – all of it or from a folder within it. That suits a department that keeps its material in the OneDrive of a shared account, such as marketing@company.com. For files a team maintains together, SharePoint is usually the better source.
As with SharePoint, DDM signs in as an app that you register in your Microsoft Entra ID. The person does not have to do anything or sign in anywhere.
1. Register DDM in Entra ID
Proceed as for SharePoint: register the app, note the Application (client) ID and the Directory (tenant) ID, create a client secret and copy its Value.
Under API permissions, choose Files.Read.All under Microsoft Graph › Application permissions and grant admin consent. If you have already registered the app for SharePoint, you can use the same one and add Files.Read.All there.
2. Add the source in DDM
Under Settings › External sources, add a source with New source, give it a name and choose OneDrive as the System type.
| Field | What to enter |
|---|---|
| User (sign-in name) | The sign-in name of the person whose OneDrive is read, e.g. marketing@company.com |
| Directory (tenant) ID | The app's Directory (tenant) ID |
| Client ID | The app's Application (client) ID |
| Client secret | The client secret's Value – stored encrypted, never shown again |
| Folder (optional) | A folder in the OneDrive from which files are taken over, e.g. /Catalogues. Empty = the whole OneDrive |
3. Test the connection
Click Test connection. DDM gets an access token from Microsoft and opens the person's OneDrive.
| Message | What to do |
|---|---|
| Connected — “…” is readable. | All good – DDM names the OneDrive it found. |
| Details are still missing — the site URL or user, the directory ID and the client ID. | The user, directory ID or client ID is missing. |
| Microsoft rejected the app — check the client ID, the directory ID, the client secret (expired?) and the admin consent. | Microsoft refused the app: the client secret is wrong, missing or expired, the IDs are swapped, or admin consent for Files.Read.All is missing. |
| The site, user or folder was not found — check the details and whether the app may access them. | The person or the folder was not found – a typo in the sign-in name, or the person has no OneDrive yet. A OneDrive only comes into being once they have opened it (or IT provisions it in advance). |
| The address does not answer — check the URL, the port and the firewall. | The DDM server cannot reach Microsoft – allow outgoing connections to login.microsoftonline.com and graph.microsoft.com. |
4. Import scope and sync
Under Import scope, decide how folders become categories and which files count, sync once with Sync now and switch on Source active – see Overview.
What applies to OneDrive:
- DDM takes over all files from the given folder, in sub-folders too.
- A file is recognised by its path. Renamed or moved, it becomes a new document in DDM; the old one stays.
- DDM does not take over sharing from OneDrive – who sees a document is governed by the category's permissions.
- If the person leaves and their account is deleted, their OneDrive is gone too: the sync then reports The site, user or folder was not found. The documents already taken over stay in DDM.