# Identify the encryption layer before resizing an ADE-protected Linux logical volume

> DSE recommends drawing the current disk, encryption, physical-volume, volume-group, logical-volume, and filesystem relationships before selecting a procedure.

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260917-183-identify-the-encryption-layer-before-resizing-an-ade-protected-linux-logical-volume/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-17T16:31:57+00:00
- Modified: 2026-09-17T16:46:29+00:00
- Last reviewed by DSE: 2026-09-17
- Resource type: Guide
- DSE priority: Information
- Topics: IT
- Reading time: 1 minutes

## What you need to know

DSE recommends drawing the current disk, encryption, physical-volume, volume-group, logical-volume, and filesystem relationships before selecting a procedure.

## Potentially affected

Use this check for an existing Linux data-disk configuration protected by Azure Disk Encryption when an experienced LVM operator is preparing a resize.

## DSE recommendation

DSE recommends drawing the current disk, encryption, physical-volume, volume-group, logical-volume, and filesystem relationships before selecting a procedure.

## Article

## Source facts

Microsoft’s resize procedure covers encrypted data disks and explicitly excludes OS disk resizing. In traditional LVM encryption, the logical volumes are encrypted; LVM-on-crypt places encryption at the whole-disk layer. The guide advises against combining those two encryption layouts on one VM. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/linux/how-to-resize-encrypted-lvm)

## Applicability

Use this check for an existing Linux data-disk configuration protected by Azure Disk Encryption when an experienced LVM operator is preparing a resize.

## DSE recommendation

DSE recommends drawing the current disk, encryption, physical-volume, volume-group, logical-volume, and filesystem relationships before selecting a procedure. Confirm that the target is a data volume and record the free space available in the relevant group. Have the workload owner approve the capacity goal and recovery arrangements. Treat the source’s separate layout branches as distinct procedures and avoid copying device names or sample sizes into a production command.

## Verification

Inspect the observed block-device and LVM layout against the plan before any change. After the authorized resize, check both logical-volume size and filesystem capacity, then run the agreed workload-access test. Retain the before-and-after mapping and resolve any encryption-layer or mount discrepancy before accepting the new capacity.

## Official references

- [Microsoft: How to resize disks encrypted using Azure Disk Encryption – Azure Virtual Machines | Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/linux/how-to-resize-encrypted-lvm)

## Primary reference

- Name: How to resize disks encrypted using Azure Disk Encryption - Azure Virtual Machines | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/virtual-machines/linux/how-to-resize-encrypted-lvm
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Identify the encryption layer before resizing an ADE-protected Linux logical volume,” DSE Security, https://update.dsesecurity.com/updates/dse-20260917-183-identify-the-encryption-layer-before-resizing-an-ade-protected-linux-logical-volume/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.