Developing an app for SharePoint autohosted in Azure

22
Developing an app for SharePoint autohosted in Azure Maxim Lukiyanov Program Manager 3-023

description

Developing an app for SharePoint autohosted in Azure. Maxim Lukiyanov Program Manager 3-023. Agenda. Technology of autohosted apps Hosting environment Use cases Building an autohosted app. App model: past, present and future. Azure, IIS, LAMP, etc…. SharePoint 2007. - PowerPoint PPT Presentation

Transcript of Developing an app for SharePoint autohosted in Azure

Page 1: Developing an app for SharePoint  autohosted  in Azure

Developing an app for SharePoint autohosted in AzureMaxim LukiyanovProgram Manager3-023

Page 2: Developing an app for SharePoint  autohosted  in Azure

Technology of autohosted appsHosting environmentUse casesBuilding an autohosted app

Agenda

Page 3: Developing an app for SharePoint  autohosted  in Azure

SharePoint 2007SharePoint 2010SharePoint

SandboxSharePoint

Azure, IIS, LAMP, etc…

_api

SharePoint 2013App model: past, present and future

Page 4: Developing an app for SharePoint  autohosted  in Azure

SharePoint-hostedBuild your whole app or use SharePoint for list and document storage in autohosted or provider-hosted apps.AutohostedWhen you need server code and SQL Azure for your team app but don’t want to get into the hosting business.Provider-hostedUse for apps requiring the greatest amount of flexibility and scalability and toolset and backend services that cross app instances.

Three hosting options to provide the flexibility and scalability your app needs.

App model: hosting

Page 5: Developing an app for SharePoint  autohosted  in Azure

What is autohosted app

App Catalog

SharePoint Store*

Web Site SQL DB Workflow

Deploy

AzureSharePoint Online

* support for autohosted apps in SharePoint Store is coming soon.

ASP.NETWeb formsWeb pagesMVCAzure SQL Database1GB size limitGeo replicated copy for disaster recovery

Page 6: Developing an app for SharePoint  autohosted  in Azure

Instance isolationSharePoint

OnlineAzure

Tenant 1Site A

Site B

Tenant 2Site C

Site D

Web Site SQL DBWeb Site SQL DB

Web Site SQL DBWeb Site SQL DB

Page 7: Developing an app for SharePoint  autohosted  in Azure

Demo

Kudos App

Page 8: Developing an app for SharePoint  autohosted  in Azure

How it works1. Developer builds *.APP package 2. App is published to SharePoint 3. User installs app 4. SharePoint provisions Azure Web Site 5. SharePoint provisions Azure SQL Database 6. SharePoint provisions Azure Workflow

Visual Studio

SharePoint Site

App Catalog / SharePoint Store

*.app

Azure Web Sites Azure SQL DB

Azure Workflow

Page 9: Developing an app for SharePoint  autohosted  in Azure

Azure SQL Database

Windows Azure

SharePoint Online

App’

Web Site v2

DB’

App v2.0

Web Site v2

DB v2

Reliable upgradeVisual Studio

App Catalog / SharePoint Store

Browser

App v1.0

Web Site v1

DB v1

App v2.0

Page 10: Developing an app for SharePoint  autohosted  in Azure

Hosting environment

Page 11: Developing an app for SharePoint  autohosted  in Azure

Hosting modelAutohosted apps are provisioned into Microsoft owned Azure accountNo person has access to this accountHosting is provided by tenants, developer doesn’t pay for hosting

1 app hosting license = 1 user / app / month

Initial number of app hosting licenses included for freeTenant admins can purchase more licenses

* Support for autohosted apps is coming soon

Per user pricing App Catalog SharePoint Store*

Page 12: Developing an app for SharePoint  autohosted  in Azure

Demo

App hosting licenses

Page 13: Developing an app for SharePoint  autohosted  in Azure

Resource throttlingApp resources scale up with number of app users.Other limits1 Web Site instance1 GB of Azure SQL DB

0 25 50 100 150 200 250 3000

50

100

150

200

250

app hosting licenses

CPU time / day, in minutes

Usage quotas can be adjusted in the future.

Page 14: Developing an app for SharePoint  autohosted  in Azure

1 user

Usage quotas

Usage Quota 25 users 250 users and more

CPU TIME (Daily) 25 MINS / DAY 100 MINS / DAY 200 MINS / DAY

CPU TIME (5 minutes) 2 MINS / 5 MINUTES 7 MINS / 5 MINUTES 13 MINS / 5 MINUTES

DATA OUT 132MB / DAY 732MB / DAY 1533MB / DAY

FILE SYSTEM STORAGE 1GB 1GB 1GB

MEMORY USAGE 640MB 640MB 640MB

Page 15: Developing an app for SharePoint  autohosted  in Azure

Use cases

Page 16: Developing an app for SharePoint  autohosted  in Azure

Team appsResource trackingTeam processesEvent receiversIndividual productivityDocument assembly, etc.

Autohosting is for team apps

Autohosted appsProvider-hosted apps

Number of users

Apps

Page 17: Developing an app for SharePoint  autohosted  in Azure

Demo

Building Kudos App

Page 18: Developing an app for SharePoint  autohosted  in Azure

Takeaways:SharePoint autohosted apps are easy to develop and deploy, use standard Azure Web Site and SQL, have reliable lifecycle and DR capabilities.

Page 19: Developing an app for SharePoint  autohosted  in Azure

SharePoint Apps:http://dev.office.comhttp://blogs.msdn.com/b/officeapps

Windows Azure Web Sites: http://www.windowsazure.com/en-us/home/scenarios/web-sites/

Office & SharePoint Resources

Please submit sessions evals on the Build Windows 8 Appor at http://aka.ms/BuildSessions

Page 20: Developing an app for SharePoint  autohosted  in Azure

3-020, Building apps for Office and SharePoint 2013 using the web technologies you know and love, Part 1 (Rolando Jimenez Salgado)

3-021, Building apps for Office and SharePoint 2013 using the web technologies you know and love, Part 2 (Eray Chou)

3-022, Building end-to-end apps for SharePoint with Windows Azure and Windows 8 (Rob Howard)

Related sessions

Page 21: Developing an app for SharePoint  autohosted  in Azure

Questions

Page 22: Developing an app for SharePoint  autohosted  in Azure

© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.