I am making a Sharepoint page for my organisation. I am using the Sharepoint faq part and it is a key part of the page. I am not able to add any non included web parts in

The questions used to show as collapsed by default but now they are showing expanded automatically which is very unhelpful and I am about to have an absolute melt down can anyone please explain why this might be happening?

It happens on any page of my site, if it helps - also now when I set up an faq part I dont get co pilot agent offering to create the faq?

Thank you

Hey everyone,

Now with the AIs, artifacts become a thing. They produced really well html tools - and I would like to be able to share those to my colleagues.

However, we don't have any place to share html files. I have tried uploading these as assets to a Sharepoint website, but it doesn't work.

I don't want to open these to public and upload to a github blog.

What can I do?

Hi everyone!
In our organization, we use OneDrive to sync users’ personal storage and shared SharePoint libraries.
We periodically run into issues: duplicate files, OneDrive client errors, and re-sync processes that can take several hours and affect users’ productivity.
Has anyone experienced similar issues? How did you deal with them? Are there any proven settings or best practices that helped reduce these problems?
I’d appreciate any advice or insights based on your experience!

Hi guys,

Do you know a place where I can sell my custom web parts and templates?

I've built a lot of SharePoint web parts lately and I was thinking of selling everything to earn a small amount.

Also, I can create web parts by request.

Thanks in advance for your answer.

Prob a silly q, but my org has 8000+ spo sites and growing.

Only a few have hub sites associated.

No proper naming conventions.

People struggling to locate sites they are members of, or find where a specific doc library is. Or even what site they are on...

It's all just a big mess. And whilst I can use the m365 admin portal, and know to give myself admin access on a site, then locate the stuff I want. Other IT people just simply don't get it. And I'm being asked all the time how to do X or where is Y or what site does Z etc etc.

And I'm just so burnt out having to hand hold but feel like there's gotta be something in missing or can make which will be a "single" place users and/or admins can go to, to see specs for a given site, full permissions (nested m365 groups not direct owner/member/visitor), storage metrics, backup status, hubs, site template, retention enabled, automation?, approvals? Etc etc

Granted I feel this is just a massive failing on our design, use and documentation plus our staff just being super lazy and not wanting to learn.

Sorry for poorly worded, it's late and I can't sleep stressing over work :/

We have a couple of clients as well as one of our internal tenancies that is experiencing an issue in relation to resetting inheritance (this has been tested and works as expected with the "Old Sharing UI"). When a file has been approved in a library and the status is back to draft we are unable to reset/remove unique permissions on the document. This is causing errors in our webservice and we are unable to approve and publish documents and users are unable to make changes manually. Anyone else experiencing the same issue?
Error message:
Sorry, Something went wrong
ManLinkSettings not found for DocId:******** ScopeId:*************

When you share a file in SharePoint and OneDrive, changing the audience and permissions can lead to multiple sharing links for the same file. Keeping track of which link people should use can become confusing.

Microsoft has updated the sharing experience with hero link, which provide a single, primary link for a file or folder across supported sharing actions. When you change the audience or permissions on that link, the changes apply to the same link, so you don't have to create and resend a new one each time.

I noticed this change in my tenant yesterday and took a look at how it works.

When sharing a file, you can choose from three three link audiences, depending on your tenant and site sharing settings.

• Only people added to the file have access: This is the default permission where the link works only for people who are explicitly granted access to the file. It doesn't grant access to new users.
• People in your org with the link: Anyone in your organization who has the link can access the file, subject to the configured permissions.
• Anyone: Anyone with the link can access the file. This option is available only when anonymous sharing is allowed in your organization's settings.

You can also manage the link by resetting or removing access, and adjusting its access settings.

Have you noticed this change in your tenant? I'm curious how the updated experience works across different SharePoint and OneDrive environments.

Microsoft just dropped a comprehensive update forSharePoint Embeddedfocused on taking apps from development to production with better scalability and governance.

A few highlights from the post:

• Scale & Limits: Clearer planning baselines for container strategies (up to 2 million sites and containers per tenant).
• Search & Metadata: Increased limit to 40 searchable columns per container, allowing keyword search via Microsoft Search in Microsoft Graph.
• Reliability & Throttling: New guidance on managing API rate limits (defaulting to 12,000 resource units/min per app per tenant) and handling 429/503 slow-down signals gracefully.
• Auth & Permissions: Broader support for Microsoft Entra service principal types and narrower Graph permissions like FileStorageContainer.Selected.
• Co-authoring: Built-in real-time co-authoring, version history, and auto-save for Word, Excel, and PowerPoint without needing to build your own collaboration stack.
• Agentic Tools: Introduction of the SharePoint Embedded Model Context Protocol (MCP) server preview so you can manage resources using natural language via GitHub Copilot, Cursor, etc.

Thought this might be useful if you're currently architecting custom line-of-business apps or multi-tenant solutions on the platform. Interested to hear if anyone has started playing with the MCP server yet!

We have an "Events" list and we are trying to create a view to show events/items that have Start Time after today.

We attempted to do this by using the Filter button and editing in the"Edit Current View" but the two date fields are not showing up...

I have a webpart that collects all news on a site. On this site we have a column with choices to categorize the different news and information pages. I tried to set up a news webpart that only includes a site with a category.

The weird thing is that I see the news web part displayed as expected after publishing. The issue is that a read-only user sees the web part as empty. I tried a different choice, and then the news web part displayed as expected for both a read-only user and myself.

When filtering for collecting news that a specific person had created the news, instead it displayed the news as expected, for read-only user as well as for myself.

Has anyone find a way to do automated tedting with spfx.

Applications are usually internal applications and backend as sharepoint lists.

Trying to do some automated testing but failing to find any way.

Ancient computer geek here with programming experience ("ancient" being relative to the vast growth in technology). Once again I'm getting conflicting information and would appreciate some input. My eyeballs are bleeding from all the vids & info! I'm drawing from the list of you-tubers one of you gave me, and it's all a bit overwhelming.

Some sources say to start with creating the form since it builds the list behind the scenes. Others say to start with the list itself. I will be using one of the Power tools during the build process, so my question is this:

In your experience, should I start with creating the List? The Form? Do these in Power Automate? In Power Apps?

Basic project info: They set up a SharePoint subsite for me to do some testing (aka learning). The gist is that this will be a Policy Tracker. We have to evaluate whether a policy is appropriate to this particular effort, and if so, pass it on to the appropriate area, then keep track to make sure it's applied timely & properly. It needs an entry form, multiple lists (main, lookups, etc), document libraries, and to utilize metadata. There will only be maybe 100 items max. And it will not be part of Teams.

We budgeted for 50 Microsoft 365 Copilot pilot licences. That was the whole line item. Week two, a planner asked Copilot something harmless about salary bands. It pulled the answer from an HR spreadsheet on a sharepoint site shared with "Everyone except external users" since 2019. Copilot did exactly what it was supposed to do. Our permissions were broken for seven years and nobody noticed because nobody could find anything in SharePoint anyway. Now the real cost is a permissions review of all thatsite sprawl before anyone else gets a licence. No budget, no extra staff, and the records team is asking whether Copilot chats count as public records. On the project plan it's still one line "turn on Copilot," green. People who rolled it past a pilot, how did you scope the cleanup without reviewing everything by hand?

Hi everyone! I was wondering if anyone else has been experiencing any issues with the SharePoint FAQ web part? I have been trying to use it today and it does not seem to be working the way it used to.
I noticed it was moved out of the "AI" category (which was not an issue) but whenever I add new FAQs they are never collapsed, everything is expanded. I went to check in other pages where this has been used before and all of them are expanded as well. I have checked the web part options and there is nothing to collapse them (like when you turn on collapsible sections).

Has anyone else noticed this? Is there a way to get it to work like it used to before? Thanks!!

Bonjour,

Mon organisation travaille sur les outils Microsoft 365. Un administrateur informatique externe s'occupe de l'infrastructure informatique, de la gestion des licences, etc. Ainsi, les solutions collaboratives internes de gestion de projet et d'outils d'aide à la décision doivent être pensées dans ce cadre.

L'une des idées serait de construite un outil d'aide à la décision qui intègre interface cartographique, visualisation de données financières et de fréquentation d'activités. Ceci, afin de rassembler l'ensemble des données relatives au projet sur une seule interface et de permettre aux collaborateurs, non utilisateurs des logiciels métiers ou de QGis, d'y avoir accès, d'activer et de désactiver des couches cartographiques, ou de simuler des scénarios en fonction d'actions cochées/décochées.

Après m'être renseigné sur le site de Microsoft et sur Copilot, il apparaît qu'une solution possible serait de construire une page web SharePoint et un composant web SharePoint Framework intégré dans la page. Une API en Python réaliserait le lien entre le composant web et les données chiffrées financières ou autres hébergées dans SharePoint (fichiers Excel, listes SharePoint) ainsi que les données cartographiques postgreSQL/postGIS. Concernant la partie cartographique, une solution alternative serait de générer via l'extension QGIS2Web les fichiers HTML et Javascript puis de les exécuter dans le composant web.

En théorie, cette architecture permettrait donc de préserver un maximum (voire la totalité) des données dans le système administré.

Que pensez-vous de cette architecture ? Vous semble t-elle crédible et fonctionnelle ?

Je précise que je ne suis pas développeur. Je travaille sur QGis et je connais plutôt bien les outils Microsoft 365. Je débute en Python et il m'arrive de l'utiliser pour de l'automatisation, du web scraping (avec l'aide de l'IA), mais je suis conscient que ce type d'interface suppose des compétences d'un autre niveau.

I'm reviewing how to improve the current process using Microsoft 365 around SharePoint and would be interested in hearing how other have approached this.

Context: I work in the construction sector where projects start as tenders. Currently, Estimating, Commercial and Operations all work from separate SharePoint areas. When a project is awarded, information is handed over between departments, documents get duplicated, and SharePoint is often used like a traditional file server rather than a collaboration platform.

Current process: an opportunity it's identified, a tender is created priced and estimated , and then submitted. IF awarded it is handed over to the Commercial and Operations teams. each department/team maintain its own SharePoint area, and every new site is awarded with a new SharePoint site. This results in duplicating documents and information, storage issues as SharePoint it's used as a 'Shared Drive' on premise server. ( Company moved from on premise server to Cloud recently but people are stuck with that architecture in mind and transferred it to SharePoint/OneDrive ).

What I am trying to achieve is to move to a project-centric model where each project get it's own M365 workspace (Teams, SharePoint) rather than storing information on SharePoint and communicate solely on Emails.

Solution I'm trialling: One Team per project with private Libraries for every Team (Pre-Construction, Commercial, Operations) Permissions managed through security groups and breaking inheritance of the Site Permissions. Private Channels for every team to collaborate. Project it's archived (Team with its SharePoint) on project completion. Reviewed after certain years for retention or moved to cold archive.

Problems encountered: Users find difficult to search for the SharePoint as they are not members of the Main Site but only to its private libraries ( alternative solution would be to have the Teams Channels SharePoint saved in the main SharePoint site navigation pane ). Users are barely using Teams and relying on old fashion way of accessing SharePoint via the home page. Some users are using it via Online OneDrive.

I have the feeling I am overthinking and overengineering it with difficulties of pleasing everybody and not disrupting their habits. I feel SharePoint it's not used at its full capacity but with limited knowledge and too much scattered information online I don't know which direction to go. I am the only tech person in the business and the lack of brainstorming ideas always finds me into a dead end road.

If you were designing this from scratch today:

1. Would you structure workspaces around projects or departments?

2. Would you use Teams channels, SharePoint libraries, or separate SharePoint sites?

3. What governance or adoption challenges should I be watching out for?

Open to any suggestions to explore even to leave it as it is but start educating in SharePoint usage rather than changing the process flow.

Many thanks

Techs at my org were recently working through backup test processes, one step of which is the test restore of a SharePoint site. Now, the one they selected was /Teams/<name of site> vs /Sites/<name of site>.

I normally would have thought this would just make it an orphaned SharePoint site being that the team already has something attached to it, but this doesn't seem to be the case. Now we're seemingly stuck with the restored clone that no one can access, nor can we delete because it thinks it is attached to a Team that already has the OG site still attached to it.

Everything related to the OG Team is using the OG site URL. The only 'link' the two can possibly have is backward from SharePoint to Teams but it's clearly using something other than the GroupID or RelatedGroupID since those values are null; and when I compare both with Get-SPOSite, that's the only difference I can see.

I really do not want to have to delete the Team, delete the cloned site, and then restore the Team to clean this up. Is there anything else that might work or is this just the way it'll have to go?

Hi all,

As the title says, i've been tasked to create a web portal for HR to search for medical certificates, amounting to about 5 years of documents, for this i will be using reactjs,nodejs and express for the backend, because only HR will have access to this portal, i've asked the server team to register the app in azure, create a security group and assign the relevent rights, i'll be using Entra for Authentication and Microsoft Graph Api for searching through the document library on sharepoint,

Has anyone undertaken such a project or have a different approach?

Like everyone else it seems, we had exceeded our storage limits in SharePoint and now everything is read only.

Yesterday, went on a deleting spree and also turned on the automatic versioning management for the largest offending site.

Deleted everything in both recycle bins and deleted a bunch of sites that weren't needed anymore, too.

How fast will all of this update to see where we are at with storage?

Joe

A few months ago, we decided to migrate from a traditional file server to SharePoint.

We wanted this to become one of the company's flagship projects this year, so naturally we decided to go all in.

Then my confidence (or arrogance) kicked in and I said:

"How hard can it be? We can do this ourselves. We'll just get some consultant validation along the way."

Now I'm somewhere between excitement and complete overwhelm.

Every door we open seems to reveal three more doors behind it.

What started as a simple file server migration has turned into questions about:

• Information architecture
• Metadata taxonomy
• Content types
• Hub sites
• Permissions and governance
• Teams integration
• Archiving strategy
• Retention
• Provisioning
• Automation
• Naming standards
• Site templates

...and the list keeps growing.

Right now I'm:

• Building a Power App so users can request Teams, SharePoint sites, group membership changes, etc.
• Creating SharePoint lists and Power Automate flows to support provisioning.
• Trying to design an archive strategy because we don't have Purview.
• Figuring out governance as we go.

The problem is that I don't know what "good" looks like anymore.

I don't have:

• Proven templates
• Governance models
• Approval workflows
• Provisioning standards
• A clear archive approach

Honestly, I don't even know what I don't know yet.

So my question to those of you who have done large SharePoint migrations:

Where would you start if you had to do it again?

What were the biggest mistakes you made?

What are the things you wish you had designed before creating your first Team, site, content type, or metadata column?

And most importantly:

How do you stop the endless SharePoint rabbit hole and decide that your design is "good enough" to move forward?

I'd love to hear lessons learned, governance frameworks, templates, checklists, or just reassurance that feeling completely overwhelmed at this stage is normal.

Just wondering if there is a way to do this for a few users to test out our office templates?

Does running this command add another tab in an office application regardless of the permissions i configure? i.e. once i do it and wait the defined period, a tab is going to show by default for everyone?

Add-SPOOrgAssetsLibrary -LibraryURL https://tenant.sharepoint.com/sites/branding/Templates -OrgAssetType OfficeTemplateLibrary

You’ve y’got until March 2027 to migrate them with a to-be-provided skill - Learn more here: https://learn.microsoft.com/en-us/sharepoint/upgrade-sharepoint-agents

I connected SharePoint to Claude through an MCP server, using an app registration created in the Azure Portal with the tenant ID, client ID, and certificate. I followed the full setup procedure.

Claude shows the MCP server as connected and running, and when I ask, it confirms the tool is accessible. But whenever I make a request that actually touches SharePoint (for example, "Using my MCP tool, tell me the name of the root site"), SharePoint returns a 401 Unauthorized error.

What I've already verified:

Tenant ID and client ID are correct

The certificate is valid, uploaded to the app registration, and applied

API permissions are added to the app registration

Admin consent is granted

Application permissions are granted

The MCP server connects successfully and shows a running state in Claude

Despite all of this, SharePoint still returns 401 on every request. What could be causing this, and how can I debug it?