You are building an SAP environment by using Azure Resource Manager templates. The SAP environment will use Linux virtual machines. You need to…

When attaching data disks to an Azure Linux VM for an SAP workload, a stable naming convention is required for automation, as device names like /dev/sdc can change upon reboot. Azure provides a set of stable symbolic links under the /dev/disk/azure/ directory. Specifically, data disks are organized by SCSI controller and LUN. The path /dev/disk/azure/scsi1/ contains symbolic links named lun0, lun1, lun2, etc., which correspond directly to the LUN specified in the ARM template. Running the ls /dev/disk/azure/scsi1 command lists these links, allowing a direct correlation between the LUN and the underlying kernel device name (e.g., sdc), which is the goal of the question.

A. ls /dev/disk/azure/root: This path is a symbolic link to the operating system (OS) disk, not the attached data disks.

C. tree /dev/disk/azure/root: This command also targets the OS disk path. It is used for viewing a directory tree, which is not the intended use for this specific path.

D. tree /dev/disk/azure/resource: This path is a symbolic link to the temporary resource disk, not the persistent data disks used for SAP files.

1. Microsoft Learn

"Configure LVM on a Linux VM in Azure": This document demonstrates using the /dev/disk/azure/scsi1/ path to identify disks by their LUN. Under the "Identify the data disks" section

it shows the command ls -l /dev/disk/azure/scsi1/ and its output

which clearly maps lun0

lun1

etc.

to their corresponding /dev/sd device names.

2. Microsoft Learn

"Azure Virtual Machines storage configuration for SAP NetWeaver": In the "Linux" section

this guide states

"On Linux

the Azure platform creates friendly names in the directory /dev/disk/azure. For your automation scripts

use the devices in the /dev/disk/azure directory." This confirms the recommended practice for SAP workloads is to use this stable path for disk identification.

3. Microsoft Learn

"Troubleshoot Linux VM device name changes": This article explains the problem of non-persistent device names and recommends using persistent naming conventions. It mentions that the Azure Linux Agent creates symbolic links under /dev/disk/azure based on the SCSI address (including LUN) of the disks

reinforcing the reliability of this path for correlation.