Intermittent failures when creating new libraries in modern SharePoint
Hi everyone, I’m seeing an issue in our modern SharePoint Online site collection where creating new document libraries has started failing. This site has worked normally for years, but over the past week, most library creation attempts haven't worked. 1) The page briefly flashes or glitches during the creation process. and 2) A non‑ending spinning wheel when I hit "create" or 3) Creation attempts return “Something's not right.” error page. The failures happen across all subsites, in multiple browsers, and I’m a Site Collection Administrator. No permission changes were made recently. Has anyone seen similar intermittent library creation failures in a modern site collection, or know what might cause this kind of inconsistent behavior? Any guidance would be appreciated. Thanks! Meagan
Document libraries added programmatically as tabs to Shared Channels are not visible
With the recent Teams UX updates, any document libraries added programmatically to Shared Channels no longer appear in the Teams interface even though they do show up when queried through PowerShell. Following the guidance in https://learn.microsoft.com/en-us/graph/teams-configuring-builtin-tabs%22https://learn.microsoft.com/en-us/graph/teams-configuring-builtin-tabs%22https://learn.microsoft.com/en-us/graph/teams-configuring-builtin-tabs%22https://learn.microsoft.com/en-us/graph/teams-configuring-builtin-tabs%22as well as the approaches I outlined in my blog post https://reshmeeauckloo.com/posts/powershell-teams-add-documentlibrary-as-tab/%22https://reshmeeauckloo.com/posts/powershell-teams-add-documentlibrary-as-tab/%22 using Microsoft Graph or PnP PowerShell, the tabs still fail to surface in the new Teams experience. The behaviour is inconsistent: The same tab‑creation methods work perfectly in standard channels. They also work for users who haven’t yet received the new Teams UX. And if the document libraries are added manually, they appear as expected in shared channels. At the moment, I’m trying to determine whether there is a supported way to add document library tabs to shared channels programmatically so that they remain visible in the new Teams interface. Any insights or confirmed workarounds would be appreciated.
File Type Version Limits
Hi all, In trying to solve an old issue I stumbled across this new feature currently in preview and am wondering if the file type arrays will be editable or if new arrays could be or will be added? I have a handful of file types which do not need 100 versions, let alone a version every 2-5 minutes, requiring frequent culling... Ling. https://learn.microsoft.com/en-us/sharepoint/file-type-version-limits
Renaming a folder with too many files
One of our teams has a Team/SharePoint site with an archive folder. Everything in there is old files, and they'd like to rename the folder. However, we get the error that it exceeds the list view threshold. I've spent the afternoon trying to find out how to get this folder renamed and so far nothing has worked. The general consensus is to create a filtered view, but I'm not sure what to filter it based on, as all of the files have been there and untouched for some time, causing most of the columns I could index be fairly similar (they were moved to SharePoint 3 years ago from an on-prem fileshare). One of the options I'd seen was to sync it using OneDrive and rename it locally but that still gave me the same error. I also tried renaming the folder from within Teams without success. If someone could provide some guidance for how to get this done, I'd appreciate it. Right now, I'm thinking I'll just have to move a bunch of stuff out of some of the folders to temporary locations, but even that is challenging as I'm not aware of a good way to get a count of items in folders and subfolders in SharePoint to know which are the best ones to move out.Trimming SharePoint Version History - Minor Versions
Hello, I am a SharePoint Admin at my organization and I have been asked to reduce our total storage usage by reducing the number of versions and minor versions in our environment on all SharePoint sites. I have written a simple PowerShell script that loops through a csv file with site addresses, and runs this command per site -> New-SPOSiteFileVersionBatchDeleteJob -Identity $site.siteURL -MajorVersionLimit 100 -MajorWithMinorVersionsLimit 5 It was my understanding that for all sites in the csv file, for all document libraries on the site, and for all files in the libraries this command will reduce the file to the last 100 Major versions, and the last 5 minor versions of each major version. Unfortunately, this command is not actually reducing the minor versions. It is working with the Major versions just fine, but all minor versions are being retained for each major version retained. Is my understanding of this command wrong, or is it not working? Are there other factors to consider? Does anyone know of an alternative that can fit my needs? The overall plan is to trim the current version history, then apply the automatic version setting to each library in our tenant. Here is the MS guide I referenced, maybe I missed something -> https://learn.microsoft.com/en-us/sharepoint/tutorial-queue-a-trim-job Any help is greatly appreciated, CamMultiple Page Libraries on site
Hi everyone I have a strange issue that I haven't come across before. A customer has got an old subsite on SharePoint Online that was created with the STS#0 template (classic Team Site with no group) and they want to modernise their old wiki pages. This should have been straightforward as I was planning on using the https://learn.microsoft.com/en-us/sharepoint/dev/transform/modernize-userinterface-site-pages-powershell. However, on this site they have two page libraries - the standard Site Pages library and then what looks like a custom page library (I've blanked out the name of the custom library as it contains the company name): All of the pages they want to modernize are in the custom library but the issue with this is that the only content type available is Wiki Page: This means that although the PnP PowerShell runs successfully against pages in this library, the new versions don't actually appear in the library. I assume this is because the modern Site Page content type isn't available in the library. I was under the impression that a site could only have one page library so I'm not sure how this site has the two. On a more urgent note I need to work out the best way of modernizing these pages. Currently the only way I can see is using Power Automate to copy the pages to the Site Pages library and then convert them there. The only issue with that is that there are links within the pages to other pages so I'd need to go through them and fix these once they've been moved. here are over 300 pages so I don't really want to do this. Does anyone have any ideas on the best way forward with this. Also, if you know how there are multiple page libraries I'd be keen to hear it as I haven't come across this before. Thanks in advance for your help.
External guest users now see Classic view in document libraries (was Modern)
We are seeing a recent change in behaviour (last ~1–2 weeks) affecting external/guest users only. Context: Sites are created from an approved SharePoint Communication Site template Tenant and site are configured for Modern (New) experience Document libraries were previously rendering in Modern view for external guests Internal users still see Modern view as expected Current behaviour: External/guest users now consistently see document libraries rendering in Classic view The library shows “Exit classic experience”, but selecting it does not switch the library to Modern This occurs even when: Accessing via the site home page Navigating via the site menu Using a newly created site from the same template Testing in InPrivate/Incognito Library settings are explicitly set to Default experience = New experience SharePoint Admin Centre is set to New experience (no Classic defaults enabled) Important observations: This behaviour did not occur during earlier testing using the same template and permissions No template changes have been made Reproduces across multiple sites Reproduces only for guest users (internal users unaffected) The issue persists even after refreshing, changing views, or setting the library experience explicitly to Modern Question Has there been a recent change or regression in how SharePoint Online renders document libraries for guest users, particularly when accessing libraries on Communication Sites created from templates? Specifically: Are there known issues where guest sessions are forced into Classic rendering despite Modern being configured at the tenant, site, and library level? Are there any recent changes (late 2025 / early 2026) affecting guest rendering or Classic fallback behaviour? Any guidance or confirmation would be appreciated, as this represents a change from previously working behaviour and impacts external user experience.New to board, question
Hello, I am trying to find the right place to ask architecture questions and issues with SharePoint. If this is the right place, please let me know suggestions or where I can search for the following: We are running SharePoint Online. I do not have O365 Admin rights. I had created the Vandelay Project examples, site columns and document content types. After "playing" with the project I deleted the site columns from the content types, tried to delete the content types but keep getting the message they are being used somewhere. I put a ticket in with our IT but they have been unable to delete these with their rights. I have renamed them with a "z_" and assigned them to a Deprecated group. Can someone suggest what to do? Thank you, Carol
Automated upload competing with users who have a file open in Co-authoring mode
This behavior began approximately mid-December. An automated process uploading/overwriting a file located in SharePoint online was constantly receiving errors when executing. We ran through several scenarios for troubleshooting but in the end, we had found that a user would open the file and leave it open in the background through the working day. This behavior produced some co-authoring lock on the file where people could get in and work on the file at the same time but locked out the automated process that would upload a new version of the file regularly. We fixed the behavior after consulting with the people who were referencing the file, they were gathering data from it and were not updating it in any way. So, we broke the permission inheritance for this file and set it up to be read-only for all users but the process that was uploading the file. This allowed the people to reference the file and undid the locking behavior that we had observed. Now, before the middle of December, this locking mechanism didn't exist. Users could have the file open in edit mode and our automated process to update the file was able to upload and overwrite at the same time without issues. Has anyone else observed this behavior within the last few months? We didn't open up a ticket with Microsoft to get an official answer if something new was perhaps implemented and we're curious if anyone has opened a ticket regarding this behavior. Also, I briefly look through the message center and couldn't find any changes in there that seemed to be related to this change by their titles. The error that was seen from the automated process was: The remote server returned an error: (423) Locked. Any input appreciated - I am definitely curious to hear if others are observing this as well.
