August 2, 2013 Leave a comment
With Server 2012 and VMM 2012 SP1, Microsoft enabled new foundational scenarios from Continuous Availability (with in-box NIC Teaming) to building blocks for Software Defined Networking (with the extensible Hyper-V Virtual Switch and Hyper-V Network Virtualization [HNV]) to IP Address Management (IPAM).
Now with Server and VMM 2012R2, Microsoft is targeting the reduction of networking Capital Expenditures (CapEx), by enabling customers to maximize utilization of their existing resources and reduce the need for specialized hardware over time.
Microsoft got the feedback from customers advising that they want choice and flexibility in both the networking vendors they use and the cloud in which their workloads run. They need the ability to plug and play between vendors without having to change management software, processes, or knowledge, plus the ability to deploy any workloads across any cloud provider.
The other feedback received by Microsoft is that network automation is key. Automation is required across the Service Provider’s network, the tenant’s network, and network infrastructure services (load balancing, firewall, etc.).
As you can see in the figure below, the feedback is giving notably results to the customers with many features that further enhance Microsoft end-to-end capabilities: