Regression: /me/drive/sharedWithMe returns only 1 item starting Nov 2025 (no @odata.nextLink)

[lukedavis76-netizen]

Multiple users reporting similar issue starting 11/7 or so.
https://statics.teams.cdn.office.net/evergreen-assets/safelinks/2/atp-safelinks.html

Situation:
Before we were able to see all shared with me files
As of 11/7+/- a few days, this functionality was working: now it only presents a single item.

IMPACT:
users attempting to save to folders shared with them no longer can browse/navigate to the folders unless it is the "most recently created"
users are attempting to retrieve a file shared with them are no longer able to do so, nor select files which are not the most recent updated. Essentially only 1 file is displayed when the query to retrieve all users me/dirve/sharedWithme files /folders.

This means new workflows or updates to existing workflows no longer are able to be created/updated due to this change in functionality.

[improbabil3]

Same here, please check and fix

[mfeingol]

Seeing the same issue. sharedWithMe is marked as deprecated. What is the programmatic replacement?

[NuxXDev]

SharedWithMe does not seem to be working consistently, I have been using it for 2+ years with no issues.

This Microsoft page says it will be deprecated in the future (and its currently running in a degraded state), with no migration suggestions. How can it run in a degraded/broken state before the end of life?

https://learn.microsoft.com/en-us/graph/api/drive-sharedwithme?view=graph-rest-1.0&tabs=http

[lukedavis76-netizen]

From what we can determine, Microsoft’s long-term direction appears to be moving away from SharedWithMe toward Drives and/or Search-based access patterns. Multiple articles and discussions indicate that Search should be used instead of relying on SharedWithMe for browsing or persistence scenarios.

At the same time, SharedWithMe appears effectively broken or deprecated, with no clear statement on remediation or timelines.

This directly impacts SAP BusinessObjects, which relies on the Microsoft Graph API and specifically uses SharedWithMe to browse and save content. SAP’s current implementation is tightly coupled to this capability. As a customer, we are actively pushing SAP to adopt Search or Drives-based approaches, since those appear to be the supported path forward.

What is most frustrating is the lack of notice and transparency. If SharedWithMe is being deprecated, reduced, or throttled, this should be clearly communicated. The simultaneous loss of browsing functionality and apparent degradation of save functionality is especially concerning.

Observed production impact
Date: 12/10/2025 Time: ~3:30 AM CST to ~7:45–8:15 AM CST

Issue: Existing scheduled jobs (running successfully for 1.5–2 years, with no system updates) were unable to save to SharedWithMe locations.

Recovery: Functionality returned without intervention around 7:45–8:15 AM CST.

Because nothing changed on our side, the only reasonable conclusion is that SharedWithMe behavior changed or degraded during that window, possibly due to a backend service update or enforcement.

Current state

• Saving to OneDrive still works.
• Saving to SharedWithMe is unreliable and appears unsupported going forward.
• There is no viable workaround until vendors like SAP stop using deprecated Graph features.

We are looking for:

• Confirmation of the current status of SharedWithMe
• Official guidance on replacement patterns (Search vs Drives)
• Clear communication around breaking or behavior-changing updates
• This has real production impact for enterprise platforms that depend on Graph API stability.

[mfeingol]

Adding to that... the Search APIs are not available with personal accounts / MSAs, so if the guidance is to use Search instead of SharedWithMe, all scenarios using SharedWithMe with personal accounts are permanently broken.

[lukedavis76-netizen]

Following up on this mornings comment: it appears SharePoint had an infrastructure issue effecting authentication services performing below acceptable performance thresholds overnight from about 1:15AM UTC to 12:09PM UTC. this was a different incident impacting Brazil and North America users. So different issues.

[mfeingol]

So have we seen anyone from the OneDrive team address this... anywhere?

[lukedavis76-netizen]

I have not. All the research I've done has the underlying implication use of SharedWithMe is contrary to the direction MSFT want's to go in. As a result; there is no desire to fix it. We should shift to using search or Microsoft Drives which require site.* scope. and not just files.* though search seems to potentially have some issues. As our use of SharedWithMe is through a 3rd party application; we have no control of how it's used. The third party has indicated they will no longer support saving to SharePoint as a result. We are up the proverbial creek at the moment. with 100's of jobs at risk of no longer working and an inability to save to or use data from SharePoint using SharedWithMe. The Graph API does support other methods; just nothing the third party vendor wants to take on at this stage.

The deprecation is understandable. The quick regression and diminished functionality was what really hurt.

[mfeingol]

You are honestly too kind. "What's shared with me?" is pretty basic table stakes for a cloud storage platform, and removing the only layer of discoverability available (for personal accounts) is pretty wild.

[mfeingol]

Incredible this is still open, and not an official word from MSFT.

[lukedavis76-netizen]

Yep; and time is running out. In November of 2026 sharedwithme stops returning data entirely:
https://learn.microsoft.com/en-us/graph/api/drive-sharedwithme?view=graph-rest-1.0&utm_source=chatgpt.com&tabs=http

states:
The sharedWithMe API is deprecated and will operate in a degraded state until November, 2026, after which it will stop returning data.

So either our third party application updates code by then or we no longer can save to SharePoint (one Drive ok). So existing processes for hundreds of jobs stop working.

Put simply: This major 3rd party app (SAP BO BI2025) which was working with sharewithme ; will no longer work. MSFT has provided an alternative mechanism using site/drives ; but so far SAP doesn't seem to want to change how they integrate. Basically SAP says it's MSFT Fault, MSFT says, yep; we're moving away from that API use this instead. us kids are caught in the middle. Update code to use new functionality.

[jonha892]

Hi,we ran into the same problem and were slightly disappointed / annoyed that there wasn't a clear migration plan.

Our current workaround/approach is to use the search API using a path-filter like this:

query = 'path:"https://site-name-xyz.sharepoint.com/personal/"'
response = client.post(
            "/v1.0/search/query",
            json={
                "requests": [
                    {
                        "entityTypes": ["driveItem"],
                        "query": {"queryString": query},
                        "from": offset,
                        "size": size,
                    }
                ]
            },
        )

This query seems to find onedrive files and folders shared with the user, teams files shared in personal chats, and the drive-items of the user itself.You could also extend the query to filter for folders, or exclude the users files.

[mfeingol]

Jonas Halstrup (@jonha892): unfortunately that workaround only works for work/school tenants, not personal accounts.