How to Build out a Basic PnP Search Page

 This requires PnP Search Web Parts for SharePoint

1. Create a SharePoint Page and call it "Search"
2. Add a "One Column" panel for the Search Box
3. Add the "PnP - Search Box" Web Part
4. Create a "One-third right" panel
5. In the left section, add the "PnP - Search Results" Web Part
6. In the right section, add the "PnP - Search Filters" Web Part

Search Results

1. On the "PnP - Search Results" Web Part, set the data source to SharePoint
2. Change the Query template to the Document Library you want to search. This can be mutiple places, but for todays example it will just be one.
1. {searchTerms} - This connects it to the Search Box
2. Path: https://{root site url}/sites/{my site}/{document library}
3. Click "Apply"
4. If you have custom field, you must make sure they are selected in  "Selected properties"
1. I have: "RefinableString01" which I have mapped to a "Division" field in my Document Library
5. Leave all the rest of the default setting for "page 1" and go to "page 2" of the properties
6. Set the layout as "List"
7. 
   
   
8. Leave all the rest of the default setting and go to "page 3"
9. For "Use input query text", turn on
1. Set it to "Dynamic value"
2. Connect to Source = PnP Search Box
3. PnP - Search Box's proterties = "Search query"
4. Use a default value = Off
10. For "Connect to filter Web Part", turn on
1. Use filter from this component = Refinable Filters - {Unique GUID}
11. 
    
    
12. Leave all the rest of the default setting

Search Filter

1. Use data from these Web Parts = Search Results - {Unique GUID}
2. Under "Filter settings"
1. Click "Edit" for Customize filters
2. Filters:
1. Created Date - Created
2. Created By - CreatedBy
3. File Type - FileType
4. Division - RefinableString01
3. 
   
   
4. Click "Save"
3. Leave all the rest of the default setting

Save the whole page

Workflow failing on 29 Feb 2025

 Funny New error for me today.

The SharePoint list date needs to be increased by 1 year. Seems simple, right. 

However last year this item was done on 29 Feb on a Leap year, and there is no 29 Feb this year, so the Workflow is failing to update the year, because the year is invalid.

Error message: 

The DateTime represented by the string is not supported in calendar System.Globalization.GregorianCalendar.

The Fix

Do a simple replace of the Date String

replace({DataString},'-02-29','-02-28')

SharePoint Feature Retirements and Deprecations: Everything Ending by 2026

SharePoint Feature Retirements and Deprecations: Everything Ending by 2026

Microsoft is accelerating its modernization of SharePoint and Microsoft 365 by retiring legacy technologies that were once central to classic SharePoint environments. Between 2025 and 2026, multiple long-standing features will reach end of support or be fully removed from Microsoft 365 and SharePoint Online.

The most significant retirements include:

• InfoPath Forms Services and the InfoPath 2013 client (end July 14 2026), ending browser-based form support.

• SharePoint Add-Ins and SharePoint 2013 workflows (April 2 2026), replaced by Power Automate and SharePoint Framework (SPFx).

• SharePoint Alerts (classic “Alert Me”), Secure Store Service, and Power BI list integration, all phased out by late 2025–mid 2026.

• On-premises products—SharePoint Server 2016/2019, Designer 2013, and Office Online Server—will also reach end of extended support by mid-to-late 2026.

These changes reflect Microsoft’s focus on modern, cloud-based, and low-code technologies: modern pages, Power Platform tools, and SPFx-based customizations.

The next few months mark a crucial transition period for organizations still relying on legacy SharePoint features. While many classic components will continue to function temporarily, Microsoft’s roadmap makes it clear that modernization is no longer optional — it’s essential for compatibility, security, and long-term sustainability.

To prepare:

1. Inventory all classic pages, InfoPath forms, workflows, and add-ins.

2. Prioritize migrations based on confirmed end dates (especially anything ending by mid-2026).

3. Adopt Power Apps, Power Automate, and SPFx for modern replacements.

4. Communicate and train users early, so change is smoother when retirements take effect.

By planning now, organizations can ensure a controlled, strategic modernization rather than a last-minute rush as these legacy services go dark in 2026.

Timeline (now → end of 2026)

2026-01 (rolling)

SharePoint Alerts (“Alert Me”)
What happens: Creation of new alerts turned off for all tenants.
Replacement: Use Power Automate / SharePoint rules / Teams notifications.
Reference: TECHCOMMUNITY.MICROSOFT.COM+1

2026-04-02

SharePoint 2013 Workflows (SharePoint Online)
What happens: Removed from existing tenants (already off for new tenants since 2024-04-02).
Replacement: Power Automate.
Reference: Microsoft Support+1

2026-06-30

SPFx Field Customizers (specific scenarios)
What happens: Microsoft signaled retirement by June 2026.
Replacement: Prefer Column JSON formatting / Power Apps.
Reference: voitanos.io

2026-07-14

InfoPath Forms Services (SharePoint Online)
What happens: Removed from SharePoint Online; InfoPath browser forms stop working.
Replacement: Power Apps / other modern form solutions.
Reference: TECHCOMMUNITY.MICROSOFT.COM

2026-07-14

InfoPath 2013 client
What happens: Product reaches end of extended support.
Reference: Microsoft Learn

2026-07-14

SharePoint Server 2016 (on-prem)
What happens: End of support (no updates/support).
Replacement: Migrate to SPSE / M365.
Reference: Microsoft Learn

2026-07-14

SharePoint Server 2019 (on-prem)
What happens: End of extended support (Mainstream ended 2024-01-09).
Replacement: Migrate to SPSE / M365.
Reference: Microsoft Learn

2026-07-14

SharePoint 2010 workflows (SP Server SE note)
What happens: SP2010 workflows no longer supported in SPSE after this date.
Replacement: 2013 workflows / Power Automate (per scenario).
Reference: Microsoft Learn

2026-07-14

SharePoint Designer 2013
What happens: End of extended support.
Replacement: Use Power Automate/Power Apps; Designer is legacy.
Reference: Microsoft Learn

2026-07 (Month)

SharePoint Alerts (classic)
What happens: Microsoft removes ability to use Alerts; existing alerts stop working.
Replacement: Power Automate / SharePoint rules.
Reference: Microsoft Support+1

How to Update your Birthday in Microsoft 365 User Profile

 The Birthday comes from the Microsoft 365 User Profile.

Its all the way at the bottom

Click "Save changes"

Favorite functionality in SharePoint

How to mark items as favorites in SharePoint

Marking items as favorites in SharePoint allows you to quickly access important documents, libraries, or sites. The process is straightforward and can be completed in just a few steps:

• Navigate to the SharePoint site, document library, or specific item you wish to favorite.
• Look for the "Favorite" icon, typically represented by a star or similar symbol, near the item or in the site navigation bar.
• Click the "Favorite" icon. The item will be added to your list of favorites, making it easily accessible from your SharePoint dashboard or favorites section.
• To remove an item from your favorites, simply click the "Favorite" icon again to unmark it.

Using the favorite functionality helps streamline your workflow by keeping frequently used resources at your fingertips. 

Favorite Folders

Where to find your Favorites

• If you favorite a file (or a folder) in a SharePoint library, you will find it under “Favorites” in the left menu when you view your OneDrive for Business via the web.
• If you “Save for Later” on a SharePoint article or News posts it will also be visible on OneDrive Favorites.

 

Benefits of using favorites for quick access

Utilizing the favorites feature in SharePoint offers several advantages for users seeking efficient access to important resources:

• Reduces time spent searching for frequently used documents, libraries, or sites.
• Enables personalized navigation, allowing users to tailor their SharePoint experience to their workflow.
• Improves productivity by keeping essential content easily accessible from a centralized location.
• Supports better organization, especially when managing multiple projects or collaborating across teams.
• Minimizes the risk of overlooking critical information by keeping it at the forefront of your workspace.

By leveraging favorites, users can streamline daily operations and ensure that key resources are always just a click away. 

 

Also you can Favorite a SharePoint list

Other References:

https://techcommunity.microsoft.com/blog/onedriveblog/feature-deep-dive-favorites-and-shortcuts-in-onedrive/3960478?utm_source=chatgpt.com

https://adoption.microsoft.com/files/onedrive/Microsoft-OneDrive-quick-start-guide.pdf 

OOTB SharePoint Document Approval

I have created a blank Document Library: DocumentApproval1

1. Turn on the OOTB Approval
2. 
3. This brings up a dialog box. Enable Approvals, and Apply.
4. 
5. The “Approval status” column will appear.
6. Turn on the other Approval columns. Goto the “Show or hide columns” area. 
7. Add columns:
8. 
9. Columns:
1. Approval status: The status of the process
2. Approvers
3. Responses
4. Approval Creator: The person who starts the approval process

How it works

1. Upload a file
2. 
3. Click on Approval status: Not submitted. This will open the approval request form.
4. 
5. The Request approval form looks like this:
6. 
7. To have the approvals in series (one after another), select “Require responses in the assigned order”. If you want them in parallel (all at the same time), then don't select it.
8. Then add the people you would like to be the approvers.
1. Example of in Series turned on: “Require responses in the assigned order”
9. 
10. If Parallel is on, it will ask “Require a response from all approvers”. Which means the document wont approved until everyone in the list has approved.
1. Example:
11. 
12. If this Example I'm just going to assign it to myself, and submit.
13. 
14. It start the approval process (aka the workflow).
15. 
16. Then the Approver gets an Approval request, which will arrive by Teams only (not by Email).
17. 
18. The really interesting thing, is you can get that same view on the Document Library, and click on the Approval status, as the approver you will see the same thing.
19. 
    
    
20. 
21. As the non-approver you will see this:
22. 

    
    
23. Then the Approver, I write my comment and approve. This can be done, on the document library or Teams.
24. Once approved it kicks off the workflow process and changes the status to Approved.
25. Now it looks like this, and you can click on it and it show the full process.
26. 
27. 

What happens when you update the document properties?

1. Update the Title, because for this example that is the only property
2. It then pops up with this:
3. 
4. 
5. When you apply the changes, the Approval Status changes
6. 
7. Then you have to do the full process all over again.

Other

The Approval Process is not tracked in Version history:

The is no OOTB Email when Approval are request. So if you do want an email, a custom Power Automate workflow will need to be created on the “Approval Requests" list in Dataverse.

A Guide to SharePoint Header Options

When customizing your SharePoint site, one of the most impactful design elements is the site header. The header sets the tone for your site, provides quick access to key navigation, and ensures branding consistency. SharePoint offers several configurable options for headers, including layout choices and tick-box settings that affect visibility and functionality.

In this article, we’ll walk through each option available, what it does, and show how it looks in practice.

Header Layout Options

SharePoint provides multiple header layouts to choose from, allowing you to set the look and feel of your site:

• Standard
• A balanced header layout with logo, title, and navigation placed neatly at the top

• Compact
• Reduces vertical space, making it cleaner and more minimalistic. Great for sites with a lot of content.

• Minimal
• Focuses heavily on content, hiding most of the header elements except essentials.

• Extended
• Provides additional space for logos and branding elements.

Header Settings:

Horizontal Navigation Settings

By default, SharePoint headers display with Horizontal Navigation, giving your users an easy way to access top-level links.

However, this navigation can be turned off if you prefer a cleaner look or if you want to emphasize page content over navigation.

This flexibility allows you to adapt the header design depending on your site’s purpose. For example, communication sites might benefit from visible navigation, while landing or campaign-style pages may look better without it.

Navigation Settings:

Header Elements & Tick-Box Options

Beyond layouts, SharePoint lets you fine-tune what appears in the header using simple toggle (tick-box) options:

• Site Logo Visibility
• Control whether the site logo is displayed in the header.
• No Logo

• With Logo

• Site Title Display
• Choose whether the site’s name is shown next to the logo or hidden for a cleaner look.

 

Hub Settings and the Header

If your site is connected to a hub site, the header options expand to include hub-specific settings. These ensure consistency across connected sites and provide a unified navigation experience.

Hub Settings in the Header:

• Hub Site Navigation
• A horizontal navigation bar that appears below or integrated into the header for cross-site navigation.

• Global vs Local Navigation
• Choose whether to show hub navigation only, site navigation only, or both together.

Permissions Required to Customize Headers

Not everyone will see the same customization options. Permissions play an important role in what you can do with headers and hub settings:

• Site Owner (Full Control)
• Can customize the site header layout, toggle all tick-box options, and change logo, title, or background.
• Can also associate or disassociate a site from a hub.
• Hub Site Owner
• Has additional permissions to manage hub navigation, apply hub-wide branding, and control how associated sites inherit hub header settings.
• Site Member (Edit)
• Typically cannot adjust the header. Members can create/edit content but not alter site design.
• Site Visitor (Read)
• No customization permissions. Can only view the site as configured by owners.