What's changed: Created AZ-120 Chapter 5, completing the textbook (Domain 4 second-half: monitoring (Azure Monitor VM Insights, Azure Network Watcher, Azure Monitor for SAP solutions AMS integrating SAP HANA/NetWeaver internals); backup management (Azure Backup, Recovery Services vault, Azure Backup for SAP HANA DB-consistent, instant restore, restore validation); SAP operations (Azure Center for SAP solutions virtual instance VIS, start/stop, SAP LaMa connector for Azure)).
5.3SAP operations (Azure Center for SAP and LaMa)
Understand starting/stopping SAP systems and virtual-instance management via Azure Center for SAP solutions, and operations integration via the SAP Landscape Management (LaMa) connector for Azure.
Integrating day-to-day SAP operations (start/stop, status, lifecycle) natively into Azure improves operational efficiency and consistency.
5.3.1Operations with Azure Center for SAP solutions
Azure Center for SAP solutions represents an SAP system in Azure as a Virtual Instance for SAP solutions (VIS), letting you start/stop SAP systems/instances, visualize status, and manage lifecycle from the portal/API. The benefit is a consistent resource model spanning deployment (Chapter 2) and operations (this chapter). Think "start/stop and integrated-manage SAP as an Azure resource" = Azure Center for SAP solutions.
5.3.2SAP LaMa connector for Azure
Organizations already operating their SAP landscape with SAP Landscape Management (LaMa) can use the LaMa connector for Azure to operate Azure VMs and storage from LaMa (start/stop, scale, copy/refresh, etc.). This integration controls Azure resources from the SAP operations tool (LaMa)—a different approach from Azure Center for SAP (Azure-initiated). Distinguish "operate Azure from SAP LaMa" = LaMa connector.
Cues: "start/stop and integrated-manage SAP as a virtual instance (VIS) in Azure" = Azure Center for SAP solutions. "operate Azure VMs/storage from SAP LaMa" = LaMa connector for Azure. Consistent deployment/operations model = Azure Center for SAP.
Watch the mix-ups: (1) Azure Center for SAP (Azure-initiated management) vs LaMa connector (SAP-LaMa-initiated Azure operations)—opposite approaches. (2) Azure Center for SAP differs in role from SDAF (build vs operate/manage). (3) Start/stop saves cost but mind SAP dependency order. (4) The LaMa connector targets orgs already using LaMa.
5.3.3Section summary
- Azure Center for SAP solutions start/stop and integrated-manage SAP as a virtual instance (VIS)
- The LaMa connector for Azure operates Azure VMs/storage from SAP Landscape Management
- Azure-initiated (Azure Center for SAP) vs SAP-initiated (LaMa connector) differ in approach
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. You want to represent SAP systems as virtual instances in Azure and start/stop and integrated-manage them from the portal/API. Best?
Q2. An org already operating with SAP Landscape Management (LaMa) wants to operate Azure VMs/storage from LaMa. Best?
Q3. What is the SAP representation unit in Azure Center for SAP solutions?
Q4. Which correctly distinguishes the roles of Azure Center for SAP solutions and SAP Deployment Automation Framework?
Q5. Which correctly distinguishes the approaches of Azure Center for SAP solutions and the LaMa connector?
Keep track of your progress
The full study guide is free to read. Sign up free to practice with the question bank, track what you have read, review your mistakes, and highlight passages.