Appfolder is named Graph

[steingrd]

Category

• Question
• Documentation issue
• Bug

Expected or Desired Behavior

According to the documentation at https://learn.microsoft.com/en-us/onedrive/developer/rest-api/api/drive_get_specialfolder the special appfolder should be named /Apps/{Application Name}

Observed Behavior

For some users the appfolder is named /Apps/Graph even though the app name is not Graph.

For users with the appfolder named Graph the create subscription request fails. The create subscription request for the resource /me/drive/special/approot fails with 503 and the message [Status Code: ServiceUnavailable; Reason: User content migrated. Cannot access disabled item.]

Example request id for a create subscription request on a user where this behavior is seen:

• date: 2024-07-25T09:52:23
• request-id: dd2cc86a-5f3d-4ab2-9406-071e8959a2fd
• client-request-id: dd2cc86a-5f3d-4ab2-9406-071e8959a2fd

Steps to Reproduce

This happens for some of our users, but not all. I have been able to reproduce it on one onedrive-user that i have personal access to.

[ ]: http://aka.ms/onedrive-api-issues
[x]: http://aka.ms/onedrive-api-issues

[lilleydnSub]

I am also hearing about this issue, but unable to reproduce it.

[lilleydnSub]

I cannot be certain but it seems to be for users where there upload session redirects them too

https://my.microsoftpersonalcontent.com/personal/ ....

@steingrd Have you found a workaround or solultion for this ?

[steingrd]

We did not find any solution to this problem @lilleydnSub

We also encountered many other problems with the Onedrive Graph API - 503 errors from the create subscription (webhook) API that persisted for some users. We filed an issue with Microsoft Support regarding this, but it was never resolved, which ultimately led us to deprecating the Onedrive support in our product.

[lilleydnSub]

@steingrd Thanks for the feedback. I will try and persist but I am not sure if I will be successfull.

[AntGK]

This was encountered by one of my app user recently. One main data folder suddenly went missing and the user found out later it was inside /Apps/Graph folder!

[tipa]

I also recently started to see this - with my own test account as well as in reports from users.
To reference another part of the docs (https://learn.microsoft.com/en-us/onedrive/developer/rest-api/concepts/special-folders-appfolder?view=odsp-graph-online#naming-your-apps-folder):

Naming your app's folder
When OneDrive creates your app's folder, it uses the Application name set at that point for the calling app id. You may change your app's folder name in the Azure App registrations page. If you choose to do so, you may localize your app's folder name by going to the Azure App registrations page and editing your app's localization settings. Changing your app's folder name in the Azure App registrations page will not rename existing special folders associated with your app.

Renaming my app in the registrations page did not make any difference and I was not able to find a way to localize my app name, either.

Looking at the activity of other issues in the repository, it feels like it isn't monitored by Microsoft. Anyone has an idea where else this could be reported?

Edit: I've found that this issue has been posted also in the Microsoft FAQs section (maybe worth clicking that "I have the same question" button):
https://learn.microsoft.com/en-us/answers/questions/2129599/onedrive-app-folder-named-graph-instead-of-applica
https://learn.microsoft.com/en-us/answers/questions/1840991/appfolder-is-named-graph

[steingrd]

Looking at the activity of other issues in the repository, it feels like it isn't monitored by Microsoft. Anyone has an idea where else this could be reported?

We tried opening a (paid) support case to raise this, as I had the same feeling as you, that noone is monitoring this repo. I got some replies and they escalated the issue to a few different teams, but I was only met with "can you provide a request id" and endless questions to reproduce it and then provide a fresh request id yet again.

I have a suspicion that this has something to do with Sharepoint and that some users have been migrated to Sharepoint or that their OneDrive is a Sharepoint-drive, but since we have now deprecated Onedrive support in our app (due to so many errors) I have not investigated it further.