r/sharepoint

So, I’m working on a SharePoint intranet but been trying to figure out a good way to display a few things. I would like to be able to search for employees and display them by department, but not sure if this is possible in SharePoint. I'm also trying to figure out how to show company events alongside personal calendars and have something that automatically shows employee work anniversaries.

and, any good suggestions on what others have done with LinkedIn?

Please, no coding if possible, but I'm open to third-party tools too.

I Working on create custom app for construction on SP online 365 i plan to contain some features exist help construction users i need some suggestions about plugins for edit Auto cad and construction drawings

We're experimenting with the new SharePoint HTML pages that Copilot can generate, and we can't get any web links to work. Here's my bug description I'm submitting to MSFT:

>Bug: Hyperlinks on SharePoint HTML pages created via Copilot's HTML page capability do not navigate when left-clicked. Users receive "This link can't be opened because your organization doesn't allow access to this site." The identical URLs work when opened via right-click → Open in new tab/window, and also work from traditional SharePoint ASPX pages. Hyperlinks are stored correctly and display correctly in edit mode. Issue reproduced by multiple licensed Copilot Premium users on multiple sites.

Anyone else seeing this? Note: if I generate an HTML page that links to actual list or library content on the site, those links do work.

Some context about my background I'm in the Military however, since I've been dealing with noise induced hearing loss, I've been out into an administration role. Currently, I'm the SharePoint Admin, I design sites, lists, do permissions and work with Power Automate.

Is there a decent future in working with SharePoint? What certificates/programs should I learn to upskill?

Honestly if there is any advice from people who do this for a living in the civilian world, I'm all ears.

Hey everyone,

I'm leading a project to migrate a large on-prem shared drive environment (multiple departmental and service-line file shares) to SharePoint Online, and I'd love to learn from people who've already been through it.

A few things I'm looking for advice on:

• Biggest mistakes you made or saw others make
• Lessons learned during planning and discovery
• How you structured SharePoint hubs, sites, libraries, and permissions
• Approaches for handling departments with unique security requirements
• User adoption and change management strategies
• File inventory, cleanup, and ownership validation processes
• Recommended migration tools
• Governance standards you wish you'd implemented from day one
• Training resources, books, blogs, videos, or courses you found valuable

We're currently in the planning phase and trying to avoid creating a structure we'll regret later. If you've done a shared drive to SharePoint migration at scale, what would you do differently if you could start over?

Any tips, resources, screenshots, diagrams, or war stories would be greatly appreciated.

Thanks!

Are there any businesses out there that offer commercial support for PnP modern search? Where I work I have requested permission to use it, but unfortunately our cyber security team has denied use of it as it is a community backed product with no commercial support - they’ve said that unless I can find a commercial fork of it that offers paid support then it’s not going to happen - this is regardless of me having 6 years experience of it in my previous job.

Company moved all systems to MS for compliance reasons and all work is stored in Sharepoint Online. But using PPTX and docx files is clumsy at best -- formatting never holds in Sharepoint Online. When I move to desktop app for editing (which saves formatting), I can't easily go back to Sharepoint -- I end up in this death cycle of constantly opening and closing Sharepoint in my browser window after interacting with one doc. I'm a Mac user and using the Safari browser. Any advice welcome.

As mentioned in the title, this is the first job i’ve used sharepoint at and i’m not sure of all its capabilities and such so this may seem like a simple task 😅

i’m trying to create a form for employees to submit per diem requests. so i need them to have access to the form for starters.

When they enter their name, i want the “employee code” field to auto populate with their code based off a data list that contains all employees and their codes.

next, when they start typing the job number, i want a drop down menu of all the available matching job numbers based on what they entered so they can select it. currently, we have it so they manually enter the job number, but if they make a typo without realizing and submit their form, it creates a mess behind the scenes so we want to prevent that by allowing them to select the number from a drop down list.

i have a list of all available job numbers as well as employees and their codes, but im not sure how to connect those to the sharepoint form for the data to be pulled from.

any and all help and advice is appreciated :)

We have a SharePoint site with a folder structure related to a project. The project currently contains approximately 111 GB of data.
We have recommended moving these files to a separate, dedicated SharePoint site. The reason is that the customer now wants to restrict access to certain folders, as not everyone with access to the current site should be able to access all of the project files.
Our recommendation is therefore to move the project files to a separate, restricted SharePoint site.
Our main goal is to keep the structure as simple as possible and avoid creating a deep folder structure with unique permissions on individual folders. We believe that this could become difficult to maintain over time.
Instead, we are considering using the standard SharePoint roles/groups:
Owners – Two people are appointed by the project manager as site owners. They are responsible for maintaining the site and managing access.
Members – Members have edit permissions.
Visitors – Visitors have read-only access.
Our proposed structure is to use two document libraries on the site:
Documents
This is the default document library that comes with a SharePoint site. The content here should be accessible to all members and visitors.
Documents – Confidential
We would create a second document library specifically for confidential/sensitive project documentation. On this library, we would break permission inheritance so that only the Owners group has access by default.
We would then add this document library to the site’s navigation so that it is clearly visible and easy to find.

The idea is that the site owners would then grant specific members access to the entire Documents – Confidential library when required, rather than managing permissions at folder or file level.
This would allow us to keep the information architecture at a high level, while still keeping the data on the same SharePoint site. It would also avoid creating a complex folder hierarchy with unique permissions.
What do you think about this approach?
Would this be considered a good SharePoint best practice, or would you recommend a different approach?
Our main priorities are:
Keeping the structure simple and maintainable
Avoiding unique permissions on individual folders/files where possible
Making access management easy for the site owners
Keeping the confidential and non-confidential content clearly separated
Keeping the data within the same SharePoint site
One additional question regarding permissions:
Is it correct that if a site owner grants a user Edit permissions to a folder or document library, that user may then be able to share individual files or folders with other people who do not otherwise have access to the site or document library?
If so, how would you recommend preventing users with Edit permissions from extending access to confidential content themselves? Would this be another reason to use a separate SharePoint site for the confidential content?

I have been using PowerShell 7 and SharePoint Online Management Shell for months.

I tried a few weeks ago and got an error when I was trying to go to Connect-SPOService -Url https://TENANTNAMEHERE -admin.sharepoint.com

I had PIM in with SharePoint Administrator RBAC as I had done before.

Now I get an error

WARNING: Unable to load DLL 'msalruntime': The specified module could not be found. (Exception from HRESULT: Ox8007007E)

I uninstalled the SharePoint Online Management Shell and restarted and ran sfc and DISM checks and restarted.

I AM able to get it to work if I tell it to go to the web browser yet not with the msalruntime where it is unable to load the DLL. I don't know if I should try to install this on another system and copy the DLL yet I would think with a fresh install it would write the DLL.

Windows PowerShell

Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\WINDOWS\svstem32> Import-Module Microsoft.Online.SharePoint.PowerShell

PS C:\WINDOWS\svstem32> Connect-SPOService -Url https://TENANTNAMEHERE-admin.sharepoint.com

WARNING: Unable to load DLL 'msalruntime': The specified module could not be found. (Exception from HRESULT: Ox8007007E) See https:/ aka.ms msal-net-wam#troubleshooting

Connect-SPOService : No valid OAuth 2.0 authentication session exists

At line:1 char:1

+ Connect-SPOService -url https://TENANTNAMEHERE-admin.sharepoint.com

+--------

CategoryInto : NotSpecified: (:) [Connect-SPOService], AuthenticationException

+FullyQualifiedErrorId : Microsoft.Online.SharePoint.PowerShell.AuthenticationException,Microsoft.Online.SharePoint.PowerShell.ConnectSPOService

PS C: \WINDoWS\svstem32>

Retention and Purview are the bane of my existence.

Since MRM is going away, I'm working on retention via Purview. We have doc libs with various retention policies, say 1, 3 and 5 years for example. With Purview I push a label policy out to the site, the policy has the 3 retention policies in it, and I can then assign which of the 3 policies to whatever doc library I want, and apply it to all documents in the library.

Where I'm stuck is that if I move a file with a 1 year label on the document into a 5 year area, the 1 year sticks instead of adopting the 5 year policy. I can see this being a major headache down the road when users think they've moved something into a 5 year folder and it disappears.

Anyone already figured out a way around this? Doing a script is untenable for the # of files we have in SPO.