web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Power Automate "Get fi...
Power Automate
Suggested Answer

Power Automate "Get file" action not showing OneDrive root files

(0) ShareShare
ReportReport
Posted on by

Hi community,

I’m facing an issue with Power Automate when working with OneDrive for Business.

I’m using the "Get file" (or similar file-related actions), and when I try to browse files, the connector does not display any files located in the root directory of my OneDrive. The folder appears empty, even though I do have files stored there.

Details:


  • Connector: OneDrive for Business

  • Issue: Root directory does not show any files when selecting file path

  • Files are visible in OneDrive web

  • Subfolders sometimes appear, but root files do not

  • This happens when using the file picker UI
 

What I’ve tried:


  • Confirmed files exist in OneDrive

  • Refreshed connection

  • Tested with different flows

  • Tried re-authenticating the connection
Screenshot 2026-0...

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:
I have the same question (0)
  • Suggested answer
    Sunil Kumar Pashikanti Profile Picture
    2,318 Moderator on at
     
    This is a known quirk with the OneDrive for Business connector.
    The file picker UI does not reliably show files in the root directory, even though they exist. This is a UI limitation, not a permissions or connection issue.
     
    Workarounds:
    1. Use “Enter custom value” with path
    Instead of browsing, enter the path manually:
         /YourFileName.xlsx
    Make sure you use the “Get file content using path” action when passing a path.

    2. Move the file to a folder
    Files in subfolders are picked up consistently. Moving the file into a folder (for example /Automations/) usually resolves the issue.

    3. Use “List files in root folder”
    Add this action, then pass the Id or Path dynamically into the next step.

    4. Use file Id directly
    If the file comes from a previous step, avoid the picker and use the Id from dynamic content.
     
    Summary:
    This is a file picker limitation with root files. Using path-based actions or organizing files into folders is the most reliable approach.
  • chiaraalina Profile Picture
    2,425 Super User 2026 Season 1 on at
     
    Please add the screenshot directly.
     
    Thanks!
  • Suggested answer
    RaghavMishra Profile Picture
    261 on at

    Hi CG-25062141-0,

    Thanks for the detailed write-up - the fact that subfolders sometimes appear but root files don't, while everything is visible in OneDrive web, points to the file-picker behavior rather than your files actually being missing. Here's what I'd check and the most reliable way around it.

    Use the path instead of the picker

    The dynamic file-picker (the folder-browse UI) is convenient but can be inconsistent about what it enumerates. The robust pattern is to not depend on the picker at all:

    • Switch the action to enter the path manually (most file actions let you toggle to type the path), or use a path-based action and supply the file's path/identifier directly.
    • You can get the exact identifier/path first with "Get file metadata using path", then feed that into "Get file content".

    Rule out a policy blocking enumeration

    Microsoft documents that certain tenant policies can prevent the OneDrive for Business connector from accessing/enumerating content, including:

    • "Prevent file download" (the connector relies on downloading file content, so this can block it),
    • Conditional/unmanaged-device controls, and
    • Network-location-based access controls.

    If any of these are enabled, the connector may show partial results. Worth checking with your admin if the path-based approach still misbehaves.

    Other quick checks

    • Confirm the connection is authenticated to the same account/tenant where the files live (cross-tenant and multi-geo access aren't supported).
    • Try a fresh connection reference rather than just refreshing the existing one.

    One honest caveat

    Microsoft Learn documents the OneDrive for Business connector's known limitations (file-size skips, Copy File timeouts, policy-based access blocks, cross-tenant/multi-geo restrictions), but it does not specifically document a "Get file picker hides root-level files" symptom. So the picker-vs-path guidance above is grounded in the connector's documented behavior and limitations, not in a single Learn page describing this exact issue - if the path-based approach doesn't resolve it, this may be worth raising with Microsoft support.

    Reference

    Found this helpful? Please mark ✅ "Does this answer your question?" so others searching for the same issue can find it quickly. A 👍 on "Was this reply helpful?" or a ♥ Like is also much appreciated!

    Raghav Mishra - LinkedIn | PowerAI Labs

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Valantis Profile Picture

Valantis 377

#2
11manish Profile Picture

11manish 279

#3
David_MA Profile Picture

David_MA 234 Super User 2026 Season 1

Last 30 days Overall leaderboard