Forum Widgets
Latest Discussions
Bulk cleanup of content / documents in SharePoint
Hi, We currently have a few SharePoint sites that have old content / documents in document libraries. These are outdated and some are more than 5 years old. To delete these, we currently need to go to each document library / page (and its subfolders), sort by the date created / modified and then manually delete, which would take some time. Is there a way to bulk delete older content/ documents based on date, either within SharePoint admin or a third party program? (e.g. maybe run a query on a site to list any older content and then check off which page / document to delete). Jason
I don't want 100 different SharePoint sites. How to create private teams w/o a new site?
Guys. WTF. I've inherited a problem where a company of 50 people has 100 sharepoint sites - because users created different Teams for different projects, and Microsoft makes it incredibly opaque what this actually means. Now we have 100 SharePoint sites, many of which are unused, but all of which appear in the list of sites in 365AC. The structure we WANT is 1 Sharepoint site for our 1 org, but multiple locations within that site, and multiple groups for multiple projects. I THOUGHT what could work was converting the excess Teams into Private Channels. But I have now learned that private channels ALSO create SharePoint sites, because _______. Most confusingly, all of these sharepoint 'sites' DO exist within our main SharePoint website - they're just pages (but not 'pages') pretending to be a fresh sharepoint website. This confuses the **** out of people, the way they've redefined what a 'site' is, what a 'team' is, etc. This is genuinely hot garbage, and it's suddenly clear to me why people always push back on using SharePoint over OneDrive. Recommendations for... not having this disaster? Making a structure that is intuitive and doesn't redefine what a site and page are, and allows you to have private locations for management or projects, but DOESN'T create a 'site' within the main 'site', with it's OWN 'documents', and it's own 'Notebook' (which isn't a document) and it's own 'Conversations' (which are NOT conversations), and it's own 'pages'? I don't work with dumb people - these are very technical people. But even our main SharePoint guy is mystified by these interactions. Does it make more sense in another language? If anyone at Microsoft is reading - the english term 'site', comes from the word 'website', which generally refers to a distinct web service with a distinct domain name. These contained different webPAGES.. When websites started existing off a shared domain name, like company1.sharepoint.com and company2.sharepoint.com - this confused people, but they put up with it, because it was relatively easy to explain the tech behind this - having websites under a single site, that wasn't too hard to understand. But what SharePoint seems to do, is extend this practice into absolute hysteria, where a particular webPAGE of a webSITE is ALSO a site, but also is a TEAM, or COULD be a CHANNEL. OR it could be a PAGE - WHO knows? If it's a TEAM, that TEAM could have CONVERSATIONS, which aren't actually Team Conversations - they're EMAILS. But this is fine, because all CONVERSATIONS of a TEAM done in TEAMS are actually stored as EMAILS so really those, CONVERSATIONS should be CONVERSATIONS... So why aren't these conversations in Teams between a Team that are stored as Emails not showing in the Conversations which show emails within that Team? aefggaddadsfasd
SharePoint News Email “Content too large” issue – size limit clarification
Hi, We are currently trying to send a SharePoint News post via email and encountering the following error: “The contents of this page are too big to send in email.” We performed testing to understand the limitation and observed the following: Full newsletter (~5.29 MB) → ❌ Error Pages 1–12 (~3.11 MB) → ❌ Error Pages 1–11 (~2.80 MB) → ✅ Works Slight increase (~2.90 MB) → ❌ Error again ✅ Based on testing: Practical threshold seems around ~2.7–2.8 MB Above this, email rendering fails ❓ Questions: Is there a documented maximum size limit for SharePoint News email content? Is the limit based on: Total content size after rendering? Image count/size? Can this limit be configured or increased? What are the recommended best practices for image-heavy newsletters? ✅ Current understanding: It appears that the limitation is due to HTML email rendering size rather than just file size Any clarification or official guidance would be appreciated. Thanks.
Webpart "See All" ASPX link Not displaying List of News for Read-Only Users
We have an extremely simple Sharepoint site in M365 Sharepoint that we created a very simple News webpart, list form, 1 item, from news posted to this site only. The idea being people come and see the most recent news post, they click "See All" to view more if they desire. Visitors can see this link and go and view the article, along with any other news article posted to this site if they have the direct link, but only people with Edit or higher access are able to click the "See All" link and get a list of more news articles. People with regular Visitor/Read access see the title of the list but the page is otherwise empty like it's failing to return query results. We've chopped up the URL since it's aspx and have at least figured out the point of failure is in the : &serverRelativeUrl part of the link. If they chop off link before that variable, they can get an (albeit unformatted) list of the news articles. I am absolutely not a Sharepoint guru. We've inspected the permissions on the Site Library, we've reindexed the site, we've even experimented with different usergroups, nothing seems to change this behavior. Can anyone explain what's happening here and how to fix it or is this just busted behavior in Sharepoint Webpart command link?SharePoint Video Playback Quality Defaults to 480p – Horrendous
I manage multimedia training for over 600 locations and two distribution centers, supporting nearly 10,000 team members. We have made a significant investment in producing high-quality training content through professional equipment, structured scripting, and dedicated production and editing time. However, once videos are uploaded to SharePoint, the default playback quality often degrades the experience to what appears to be approximately 480p. As a result, professionally produced content can look noticeably poor on initial playback. Many of our store-level team members are not in a position to manually adjust playback settings, so the default experience matters. The source files are high resolution, but the default playback does not reflect that quality. This also creates issues when leadership reviews training content, because the playback quality can reflect poorly on the production even though the original video is clear. We moved away from third-party hosting due to ad exposure during onboarding and the need for a controlled internal platform. We are intentionally using SharePoint and Stream as part of our existing Microsoft 365 ecosystem for scalability, governance, and centralized access. Introducing additional paid hosting platforms or external streaming solutions is not a direction we are pursuing. From an enterprise training standpoint, defaulting to low-resolution playback undermines engagement and credibility. Are there plans to allow administrators to define a default playback resolution for SharePoint or Stream videos? Are there recommended encoding settings that influence the initial playback quality more reliably? Are there roadmap updates around improving adaptive streaming behavior or default resolution selection? Any guidance or insight would be appreciated.
News Web Part Not Returning Items When Using Managed Property Filter Across Multiple Sites
We are experiencing an issue with SharePoint Online News web parts that are configured to filter items using a managed property, specifically mapped to a RefinableString (RefinableString01) linked to our custom metadata column “Conteúdo Informativo”. Despite the proper mapping and reindexing of the relevant sites, the web part fails to return any items when the number of source sites exceeds 14. Details: The web part is configured to pull news items from a specific set of sites. When configured with up to 14 sites, the web part works correctly, displaying all news items that match the filter (RefinableString01:"Notícia:Regional:Aprovada"). When a 15th site is added to the web part source, the web part stops displaying any items, although the underlying search query returns results correctly when tested via KQL in the search API (_api/search/postquery). All sites involved have been reindexed, and the managed property (owstaxIdConteúdox0020Informativo) has been mapped to RefinableString01 as recommended. Using the web part configured with the option “All sites in this hub” works correctly and returns all items, but this is not a viable solution because it includes items from sites that should not be part of the filter scope. Impact: Numerous web parts across multiple sites are affected, preventing proper display of news items filtered by metadata. The issue appears to be related to the number of sites configured as sources in the web part. What can be done to solve this issue? Thank you very much!
SharePoint Online modern pages – spacing/gaps lost between web parts in flexible sections 2026
We're experiencing an issue across all our SharePoint Online modern pages. All existing pages with flexible sections have lost the spacing/gaps between image web parts — tiles are now butted right up against each other with no padding or margins. Key details from our troubleshooting: Affects all existing modern pages across multiple SharePoint sites (8+ sites, many pages) New pages created after the issue started render correctly with proper spacing Affects multiple users in our tenant Tested across multiple devices and browsers (Chrome, Edge, mobile) — same result We are on Standard release, no targeted release enabled No changes made to our tenant settings This is causing our intranet pages to look unprofessional and difficult to navigate. Please can Microsoft investigate and roll back whatever CSS/rendering change caused this. Tenant region: UK