No features will be available in Azure Stack that are not available in Azure, as it is a
joint engineering effort. This does mean that sometimes the base hypervisor has
capabilities that will not initially be available for Azure Stack deployments, but they
should be added over time as Azure enables them.
Where Does System Center and Operations Management Suite Fit
with Azure Stack?
Azure Stack does not utilize System Center as part of its architecture, but this does not
mean that System Center has no place. Consider services running in Azure IaaS today.
You may deploy Operations Manager agents to monitor services or utilize Operations
Management Suite (a set of cloud services that complements System Center). You
may patch using Configuration Manager. You may deploy configuration through
PowerShell DSC with Azure Automation/OMS. Automation through Azure
Automation enables activities such as deployment, scale operations, and really any
other type of action for workloads. The same applies with Azure Stack. System Center
and OMS may be utilized to provide services to the workloads running on Azure Stack,
especially IaaS VMs.
For most organizations, I expect Azure Stack to be a new deployment sitting next to
their existing virtualization solution that will continue to house the standard
infrastructure workloads. The Azure Stack instances will be utilized for the true cloud
service requirements for scenarios in which Azure consistency is key.