Cloud ComputingA Fortune 200 consumer packaged goods company recently partnered with CapTech to commercialize Microsoft Azure's Platform as a Service (PaaS) as an enterprise service offering. This blog is the eight in a ten-part series of blogs. The purpose of this post is to highlight the design considerations and implementation activities involved in facilitating the Enterprise's adoption of the new cloud service offering. It is intended for anyone interested in gaining insight into the major bodies of work and considerations involved in commercializing cloud services for large enterprises.

Recommended Bodies of Work

The next couple of posts in this series are going to focus on some of the recommended bodies of work for commercializing the cloud at your organization. Below is a diagram that illustrates a high level and comprehensive view of the bodies of work with their relationships and dependencies. In the remainder of this post, we will explore what's involved in facilitating adoption of the cloud service provider as identified by the items highlighted in green.

Adoption Workstreams

Facilitate the Adoption of the Service

Now that you've gone through and conducted your cloud security assessment, established your MPLS connection, designed your solution architecture, and defined your governance model, it is time to facilitate the Enterprise's adoption of the new Azure PaaS service offering. Without this adoption all of the previous activities would be for naught. Below are suggestions for three activities that will make it easier for the enterprise to adopt the service.

Pilot / Use Case

The first activity that you can perform is to identify a few low risk, low complexity candidate applications to deploy, operate, and support in Azure PaaS to catalyze the enterprise's adoption of the service offering. These pilots can reflect the three different design patterns mentioned in the prerequisites. Recommend piloting not only a technical solution, but also the governance model that would support the service offering. This effort tells the enterprise not only are we willing to "eat our own dog food", but that it also tastes pretty good.

Conduct Cost Comparison

Perhaps one of the most important activities that you can perform is to conduct a cost comparison. No matter what benefits the organization might see by moving to the cloud from a time and efficiency standpoint, at the end of the day, most business decisions come down to dollars and cents. This effort helps Senior Managers understand the value of Azure PaaS by having a quantifiable business conversation on the time, cost, and resources involved comparable to the same parameters required to deploy, operate, and support a similar application using the enterprise's traditional model.

Advertise Service Offering

Most technical-minded folks at any organization will most likely be willing to move to the cloud without much prodding. For those that are not as familiar with the cloud capabilities, advertising the service offering can be a very beneficial mechanism to help the organization adopt the cloud service offering. Depending on how your enterprise is structured, it may be helpful to advertise the Azure PaaS service offering to the Functional Architects because they are responsible for determining what technology platform is appropriate for projects across the various business operating companies. Help Architects understand Azure PaaS capabilities and use cases so they may direct the appropriate work to the service offering.

Conclusion

This eighth post in the ten-part series described facilitating the adoption of the cloud service offering in order to commercialize Azure with this Fortune 200 CPG client. These were just three actions we took to help facilitate this adoption and there are most likely other mechanisms to help in the adoption process.

The entire series:

In the next post we are going to talk about transitioning to support.