In a modern Intranet, we generally want to store content on the site where it should be managed. We think of this as distributed content management. It’s similar to the way News works in modern SharePoint. This usually means each department or organizational unit can (and should) manage their own content using a process which makes sense for them. At the same time, we may want to roll up that content in one central location for ease of access. A Policy Center is a great example of this approach and one we find ourselves building for many of our clients. But this approach works for many types of content. In this session, you’ll see how the following components add up to make a Policy Center: * Information architecture (IA) in the form of Site Columns and a Content Type to represent a Policy * A Site Template which only instantiates a Policy library in the site and applies the appropriate IA (Content Type, views, etc.) * A Policy library in each department Intranet site where it will be used, deployed using the Site Template, with Policies specific to that department * Changes to the search schema to support metadata filtering * A Policy Center page built using PnP Modern Search Web Parts to display the Policies from across the Intranet Additionally, we’ll discuss various approaches to solve the content management puzzle – before the Policy is even visible on the Intranet. We'll also talk about how an approach like this prepares your content for a solid retention approach.

With all the machine learning (ML) and artificial intelligence (AI) available in Microsoft 365 these days, do we still need to think about information architecture? Can automation fulfil the promise of reducing the load on information architects and developers? In this session, we’re review some of the better practices for constructing a powerful information architecture and why it still matters. We’ll look at real-world examples and talk about what automation can and can’t do for you. Technology is evolving quickly, so expect to see a few tidbits you don't expect, as well as a healthy doses of reality.

An intranet can support your organization’s ability to communicate and collaborate effectively, make information easy to find, automate business processes, and help cut administrative costs. But where do you start? In this all-day tutorial, we will focus on the processes for designing and planning a powerful intranet. We’ll also review the mechanics of building the basic structures in modern SharePoint Online and surfacing it in Teams through Viva Connections. At the end of the tutorial, we will have demoed common solutions like a Policy Center, global navigation, and personalized content experiences. Some of the approaches we will cover include: -Creating a branded experience -Building an enterprise information architecture -Surfacing the right information, at the right time -Centralizing information and creating search-based experiences -Implementing better practices for writing for the web -Creating a seamless connection between your SharePoint-based Intranet and Microsoft Teams Join MVPs Marc Anderson and Emily Mancini to gain a deeper understanding of the out of the box technical capabilities so you can focus on identifying your desired business outcomes, defining your overall content strategy and governance, and driving the adoption of your intranet at your organization.

PnP Modern Search is one of the Swiss Army knives of SharePoint; every tenant should have it installed. In this all-day, hands-on workshop, we'll start with installation and work through basic and advanced topics. At a minimum, we will cover: * The relationship between PnP Modern Search, "out of the box" search, and Copilot. i.e., when and why you might need PnP Modern Search * Installing the PnP Modern Search solution in the tenant App Catalog (or Site App Catalog - but you'll want it across the tenant!) and staying up to date with new releases * Setting up the search schema to support the search-driven experiences you'd like to build with PnP Modern Search * Setting up list and/or libraries with the appropriate information architecture applies to serve as the source(s) for PnP Modern Search * Adding the four Web Parts - Search Results, Search Filters, Search Box, and Search Verticals - to a page and connecting the Web Parts to each other to build custom capabilities * Understanding the different combinations of PnP Modern Search Web Parts we can use to build sophisticated search-driven experiences * Returning different types of objects with Search Results, like items, documents, lists and/or libraries, sites, etc. by adapting our queries * Using SharePoint Search or Microsoft Search - which should you choose when? * Writing custom Handlebars or Adaptive Card templates to style your search results and filters * KQL tips and tricks to optimize your results * Styling search results using hTWOo and custom CSS

As an information architect, you may have been ceding understanding of Purview to others in your organization – or ignoring it entirely, especially in smaller organizations. The first thing many organizations want to do is apply some level of retention (Policies or Labels) to their content. If you don’t plan well for this, you may end up locking down content you don’t intend to lock down, and reversing your decisions can be difficult. This can lead to rapid storage consumption within your tenant, among other issues. In the end, what you can do well in Purview is dependent on a strong information architecture. Knowing what content is stored where – and being able to identify it in Purview – is the big key to success. Purview depends in part on search, and search works well with a strong information architecture. If you’re embarking on this journey, perhaps due to wanting to roll out Copilot in your organization, this session will give you some Purview basics, considerations to apply to your information architecture, and some of the pitfalls we’ve seen in the field.