Earlier in this section, we have discussed the cloud and on-premises deployment models. The following table highlights and compares the key differences between these two deployment models:
|
Capabilities |
Cloud |
On-Premises |
|
Infrastructure |
Full Microsoft-managed cloud service |
Customer/partner managed Not supported on any public cloud infrastructure, including Azure |
|
Data residency |
Microsoft-managed data centers |
Local data residency |
|
Application Lifecycle Management (ALM) |
Managed by Microsoft Customer/partner have access to telemetry and ALM data through LCS |
Managed by customer/partner using LCS
|
|
Licensing |
Subscription: Per month per user cost |
License with software assurance/business-ready enhancement plan or subscription |
|
User count |
Minimum 20 users |
No minimum user requirement (minimum hardware is scoped based on 250 users) |
|
Intelligence and analytics |
Author and publish Power BI reports Ready-made analytical reports Pinning tile and reports from PowerBI.com (https://powerbi.microsoft.com/en-us/)
|
Author and publish Power BI reports |
|
High availability (HA) and Disaster Recovery (DR) |
Included in enterprise offer and managed by Microsoft |
Customer-managed
|
|
Internet connectivity |
Must |
Periodic connectivity for deployments and servicing |
While it helps customers to have on-premises deployment as an option, the cloud deployment is, however, the preferred and recommended option.
Let's learn the environment-planning aspect of cloud deployment projects in the next section of this chapter.