Operating Azure Stack

Share on Facebook1Share on Google+0Share on LinkedIn0

Operating Azure Stack

Operating Azure Stack is very different.

Today, your on-premises IT infrastructure provides a secure and a controlled environment for your business solutions, but it also requires the configuration, deployment, backup, and then management tasks. Your IT administrators will spend most of their time on these tasks, to simply and keep your on-premises environments are to be running.

Azure Stack is an extension of Azure, it enables you to run the Azure services in your on-premises environments. That way, you can enable the modern application development environment for your organization across the cloud and on-premises, while taking an advantage of all the Azure native toolsets and the APIs.

To ensure you can successfully provide the Azure services in your own on-premises environments and you can operate them with the cloud SLAs, we’ve spent the last several months talking with many of you who’ve told us that the following infrastructure management tasks are the most important, it is time-consuming and complex, and these should be our focus for the simplification:

  • Managing the capacity: Ensuring that your infrastructure capacity is to be configured to correctly deal with the demands of providing the cloud capacity.
  • Checking and maintaining health: From the monitoring, business continuity, security, and the disaster recovery, customers want solutions that address these operational tasks and allow them to focus on the service delivery.
  • Managing the tenants’ use of resources: Infrastructure is successful only when tenants are satisfied with the services, and the customers want to be assured that they can successfully provide and to operate these services for tenants.

The “Azure Stack Operator” will be responsible for these tasks. It was with these tasks in the mind that we made the necessary investments in the infrastructure management capabilities of the Azure Stack and in the definition of the “Azure Stack Operator” role.

This introductory post will be followed by a series of posts where we will go into more detail about each of these investments, which includes the:

  • Monitoring & diagnostics: Monitoring, management capabilities, and notifications allow you to manage the infrastructure and service health, performance, and capacity that underlie your tenant workloads.
  • Patching & update: With the Azure Stack itself, you can update your infrastructure software while minimizing the impact on your business applications, services, and workloads.
  • Business continuity: Azure Backup and the Azure Site Recovery will enable tenant-driven protection for business applications and services.
  • Security and then compliance: Azure Stack should be secure-by-design approach across the network, data, and the management.
  • Hardware lifecycle management: Azure Stack should be validated for the workflows to enable the replacement of the failed components.
  • Intuitive experiences: A portal and command-line experience highlight the common actions you need to be performed. This allows you to make the decisions quickly and intuitively.

Future posts will also address the ways to Azure Stack that can be integrated into your existing data center including networking, identity, and ticketing and will go into more depth on the Azure Stack Operator role.

Operating Azure Stack is different.

Although many scenarios are familiar, I want to make sure you approach the Azure Stack knowing that how you operate it will be different. Your value will not be only measured by how you manage Azure Stack infrastructure, but also by what services you have to provide to your developer community and how fast you can enable them.