Skip to main content

Constant Change: The Hidden Cost of Cloud Computing


The benefits of cloud computing are widely known, and most organizations have moved or are planning to move from their on premises data centers to cloud facilities hosted by Amazon Web Services, Microsoft, Google or other providers. 

One of the cloud computing benefits is that the cloud provider is responsible for continuously improving the environment that hosts, and that these updates and fixes do not usually require work by the customer.  There is a downside to this benefit, however, especially as you move from cloud infrastructure to cloud solutions. The downside is that you must deal with the consequences of constant change and innovation.

Organizations have always had to handle upgrades of hardware and software, but when the computing was inside their data center they had full control of the timing of changes.  They could more quickly with inexpensive changes and patches, and choose their timing for major changes.  

Today the cloud providers largely choose the timing to introduce new versions and features as well as removing old features.  While major versions were formerly one or two years apart, today you can expect noticeable changes every three to six months.  As innovation becomes constant, the concept of a major version may go away all together.  

Cloud customers must allow for testing and in some cases accreditation of new software versions.  This process can take months for government agencies and large institutions, by which time a new version is already available and the process must start again. 

Some changes to solutions require retraining users and updating documentation.  The training challenge is especially acute for occasional users who return to a system to find it unrecognizable from their last session weeks or months ago.

Perhaps the most dire example of the risk of change is when a cloud vendor discontinues a product altogether.  Vendors must periodically consolidate their offerings based on sales or as a result of a corporate merger that results in two overlapping products.  Free products may be even more likely to be chopped if they do not gain traction and result in benefits for the offeror. 

There is no easy fix for the challenge of constant change.  It is driven by competitive forces which promote innovation along with the imperative of providing strong security and patching vulnerabilities as they are discovered.  Organizations must become more nimble in order to stay aboard the cloud computing train. 

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan