What's New for SharePoint Server – March 2024

In this article:


 



 


SharePoint Server Subscription Edition Version 24H1 feature update


 


Today we’re delighted to share the latest steps in our evergreen journey for SharePoint Server with the release of the Version 24H1 feature update for SharePoint Server Subscription Edition. This feature update brings greater customization capabilities to our modern UX, simplifies Open ID Connect configuration, and opens up a new channel for on-premises customers to share their feedback directly with the SharePoint Server product team.


 


Search vertical customization in modern search results


 


Long-time SharePoint Server customers are aware of the breadth of functionality available in the classic SharePoint UX. This power can also be its Achilles’ heel, overwhelming users with options as they carry out their day-to-day work. Microsoft introduced the modern UX to address these concerns, simplifying the SharePoint experience and making it easier for users to perform their most common tasks.


 


While the modern UX has been a welcome redesign of the SharePoint experience, Microsoft recognizes that there are opportunities to further enhance the modern UX without negating its advantages in ease of use. Search verticals are a good example of this.


 


Search verticals provide a way for users to quickly filter the types of search results returned for a query, such as by only returning documents, news posts, and so on. Customers have the flexibility to customize which search verticals are present in the classic search results page. However, search verticals couldn’t be customized in the modern search results page. Customers were locked into using the default search verticals that were built-in to SharePoint Server Subscription Edition.


 


This limitation is removed starting with the SharePoint Server Subscription Edition Version 24H1 feature update. Customers now have the ability to add custom search verticals to their modern search results page at both the site and organization level. This will help users to quickly find what they’re looking for while staying in the simplified modern UX.


 


OpenID Connect (OIDC) integration with SharePoint certificate management


 


The initial RTM release of SharePoint Server Subscription Edition introduced several new features that were designed to improve the security and manageability of SharePoint Server.


 


One of those new features was OpenID Connect (OIDC) authentication support. OpenID Connect is a modern authentication protocol that makes it easy to integrate applications and devices with an organization’s identity and authentication management solutions to better meet their evolving security and compliance needs. For example, organizations can enforce authentication policies such as multifactor authentication (MFA), conditional access policies based on device compliance, and more.


 


Another new feature was SSL/TLS certificate management. This feature allows farm administrators to directly manage the deployment and lifecycle of SSL/TLS certificates in their SharePoint farms. This includes importing and exporting certificates into SharePoint, deploying those certificates to each server in their SharePoint farm, assigning certificates to web applications or other SharePoint resources, and automatic notifications when certificates are approaching their expiration date.


 


SharePoint Server Subscription Edition’s OIDC implementation includes a nonce cookie certificate, which is part of the infrastructure that ensures OIDC authentication tokens are secure. However, this nonce cookie certificate wasn’t managed by the SharePoint certificate management feature. As a result, customers had to manually deploy, configure, and monitor the expiration of this certificate on each server in their SharePoint farm.


 


Starting with the SharePoint Server Subscription Edition Version 24H1 feature update, the OpenID Connect (OIDC) nonce cookie certificate is now integrated into the SharePoint certificate management experience. SharePoint farm administrators can use the SharePoint certificate management feature to manage the full lifecycle of the OIDC nonce cookie certificate, including deployment of the certificate to all servers in the farm and automatic configuration of the necessary permissions. A new SharePoint Health Analyzer health rule has also been added to notify administrators if the nonce cookie certificate isn’t being managed through SharePoint certificate management.


 


Customer feedback experience in SharePoint Central Administration


 


Microsoft aspires to bring the best possible experiences for users around the world through its innovative product offerings. Customer feedback is critical to ensure we’re meeting the needs of our customers. That’s why we’re happy to announce a new way for customers to share their feedback with Microsoft from directly in the product.


 


Starting with the SharePoint Server Subscription Edition Version 24H1 feature update, an optional survey will appear to SharePoint farm administrators from time to time when they visit the SharePoint Central Administration site. The feedback shared through this survey will go directly to the SharePoint Server product team to help us improve the product to meet your needs. Customers can disable this customer feedback experience on a per-user or farm-wide basis if they so choose.


 


For more information about these new feature experiences, see New and improved features in SharePoint Server Subscription Edition Version 24H1.


 


End of support reminder for SharePoint 2016 and SharePoint 2019


 


It may be hard to believe, but SharePoint Server 2019 reached the end of Mainstream Support on January 9th of this year and is now in Extended Support. This means that it’s no longer eligible to receive non-security quality updates. Going forward, it’s only eligible to receive security updates.


 


In fact, the end of support for SharePoint Server 2016 and SharePoint Server 2019 is just over 2 years away. On July 14, 2026, both of these products will reach end of support. After that date, these products will no longer be eligible to receive support of any kind, including security updates.


 


If you’re currently using either of these products, now is the perfect time to start thinking about your future. There are two paths forward to remain supported:


 



  1. Migrate to SharePoint in Microsoft 365, which is our recommended approach. SharePoint in Microsoft 365 is our premier SharePoint experience and gives customers access to all of the latest productivity, security, and usability investments that Microsoft is making now and in the future.

  2. Upgrade to SharePoint Server Subscription Edition, which is the latest version of SharePoint Server. SharePoint Server Subscription Edition is based on our modern engineering and support lifecycle, which means we’ll continue to introduce new feature experiences and capabilities for it on a regular basis through feature updates, focusing on security and key customer scenarios. Note that while we’ll continue to make investments in SharePoint Server Subscription Edition, the scope of those investments will be much smaller compared to SharePoint in Microsoft 365, so the feature gap between them will only increase over time. For this reason, we encourage customers to migrate what they can to SharePoint in Microsoft 365 and only keep what they must in SharePoint Server Subscription Edition.


 


Summary


 


We hope SharePoint Server Subscription Edition customers take this opportunity to explore the new feature experiences we’ve introduced in the Version 24H1 feature update. We look forward to sharing even more new feature experiences with you in our next feature update, coming in the second half of this year.


 


And for SharePoint 2016 and SharePoint 2019 customers, don’t wait to begin planning your path forward to remain supported once these products reach end of support. Planning now will give you plenty of time to evaluate your options to either migrate to the cloud or remain on-premises, and begin executing on your decision. Whichever option you choose, Microsoft stands behind you with products and services designed to meet your needs today and in the future.

Simplify your work with Table rules in Microsoft Loop

Microsoft Loop is a powerful productivity tool that enables collaborative work and flexible information organization. It provides teams with a shared workspace where they can create and collaborate on content such as notes, tasks, and files. Loop integrates seamlessly with Microsoft Power Automate, allowing users to automate repetitive tasks. By creating rules, you can trigger specific actions based on conditions, saving time and effort. For instance, you can set up a rule to send an email notification to your team whenever a new task is added to a project table in Loop. Overall, Loop enhances teamwork and streamlines communication by combining a shared workspace with automated workflows.

Building an Automation Solution with Nintex and PowerApps

Building an Automation Solution with Nintex and PowerApps

Building an Automation Solution with Nintex and PowerApps

Modern organisations often look for efficient ways to automate their workflows and processes. Nintex and PowerApps are two powerful tools that enable businesses to create robust automation solutions. Below, I will outline the step-by-step process for building an automation solution using these technologies.

  1. Define the Problem and Objectives

The first step in creating an automation solution is understanding the process you wish to streamline. Ask the following questions:

  • What specific tasks or workflows need automation?
  • What are the expected outcomes or benefits?
  • Who will be the primary users of the solution?

Clearly defining the problem and objectives ensures alignment and provides a roadmap for the development process.

 

  1. Analyse the Workflow

Break down the process into its individual steps. Identify:

  • Inputs: What data or information is required at each stage of the workflow?
  • Outputs: What results or actions should the process generate?
  • Pain Points: Where are the inefficiencies or bottlenecks?

Document these details to design the automation solution effectively.

 

  1. Design the Solution Architecture

Map out the architecture of your solution, incorporating both Nintex and PowerApps:

  • Nintex: Use Nintex workflows for process automation and orchestration. Nintex can manage complex workflows, approvals, and document generation.
  • PowerApps: Build a user-friendly interface using PowerApps to interact with the automated processes. PowerApps can act as the front end for data input and user interaction

Clearly define how the tools will integrate and interact to achieve the desired objectives.

 

  1. Develop Nintex Workflows

Nintex workflows are designed to automate repetitive tasks and manage approval processes. Follow these steps:

  • Access Nintex within your SharePoint or Nintex platform environment.
  • Create a new workflow and select the appropriate template.
  • Configure workflow actions, such as data collection, condition checks, approvals, notifications, and integrations with external systems.
  • Test the workflow to ensure it functions as intended.

 

 

Nintex provides a drag-and-drop interface, making it easy to configure workflows even for users with limited technical expertise.

 

  1. Build the PowerApps Application

PowerApps allows you to create custom apps without extensive coding knowledge. Here’s how:

  • Open PowerApps and select “Create an App.”
  • Choose a blank canvas or a template based on your use case.
  • Design the app interface, including input fields, buttons, and navigation elements.
  • Connect the app to the data sources and Nintex workflows using connectors.
  • Test the app to ensure seamless interaction with the workflows.

PowerApps also supports mobile-friendly designs, enabling users to interact with your automation solution on the go.

 

  1. Integrate Nintex and PowerApps

To ensure both tools work together seamlessly:

  • Use APIs or connectors to establish communication between PowerApps and Nintex workflows.
  • Configure triggers in PowerApps to initiate workflows based on user actions (e.g., form submissions, button clicks).
  • Ensure data flows correctly between the app and workflows, maintaining accuracy and efficiency.
  1. Test and Refine the Solution

Before deploying the automation solution:

  • Perform thorough testing of the workflows and application.
  • Collect feedback from potential users and stakeholders.
  • Refine the solution based on feedback and test results.

Testing ensures that the solution is robust, user-friendly, and aligned with organisational needs.

 

  1. Deploy and Monitor

Once the solution is finalised:

  • Deploy it within your organisation.
  • Train users on how to interact with the app and workflows.
  • Monitor the solution’s performance and gather metrics to identify areas for improvement.

Regular monitoring helps ensure the solution remains effective and continues to deliver value.

 

Conclusion

By combining Nintex’s powerful workflow automation capabilities with PowerApps’ user-friendly app development platform, organisations can create customised solutions to automate processes, enhance productivity, and reduce errors. Following the steps outlined above ensures a methodical approach to designing and implementing an effective automation solution.