Office 365 Platform Flexible Tools

Understand different provisioning options and their advantages and disadvantages…

 Key objective  Extend site provisioning with out of the box site definitions  Challenge  Cannot be used to bring new template options  Only available in Office365 at site collection scope Modify oob site definition provisioning model

 Key objective  Provide new site options to be available for the end users  Same capabilities as for out of the box site definitions  Challenge  Impacts on major version upgrade  Cannot be supported in Office365  Deployed in farm level Classic templating system available since 2003 or 2007

 Key objective  Provide new site options to be available for the end users  Site associated to out of the box site definition  Challenge  Have to be updated with minor version updates to the farm  Causes significant maintenance challenges due complete replacement of oob site definition  Supported in site collection level in Office365 Introduced in 2010 initially for site templates, but can be used “manually” as well

 Key objective  Provide self service and polished site collection creation opportunity for end users  Can be extended with workflows and timer jobs  Challenge  Not supported in Office365 as such  Requires full trust code  Can be complex to setup and maintain

What if… We would use same model for on- premises and cloud?

Own app specific configuration Artefacts CSOM / REST

SP2013 Loosly coupled SharePoint customizations O16O17O18 Development You choose when and how applications are updated... Backwards compatibility for API level to move customizations cross versions Customizations don’t block new capabilities from SharePoint Customizations extend, not change SharePoint Customizations can be updated with minimal impact on SharePoint Customizations will utilize services from SharePoint and other services, but won’t usually change out of the box services.

Denial is the first step… Product roadmap is clear though…

Remember when feature framework and solutions were introduced…

Or when you were told that you’ll have to learn CAML…

SharePoint App Development If you know general web development, you also know SharePoint development…

We are in the biggest change of the SharePoint history… Choose your path…

Existing sites and services (host web) Application site (app web) Dedicated server or hosting service

/sites/site 1234

Developing SharePoint Apps running on Azure Cloud services works great on Visual Studio 2013 and Azure is an easy to use and scalable host for your provider hosted apps Remote provisioning of a site via CSOM is a powerful, flexible and future proof method

Own app specific configuration Artefacts 1 CSOM / REST Custom WCF service 23

/sites/site /sites/site Operations are driven from the on- premises Integration to cloud is pretty simple with the tenant CSOM 21

Operations are driven from the cloud Connectivity from cloud to on- premises using service bus /sites/site /sites/site Site Creation WCF service Service Bus Tunnel CSOM 12

Site collection creation is not available with CSOM in on-premises You can easily extend the supported remote capabilities by using “smart” extensions with farm solutions Expose additional APIs, do not cause maintenance challenges by placing business logic on the SharePoint side

Own app specific configuration Artefacts 1234 CSOM / REST

Modify OneDrive for Business sites by accessing them using Social CSOM Can be used for branding and for any other configurations

Sponsored by