A developer and IT Pro focused session on planning and moving the SharePoint Development to Azure Virtual Machines as presented at SharePoint Sri Lanka monthly gathering on 14th October 2015.
1. Moving your SharePoint Development to
Azure
Malin De Silva
SharePoint Specialist
Exilesoft
malindesilva@live.com
2. About Me
• Experienced with SharePoint 2007/ 2010/
2013
• Presenter at many meetups and
conferences
• A BIG Azure fan.
3. Let’s Get to Know
SharePoint Developers?
Experienced with Azure?
Worked with Azure Virtual Machines?
SharePoint Development Experience on Azure?
4. Agenda
Introduction
Planning infrastructure
Azure VMs for SharePoint
Capex vs Opex
Cost saving tips
Q and A
malindesilva@live.com
5. Running SharePoint on Azure
How much bandwidth required?
Develop from ANYWHERE
Can scale up easily/ quickly
Resources are not idle when VMs are stopped
No concerns on local storages
Updates automatically if allowed
Backup and restore mechanisms
6. Our Team
5 Members
Full Trust Solutions
1 SharePoint 2010 Development Environment
5 SharePoint 2013 Development Environments
1 QA Environment
12. Capex vs Opex
Virtual Machine A1 (DC) A5 (Developer) A6 (Database) A3 (QA)
No. of machines 1 5 1 3
Cost per hour
(USD)
0.09 0.33 * 5 = 1.65 0.66 0.36 * 3 = 1.08
Active hours per
month
220 220 220 33
Annual Cost
(USD)
237.6 4356 1742.4 427.7
Total Cost per Year (USD) 6763.7 ~ 6,040
EUR
Assumptions:
Each machine will stay started for 10 hours daily for 22 days a month.
QA server will remain up every quarter for 10 days with 10 hours per day.
We will keep creating full trust code through the year.
13. Cost Saving Tips
Auto scaling or Automation
License mobility
Start with Windows Server installations