OneDrive Exact Roots, Subdirectories, and Troubleshooting

This article explains the OneDrive root boundary and combine common troubleshooting for callback routing, application credentials, tenant mismatch, account consent, inaccessible roots, and provider errors.

What you need to know

  • Each Storage Connection represents one provider and one exact root. QCSB normalizes paths and refuses navigation/operations outside that boundary.
  • Allow access to subdirectories controls depth below the root; it never exposes or infers parent directories above the root.

Root and subdirectory check

  1. Confirm the Microsoft account is connected to the intended saved OneDrive connection.
  2. Verify the Exact OneDrive root folder path is the intended top boundary.
  3. Enable subdirectories only when descendants below that root should be browsable.
  4. Run Test Connection after root, tenant/audience, client-secret, or OAuth changes.
  5. If the root test fails, correct the Microsoft Client Secret Value, redirect URI, tenant/account type, authorization, or folder path as appropriate; do not broaden the root to hide the actual setup error.

Verify the result

  • Test Connection succeeds.
  • The displayed/usable root is exactly the intended root and no parent folder is reachable.
  • A normal authorized user can perform only the operations intended for that connection/Workspace role.

Important limits and mistakes to avoid

  • Never broaden a connection root merely to work around a permission or provider error; fix the actual root/credential/hosting problem.

Troubleshooting

  • If the provider is unreachable, test the connection in Administrator before troubleshooting the Workspace UI.
  • Keep passwords, OAuth secrets/tokens, private keys, and unrestricted private paths out of public screenshots and support posts.

Community Discussion

For practical QCSB workflows and discussion with other Joomla site owners, visit the QC Storage Bridge Community. For private support, bug reports, account-specific entitlement issues, or feature requests, use the QuantaCade support system.