Book Image

Modernizing Legacy Applications to Microsoft Azure

By : Steve Read, Larry Mead
Book Image

Modernizing Legacy Applications to Microsoft Azure

By: Steve Read, Larry Mead

Overview of this book

Organizations have varying circumstances, objectives, and prerequisites when contemplating a hyper-scale cloud solution transformation to a platform such as Azure. Modernizing Legacy Applications to Microsoft Azure uncovers potential scenarios and provides choices, methodologies, techniques, and prospective possibilities for transitioning from legacy applications to the Microsoft Azure environment. You’ll start by understanding the legacy systems and the main concerns regarding migration. Then, you’ll investigate why distributed architectures are compelling and the various components of the Azure platform needed during migration. After that, you’ll explore the approaches to modernizing legacy applications and the Rs of modernizing (i.e., rehost, refactor, rearchitect, and retire). You’ll also learn about integration approaches and potential pitfalls. By the end of this book, you’ll be well equipped to modernize your legacy workloads while being aware of pitfalls and best practices.
Table of Contents (18 chapters)
Part 1: Legacy Estate Options
Chapter 2: Strategies for Modernizing IBM and Unisys Mainframes
Part 2: Architecture Options
Part 3: Azure Deployment and Future Considerations

Azure security and identity

Consider that up to now in this chapter, we have talked about various Azure services that provide essential functionality for your legacy migration journey. Arguably, one of the most important services that keep these resources secure and provide access, or deny access, to these Azure resources is Azure Active Directory (AAD). It should be noted that Microsoft AAD is now called Microsoft Entra ID. The first thing you need to know about AAD is that it is a completely different service than Active Directory (AD), which was the on-premises directory service that was the center of Microsoft on-premises-based implementations in the days preceding Azure and until this day. Active Directory was designed for on-premises data centers and used Kerberos and New Technology Lan Manager (NTLM) for its authentication implementation. AAD was designed for cloud-based environments and used Open Authorization 2 (OAuth2), Security Assertion Markup Language (SAML), and Web Services...