Local Onedrive files won't open when away from Wifi
Why can't I open a Onedrive file that is saved to my Surface harddrive when I am away from WiFi. I literally opened the file up while I was with WiFi, so when I travelled to the non-WiFi location, the file would be available, or updated, or not be corrupted, or not do whatever crazy thing it does when it can't connect. Sadly I forgot to plug it in so it had to restart and did an update. When I tried to re-open the file that is literally on my harddrive, it said "Excel cannot open the file because the file format or the file extension is not valid". This is ridiculous, and not the only time it has happened. Even if my Onedrive sync is up to date, at times when I am away from WiFi, when trying to open a file I get the same report. To be safe, I have made a practice to open the files I need to ensure that they will be available when I am away from WiFi. If the files are on my computer drive, why can't I open them?? Please give a better solution then me hoping it is going to work every time I go out.Why isn't there a PowerShell module for OneDrive?
Out of all the various applications that Microsoft produce, OneDrive stands out as an anomaly. Where is the PowerShell module for managing it? Some very simple requirements by developers are simply missing. A very simple one - can I test whether OneDrive is still synchronising and therefore I have to wait before my program/script progresses so that I'm sure we've got the latest versions or won't suddenly get "Cloud provider not running". OneDrive has been around years, this really perplexes me...
Congratulations, Microsoft products couldn't have been worse even if you tried.
I was thinking why should I bother posting about this, who would read it, and would it make Microsoft any better if someone reads this? But the world would never improve if no one reports this kind of bad design. So here we go. Why make it so hard to sign up for Azure, register an app, set up permissions, register an app in the MDN (whatever the F it stands for), just to be able to connect to build an ETL job that pulls from multi-tenant onedrive. Why so much text everywhere that it becomes unreasonable to read and find information that matters. Why pretend you have an AI called Copilot when it doesn't have access to data and all it does is spit back information from the docs. How to fix this? Put yourself in the shoes of someone new who's integrating Microsoft products for the first time. No assumptions. No required prior knowledge. Less text, straight to the point. No weird error messages with complicated Error IDs. If no one understands them, why bother bloat the limited screen space with it? Why not have an actual AI that can give concrete pointers instead of showing a link to a generic documentation page? This could go on, but I'm gonna practice what I preach and get straight to the point with the suggestions above. The only moat Microsoft has is the heavy corporate contracts that bind stupid corporations to use Microsoft products and services. The moment a new provider with simpler/faster/cheaper services shows up, developers and people working day-to-day with Microsoft services will gladly migrate over. My 2-cent bottle in the sea.
OneDrive repeatedly misguiding users
Hi, Just letting you guys know that you are pushing the OneDrive agenda way too much and you are repeatedly misguiding and misrepresenting users on how and where they should store their files, without acquiring proper permission, without disclosing proper procedures, and without informing users on the consequences of their decisions. It's not your place to dictate to users how they should store their files and where to store them and organize them. Additionally, I have brought this up to support in the past: Windows Updates get installed and before I can even login, I get these blue screen prompts to go back to using Edge, as well as to use OneDrive, and to "Backup with OneDrive." The users are essentially being pushed or tricked into agreeing with whatever you want them to do and this is completely wrong. Where do these backups go? What are the folder structures? What "apps" get backed up? How do you offer Restoration in the event of a failure? What is the proper procedure to recover lost files? Do you have File/Version History? Who said it's correct, for example, to synchronize the Windows Desktop among computers? Who is issuing all these incorrect procedures on file management, backup, and synchronization?Uploading files to OneDrive Personal via API fails when filename starts with "Windows"
Hi everyone, We've encountered a strange issue with our backup tool that affects random users. Files with names starting with "Windows" (e.g., Windows.gif) fail to upload to OneDrive Personal accounts, regardless of whether we're using: Simple Item Upload (PUT request) Resumable Item Upload (POST to create an upload session) Both methods return a 404 Not Found error. Details: Simple Upload Fails after the PUT completes. Resumable Upload Fails during the session creation call. No issues with filenames not starting with "Windows." A similar unresolved issue was reported https://github.com/OneDrive/onedrive-api-docs/issues/1785. Sample Request & Response: Simple Upload: PUT /v1.0/drive/items/{item-id}:/Windows.gif:/content Authorization: Bearer [token] Host: api.onedrive.com Response: HTTP/1.1 404 Not Found Payload: json { "error": { "code": "itemNotFound", "message": "Item does not exist" } } Resumable Upload: bash POST /v1.0/drive/items/{item-id}:/Windows.gif:/upload.createSession Authorization: Bearer [token] Content-Type: application/json Response: HTTP/1.1 404 Not Found Payload: json { "error": { "code": "itemNotFound", "message": "Item does not exist" } } Key Observations: Random Accounts Affected: Issue occurs inconsistently across different OneDrive Personal accounts. No Request ID: Failed responses lack request IDs, making tracing difficult. Inconsistent Reproduction: I can't reproduce it on my account, but my colleague can. Uploading the same file via the OneDrive web interface works fine. Trying to force URL-encode the filename in the request results in the same error Questions: Has anyone encountered this before? Could this be related to reserved keywords or API filtering rules? Any advice on debugging this further, given the lack of request IDs? Thanks.OneDrive direct download link
Hi, We have tried to get direct download link or to access publicly shared drive file with Graph API . It seems that the the URL structure has changed as well as the API. The thing behind the API is that i cant access file though https://graph.microsoft.com/v1.0/shares/{sharedDriveItem-id} this endpoint since when i get the link and try to encode it to get sharedDriveItem-id the response is that the "The sharing link no longer exists, or you do not have permission to access it.". Anyone has any idea how to get direct download URL from initial public share URL give by someone? Thank you.
Size Discrepancy Between /drives & /root Endpoints
To preface this post, please view the below link. https://learn.microsoft.com/en-us/answers/questions/1257868/microsoft-onedrive-drive-size-is-different-in-driv When retrieving the total size of a drive via the /drives endpoint - one gets a response as follows. { "deleted": 3143, "remaining": 212025579370, "state": "normal", "total": 1099511627776, "used": 887486045263 } When retrieving the same drive via its /drives/{id}/root endpoint - it returns the following metric. "size": 75217259136 The 'used' metric matches the Microsoft Admin Center OneDrive usage panel. The 'size' metric matches the actual downloaded size of the drive. What is the cause for a discrepancy of 800 GB? A response to the other post details, "The difference between the two values is the additional space used by the system." Could I have some specifics of where I could acquire this system data (or at the very least view some metadata for it)? Thanks!
What do I need to connect OneDrive with non-Azure cloud using webhooks?
Currently, I have a Dropbox shared folder connected with AWS processing pipeline via webhooks. In this setup, every time a user authenticated by Dropbox makes a change in the Dropbox folder, an AWS Lambda is triggered to download the changed file to AWS infrastructure and do some computations there. Now, our partner requested Dropbox to be replaced with OneDrive, but to keep the existing AWS pipeline for processing. Thus, a question arises: what would be sufficient to connect existing AWS infrastructure with OneDrive shared folder (after every change to a file in OneDrive the file has to be sent to AWS)? What should I recommend to our partner for this use case? Especially: - should I recommend the "OneDrive for business" license? - is a stand-alone OneDrive license enough to utilize webhooks or are additional solutions like Azure needed? Please note that the relationship with the partner is a formal one, so I can't change my recommendation. Also, for unrelated reasons I am unable to set up my own account, prototype and check for myself, as I normally would. In the future I will be able to make additional recommendations when specification changes, so there isn't any problem with changing the license to a higher one later on. Research I've done so far: - I've read the [OneDrive API documentation on webhooks](https://learn.microsoft.com/en-us/onedrive/developer/rest-api/concepts/using-webhooks), but it is unclear to me what pre-requisites I need to set this up. Especially, is it supported on every license? - The onedrive-webhooks-aspnet repo on GitHub lists prerequisites, but since the README.md was updated 6 years ago, I am unsure how up-to-date it is. It advises to use OneDrive Personal registered with the Microsoft registration portal or OneDrive for Business with Microsoft Azure Active Directory and Office 365 app registration tool. The links do not work, though. - There is also a fairly recent guide on rollout.com on implementing webhooks in OneDrive, but it relies on Microsoft Graph. Is Microsoft Graph a necessity? Any additional links to resources on how to set this up are welcomed :)
