This guide walks you through permission & access issues using Microsoft-supported steps first, with WPS only where it genuinely helps.
Problem Description: Folder Copy Operation Should
Current Behavior: When using the Microsoft Graph API to copy an entire folder (via `POST /drive/items/{folder-id}/copy`), if **any file within the folder lacks sufficient permissions** for the calling user (e.g., a file with "Restricted View" permission that does not allow content read/download), the **entire copy operation fails immediately** and returns a generic `403 Forbidden` or `Access Denied` error. Critically, **the API provides no information about which files succeeded or failed**, nor does it indicate whether *some* files were already copied before the failure occurred. In practice, files with full read/edit permissions may have been successfully copied to the destination, but the caller has no way to know this. Impact: Applications (e.g., our product: DMSO) cannot reliably handle partial outcomes. Users receive misleading “complete failure” messages, even when most content was copied. No ability to retry only the failed items or audit what was actually transferred. Forces developers to avoid folder-level copy entirely and implement inefficient per-file logic. Expected Behavior: The folder copy operation should either: Return a detailed response indicating which items succeeded and which failed (similar to batch request responses), or Continue copying all accessible items and return a 207 Multi-Status–like response with per-item results, or At minimum, provide an optional query parameter (e.g., ? continueOnError=true) to enable best-effort copying with result reporting. Use Case Example: DMSO copies user-selected folders from a shared team site to a user’s OneDrive. The folder contains 50 editable files and 1 restricted file. The current API fails the whole operation due to the single restricted file, leaving the user confused—even though 50 files could have been safely copied. Suggested Improvement: Enhance the /copy endpoint for folders to support partial success semantics with structured error details, aligning with real-world permission heterogeneity in collaborative environments. ```aspx-csharp public async Task
Quick Answer for Resolving Permission
The current behavior of the Microsoft Graph API when copying folders does indeed lead to issues when some files within the folder have insufficient permissions.
Likely Causes Behind Permission & Access Issues
The Microsoft account or license context may not match the purchase or device.
Cached credentials, outdated builds, or damaged local components can trigger permission & access issues.
A file-specific corruption or add-in conflict can mimic a broader application failure.
Recommended Solution: Fixing Permission Step by Step
When to use this: Apply these steps when the symptoms match and you can access the relevant Microsoft account or administrator.
As you noted, the entire copy operation fails without providing detailed feedback on which items were successfully copied and which were no...
Alternative Solutions for When Office Still Fails
Test the same action in a private browser session or a new blank file to isolate account vs file issues.
Capture exact error text and screenshots before contacting Microsoft Support or your administrator.
Working with WPS Office: WPS Office for Local Document Work

WPS Office cannot replace Microsoft account, activation, or cloud fixes for this scenario. It remains one of the best free Microsoft Office-compatible alternatives for opening and editing local files.
Download and install WPS Office from the official website.
Open local Word, Excel, PowerPoint, or PDF files in the matching WPS app.
Save a working copy locally while Microsoft-side issues are resolved.
Return to Microsoft Office after the primary fix succeeds.
If you need a practical local workspace in the meantime, try WPS Office.
Prevention Tips for Safer Document Habits
Keep one primary Microsoft account for subscriptions and Office sign-in.
Install updates for Office and Windows before retrying failed workflows.
Back up important files before repair, reset, or reinstall actions.
Work on copies and keep version history enabled when available.
FAQs About Common Permission Answers
Can WPS Office fix this permission & access issues issue directly? Only when the WPS steps match the formatting or file task. Account, activation, and cloud issues stay on the Microsoft side.
Should I reinstall Office before trying these steps? Not first. Confirm account, license, and the exact error before reinstalling.
What should I send to Microsoft Support? The affected account email, device type, Office version, exact error text, and screenshots with personal data hidden.




