2. Agenda
Transforming ISV to Azure
Motivation (Why SaaS, why Azure or vice versa)
The customers (ISV’s) and their applications
Technical challenges
Non technical challenges
Our role
Next Steps
4. There is a growing demand and a global market
Swiss ISV Solutions as SaaS offering
Pure SaaS Players
e.g.
Hybrid Players
Providing SaaS
offerings to
Swiss customers
Swiss Customers
Asking
for SaaS offerings
International Companies
Swiss Companies like:
Providing Swiss
SasS offerings
to the whole world
Founded
1999
Cloud first,
mobile first
6. Source #2: IDC Direction 2014, Transformation Everywhere How SaaS Gets Built, March 2014
Source #1: IDC Forecasts Worldwide Public IT Cloud Services Spending to Reach Nearly $108 Billion by 2017 as Focus Shifts from Savings to Innovation, 2013 )
Software Revenue Growth
Rate in 2017
Customers are buying services, not
applications or servers
Shifting adoption patterns:
using SaaS as a way to extend on-premises
applications to replace existing applications
with cloud alternatives
91% of net new software is built for cloud
delivery in 20142
20% of all applications revenue in 2014 is
generated by SaaS1
22%
4%
0%
5%
10%
15%
20%
25%
SaaS/PaaS
Revenue
Packaged
Software
5.5x higher
Cloud SW
growth than
packaged SW
7. Customers (Consumers) are more and more inspired by SaaS
Transforming ISV to Azure
Cloud Infrastructure and Operations
Consumer
and small
business
services
Enterprise
services
Third-party
hosted
services
Software as a Service (SaaS)
SecurityGlobal NetworkOperationsDatacenters
PaaS
Application
Physical
Certification&
SecurityReliance
IaaS
8. Why Azure
Transforming ISV to Azure
Azure provides a broad set of IaaS, PaaS and SaaS service that can be used to form
a SaaS offering of the existing ISV Solution
Excellent price/performance tag
Global available (where the money is)
Highly secured
IaaS PaaS SaaS
Azure VM
Office 365
Active Directory
SQL DB
File Share
(RemoteApp) App Service
Popular Services for ISV’s:
9. Customers (Consumers) are more and more inspired by SaaS
Transforming ISV to Azure
Cloud Infrastructure and Operations
Consumer
and small
business
services
Enterprise
services
Third-party
hosted
services
Software as a Service (SaaS)
SecurityGlobal NetworkOperationsDatacenters
PaaS
Application
Physical
Certification&
SecurityReliance
IaaS
10. One platform -> Simplified Software Management
Swiss ISV Solutions as SaaS offering
Instead of a broad spectrum
of hard and software
There is a professional infrastructure
with controlled software releases
11. Location CH = Everything i.o?
In der Schweiz gab es in der vergangenen Woche eine Reihe von DDoS-
Angriffen auf Online-Shops, die Schweizerischen Bundesbahnen und
Finanzinstitute. In einem Fall wurden offenbar über 9000 Euro an die
Erpresser gezahlt.
Während sich die Schweiz als Partnerland der CeBIT 2016 in Hannover
präsentierte, haben Angreifer DDoS-Attacken auf viele Schweizer Websites
gefahren, darunter vor allem Online-Shops. Wie 20 Minuten berichtet,
befindet sich auch die Website der Schweizerischen Bundesbahnen (SBB)
unter den Zielen. Sie war am Montag für über eine Stunde nicht erreichbar.
DDoS-Angriffe ohne Lösegeldforderung
Die Attacken begannen offenbar am vergangenen Montag und betrafen
unter anderem die Shopping-Seiten Do-it, Digitec, Galaxus,
Interdiscount, LeShop, melectronics.ch, Micasa und Microspot. Ferner
war die Site der Schweizerischen Bundesbahnen (SBB) von 14:15 bis 15:30
Uhr nicht erreichbar. Es handelte sich um DDoS-Attacken, die Angreifer
haben die Dienste also mit Anfragen überflutet, bis die Server überlastet
waren. Zugriff auf die Infrastruktur ist dafür nicht nötig.
Transforming ISV to Azure
12. Microsoft Azure
Trustworthy foundation
BUILT ON MICROSOFT EXPERIENCE AND INNOVATION
20+ Data
Centers
Trustworthy
Computing
Initiative
Security
Development
LifecycleGlobal
Data Center
Services
Malware
Protection
Center
Microsoft Security
Response Center
Windows
Update
1st
Microsoft
Data
Center
Active
Directory
SOC 1
CSA Cloud
Controls Matrix
PCI DSS
Level 1
FedRAMP/
FISMAUK G-Cloud
Level 2
ISO/IEC
27001:2005
HIPAA/
HITECH
Digital
Crimes
Unit
SOC 2
E.U. Data
Protection
Directive
Operations
Security
Assurance
13. Microsoft Azure
20+ Data
Centers
Trustworthy foundation
BUILT ON MICROSOFT EXPERIENCE AND INNOVATION
Trustworthy
Computing
Initiative
Security
Development
LifecycleGlobal
Data Center
Services
Windows
Update
1st
Microsoft
Data
Center
Active
Directory
SOC 1
CSA Cloud
Controls Matrix
PCI DSS
Level 1
FedRAMP/
FISMAUK G-Cloud
Level 2
ISO/IEC
27001:2005
HIPAA/
HITECH
Digital
Crimes
Unit
SOC 2
E.U. Data
Protection
Directive
Operations
Security
Assurance
Malware
Protection
Center
Microsoft Security
Response Center
Security Centers
of Excellence:
Protecting Microsoft
customers by combatting
evolving threats
14. Microsoft Azure
20+ Data
Centers
Trustworthy foundation
BUILT ON MICROSOFT EXPERIENCE AND INNOVATION
Trustworthy
Computing
Initiative
Security
Development
LifecycleGlobal
Data Center
Services
Malware
Protection
Center
Microsoft Security
Response Center
Windows
Update
1st
Microsoft
Data
Center
Active
Directory
SOC 1
CSA Cloud
Controls Matrix
PCI DSS
Level 1
FedRAMP/
FISMAUK G-Cloud
Level 2
ISO/IEC
27001:2005
HIPAA/
HITECH
SOC 2
E.U. Data
Protection
Directive
Operations
Security
Assurance
Digital
Crimes
Unit
Digital Crimes Unit:
Using legal and
technical expertise
to disrupt the way
cybercriminals operate
16. Main Reasons for SaaS
Swiss ISV Solutions as SaaS offering
Global market/
Changing customer requirements
New customer segments
in the existing market
Stable, cost efficient and secure
infrastructure
20. New Customer Segments
The cloud allows ISV to rollout their solution
or subsets of their solutions to new customer
segments
For example Provis:
- Main player in huge constructing projects
Module for
defect management
New segment,
smaller companies
/ architects
SaaS helps
to speed up
adoption
22. Common patterns
Transforming ISV to Azure
Main client is grown over the last years
- No Web UI
- Tight integration with Office
New client parts are written as mobile apps
and communicate via Web Services with
the backend
Most data is stored in SQL Server database
Some data is stored on the regular file system
23. Transforming ISV to Azure
U-DB
T-
DB
T-
DB
Web Service
RDP
Azure
AD
Azure
APP Service
Azure
RemoteApp
Azure
SQL DB
(U-DB = User Database
T-DB = Tenant Database)
T-SQL
Provis
Client PC
Provis Baumängelmanagement – Recommended Services
24. Common patterns -> Azure options
Transforming ISV to Azure
Main client is grown over the last years
- No Web UI
- Tight integration with Office
New client parts are written as mobile apps
and communicate via Web Services with
the backend
Most data are stored in SQL Server database
Some data are stored on the regular file system
Azure VM
or
Office 365
Active Directory(RemoteApp)
App Service
SQL DB
File Share
27. Office 365 and Azure Active Directory
Transforming ISV to Azure
RemoteApp/XenApp require Office License
- Office 365 Business Premium contains Office Products (Office Business) but not the
required ProPlus versions
- Only Office 365 (E3, E4, E5) can be used in this context
- The same licenses can also be used on-premises
Azure Active Directory is used for user management
- Small customers in one ISV domain
- Bigger customers can have their own domains with integration
to existing, on-premises AD
28. App Service
Transforming ISV to Azure
Azure App Service includes the Web App
+ Mobile App capabilities that we previously
delivered separately (as Azure Websites
+ Azure Mobile Services)
The Azure App Service pricing is exactly
the same price as our previous Azure Websites offering.
30. SQL DB Elastic Pool
Transforming ISV to Azure
All the databases in an elastic pool share a common set of resources.
The performance characteristics are measured by elastic Database Transaction Units (eDTUs).
Pools come in three service tiers: Basic, Standard, and Premium.
Pools allow databases to share and consume DTU resources without needing to assign a
specific performance level to each databases in the pool.
31. Transforming ISV to Azure
Best migration experience if:
- We have the most actual SQL Server tools
- We are close to Azure (network)
Simple way to achieve this goals
- Install a VM in Azure
with the latest SQL Sever database and tools
- Backup DB on local System
- Copy Backup-File to Azure
- Restore DB on SQL Server in Azure VM
- Do the next steps in the Azure VM
Azure SQL DB Migration
32. Transforming ISV to Azure
SQL Server Data Tools are very helpful to detect
incompatibilities between regular SQL Server and
Azure SQL DB
- Create New SSDT Project from existing SQL DB
- Set Target Platform to Azure SQL Database V12
- Check “errors”
Azure SQL DB – Prepare Migration
33. Azure SQL DB - Migrate
Transforming ISV to Azure
SQL Server Management Studio offers a “one step”
Migration option
Choose strong enough edition
to enable successful loading.
Scale down after data loading
is possible
34. Azure AD Authentication with SQL V12 DB
Transforming ISV to Azure
Azure Active Directory authentication
is supported by:
SQL Server 2016 Management Studio
and SQL Server Data Tools
for Visual Studio 2015
– Azure Active Directory users are
not shown in SSDT Object Explorer
• view users in sys.database_principals
.NET Framework Data Provider
for SqlServer .(NET Framework 4.6)
ODBC version 13.1
– bcp.exe cannot connect using AADA
Microsoft JDBC Driver 6.0
35. Azure File Storage (Share)
Transforming ISV to Azure
Azure File storage is a service that offers file shares in the cloud using the standard Server
Message Block (SMB) Protocol.
- Both SMB 2.1 and SMB 3.0 are supported
- Azure virtual machines, cloud services and on-premises clients
can mount the share
- Quota are supported
- A file share can only be mounted using the access key
of the storage account
36. Simple Pattern for Multi-Tenant
Transforming ISV to Azure
Existing applications are not written with a multi-tenant architecture
- They have just a user-data database
Application start logic has to be adapted
U-DB
T-
DB
T-
DB
Azure
SQL DB
(U-DB = User Database
T-DB = Tenant Database)
Login Company TenantDB
meier.hans@isv1.xy Top Architect Tenant1
huber.jolanda@isv1.xy Top Architect Tenant1
kalt.erika@isv1.xy Top Architect Tenant1
frei.peter@isv1.xy Baumeister Tenant2
Firstlogin
Tenant1User
Tenant2User
38. Scale problem
Transforming ISV to Azure
Many ISV provide very specialized Software
- They have currently just a view number of customers
- Setup of a new customer is time consuming
- Very customer specific
- Not highly automated
- License fees are quite high
- Price changes are not that simple without making the existing customers unhappy
- Support activities are executed by developers of the software
- No 7 * 24 support available
If their SaaS solution takes off then they are not able to deal with the mass
40. Our role/options
Transforming ISV to Azure
Consult ISV
- Choosing the right services
- Solve SQL migration problems
- Multi-Tenant approach
- Using templates to instantiate infrastructure
Educate ISV
- On the required
services & technologies
Rollout SaaS solution on behalf of ISV
Act as help desk
- Provide 7 * 24 support
- Provide Premier Support access
41. Conclusion (1)
Opportunities
Challenges
Expanding Market Opportunity
Sell directly to business decision makers
More predictable revenue
Lower infrastructure support costs
Requires business model shifts
Revenue builds up more slowly, harder to invest back in business
Legal and regulatory concerns around data
SLA management - Requires high level operational disciplines
Requires re-architecting existing applications
42. Conclusion (2)
Software
Core Competencies
Essential value for ISVs to build
As-a-Service
(Platform & Infrastructure
Management)
Non-core, but Necessities
Limited value for ISVs to build
Optimal managed infrastructure & services (SLA > 99.9%)
“Always” the same infrastructure -> Good for automation
Optimal time to market