Supported7 min readUpdated June 5, 2026

Use Microsoft 365 discovery to load real SharePoint columns

Connect an account, enter the site URL, load lists and libraries, and import real column metadata into the mapping table.

Quick answer

In short

Microsoft 365 discovery reads list and library metadata from the destination site so mapping uses real SharePoint column names and types instead of inferred guesses.

Most likely cause

Wrong control types, missing dropdown choices, or bad save formulas often trace back to exporting before importing the real destination column inventory.

What to do next

Click Load lists and libraries, select the target, then import columns into mapping before reviewing Optional Settings.

What discovery reads

  • Accessible lists and libraries on the destination site.
  • List/library display names, URLs, IDs, and types.
  • Column display names, internal names, required flags, and column types.
  • Enough metadata to select SharePoint targets and improve field mapping.

What discovery does not guarantee

Discovery confirms metadata access, not that every end user has permission to edit list items or that every lookup list contains production rows. Still validate the generated app using an account that matches the intended maker or user permissions.

URL format

Use the site root URL for discovery, such as the site collection or subsite URL. Do not paste a list view URL into the destination site field unless the UI specifically asks for the list URL.

Keep reading the next most relevant guides for this form pattern.