Options for Deploying Apps / Add-Ins Deploying to the Store Deploying To Exchange Deploying to The...

29
park the future. May 4 – 8, 2015 Chicago, IL

Transcript of Options for Deploying Apps / Add-Ins Deploying to the Store Deploying To Exchange Deploying to The...

Spark the future.

May 4 – 8, 2015Chicago, IL

Deep Dive into Custom App Provisioning and Deployment in Microsoft Office 365Steve WalkerSenior Program ManagerOffice365 Developer Experiences & Analytics Team

BRK3170

Agenda

Options for Deploying Apps / Add-Ins

Deploying to the Store

DeployingTo Exchange

Deploying to The Corporate

Catalog

AdditionalApproaches

Options for Deploying Apps/Add-Ins

Options for Publishing Apps/Add-InsDeployment Options vary by App/Add-In Type

App type Office Store Corporate catalog

Shared folder app catalog*

Exchange server

Task pane app x x x

Content app x x x

Mail app x x

App for SharePoint x x* Must be accessible by the Office Client– Can be configured for Office365 Pro Plus

Considerations for Publishing Office Apps/Add-insOffice Store App Catalog File Share

App is publically available.App is available to users with access to the SharePoint App Catalog

Apps available to anyone with access to the File Share & has the location registered in the office client Trust Center

Licensing framework available.

Licensing framework is not available for use.

Only the Manifests are located here. The App itself is still deployed to a web server

App package verified by Microsoft for technical and content adherence to policies.

App package verification performed by SharePoint when app is uploaded.

No validation. It’s just a file share.

You must be signed up with Microsoft Seller Dashboard to upload apps.

No registration with Microsoft required.

No Registration with Microsoft required.

Considerations for Publishing Sp Apps/Add-insOffice Store App Catalog

App is publically available. App is available to users with access to this SharePoint deployment

Licensing framework available. Licensing framework is not available for use.

App package verified by Microsoft for technical and content adherence to policies.

App package verification performed by SharePoint when app is uploaded.

You must be signed up with Microsoft Seller Dashboard to upload apps.

No registration with Microsoft required.

Mail Apps/Add-Ins are installed to an Exchange Catalog that is available to the users of the Exchange Server on which it resides

App Manifest is registered with Exchange. App Content is still required to be hosted in a Web Server accessible by the Exchange Environment.

Considerations for Publishing Mail Apps/Add-ins

Deploying to the Store

Considerations when deploying to the Store• Ensure that you familiarize yourself with

the App Validation Policies & the FAQ• Icons and Images/Screenshots must have

accurate size/resolution. Even minor deviations will result in rejections.

• ALL App Changes/Updates require re-approval.

• Be careful with CDN References. You can use them but they must be accessible through https as well as http

Things We Validate in the Store• Provide value to the Office Store Customer• Can display certain ads but ads must

adhere to content guidelines• Must behave predictably• Must put customer in control• Must be appropriate for a Global Audience• Must be easily identified and understood• Updates must not decrease functionality*

Things We Validate in the Store (cont’d) • Must Utilize Supported Capabilities• Creative workarounds and approaches not supported by the engineering team will be

rejected. In short, If we think we’ll break it in the future due to the undocumented nature OR you are utilizing deprecated functionality.

• Must provide a Seamless and Fluid Experience

• Follow the UX Guidelines: https://msdn.microsoft.com/en-us/library/jj220039.aspx • These are helpful guidelines to help you even for your corporate apps.

DemoDeploying to the Store

Steve Walker

Deploying Mail Apps/Add-Ins

Managed through the Exchange Admin Center

Office365 Admin > Exchange > Organization > Apps

Must have Exchange Administration rights OR “My Custom Apps” permissions

Deploying to the Exchange Admin CenterThis is your catalog for Mail Apps/Add-ins

DemoDeploying Mail Apps/Add-InsSteve Walker

Deploying to the Corporate Catalog

Special Site Collection for storing/managing/delivering apps for Office and SharePoint

Administrators of the catalog can upload and make apps available in the catalog.

Catalog must be CREATED before initial use.

https://technet.microsoft.com/en-us/library/fp161236.aspx

What is a Catalog ?

Corporate Catalog is per Web Application in SharePoint

SharePoint Online has 1 Web App Centralized Catalog Deploy Once, Available to all sites*

SharePoint On-Prem can have many Web Applications. May require multiple deployments of your app to multiple catalogs OR this is a feature to provide isolation.

Deploying to the CatalogDifferences between Office365 & On-Premises

Additional Approaches for SharePoint Apps/Add-Ins

App Stapling

Apps can be INSTALLED on the Catalog Site

This enables additional capability to target apps to sites

Additional “Deployment” option available

This is only available in the Catalog, not on any other site collections

• Specific SitesManaged PathsSite Templates

Apps can be stapled to:

• Cannot be removed by Site Administrators as long as the site meets the criteria

App Stapling Limitations Centralized deployment means centralized app

resources App Web, Remote Web are shared among all instances of the app

Remote Events such as “Handle App Install” are only executed in the catalog site NOT on each instance of the app. Because of this, you cannot reply on these events to deploy artifacts to

the host web. Limits the usefulness in scenarios such as branding OR creation of Host Web Level lists, libraries, site columns, content types.

DemoCorporate Catalog

Steve Walker

SharePoint – Own your Site ProvisioningMany limitations that we described can be addressed through a combination of Apps (to provide discreet, modular functionality) as well as owning your Site Provisioning Process

Examples of this would be:• Applying Branding to a site when created• Deploying common Content Types/Site Columns • Manipulating Host Web in various ways

Great examples of the remote provisioning approach for sites and site collections are in our Office Developer Patterns & Practices Projecthttp://dev.office.com/patterns-and-practices

Wrap Up

Options for Deploying Apps / Add-Ins

Deploying to the Store

DeployingTo Exchange

Deploying to The Corporate

Catalog

AdditionalApproaches

Visit Myignite at http://myignite.microsoft.com or download and use the Ignite Mobile App with the QR code above.

Please evaluate this sessionYour feedback is important to us!

© 2015 Microsoft Corporation. All rights reserved.