SharePoint Online: Get content from default Document Library via graph API fails

[F7aHu]

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Developer environment

None

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

Describe the bug / error

Since today I have multiple customers reporting an error when trying to resolve the default Document Library's content using the Graph API. As of this morning, this is apparently only functional for some users.
This appears to be a breaking change that has been released in to SharePoint Online live and affecting more tenants as the change is rolled out.

Steps to reproduce

1. Open Microsoft Edge
2. Sign in to SPO site default document library

3. Using Graph Explorer shows no content

• https://graph.microsoft.com/v1.0/sites/TenantName.sharepoint.com:/sites/SiteName:/drive/root?$select=name

Expected behavior

The API should return correctly the content of the default document library.

[Ashlesha-MSFT]

Hello @F7aHu,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

[Ashlesha-MSFT]

@F7aHu,
We were able to reproduce the issue, and we are investigating it. We have logged this as a bug, and our engineering team will look into it.
Thank you for your patience!

As a workaround, we used the drives collection to enumerate all document libraries on the site, identified the correct one by name, and then used the following endpoint, which worked as expected:
https://graph.microsoft.com/v1.0/drives/b!DfnHhSxP5EShWCyumWx0Y_r5AW_BIVRFgf8o9zOJ1Wxb94s3_7WCTb77lyXYv4Zr/root?$select=name

[F7aHu]

@Ashlesha-MSFT ,
Yes, this is currently our workaround for addressing this issue on the customer side.

[F7aHu]

Hello @Ashlesha-MSFT
The workaround isn't feasible for all our customers. Is there a timeline or estimated date for when this issue will be resolved?

[Ashlesha-MSFT]

@F7aHu,
Thanks for your feedback — completely understand that the workaround may not be suitable for all customers.

I’ll connect with the engineering team to check if there’s an estimated timeline or planned resolution for this issue. I’ll get back to you as soon as I have an update.

[MrTurtles]

Hello @Ashlesha-MSFT
We are having the same issue with our customers. The workaround isn't feasible for our customers. This ongoing issue is taking a heavy load on our Servicedesk.

Are there any updates?

[F7aHu]

Hi @Ashlesha-MSFT ,

Since the current workaround involves enumerating through all document libraries in a site collection and identifying the correct one by name, I was wondering if there is a way to determine the default library via a property in the Graph API, as described in the PnP Core documentation.
https://github.com/pnp/pnpcore/blob/c17a7a5f58abdadf6c8b180bca667620f23f34ea/src/generated/SP/Public/IList.cs#L316

I couldn't find a property like IsDefault while checking with the Graph Explorer. If this feature is not available, we would greatly appreciate it if you could forward this request to the engineering team for consideration.

Thank you!

[Ashlesha-MSFT]

@F7aHu,
Sure, I'll go ahead and forward this as a feature request to the engineering team for their consideration.

[MrTurtles]

Hi,

As this issue has become increasingly irritating and time-consuming for our team. Due to the persistent nature of this problem, we have decided to escalate the matter and have contacted our support partner. To remind this issue has been ongoing since Tuesday 24th of June.