When dealing with an expansive SharePoint deployment, the site collection boundary is a wall frequently run into in many aspects of managing such an environment. How can we ensure consistency across our sites with our content, business processes, the user experience, and customizations? Is it possible to maintain workflows and web parts in multiple sites? Microsoft has provided us with some platform support in a small number of areas, but what can be done to augment capabilities and ease the management burden? We'll dive into possible approaches for handling:
• site lifecycles including provisioning and deletion
• workflow definition, replication, and updating
• custom web parts
We'll be employing out-of-the-box features including use of SharePoint Designer and shared service applications, PowerShell, Microsoft Patterns and Practices, and some custom code. While many of these methods require on premise farm situations, we'll discuss what is possible with SharePoint in Office 365. We'll also talk a bit about what could help us in a hybrid situation.
Bob German is a Cloud Developer Advocate for Microsoft focused on Microsoft 365 and Azure development. He's been developing collaborative applications since the early days of SharePoint, and has a deep background in the SharePoint Framework, Azure Bot Framework, Microsoft Graph API, and Azure Active Directory, all of which are helpful in building applications for Microsoft Teams.
Before (re)joining Microsoft, Bob was a Microsoft MVP and Principal Architect at BlueMetal, where he led the development of numerous collaborative applications, Intranets, and other custom Office 365 and Azure based solutions.