'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix SharePoint Limited-Access Permission Lockdown Timeout
Question details
The user needs to successfully disable the Limited-access User Permission Lockdown Mode on a large SharePoint Online site collection after encountering timeouts using PnP scripts.
- Product
- SharePoint Online
- Device & OS
- not provided
- Scenario
- Deactivating site collection features on a massive SharePoint environment containing terabytes of documents and numerous subsites.
- Observed behavior
- Disabling the Limited-access User Permission Lockdown Mode through PnP times out and fails to complete due to the vast size of the site collection.
Ensure you have Site Collection Administrator privileges and verify your network stability before attempting to change global site collection features.
Disable via SharePoint Online Web Interface
Using the native web interface can sometimes bypass the API timeout constraints encountered by PnP scripts on large site collections.
When automated scripts time out, falling back to the SharePoint graphical user interface allows the backend systems to process the request natively.
Navigate to your SharePoint site, click the gear icon (Settings) in the top right corner, then select 'Site information' followed by 'View all site settings'.
Under the 'Site Collection Administration' section, click on the 'Site collection features' link.
Scroll down the list to locate 'Limited-access user permission lockdown mode'. Click the 'Deactivate' button next to it and confirm your choice if prompted.
Contact Microsoft Online Support
If the web interface also times out, the issue requires a backend investigation by Microsoft to handle the site-collection scale.
Try WPS Office for Your Document Needs
While SharePoint administrative issues require Microsoft's backend support, you can significantly enhance your daily document productivity with WPS Office. It is a highly efficient, lightweight, and free alternative to Microsoft Office that easily handles large documents and offers perfect formatting compatibility.
- 1. Download the Installer: Visit the official WPS Office website and click the download button for your operating system (Windows, Mac, or Linux).
- 2. Install WPS Office: Run the downloaded setup file and follow the quick on-screen prompts to complete the installation.
- 3. Open Existing Files: Launch the application and open your existing Word, Excel, or PowerPoint files instantly to begin working.
Frequently Asked Questions
What is Limited-access User Permission Lockdown Mode in SharePoint?
It is a site collection feature that, when activated, prevents users with 'limited access' permissions from viewing application pages like item properties or list views. It is commonly enabled on publishing sites for tighter security.
Why does PnP PowerShell timeout on massive SharePoint sites?
PnP scripts interact with the SharePoint REST API. On exceedingly large site collections containing terabytes of data and thousands of subsites, updating permission structures across all items takes longer than the API's maximum allowed response time.
Can I increase the PnP timeout duration to bypass this error?
While you can adjust local execution timeouts in your PowerShell environment, server-side limits on SharePoint Online are hardcoded by Microsoft. For exceptionally large sites, you will still hit backend service limits, making the web interface or official support the only reliable options.
