office 365 platform flexible tools understand different provisioning options and their advantages...

Site provisioning techniques with SharePoint apps Bert JansenSenior ConsultantMicrosoftVesa Juvonen

Principal ConsultantMicrosoft

SPC403

Bert JansenPre-MicrosoftRealDolmenSoftware architect, product manager, developer

Microsoft (2007-)Senior ConsultantSharePoint deliveries to on-premises and cloudLead architect for the infrastructure, development and governance aspects of the implementation

ContactEmail – bert.jansen@microsoft.com

Expertise

Cloud based deliveries

Value for your investments

Vesa JuvonenPre-MicrosoftEntrepreneur, ICL, Fujitsu, BaswareSoftware Architect, Project manager, program manager, Developer, Casino dealer and middle manager, substitute teacher in high school, Hamburger joint worker

Microsoft (2006-)Principal ConsultantSharePoint 2013 Ignite Program Manager

Instructor in SharePoint 2013 and 2010 Ignite programs

WW CoE SharePoint – RangerMCM/MCSM Instructor & Content Owner

Instruction cross 18 rotations from start to finish of the program

ContactEmail – vesa.juvonen@microsoft.comBlog – http://blogs.msdn.com/vesku

Expertise

It’s Finglish…Passion for the cloud

Office 365 Platform Contextual Apps

Robust O365 API’s Flexible Tools

Documents People | Groups

Mail Tasks

Calendars REST Web Services

Session Objective

When to use what?

Understand different provisioning options and their advantages and disadvantages…

Introduction to site provisioning patternsQuick check up of options…

Feature stapling

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

Site definition provisioning process

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

WebTemplate provisioning process

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

Full server side custom solutions

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

Pretty common solution for custom self service site collection creation

“SP Apps is pattern for cloud, not for my on premises…”

Really?

What if… We would use

same model for on-premises and

cloud?

SharePoint Farm

Remote provisioning process

Provider Hosted Apps

Own app specific configuration

Artefacts

<xml>

12

3

4

5

CSOM / REST

Evergreen and release cycle for customizations

SP2013

Loosly coupledSharePoint customizations

O16 O17 O18

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 DevelopmentIf you know general web development, you also know SharePoint development…

We are in the biggest change of the SharePoint history…

Choose your path…

How do we make this happen in real life?

Provider-hosted AppsThe theory

SharePoint Provider-hosted

Existing sites and services

(host web)

Application site (app web)

Dedicated server or hosting service

Remote Provisioning: 100% cloudA real world sample

http://teams.contoso.com/sites/site

<xml>

12

3

4

Demo

Remote Provisioning for Office365 using Windows Azure

• 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

SharePoint Farm

Site collection creation on-premises with CAM

Provider Hosted Apps

Own app specific configuration

Artefacts

<xml>

1

CSOM / REST

Custom WCF service

2

3

Hybrid self service pattern – Classic

Contoso

SharePoint Farm

http://teams.contoso.com/sites/site

<xml>

https://contoso.sharepoint.com

/sites/site

<xml>Provider Hosted Apps

• Operations are driven from the on-premises

• Integration to cloud is pretty simple with the tenant CSOM

2

1

Hybrid self service pattern – Cloud First Contoso

Provider Hosted Apps

• Operations are driven from the cloud

• Connectivity from cloud to on-premises using service bus

https://contoso.sharepoint.com

/sites/site

<xml>

SharePoint Farm

https://teams.contoso.com/sites/site

<xml>

Site Creation WCF service

Service Bus Tunnel

CSOM

1

2

Demo

Site collection creation in on-premises using SP App Pattern

• 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

SharePoint Farm

OneDrive for Business branding management with remote provisioning

Provider Hosted Apps

Own app specific configuration

Artefacts

1

2

34

CSOM / REST

Demo

Manage OneDrive for Business site collection provisioning – Branding and other customizations

• Modify OneDrive for Business sites by accessing them using Social CSOM

• Can be used for branding and for any other configurations

Key takeaways

Stop using declarative options for site provisioning…

Use SP App patterns to provide flexibility for your provisioning patterns…

SP App patterns can be use cross cloud and on-premises…

http://officeams.codeplex.com

Source for great reference app implementationsPublishing channel for ready to use examples on apps,

which you can use in your own projects

Explore our new Preview APIs

In-depth articles on MSDNSubject to change; not for production use

Connect with the community

Speak your mind at OfficeSPDev.UserVoice.ComSolve your roadblocks on StackOverflow

[Office] and [SharePoint]

Build using our toolsUnleash your development skills with Office Dev Tools for Visual Studio 2013 and Office 365 API Tools for Visual Studio 2013

Calls to Action

MySPCSponsored by

connect. reimagine. transform.

Evaluate sessionson MySPC using yourlaptop or mobile device:myspc.sharepointconference.com

© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.