To fix SharePoint file sharing permissions, first identify the correct account, file, device, or service context. The steps below isolate the cause and apply a result you can verify.
Identify the Exact SharePoint Item, Permission, or Flow
Start by confirming whether the symptom affects one file, one device, one account, or the service itself. That distinction determines whether the next action belongs in the desktop app, the web portal, or an administrator console.
Quick SharePoint or Flow Check
First, set-SPOTenant -AllowLegacyAuthProtocolsEnabledSetting $true. Next, set-SPOTenant -LegacyAuthProtocolsEnabled $true, and verify the final state before changing any backup or secondary account.
Why This Can Happen
- The wrong personal, work, school, billing, or administrator account is selected
- A license, permission, connection, file rule, or local setting does not match the requested action
- Cached credentials or an incomplete synchronization or activation state hides the current server status
- The Microsoft service or application requires a more specific control than a generic restart
How to Fix SharePoint File Sharing Permissions

- Set-SPOTenant -AllowLegacyAuthProtocolsEnabledSetting $true
- Set-SPOTenant -LegacyAuthProtocolsEnabled $true
- Go to Azure Portal → Entra ID
- Create client secret
- Use OAuth connection string in SSIS OData source
- Restart SQL Server Agent after change
After the final step, reopen the affected app, portal, file, or account page and confirm the exact status or behavior described in the title.
WPS Office: A Free, AI-Powered Microsoft Office Alternative

WPS Office cannot directly change Microsoft-side account, billing, subscription, activation, tenant, OneDrive service, or SharePoint permission state. Those changes must be completed in the appropriate Microsoft portal.
WPS Office offers a free, familiar workspace for common Word, Excel, PowerPoint, and PDF formats through Writer, Spreadsheets, Presentation, and PDF. Integrated WPS AI adds practical help for drafting and summarizing documents, building formulas and understanding data, creating editable slide decks, and extracting information from PDFs. Some AI features or higher usage limits may depend on the plan, platform, region, and app version.
Test advanced macros, add-ins, external connections, sensitivity controls, and Microsoft-only cloud integrations on a copy before moving a critical workflow.
Practical Checks That Prevent a Repeat
- Record which account, app, and file owns the workflow
- Keep a verified backup before removing access, changing ownership, or replacing a local file
- Apply high-impact changes to one test item or user before expanding the scope
- Save confirmation numbers, dates, and screenshots of the final settings when they affect billing, security, or permissions
Frequently Asked Questions
Which account, file, or app should I use when I set-SPOTenant -AllowLegacyAuthProtocolsEnabledSetting $true?
Set-SPOTenant -AllowLegacyAuthProtocolsEnabledSetting $true. File and folder sharing can differ because of inheritance, site sharing policy, sensitivity settings, or the user’s permission level. Check Manage access on the exact folder.
What result should appear when I set-SPOTenant -LegacyAuthProtocolsEnabled $true?
It keeps a copy of current permissions and can then be edited independently. Document the change so future site membership changes do not create unexpected access. Confirm the account type, product version, ownership, and permissions before assuming the control is unavailable.
What should I preserve before I go to Azure Portal → Entra ID?
Open the associated Power Automate flow and inspect Run history. The failed trigger or action shows the connection, permission, expression, or data issue to correct. Keep the relevant backup or confirmation until you have checked the result.
Where should I verify the final result after I fix SharePoint file sharing permissions?
Restart SQL Server Agent after change. Reopen the affected app or portal and confirm that the expected status persists.




