Forum Discussion

thaisstefani18_'s avatar
thaisstefani18_
Frequent Visitor
5 months ago
Solved

Mirrored SharePoint List (Preview) - “Failed to get document libraries” Error 404

Hello everyone,

I’m exploring the Mirrored SharePoint Online List (preview). I ran a test with a small list and it has been replicating changes correctly. However, I keep seeing the error 'led to get document libraries. Request failed with status code 404, x-ms-root-activity-id: …' on the screen.

Could this be happening because the feature is still in preview?



Thank you

  • Hi Tamanchu 

    I managed to finalize yesterday an approach with the pipeline:

    • LookupOldWatermark: reads the last processed date from the DW.
    • Copy Activity: filters the SharePoint List using OData between the previous watermark and the TriggerTime, writing Parquet to the Lake House.
    • Notebook: performs a MERGE of the Parquet into the Delta table using Id as the key, UPDATE if it exists, INSERT if it’s new. Returns the MAX(Modificado) of the processed data.
    • SP UpdateWatermark: saves the MAX(Modificado) as the new watermark for the next run.

     A separate Copy Job was used to perform the initial full load, outside of the pipeline.

    Thanks for your attention 🙂

     

7 Replies

  • Hi thaisstefani18_ ,

    The "Failed to get document libraries. Request failed with status code 404" error in the Mirrored SharePoint List feature is typically caused by one of the following:

    1. Permissions issue Make sure the account you're using has at least Site Member (Edit) permissions on the SharePoint site. The Mirroring feature needs access to both the site and its document libraries. Check that:
    • You have access to the SharePoint site directly (try opening it in a browser)
    • The site URL is correct and not pointing to a subsite or hub site that redirects

        2. Preview limitations Since Mirrored SharePoint List is still in Preview, there are known limitations:

    • It may not work with all SharePoint site types (e.g., classic sites vs. modern sites)
    • Some tenant-level settings might block the API calls that Fabric uses behind the scenes
    • The feature requires the SharePoint site to be in the same tenant as your Fabric Workspace

    3. Site URL format. Ensure you're using the correct format. The URL should be the root site URL (e.g., https://yourtenant.sharepoint.com/sites/yoursite), not a direct link to a list or library.

     

    4. Admin consent Your SharePoint admin may need to grant consent for Fabric to access SharePoint APIs. Check with your admin if there are any conditional access policies or API restrictions in place.

    Since this is a Preview feature, I'd also recommend opening a support ticket with Microsoft to report the 404 error it could be a bug they need to investigate.

     

    Let me know if any of these suggestions help! give a kudo 😉

     

    • thaisstefani18_'s avatar
      thaisstefani18_
      Frequent Visitor

      Hello Tamanchu 
      Thank you for your time 🙂
      Permissions and access are all correctly configured.
      I will continue to monitor this feature until it reaches GA and will consider opening a ticket with Microsoft.

  • v-prasare's avatar
    v-prasare
    Community Support
    Thank you for confirming that you’ve raised a support ticket. Please share any updates here as they become available, as this will help other community users who may be experiencing a similar issue.
  • Hi thaisstefani18_ 

    Opening a support ticket is a good idea the more feedback Microsoft gets on this Preview feature, the faster it will improve.

    In the meantime, if you need a working solution right now, here are two alternatives that work well in production:

    1. OneLake Shortcut to SharePoint Instead of Mirroring, you can create a shortcut from your Lakehouse directly to the SharePoint document library. This gives you read access to the files without the Mirroring preview limitations.
    2. Pipeline with Copy Activity Set up a Data Factory pipeline that pulls data from SharePoint via the SharePoint Online connector. It's more manual than Mirroring, but it's fully GA and reliable:
    • Source: SharePoint Online List or Document Library
    • Destination: Lakehouse Delta Table
    • Schedule: trigger on demand or on a schedule
      I've been working on a similar SharePoint-to-Fabric ingestion pattern and plan to share a detailed walkthrough soon.

    Keep us posted on your support ticket it would be great to know what Microsoft recommends!

    • thaisstefani18_'s avatar
      thaisstefani18_
      Frequent Visitor

      Hello Tamanchu 

       

      1. OneLake shortcut to SharePoint
        As I understand, this is currently only available for SharePoint Folder, correct?
      2. Pipeline with copy activity
        I’m trying to implement an incremental approach since the list currently has nearly 2 million records. However, I’m facing some challenges due to source limitations.
      3. Mirroring
        At the moment, mirroring is not replicating all records from the source and also does not keep the selection limited to List, which could help avoid the 404 error.

      Other attempts:


      In the image below, even when selecting only the “List” option, the mirroring does not preserve this setting, it always ends up with everything selected.

       

      Thank you 🙂