Downloaded 14 times
Uploaded byBiserka Cvetkovska
Developing Multi-tenant provider hosted apps: From Idea to Office Store
The document provides an overview of multi-tenant provider hosted apps within the SharePoint and Office 365 environments, highlighting their benefits, development tools, and architecture. It describes the importance of identity management, Azure AD integration, and the app publishing process to the Office Store. Additionally, it emphasizes the model's potential for enhancing accessibility and collaboration within both the SharePoint and broader web communities.
More Related Content
Similar to Developing Multi-tenant provider hosted apps: From Idea to Office Store
Developing Multi-tenant provider hosted apps: From Idea to Office Store
- 1. MULTI-TENANT PROVIDER HOSTED APPS From Ideato Office Store Biserka Cvetkovska
- 2. BISERKA CVETKOVSKA SharePoint &Office365 Specialist @biserka_ biserkacvetkovska.com biserka.cvetkoska@agitavit.com
- 3. INTRODUCTION TO MULTI-TENANT PROVIDERHOSTED APPS
- 4. THE SHAREPOINT APP(ADD-IN) MODEL • It came along with SharePoint 2013 • 4 terms to simplify the understanding of SharePoint • Site • People • Apps • Themes • Benefits • Initial core functionalities stay intact by custom solutions • Cloud-ready solutions • Openness
- 5.
- 6. MULTITENANCY • The sameversion of the app is installed on multiple tenants • Why should you develop multi-tenant apps? • Easy to maintain • Easily managed upgrades • No different versions of the app to take care of Multi-tenant provider hosted apps
- 7. DEVELOPMENT OF MULTI-TENANT PROVIDERHOSTED APPS
- 8. DEVELOPMENT TOOLS ANDTEMPLATES • Tools required for SharePoint apps development • MS Visual Studio v2013+ • MS Azure SDK for .NET • Microsoft Office Developer Tools • OOB SharePoint app template • SharePoint App SharePoint Project • Remote Web App ASP.NET MVC Web Project • Web API in case of an extendibility in the future (with native mobile app in mind)
- 9.
- 10. DATA ACCESS INA MULTI-TENANT APP • Entity Framework • Code First • Creating tables on demand • “Fixing” EF to work with a multi-tenant database
- 11. IDENTITY MANAGEMENT INA MULTI-TENANT APP • Identity management is hard. There are too many things to worry about • Storing passwords and secrets • Dealing with different parameters that work with different identity providers • Preventing prompts for credentials • … • Integration with Azure AD • OpenID Connect • ADAL (Azure Directory Authentication Library)
- 12. OPENID CONNECT &ADAL - A TALE OF FRIENDSHIP
- 13. PROVISIONING MULTI-TENANT APPSIN AZURE AD • Multi-tenant apps that enable authentication towards Azure AD must be registered in • Your company’s AD & • Each organization’s AD that will be using the app • Register your app by implementing a consent flow • Only global administrators can consent • Consent & give permissions to the app so it can access resources in your Azure AD
- 14. CONSENT FLOW FORMULTI-TENANT APPS
- 15.
- 16. PUBLISHING THE APPTO OFFICE STORE
- 17. OFFICE STORE • Introducedto contribute to the simplicity of the App Model • Benefits • For users • Simple & fast installation of apps • Increasing productivity through apps that suit your needs • For developers • Great opportunity to promote your work • Get feedback from your users • Get paid through the Store • Publish your app to Office Store • How does the process go?
- 18. “OPEN CREATIVITY. STRONGERCOMMUNITY.” • The app model makes SharePoint to be more accessible for both users and developers • In addition makes the community even stronger • Not just the SharePoint community but the Web community in general • With Office Store and technologies (such as SPFx) that are yet to come, MS finally set SharePoint on the right path
- 19.
- 20. BISERKA CVETKOVSKA SharePoint &Office365 Specialist @biserka_ biserkacvetkovska.com biserka.cvetkoska@agitavit.com