sharepoint online
18508 TopicsFeedback : building the foundations for AI adoption with AI itself
I would like to share some feedback on the recent SharePoint Copilot improvements. As a consultant, trainer, and Microsoft MVP working daily with Microsoft 365 Copilot customers, I am genuinely impressed by the direction SharePoint is taking. For years, we have told customers that successful AI adoption requires strong information architecture, metadata, governance, content organization, and naming conventions. What I find particularly interesting today is that SharePoint Copilot is starting to help organizations build these foundations instead of simply depending on them. Features that assist with site creation, page creation, content organization, metadata generation, metadata enrichment, and automation significantly reduce the effort required to establish a well-structured SharePoint environment. This is a meaningful shift. AI is no longer only consuming well-organized knowledge. It is increasingly helping users create and maintain that organization. From my perspective, this may become one of the most important accelerators for Microsoft 365 Copilot adoption because many organizations struggle more with content structure than with AI itself.16Views0likes0CommentsCreate reference number in SharePoint lists with each new entry
Migrating an Excel table into SP lists, so I can existing reference numbering system, so with each new entry I need this to increase by one. Let's say the current ref number is R5687 how to I ensure that subsequent entries are allocated a reference number, which is one more last the last85Views0likes3CommentsDocument not retaining version history on Move To
I've added new document libraries to my sharepoint site to effectively use as "Archives". The problem I am facing is when i move files to my "Archive", which resides in the same SharePoint site all of the metadata changes in previous versions are pushed to the top (the latest version) whether it's a draft or published version it doesn't matter everything is pushed to the top. How can I avoid this? The structure of the document libraries are identical. I have the same versioning settings and advanced settings and both are using the exact same content type.1.2KViews0likes3CommentsNew Navigation Menu
How does the new "Navigation Side Bar" get turned off on a site level? SharePoint without our authorization just rolled out a new feature to all our SharePoint sites. The organization defaults the web browsers to the company SharePoint Hub site causing all users to be impacted and so there for it is incredibly improper for a feature rollout on this scale without the opportunity for proper process and decision making. I have reviewed the documentation https://learn.microsoft.com/en-us/sharepoint/enable-new-sharepoint-experienceThere is a reference to settings - "Global Navigation" which does not exist, as to where the configurate is to turn this off. The owner of the site, and then tenant global admin does not see "Global Navigation", so it is not missing due to a permissions issue. If anyone can please point me in the right direction to turn off this new side bar. No global navigation.60Views0likes2CommentsNew Sharepoint Quick Access - Want "Sites" back
I want the Sites back on my quick access menu - I don't want to have to go through "Discover" it just adds an obnoxious extra step and I can get there clicking on the Sharepoint logo on the top left - having another button to take you to the hub is pointless. How do I get Sites back on the quick access?140Views0likes3CommentsSharePoint Online list filtering not display results
I have a SPO list with around 2000 items. There are around 50 columns. The issue we are facing is that certain columns can be filtered but even though there is a record nothing is displayed using the filter. Some columns do work. I took all totals off and tried but it is still the same. The columns that do work and do not work are all single line text columns. The list permissions are okay and everyone can read all records. What would be causing this behaviour? Thank you29KViews0likes12CommentsPosting news article not sending notification to Teams activity feed
Hello I am trying to troubleshoot why when posting a news article it is not coming up in people's Teams activity feed. We have a hub of sites branded as the intranet but they are not news organisation sites. When news posts are published from any site in this hub, people are receiving notifications of news posts in their Teams activity feed. Eg. 'Joe Blogs published news'. On a stand alone communication site, I publish a news post, for the members of that site they do not receive the notification in their Teams activity feed. Some facts We are not using Viva Connections - so there is no home site (no Viva license yet) No sites are news organisation sites Internet sites are not necessarily followed (most people do not follow) so this has no bearing on receiving notification in Teams Notification settings in Teams are not disabled for test users What other steps can I take to investigate why this site not connected to the internet hub is not pushing notifications? It is one example of a site, there are many that do not push notifications as well. Thank you.47Views0likes2CommentsStrange Auto-Publishing Behavior in a Homesite
I have a client who is having the strangest behavior on their homesite. If they go to add a news article - whether from the News web part or from the + New drop-down menu, once the news post page is provisioned, it is automatically publishing. The link to the blank page appears in their web part and the news post they are editing does not have a Publish button on it. The same thing is happening when you create a normal site page also. To try to work around this, they created a new page and selected the checkbox for Save as a personal draft first. Once they finished adding their content, there was no button to publish it in any way. Then they used the Managed Access option on the individual page to attempt to make it viewable in the News web part. It does appear in the news web part on their homepage BUT it is only a gray box with the page title at the top that is linked to the article. I have checked to be sure the page is a "Promoted page" - and it is. I have never seen this in any tenant before and cannot replicate it in any of the 3 other tenants I have access to. As of right now, we are only aware of it happening on the intranet home page which is a homesite and a hub site. It worked as expected until this week as far as we can tell. Is anyone else having this issue? Has Microsoft pushed out an update that broke homesites or News web parts on homesites?378Views1like3CommentsSharePoint Button Web Part "Run Flow" Action Only Works in the Default Environment
Hello! I was setting up a new workflow for a customer and encountered a limitation with the button web part's "Run Power Automate Flow" option. Background The SharePoint Button web part has a built-in action type: Run Power Automate Flow, which accepts a Flow ID. This is a clean option for giving users a one-click way to trigger an instant/manual flow directly from a SharePoint page. The Finding When configuring the Button web part with Run Power Automate Flow, it appears that the flow must reside in the Default Power Platform environment for this action to work. Flows in non-default (department-level) environments fail silently with the following error: Could not find flow '<flow-id>'. Testing Approach To isolate the variable, I did the following: Took an existing instant flow and exported it from a department-specific environment, then imported a copy into the Default environment — so the logic was identical. Created two Button web parts on the same SharePoint page: Button A → Flow ID from the department-level environment copy Button B → Flow ID from the Default environment copy Both buttons were configured identically, with the only difference being which environment hosted the flow. Result: ✅ Button B (Default environment) — triggered successfully ❌ Button A (department-specific environment) — returned "Could not find flow '<id>'" The account I used for testing is the same one that created the workflows and also has site collection admin rights, so permissions should be a factor. Related Behavior This appears to be consistent with a known behavior of running an instant flow from a SharePoint list (from the List menu , "Integrate" -> "Flows" -> <workflow name>), where instant flows with manual SharePoint triggers must also reside in the Default environment to function correctly. Both surfaces appear to share the same environment scope constraint when resolving flows by ID from a SharePoint context. Questions for the Community / Microsoft Is this a documented platform constraint for the Button web part's Run Power Automate Flow action? Is this constraint expected to change, or is it by design? Workarounds In this case, I found two decent workarounds: Instead of configuring the Button web part action as Run Power Automate Flow, it can be configured as Open Link, and then use the flow's direct run URL: https://make.powerautomate.com/environments/<environment id>/flows/<flow id>/run Also using the direct run URL, enter that into a navigation link or regular hyperlink on the SharePoint page to launch the workflow run page. Any insight from the community or the product team would be appreciated — especially if there's a documented reference I may have missed. Thanks!Solved98Views0likes4Comments