Sympraxis Consulting

In this episode of Ask Sympraxis, the team tackles a topic that refuses to disappear: SharePoint subsites. While subsites remain functional today, Microsoft has been steadily steering organizations toward modern, hub-based architecture for years. The discussion explores why the modern “hub before sub” approach provides greater flexibility, simpler governance, and a more sustainable long-term design for SharePoint Online. The conversation begins by contrasting traditional SharePoint architectures with modern site design. Historically, organizations often built large, deeply nested site hierarchies containing departments, projects, documents, and permissions within a single site collection. Modern SharePoint instead favors a flat architecture where separate sites are organized by purpose and connected through hub sites. This approach allows organizations to separate collaboration sites, communication sites, departments, and projects while still providing a unified experience through shared navigation, search, branding, and content rollups.

InfoPath’s retirement is finally real—and this time, Microsoft means it. With support ending July 14, 2026, organizations must move quickly to modernize their forms strategy. But this isn’t just a migration exercise. It’s an opportunity to rethink how you collect data, design processes, and choose the right tools for the job. TL;DR InfoPath becomes read-only on July 14, 2026—no more editing or creating new forms Forms should only collect data, not manage business processes Upgrading forms is a chance to re-evaluate and simplify your processes There’s no single replacement—choose from a range of Microsoft 365 tools AI can assist, but should not be the primary interface for structured business processes Rethinking Forms: Collect, Store, Process One of the biggest mindset shifts moving beyond InfoPath is separating responsibilities: