Establishing operational management practices in the cloud

Cloud adoption is a catalyst for enabling business value. However, real business value is realized through ongoing, stable operations of the technology assets deployed to the cloud. This section of the Cloud Adoption Framework guides the reader through various transitions into operational management in the cloud.

Actionable best practices

Modern operations management solutions provide a multicloud view of operations. Assets managed through the following recommended practices may live in the cloud, in an existing datacenter, or even in a competing cloud provider. Currently, the framework includes two reference recommended practices to mature operations management in the cloud:

  • Azure Server Management: This onboarding guide to incorporate the cloud-native tools and services needed to manage operations.
  • Hybrid monitoring: Many customers have already made a substantial investment in System Center Operations Manager. For those customers, this guide to hybrid monitoring helps to compare and contrast the cloud-native reporting tools with Operations Manager tooling. This comparison will make it easier to decide which tools to use for operational management.

Cloud operations

Both of these best practices build towards a future state methodology for operations management.

CAF Manage methodology

Business alignment: In the Manage methodology, all workloads are classified by criticality and business value. That classification can then be measured through an impact analysis, which calculates the lost value associated with performance degradation or business interruptions. Using that tangible revenue impact, cloud operations teams can work with the business to establish a commitment that balances cost and performance.

Cloud operations disciplines: Once the business is aligned, it is much easier to track and report on the proper disciplines of cloud operations for each workload. Making decisions along each discipline can then drive commitments that are easily understood by the business. This collaborative approach makes the business stakeholder a partner in finding the right balance between cost and performance.

  • Inventory and visibility: At a minimum, operations management requires a means to inventory assets and create visibility into the run state of each asset.
  • Operational compliance: Regular management of configuration, sizing, cost, and performance of assets is key to maintaining performance expectations.
  • Protect and recover: Minimizing operational interruptions and expediting recovery each help to avoid performance losses and revenue impacts. Detection and recovery are essential aspects of this discipline.
  • Platform operations: All IT environments contain a set of commonly used platforms. Those platforms could include data stores like SQL Server or HDInsight. Other common platforms could include container solutions like Kubernetes or AKS. Regardless of the platforms, the platform operations maturity focuses on customizing operations based on how those common platforms are deployed, configured, and used by workloads.
  • Workload operations: At the highest level of operational maturity, cloud operations teams are able tune operations for workloads that are crucial for business success. For those critical workloads, available data can aid in automating remediation, sizing, or protection of workloads based on their utilization.

Additional guidance like the Design Review Framework (Codename: Cloud Design Principles) can aid in making detailed architectural decisions regarding each workload, within the disciplines above.

This section of the Cloud Adoption Framework will build on each of these topics to mature cloud operations within your organization.