For teams doing cloud-friendly SharePoint or Office 365 development, apps will be a key area of focus - be they SharePoint add-ins or the newer Office 365/Azure AD apps. ASP.NET (typically MVC) is a common platform here, and fortunately ALM and Continuous Integration become MUCH easier - finally, an end to "it’s harder because it's SharePoint!" We'll demonstrate how Visual Studio Online and Azure Web Apps are a winning combination for “continuous deployment”, and also how features such as "Deployment Slots" in Azure can help with dev and test environments, and also the upgrade/push-to-live process. Several demos will ensure you’re covered for developing both SharePoint add-ins and Office 365 apps.

2. www.sharepointnutsandbolts.com
@ChrisO_Brien
http://cob-sp.com/COBLinkedIn

3. ALM focuses on:
• Efficient team development, with quality outputs
• Planning for application upgrades
• Predictable deployments
Things like:
• Continuous Integration/Continuous Deployment
• Packages not built on dev machines
• Code quality checks
• Structured deployment process

4. http://sharepointci.codeplex.com

5. ALM for ASP.NET apps is MUCH
easier 

6. Worth considering Azure for ALM in dev phase, even
if not real target
Type
Office 365 app
SharePoint Add-In/Office Add-In
Hosting
Azure
Other cloud
On-prem IIS servers

7. Developer checks-in
Build runs on hosted
build controller
Output automatically
deployed to Azure
Web App

9. Configure project for Office 365 integration
Add solution to source control
Create Azure Web App, select “publish from source
control”
DONE!

10. Some features not yet in both
In spring 2015, use:

12. * Specifically Office 365 apps i.e.
- Apps which use the Office 365 APIs
- Apps which use Azure AD auth (for SSO)

13. Office 365 apps need to be
registered in the “correct”
Azure AD (tied to O365
tenancy)
So, app needs to be
registered/deployed to
EACH Azure subscription
behind your tenancies

15. BUT: often, “test” Office 365 tenancies do not have:







16. Azure Deployment Slots!

17. Define additional
“instances” of an Azure
Web App (site)
Allow you to test purely
in production Office 365
environment, BUT with
dev/test/prod separation
for apps (Azure sites)

18. Each site gets:




http://mysite.azurewebsites.net
http://mysite-dev.azurewebsites.net
http://mysite-test.azurewebsites.net

19. In Azure
portal:
PowerShell:
Slots can be swapped to
deploy updates
Process: Switch-
AzureWebsiteSlot
–Name ‘COB website’
-Slot1 'Production'
-Slot2 <slotName>

21. Create additional deployment slots
Register separate instance of app in Azure AD:
https://msdn.microsoft.com/en-us/office/office365/howto/add-common-consent-manually
Configure “slot-specific” ClientID and Password
Deploy app to slot
DONE!

22. 1. Continuous build deploys to DEV slot
2. When ready, swap DEV and TEST
1.
2.
3. When ready, swap TEST and PROD
1.
2.

23. Traffic Routing - send
some traffic to another
slot
Uses:
Testing new functionality on small number
of users
A/B testing

25. Very easy to deploy/test against Office 365
Very similar to Office 365 apps (especially provider-
hosted), but:

26. Trusting the app:

28. Same as for O365 app:
SharePoint app specific:
http://blogs.msdn.com/b/kaevans
/archive/2014/04/02
/deploying-a-sharepoint-app-to-
azure-as-part-of-a-build.aspx

29. 1. Can’t use Visual
Studio Online?

30. 2. Need to use an
on-prem TFS build
server?
http://officesharepointci.codeplex.com

31. Test the application
Check code quality
http://docs.spcaf.com/v5/SPCAF_OVERVIEW_660_HOWTO
RUNSPCAFINTEAMBUILD.html

32. Invalid credentials in
O365 deployment site
(build config)
App previously deployed
not by build

33. Kirk Evans (Microsoft) http://blogs.msdn.com/b/kaevans
Matthias Einig (SPCAF) http://www.matthiaseinig.de
Jeremy Thake (Microsoft) http://www.jeremythake.com

34. Never done automated builds before? Well, NOW is
the time!