Session Abstract

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.

Marc Anderson

SharePoint Guy, Microsoft MVP, Enterprise Collaboration Strategist, Consultant, Developer Founder & President, Sympraxis Consulting