About This Course
Our program is different than the rest of the materials available online.
Azure, announced at Microsoft’s Professional Developers Conference (PDC) in October 2008, went by the internal project codename “Project Red Dog”, and was formally released in February 2010 as Windows Azure, before being renamed Microsoft Azure on March 25, 2014.
In this course, Configuring Load Balancers in Microsoft Azure, you’ll learn to create and configure load balancers in Azure. First, you’ll explore how to configure an external load balancer to route traffic to your application servers. Next, you’ll discover how to add health probes to only send traffic to healthy servers. Finally, you’ll learn how to extend this architecture with an internal load balancer to create a full two-tier architecture. When you’re finished with this course, you’ll have the skills and knowledge of Azure load balancers needed to configure highly available infrastructures in Microsoft Azure.
- Cloud concepts
- Azure architecture and services
- Azure management and governance.
By the end of this course, you will have the best foundation to comfortably explore the Azure cloud platform further and confidently sit the Microsoft Azure Fundamentals exam.
- Configure one of the following versions with the required software:
- Microsoft Windows Server 2022 Editions
- Microsoft Windows Server 2019 Editions
- Microsoft Windows Server 2016 Editions
- Microsoft Windows Server 2012 R2 Editions
- Comparable newcomer (at least relative to Amazon’s over ten years in the game), Microsoft Azure, has been coming up the rear, and quickly. With the vast majority of American businesses running on Microsoft software, they entered the market with a strong calling card.
- Microsoft’s virtual machines are not strictly for Windows parties, however. They also support Linux, Oracle, IBM, SAP, and so on.
- One perk of Azure that is oft cited is an eagerness to cater to enterprises seeking a “hybrid cloud” solution. For many companies, handing over all data and infrastructure to a public cloud — and its accompanying support — is not wise, and is often not an option. Retaining some on-premises systems is crucial for many enterprises for reasons ranging from scalability to security, and beyond.