Tag: System Center

Last updated by at .

System Center release cadence

System Center 2019 – What’s new

Microsoft just launched Windows Server 2019 and Windows Admin Center, which also raised the interest in System Center 2019. At Microsoft Ignite, Microsoft was talking about what is new in System Center 2019, the future of System Center, and how it fits in with Windows Admin Center and other management tools.

Microsoft Cloud and Datacenter Management Story

Microsoft Cloud and Datacenter Management Overview

With Microsoft now offering a range of products to manage your Cloud and Datacenter environments, the question comes up “which is the best solution?”. It is not only depending on the size of your company, it also depends on which services you are using and what your job role is. Coming from the Azure site, you have Azure Security and Management, which allows you not only to manage your Azure resources but also integrates and extends with your on-premises environment. System Center is aimed to manage fatacenter environments at scale, and Windows Admin Center helps you to dig deeper to manage individual servers or single cluster management. Both Windows Admin Center and System Center 2019, can be used side by side and both are integrated into Microsoft Azure.

System Center Windows Admin Center better together

System Center vs Windows Admin Center

I often get the question, does Windows Admin Center replace System Center? The answer to this is no, System Center is aimed to do management at a datacenter scale, while Windows Admin Center is giving you deep management access to a single server or clusters. In small environments you might end up using Windows Admin Center only, but in larger datacenter deployments, you are likely to use a combination of System Center and Windows Admin Center.

System Center 2019 Suite Improvements

System Center 2019 Focus

The System Center 2019 release focuses on three main areas. First of all, it adds more capabilities to the existing components and features which were requested by customers. Secondly, it brings integration for the next version of Windows Server, Windows Server 2019 and brings new Windows Server features to life in System Center. Last but not least, System Center 2019 adds more Hybrid Cloud integrations with Microsoft Azure.



Windows Server 2019

Microsoft announces Windows Server 2019 and System Center 2019

Microsoft today announced the next Long-Term Servicing Channel (LTSC) release for Windows Server called Windows Server 2019. In a blog post today, Erin Chapple, Director of Program Management Windows Server, announced the Windows Server 2019, which will be available in the second half of calendar year 2018. You can try out a Windows Server Preview build through the Windows Server Insider Program today. Microsoft also mentions that System Center 2019 will be available to manage Windows Server 2019 infrastructures.

Windows Server 2019 is built on the foundation of Windows Server 2016 and focuses on a couple of key scenarios. Microsoft in four key areas, Hybrid Cloud, Security, Application Platform and Hyper-Converged Infrastructure (HCI).

Windows Server 2019 – Hybrid Cloud Improvements

Project Honolulu Server Overview

As of today Hybrid Cloud is more real than ever. With Windows Server 2019 Microsoft is focusing to improve the customer experience in a hybrid cloud world. Taking advantage of public cloud innovation such as Artificial Intelligence and IoT, and connecting them with on-premise services is a huge enabler for customers. At Microsoft Ignite 2017, Microsoft showed of the Technical Preview of Project Honolulu, a web-based management console for Windows Server. One of the goals of Project Honolulu is to connect Windows Server deployments with Azure services. Together with Windows Server 2019 and Project Honolulu, you can easily integrate services like Azure Backup, Azure File Sync, Azure Site Recovery and much more.

Windows Server 2019 – Security

Security was already one of the big investments in Windows Server 2016. Microsoft does not stop there. With Windows Server 2019 Microsoft brings various security improvements like Shielded Virtual Machine support for Linux VMs and Encrypted Virtual Networks. One of my favorite improvements is the possibility to integrate with Windows Defender Advanced Thread Protection (ATP). ATP was first available for Windows 10 and provides preventative protection, detects attacks and zero-day exploits among other capabilities, into the operating system. This gives customers access to deep kernel and memory sensors, improving performance and anti-tampering, and enabling response actions on server machines.

Windows Server 2019 – Application Platform

Ubuntu on Windows Server using WSL

One of the key focus of Microsoft for Windows Server, was always on the developer experience. Microsoft brings a couple of improvements to make it the best application platform out there. Microsoft invests in a couple of scenarios such as bringing the Windows Subsystem for Linux (WSL) to Windows Server. Another key investment area are Windows Server Containers and Windows Server Container images. In Windows Server 2019, Microsoft reduces the Server Core base container image to a third of its current size of 5 GB. This will reduce download time of the image by 72%, further optimizing the development time and performance. Another key improvement in terms of Container support is the integration and support for Container orchestrators like Kubernetes.

Windows Server 2019 – Hyper-converged infrastructure (HCI)

The 4th improvement area is the Hyper-converged infrastructure (HCI). With Windows Server 2016 Microsoft released a new feature called Storage Spaces Direct. Together with Hyper-V and other Microsoft technologies, this was great to build you own infrastructure for your virtualization workloads. Windows Server 2019 will bring a lot of improvements for Storage Spaces Direct, Hyper-V and other related technologies. Microsoft is adding scale, performance, and reliability to the platform. Microsoft also partnered with hardware vendors to provide an affordable and yet extremely robust HCI solution with validated design.

What else?

  • Windows Server will be GA (generally available) in the second half of calendar year 2018.
  • Windows Server will be a LTSC release. LTSC will be the recommended version of Windows Server for most infrastructure scenarios and workloads like SQL Server, SharePoint and Windows Server Software-Defined Datacenter solutions.
  • With the LTSC release of Windows Server 2019, Microsoft will allow customers to use the Server with Desktop Experience as well as Windows Server Core. With the Semi-Annual Channel (SAC) release, Microsoft only provides the Windows Server Core option.
  • There will be another Semi-Annual Channel (SAC) release at the same time as Windows Server 2019 focusing on Container innovations. The SAC releases will be supported as before for 18 months, while the LTSC releases follow the normal 5+5 year support.
  • Licensing will use the same model as Windows Server 2016 today, Microsoft mentions that it is likely that they will increase the pricing for Windows Sevrer Client Access Licensing (CAL), but will share more details later.

With that we can all be very excited for the next LTSC version of Windows Server. Until then the next SAC release of Windows Server, called Windows Server 1803, will be available this spring. The Windows Server, version 1803 will focus on container improvements. If you want to try out, Windows Server 2019 or Windows Server 1803, you can join the Windows Server Insider Program.



System Center

Microsoft released System Center 1801 Semi-Annual Channel

Microsoft just release the first Semi-Annual Channel release for System Center, called System Center, version 1801. This is the first release which now comes out to support the Windows Server Semi-Annual Channel releases like 1709 and also brings some new features and performance improvements.

System Center, version 1801 is the first of our Semi-Annual Channel releases delivering new capabilities at a faster cadence. Semi-Annual Channel releases have an 18-month support policy. In addition, we will continue to release in the Long-Term Servicing Channel (LTSC) at a lower frequency. The LTSC will continue to provide 5 years of mainstream support followed by 5 more years of extended support.

What’s in System Center, version 1801?

System Center, version 1801 focuses on enhancements and features for System Center Operations Manager, Virtual Machine Manager, and Data Protection Manager. Additionally, security and bug fixes, as well as support for TLS 1.2, are available for all System Center components including Orchestrator, Service Management Automation, and Service Manager.

I am pleased to share the capabilities included in this release:

 

  • Support for additional Windows Server features in Virtual Machine Manager: Customers can now setup nested virtualization, software load balancer configuration, and storage QoS configuration and policy, as well as migrate VMware UEFI VM to Hyper-V VM. In addition to supporting Windows Server, version 1709, we have added support for host monitoring, host management, fall back HGS, configuration of encrypted SDN virtual network, Shielded Linux VMs on Hyper-V management, and backup capabilities.
  • Linux monitoring in Operations Manager: Linux monitoring has been significantly improved with the addition of a customizable FluentD-based Linux agent. Linux log file monitoring is now on par with that of Windows Server (Yes, we heard you! Kick the tires, it really works).
  • Improved web console experience in Operations Manager: The System Center Operations Manager web console is now built on HTML5 for a better experience and support across browsers.
    Updates and recommendations for third-party Management Packs: System Center Operations Manager has been extended to support the discovery and update of third-party MPs.
  • Faster, cost-effective VMware backup: Using our Modern Backup Storage technology in Data Protection Manager, customers can backup VMware VMs faster and cut storage costs by up to 50%.
  • And much more including Linux Kerberos support and improved UI responsiveness when dealing with many management packs in Operations Manager. In Virtual Machine Manager, we have enabled SLB guest cluster floating IP support, added Storage QoS at VMM cloud, added Storage QoS extended to SAN storage, enabled Remote to VMs in Enhanced Session mode, added seamless update of non-domain host agent, and made host Refresher up to 10X faster.

You can get System Center, version 1801 from the Evaluation Center or the Volume Licensing Service Center.



Microsoft Exam 70-745

Passed Microsoft Exam 70-745 Implementing a Software-Defined Datacenter

This summer I took the Microsoft beta exam 70-745 Implementing a Software-Defined Datacenter, which focuses on implementing Software-Defined Datacenter solutions, based on Hyper-V, Windows Server, Software Defined Networking and Storage, System Center Virtual Machine Manager, System Center Operations Manager and everything around it.

  • Plan and Implement System Center Virtual Machine Manager (VMM) Core Infrastructure
  • Implement Software-Defined Networking (SDN)
  • Implement Software-Defined Storage
  • Implement Datacenter Compute Solutions with Virtual Machine Manager (VMM)
  • Secure your Software-Defined Datacenter
  • Monitor and Maintain the Software-Defined Datacenter

Passing Exam 745: Implementing a Software-Defined Datacenter validates the skills and knowledge to implement a software-defined datacenter (SDDC) with Windows Server 2016 and Microsoft System Center 2016 Virtual Machine Manager (SCVMM). Candidates have experience implementing and managing highly available SCVMM infrastructures as well as implementing software-defined storage, compute, and networking components.

This week I finally got the message that I passed the Beta exam. If you want to take that exam you should really be familiar with the products and solutions mentioned above, otherwise you will have a hard time passing the exam.

If you want to know more about the exam, check out this link: Microsoft Learning Exam 70-745 Implementing a Software-Defined Datacenter

Also big congrats to all the others who passed the exam like Charbel Nemnom.



eBook on SCOM and OMS

eBook: 5 Top Questions about SCOM and OMS

Together with Microsoft MVP Dieter Wijckmans, I collaborated on an eBook with Savision about the 5 top questions that we have come across regarding System Center Operations Manager (SCOM) and Microsoft Operations Management Suite (OMS).

There is much debate around SCOM and OMS, and the common belief is that OMS is competing against SCOM. This is contributing to people thinking that OMS is still SCOM in the cloud, or that they are both doing the same thing.

For those already using Microsoft technologies to monitor their IT elements, is OMS the same as the Microsoft System Center Suite? Is OMS a replacement for Microsoft System Center?

eBook SCOM and OMS

5 Top Questions about SCOM + OMS

  1. What is OMS?
  2. Is OMS replacing System Center?
  3. What are the main differences between SCOM and OMS?
  4. Do you still need SCOM?
  5. How can I get better insights from SCOM + OMS?

To download the eBook for free, just visit the Savision download page: 5 Top Questions about SCOM and OMS



Windows Server Semi-annual Channel Overview

What is next for Windows Server and System Center with a faster release cadence

A couple of weeks ago at the Microsoft Build Conference, Microsoft released some new information about what is coming in the next version of Windows Server like Linux support on Hyper-V Container and much more. Today Microsoft just announced some new details about the next Windows Server releases and how they will work. The biggest change of todays announcement that Windows Server and System Center will also move to the Semi-annual Channel, just like Windows Client and Office moved to the Semi-annual Channel release cycle. The other large announcement is that Microsoft focuses Nano Server on Container and will remove support Nano on Hosts and Virtual Machines. This means you can run Nano Server only as a Windows or Hyper-V Container.

Nano Server is only supported as a Container Image

Microsoft is removing support for the Nano Server operating system running on physical hardware or inside Virtual Machines. Nano Server will be only supported as a Container Image. Windows Server Core will be the preferred installation option for your infrastructure servers like Hyper-V or Storage Spaces Direct.

This next release will focus on making Nano Server the very best container image possible. From these changes, customers will now see the Nano Server images shrink in size by more than 50 percent, further decreasing startup times and improving container density. As part of this effort to focus on containers, we will be removing the functionality for infrastructure-related roles. Instead of using Nano Server for these scenarios, we recommend deploying the Server Core installation option, which includes all the roles and features you would need.

Windows Server Servicing Channel

As mentioned Microsoft will offer Windows Server updates in the Semi-annual Channel as well as in the Long Term Servicing Channel for Nano Server Container Images as well as Windows Server Core.

There will be two primary release channels available to Windows Server customers, the Long-term Servicing Channel, and the new Semi-annual Channel.

Long-term Servicing Channel

The Long-term Servicing Channel is the release model you’re already familiar with (currently called the “Long-term Servicing Branch”) where a new major version of Windows Server is released every 2-3 years. Users are entitled to 5 years of mainstream support, 5 years of extended support, and optionally 6 more years with Premium Assurance. This channel is appropriate for systems that require a longer servicing option and functional stability. Deployments of Windows Server 2016 and earlier versions of Windows Server will not be affected by the new Semi-annual Channel releases. The Long-term Servicing Channel will continue to receive security and non-security updates, but it will not receive the new features and functionality.

Semi-annual Channel

The Semi-annual Channel releases will deliver new functionality for customers who are moving at a “cloud cadence,” such as those on rapid development cycles or hosters keeping up with the latest Hyper-V investments. Windows Server products in the Semi-annual Channel will have new releases available twice a year, in spring and fall. Each release in this channel will be supported for 18 months from the initial release.

Most of the features introduced in the Semi-annual Channel will be rolled up into the next Long-term Servicing Channel release of Windows Server. The editions, functionality, and supporting content might vary from release to release depending on customer feedback.

The Semi-annual Channel will be available to volume-licensed customers with Software Assurance, as well as via the Azure Marketplace or other cloud/hosting service providers and loyalty programs such as MSDN.

Windows Insider Program

At Microsoft Build, Microsoft also announced that Windows Server will be part of the Windows Insider Program, and you will see the first preview builds this summer.

System Center

in the first Semi-annual Channel release from System Center, the team will focus on System Center Operations Manager, Virtual Machine Manager, and Data Protection Manager. The key areas of investment will include support for Windows Server and Linux, enhanced performance, usability and reliability, and extensibility with Azure-based security and management services. Which will bring features like Nested Virtualization support, software load balancing, Storage QoS Self-Service and management support for heterogeneous environments with improved Linux monitoring using a FluentD agent as well as VMware backup. System Center Configuration Manager will continue to offer three releases a year to give you the latest updates for managing servers, PCs, and mobile devices.

Conclusion

This changes will improve the release cadence of datacenter and cloud innovation dramatically. Customers like service providers will have the chance to update their offerings much more often which allows them to add new features and functionality. But there is choice for customers who need a stable and not fast moving environment they can deploy builds from the Long-term servicing channel, which will have long term support. With that you should be able to choose the best solution for your environment and workload.



AzureStack Admin Portal

Microsoft Azure Stack – Azure Extension in your Datacenter

A couple of weeks ago, I had the chance to attend the Microsoft Azure Certified for Hybrid Cloud Airlift in Bellevue WA, which is close to the Microsoft campus in Redmond. I had the chance to spend the week there and talk with the Microsoft PG about different Azure Stack scenarios. Most of the discussions and presentations are under NDA, but there are a few things I can share, since they are publicly announced. I prepared this blog post already a couple of months ago, when I was talking to a lot of different customers about Azure Stack, and since then Microsoft also shared some new information about the release of Azure Stack Technical Preview 3.

The Azure Stack Announcement

Azure vs Azure Stack

Microsoft announced Azure Stack at Microsoft Ignite in May 2015. Back at this time Microsoft did only mention about the vision of Azure Stack and that it will bring cloud consistency between the Microsoft Azure Public Cloud and your Private Cloud. But Microsoft did not really announce exactly what Azure Stack will be and how it will be implemented in your Datacenter.

During the Microsoft World Wide Partner Conference (WPC 2016), Microsoft announced more information about the availability of Azure Stack. For more information, you can read the Microsoft blog posts, but I tried to summarize the most important parts.

Building a true Hybrid Cloud and Consistency with Microsoft Azure

Azure Stack

This is probably the most important part about Azure Stack today. Microsoft Azure Stack will bring Azure consistency between the Microsoft Azure Public Cloud and your Private Cloud or your Hosters Service Provider Cloud using the Azure Resource Manager. So you will be able to not only operate an Azure-like environment, like you could with Windows Azure Pack and System Center, you now get real consistency between Azure and Azure Stack. You not only get the exact look and feel from the Microsoft Azure Public Cloud, you also can use the same Azure Resource Templates and deployment methods as you can in the Public Cloud. This allows customers to really operate in a Hybrid Cloud environment, between the Microsoft Public Cloud, their own Private Cloud and also local Service Provider Clouds.

Bring the agility and fast-paced innovation of cloud computing to your on-premises environment with Azure Stack. This extension of Azure allows you to modernize your applications across hybrid cloud environments, balancing flexibility and control. Plus, developers can build applications using a consistent set of Azure services and DevOps processes and tools, then collaborate with operations to deploy to the location that best meets your business, technical, and regulatory requirements. Pre-built solutions from the Azure Marketplace, including open source tools and technologies, allow developers to speed up new cloud application development.

The Integrated System Approach

Azure Stack Integrated System

(picture by Microsoft)

Microsoft announced that Azure Stack will be available as an appliance from different hardware vendors in Mid 2017. The confirmed hardware providers delivering Azure Stack Appliance at this point in time will be: Dell EMC, HPE and Lenovo and later in 2017 we will also see an appliance from Cisco, Huawei and Avanade.

The big difference here is that Microsoft delivers the Azure Stack platform first in an appliance way, which is really different from the way they delivered Windows Azure Pack. Windows Azure Pack was based on System Center and Windows Server and every customer could design his own environment based on their needs.

This was great, but also had some huge challenges for customers. Clouds needed different designs, this ended up in very complex design workshops where we basically discussed the customer solutions. The installation and configuration of a Windows Azure Pack platform was also very complex and a lot of work which needed a lot of resources, knowledge and of course a lot of project costs. Before customers could start saving money, they had to invest money to get things up and running. Of course, system integrators like itnetX and others, built automation to spin up clouds based on Windows Azure Pack, but still the investment needed to be done.

The use of an appliance approach not only helps to spin up clouds faster, but also build environments on tested hardware, firmware and drivers. Another point here which makes a great case for an appliance solution, are management and operations. Management and operation of a cloud-like environment is not easy, doesn’t matter what software you are using. Keeping the platform stable, maintained and operational will end up in a lot of work, especially if every cloud looks different. The last thing I want to mention here is upgrading, if you want real Azure consistency, you need to keep up with the ultra-fast pace of the Azure Public Cloud, which is basically impossible or extremely expensive. An integrated system scenario can really help you keep things up-to-date, since updates and upgrades can be pre-tested before they are released for you to deploy. This will help you save a huge amount of testing since every environment looks the same.

Operating Azure Stack

Azure Stack Administration and Operation

As already mentioned, Azure Stack will be delivered as an integrated system. OEMs, will help you to setup and install your Azure Stack appliance in your datacenter, but they will not fully manage the Azure Stack environment. You will need to have some Cloud Operator managing and operating your Azure Stack. With this all the host will be sealed and administrators do not have access to the hosts or Hyper-V Manager or Failover Cluster Manager to mange the systems. Instead, Administrators or Cloud Operators will manage the system for a management portal.

Azure Stack Platform

Since this is an integrated system, you don’t even need to care what it is running in the background. But still for a lot of us it is still very interesting to see how Azure Stack is built. In the back Azure Stack runs on “common” rack mount servers from HPE, Dell, Lenovo and Cisco, for HPE this is the DL380 Gen9. From the software stack it is running Windows Server 2016, and the Software Define Datacenter features such as Storage Spaces Direct, the new Windows Server 2016 Software-Defined Networking Stack an Hyper-V. In the release version of Azure Stack we will see a Hyper-Converged Storage Spaces Direct architecture starting from 4 nodes. On top of this Microsoft used code from Azure to bring the Azure Resource Manager, Azure Resource Providers and the Azure Portal to the Azure Stack.

Azure Stack POC – Microsoft Azure Stack Development Kit

Azure Stack Development Kit

Very early in the development process of Azure Stack, Microsoft releases Technical Previews to customers, so they could test Azure Stack on one node deployments. This is called the Azure Stack POC and you can download it today on a single physical server, and it was only designed for non-productive, non-HA environments. Microsoft officially announced that they will rename the Azure Stack POC to Azure Stack Development Kit after the General Availability of Azure Stack Mid 2017. This is really a great solution to quickly spin up a test environment of Azure Stack without having to invest in hardware.

Azure Marketplace Syndication

Azure Stack Marketplace Syndication

You will be able to create your own Marketplace items in Azure Stack, building your own templates and images and offer them to your customers. One of the greatest editions Microsoft made in the Azure Stack Technical Preview 3 is the Azure Marketplace Syndication. This allows you to get Marketplace items from Azure and offer them in your Azure Stack offering to your customers. With that you don’t need to build all Marketplace items by yourself.

Azure Stack Identity Management

Azure Stack has to be integrated into your datacenter. In terms of Identity, Microsoft allows you to use two ways to integrate. First, and from my site the preferred option, is Azure AD (AAD) which allows you to integrate with an existing Azure Active Directory. Azure AD can be synced and connected with your on-premise Active Directory and this will allow you to login to Azure as well as Azure Stack. The other option Microsoft is offering is using ADFS to bring identities to your Azure Stack.

The Azure Stack Business Cases

Since Azure Stack is consistent with Microsoft Azure, the question comes up, why are we not just using Azure. There are many good reasons to use Azure, but there are also some challenges with that. Azure Stack can make sense in a couple of scenarios.

  • Data Sovereignty – In some cases data cannot be stored outside of a specific country. With Azure Stack, customers have the option to deploy in even their own datacenter or on a service provider within the same country.
  • Latency – Even Microsoft offers a solution to reduce network latency to Azure, with using Azure Express Route, in some scenarios latency is still a big issue. With Azure Stack can customers place Azure very close to the location where resources are accessed from.
  • Disconnected Scenarios – In some scenarios you really want to benefit form the consistent deployment model, and for example use Azure Resource Manager (ARM), but not everywhere on earth do you have access to Azure or sometimes you have a very bad connection. Think about cruise ships or other scenarios where you need to run IT infrastructure but you are not able to connect to Azure.
  • Private Instance of Azure – For some companies shared infrastructures can be challenging, even security standards in Azure are extremely high, it is not always an option. With Azure Stack, companies can basically spin up their completely own instance of Azure.
  • Differentiation – Service Providers or even Enterprise companies cannot only use the Azure Marketplace, but they can also build their own solutions for the Azure Stack and make them available to their customers.

Pricing and Licensing

As mentioned Microsoft will offer Azure Stack from 5 different OEMs. HPE, Dell and Lenovo will deliver a solution at GA in mid-CY17, Cisco and Huawei will be available later. The hardware needs to be bought directly from the OEM or Partner. Some of the also offer a flexible investment model like the HPE Flexible Capacity. For the pricing model, Microsoft decided to deliver the licensing of Azure Stack on a pay-per-use base. This meets of course the cloud economics and there will be no upfront licensing costs for customers. Services will be typically metered on the same units as Azure, but prices will be lower, since customers operate their own hardware and facilities. For scenarios where customers are unable to have their metering information sent to Azure, Microsoft will also offer a fixed-price “capacity model” based on the number of cores in the system.

Azure Stack will be offered in two different models, Pay-as-you-use model and Capacity model. The pay-as-you-use model is licensed by Microsoft via the Enterprise Agreement (EA) or Cloud Service Provider (CSP) programs. The capacity model is available via EA only. It is purchased as an Azure Plan SKU via normal volume licensing channels. For typical use cases, Microsoft expects the pay-as-you-use model to be the “most economical” option.

The Azure Stack pricing models

Azure Stack will be offered in two different models, Pay-as-you-use model and Capacity model. The pay-as-you-use model is licensed by Microsoft via the Enterprise Agreement (EA) or Cloud Service Provider (CSP) programs. The capacity model is available via EA only. It is purchased as an Azure Plan SKU via normal volume licensing channels. For typical use cases, Microsoft expects the pay-as-you-use model to be the “most economical” option.

Azure Stack Pay-as-you-use model

For the pay-as-you-use model you will you can take advantage of the cloud economics and only pay for resources which are actually consumed, plus additional costs for the Azure Stack hardware and the operations.

Service prices:

  • Base virtual machine $0.008/vCPU/hour ($6/vCPU/month)
  • Windows Server virtual machine $0.046/vCPU/hour ($34/vCPU/month)
  • Azure Blob Storage $0.006/GB/month (no transaction fee)
  • Azure Table and Queue Storage $0.018/GB/month (no transaction fee)
  • Azure App Service (Web Apps, Mobile Apps, API Apps, Functions) $0.056/vCPU/hour ($42/vCPU/month)

Azure Stack Capacity model

For the capacity model, two packages are available which makes you license the physical cores of your Azure Stack system via an annual subscription. The packages are only available via Enterprise Agreement (EA).

  • App Service package ($400/core/year)
    Includes App Service, base virtual machines and Azure Storage
  • IaaS package ($144/core/year)
    Includes base virtual machines and Azure Storage

You will also need additional licenses if you deploy Windows Server and SQL Server virtual machines, like you would do if you are using your traditional Hyper-V servers.

What else will you need

  • Integrated System (hardware) – you will need to purchase the Azure Stack hardware from one of the OEM vendors
  • Support – you will need to purchase support from Microsoft for software support and a support package for the hardware from the hardware provider. If you already have Premier, Azure, or Partner support with Microsoft, your software support is included.
  • Service Providers – Service Provider can also license Azure Stack to others using the CSP (Cloud Solution Provider) channel.

Azure Stack Roadmap

At the Azure Stack GA release this summer, Microsoft will deliver hardware with provides from HPE, Dell and Lenovo. Later in 2017 Microsoft will also deliver Azure Stack with Cisco, Huawei and Avanade hardware. Azure Stack at GA will support 4-12 nodes, 1 single scale-unit and a single region.

Microsoft will also deliver some of the services at General Availability on Azure Stack, and will add more and more services over time. At GA we will see:

  • Virtual Machines
  • Storage (Blob, Table and Queue)
  • Networking (Virtual Networks, S2S VPN, …)
  • App Service (in Preview)
  • SQL (in Preview)
  • MySQL (in Preview)

After GA, Microsoft  will continuously deliver additional capabilities through frequent updates. The first round of updates after GA are focused on two areas: 1) enhanced application modernization scenarios and 2) enhanced system management and scale. These updates will continue to expand customer choice of IaaS and PaaS technologies when developing applications, as well as improve manageability and grow the footprint of Azure Stack to accommodate growing portfolios of applications. Please be reminded that this will not just be a product you purchase, think about it as a service which will add features and functionality over time.

The choice for your datacenter

Windows Azure Pack

Obviously, Microsoft is pushing Azure Stack since it will bring consistency to the Azure public cloud, which means your companies and people need to understand the advantages of using methods like DevOps and Infrastructure in code. This will help you to make the most out of Azure Stack and the Azure Resource Manager. If you already have Microsoft Azure know-how, this is great, because it will also apply to Azure Stack.

No worries, if you are not there yet, or for some reason this doesn’t make sense to you, Microsoft still has a great solution to build traditional Virtualization platforms together with automation using System Center, Windows Server and if needed Windows Azure Pack. Both solutions, System Center and Windows Azure Pack, will be supported in the future and will get updates.