18. Site Collection URLs
• Environment is part of URL
• Solution is part of URL
https://foo.sharepoint.com/sites/dev-spsbe-demo
https://foo.sharepoint.com/sites/tst-spsbe-demo
https://foo.sharepoint.com/sites/spsbe-demo
19. Some services are more equal than others
• Search
• Define and use Result Sources
• MAV-SPSBE-DEV with Path: https://foo.sharepoint.com/sites/dev-spsbe-*
• Managed Metadata
• Term groups & GUID over different tenants or not
• User profiles
• SPO User Profile Properties are tenant wide
• App Catalog
20. SPFx Solutions
• Decide on: Tenant of Site Collection App Catalog?
• File Name, Product ID and Name must be unique per environment
• CDN locations are baked into your package
• Beware that you should not use skipFeatureDeployment if you have multiple
environments in the same tenant and use the Tenant App Catalog.
• Beware of asynchronously installing the App
23. Connecting the dots
• Combining different services in Azure: Geo
Redundant services
• Deploying real life products and projects:
• Resource Group
• App Service Plan
• Web Jobs
• Key Vault
• Azure AD App Registration
• Application Insights
26. Deployment Tools
• PowerShell & CLI’s for set-up and configuration
• Azure DevOps (formerly VSTS) or 3th party solution like Octopus for managing
pipeline
CI CD
Build Release
27. Next Steps
1. Read up on DevOps at https://aka.ms/devops & SPFx on
https://www.eliostruyf.com/gulp-task-to-change-environment-settings-in-
sharepoint-framework-projects/
2. Set-up a CI/CD pipeline for your projects
3. Start small, but start
4. Questions? @eivatco or @appieschot