Microsoft 365 DAM integration

What a Microsoft 365 DAM integration must do

A Microsoft 365 DAM integration must give office workers approved assets where they write documents and slides, and keep unapproved copies out of circulation.

The DAM integrations guide places Microsoft 365 among the other DAM connections. The DAM vs SharePoint and Google Drive guide explains why file shares do not replace a DAM. DAMSelection assessment: decide which Microsoft 365 surface each user group needs before the first demo.

The five Microsoft 365 integration surfaces

Microsoft 365 offers five documented integration surfaces, and each one serves a different user moment.

Microsoft 365 Copilot connectors add a sixth option for search. A full integration usually combines an Office Add-in for creators, a message extension for sharing and a Graph sync for brand images.

How the File Picker and Microsoft Graph work

The File Picker v8 and Microsoft Graph move files between OneDrive, SharePoint and the DAM under the user's or the app's permissions.

Fact: the File Picker v8 is a Microsoft-hosted page that the DAM opens in an iframe or a popup. The DAM posts a configuration to `FilePicker.aspx` and talks to the picker over a message channel. The picker sends `authenticate`, `pick` and `close` commands.

• The picker always uses delegated permissions, so a user sees only files that user can already open.
• The minimum read permission is SharePoint `MyFiles.Read`.
• On pick, the picker returns the item ID, the drive ID and a SharePoint endpoint. The DAM then requests the full file details.
• One picker instance works with OneDrive or with SharePoint, never both at once.

Microsoft Graph handles the file transfer. Fact: Microsoft recommends resumable upload sessions for files larger than 10 MiB. Each byte range must be a multiple of 320 KiB, and each request must stay under 60 MiB. Microsoft recommends fragments of 5 to 10 MiB.

Worked example: a 2 GiB video uploaded in 10 MiB fragments needs 205 requests. A 10 MiB fragment equals 32 blocks of 320 KiB, so it meets the rule.

Fact: the least privileged application permission for upload sessions is `Sites.ReadWrite.All`. Microsoft also states that app-only access cannot replace the content of a file protected by a sensitivity label.

SharePoint organization assets libraries

A SharePoint organization assets library shows approved images and Office templates inside Office apps, and a DAM can keep it filled with current renditions.

Fact: a tenant can register up to 30 organization asset libraries, all on the same site. Only document libraries qualify, never folders. Registration uses the PowerShell cmdlet `Add-SPOOrgAssetsLibrary`, and registration turns on a content delivery network, private by default.

Fact: Brand Images search uses image tags, file name, description and location. Microsoft warns that images over 10 MB slow search and download. Microsoft also advises against several formats and resolutions of the same image, because duplicates reduce search breadth.

DAMSelection assessment: let the DAM push one approved rendition per image into the library through Microsoft Graph, with tags and description mapped from the metadata schema. Staff then find brand images in PowerPoint, and the DAM stays the system of record.

Teams and Outlook message extensions

A Teams message extension lets users search the DAM from Teams and Outlook and insert the result as a card in a conversation or an email.

Fact: Microsoft documents two command types. Search commands query an external system and return a list of cards. Action commands open a form and insert a message after submission. A single message extension holds up to 10 commands.

Fact: search-based message extensions are generally available in Outlook, and action-based ones are in preview there. The app manifest must use version 1.16 or later.

DAMSelection assessment: the card should carry a governed DAM share link, with rights and expiry checked at click time. A card that embeds a downloaded copy creates the unmanaged file the DAM exists to prevent. Ask about the roadmap, because Microsoft now recommends agents for new work.

Office Add-ins in Word, PowerPoint and Excel

An Office Add-in opens a DAM panel inside Word, PowerPoint, Excel or Outlook, where users search and insert approved assets.

Fact: Office Add-ins use HTML, CSS and JavaScript and run on Windows, Mac, iPad and in the browser. Add-ins read and write documents through the Office.js APIs. COM and VSTO add-ins run only in Office on Windows and are unsupported in the new Outlook on Windows.

Admins deploy add-ins centrally in the Microsoft 365 admin center.

1. Open Settings, then Integrated apps, the portal Microsoft recommends for most organisations.
2. Choose a Microsoft Marketplace add-in or upload a custom manifest.
3. Assign it to everyone, to specific users or groups, or to the admin alone for testing.
4. Wait 24 to 72 hours for the add-in to appear on the ribbon.

Fact: Marketplace add-ins update automatically. Microsoft recommends the unified manifest for most scenarios, and that manifest deploys only through the integrated apps portal.

Search through Copilot connectors

Microsoft 365 Copilot connectors make DAM metadata findable in Microsoft Search and Copilot, without moving the files.

Fact: synced connectors index external content into Microsoft Graph. Federated connectors fetch content at query time through the Model Context Protocol and store nothing in Microsoft Graph. A schema holds up to 128 properties.

DAMSelection assessment: index asset title, description, tags and a governed link. Map item permissions to DAM access groups, because a connector is tenant-wide unless external item security is restricted.

The four depth levels for Microsoft 365

DAMSelection rates Microsoft 365 integration depth on the same four levels as every other platform, per surface.

Vendor ratings appear on vendor profiles once verified. The integrations overview explains the scale for all platforms.

What to test in a Microsoft 365 demo

A Microsoft 365 demo tests each planned surface in a test tenant with the buyer's assets. Add these steps to the scripted demo.

1. Show the permissions each app requests in Microsoft Entra ID and who must consent.
2. Insert an approved image into a PowerPoint slide from the DAM add-in, on Windows and on the web.
3. Search the DAM from Teams and post the result as a card.
4. Open the card link as a user without DAM access and show the result.
5. Import 20 files from a SharePoint library through the File Picker, with metadata.
6. Push 200 approved renditions into an organization assets library and find one in Brand Images.
7. Expire the rights on one image and show its removal from the library.
8. Upload a 2 GB video from SharePoint to the DAM and show the resumable transfer.
9. Show the usage report of assets inserted through each surface.

The Demo Script Generator formats the steps as a scenario.

Common failure points

Microsoft 365 DAM integrations fail at five points that a buyer checks before signature.

• Downloaded copies: inserted files without a link back leave no usage trail or expiry control.
• Consent gaps: application permissions need tenant admin consent and a security review.
• Rollout delay: add-ins take 24 to 72 hours to appear, asset libraries up to 24 hours.
• Platform gaps: Word and Excel on the web show no organization assets library.
• Oversized files: images over 10 MB slow Brand Images search.

Questions for the DAM vendor

The buyer sends these questions in writing before the demo and asks for documentation with each answer.

1. Which Microsoft 365 surfaces does the vendor support, and who builds each one.
2. Which manifest does the Office Add-in use, and is it listed in Microsoft Marketplace.
3. Which Microsoft Graph and SharePoint permissions does each component request, delegated or application.
4. Does the add-in insert a file, a link or both, and how does it record usage.
5. How does the sync to an organization assets library handle updates and expiry.
6. How are usage rights checked when a shared link is opened.
7. What does the integration cost, and is it priced per user or per tenant.