What changed
Item-level recovery (ILR), which Microsoft also calls file-level restore, lets you mount a backup recovery point, browse it and copy out only the files and folders you need. Until now it did not work on the two newest disk families. Microsoft's updated recovery documentation says item-level recovery (ILR) supports Standard HDD, Standard SSD, Premium SSD v1, Premium SSD v2, and Ultra disks. It adds that for Premium SSD v2 and Ultra disks, both 512-byte and 4-KB logical sector sizes are supported.
Mixed-disk VMs are covered too. ILR also supports recovery points from VMs with mixed disk types, exposing all eligible disks so you can recover individual files and folders without restoring an entire VM or disk. That matters because many production VMs keep the OS on a Premium SSD v1 disk and put database or log volumes on Premium SSD v2 or Ultra.
The Azure Backup "What's new" page lists the change under October 2026. It says the experience now matches the existing ILR workflow for Standard HDD, Standard SSD and Premium SSD v1, so ILR works the same way on every Azure managed disk type.
Summary: This adds file and folder recovery for Premium SSD v2 and Ultra disks. VM backup and full restore for these disks were already supported.
Why it matters: the old workaround
This was a real limitation. In an earlier Microsoft Q&A thread, a customer reported that file recovery stopped working after they upgraded their VMs to Premium SSD v2. The answer given there was that Azure Backup currently does not support File Recovery for virtual machines running on Premium v2 SSD or Ultra disks. The thread also explained that this limitation is causing the failure to download the Item Level Recovery script. The customer said they did not want to go down the path of creating a new VM with the disks from last restore point and recover the files.
Until now, that was the only route: restore whole disks, attach them somewhere, find the file and clean up afterwards. That is a lot of work to recover one deleted config file, which ILR is meant to handle in a few minutes.
Who's eligible
According to Microsoft Learn, ILR for Premium SSD v2 and Ultra disks supports Windows and Linux VMs running Ubuntu, RHEL, Debian, Oracle Linux, SLES, or openSUSE. Other conditions:
- Recovery Services vault and Resource Manager VMs only. Restoring files and folders is available only for Azure VMs deployed using the Resource Manager model and protected to a Recovery Services vault.
- Enhanced policy. The VM backup support matrix lists both Premium SSD v2 and Ultra disks as supported with the Enhanced policy. You can set up protection from either the Recovery Services vault or the VM blade. Microsoft says VMs still on the Standard policy can be migrated to Enhanced without disrupting existing backups.
- No agentless crash-consistent backups. The support matrix says agentless multi-disk crash-consistent backup does not support VMs with Ultra Disks, Premium SSD v2, Ephemeral OS disks, Shared disks, and Write Accelerated disks.
The general file-restore exclusions still apply:
| Scenario | File-level restore |
|---|---|
| Premium SSD v2 / Ultra (512-byte or 4-KB sectors) | Supported, including mixed-disk VMs |
| Encrypted VMs (Azure Disk Encryption) | Not supported; restore the full VM |
| Shared disks, temporary drives, deduplicated disks, write-accelerator disks | Not supported. |
| Windows Storage Spaces | Not supported on the same VM; use another machine |
| Linux LVM or software RAID | Not on the same VM; use a compatible alternate machine |
Summary: If your VM is on the Enhanced policy, isn't encrypted and doesn't use shared or write-accelerated disks, ILR should now work on its Premium SSD v2 and Ultra volumes.
Step by step: recovering files
Microsoft has not created a separate procedure for these disks; it is the same ILR workflow.
- Open File Recovery. In the Azure portal, go to Virtual machines and select the protected VM. Then select Backup and File Recovery.
- Pick a restore point. Under Select restore point, choose the recovery point that contains the files you need.
- Download the tool. Select Download Executable for Windows VMs or Download Script for Linux VMs (Linux gets a Python script). Use the copy button in the File Recovery menu to copy the password the script requires.
- Run it with admin rights. On Windows, right-click the executable, run it as administrator and paste the password. The recovered volumes get drive letters you can browse in File Explorer. The letters may differ from the original VM, but the volume names stay the same. On Linux, make the script executable with
chmod +x, run it, and the volumes are mounted under the folder you ran it from. - Copy what you need, then unmount. Back in the portal, select Unmount Disks. Don't skip this. If the connection stays open on a machine that is also backed up, its next backup may fail with "UserErrorUnableToOpenMount".
On Linux, the mount paths are not removed automatically after you disconnect. Run the script again with the clean parameter to clear them. If you're working with LVM volumes, Microsoft warns against using mount -a, because it can mount duplicate devices and cause data loss.
Know the limits before you start
ILR suits small, targeted recoveries. It is not built for bulk restores. Microsoft says this feature should be used when the total size of recovery is 10 GB or less. It also says the expected data transfer speeds are around 1 GB per hour. Premium SSD v2 and Ultra disks are often chosen for large databases, so be careful. For a multi-hundred-gigabyte data directory, a disk restore will almost certainly be faster than ILR.
Which machine runs the script matters too:
- Large VMs. If the source VM has more than 16 disks, or disks larger than 4 TB each, Microsoft recommends a separate recovery VM (it suggests a D2v3) rather than running the script on the protected VM.
- Network. The machine needs outbound port 443 to download.microsoft.com and the Entra ID endpoints, outbound port 3260 (iSCSI) to the regional Recovery Services URL, and public DNS on port 53. Proxies often don't support iSCSI or allow port 3260, so use a machine with direct access.
- OS compatibility. You can restore files only to the same or a compatible OS version. For example, Windows Server 2025 and 2022 recovery points pair with Windows 11 and Windows 10 clients. On Linux, the script needs bash 4 or later and Python 2.6.6 or later. On Windows, it needs .NET 4.6.2 or later. Both need TLS 1.2.
- Locale. The script is English-only and may need an English system locale to run properly.
- Hangs on large disks. Microsoft's troubleshooting steps cover raising disk and iSCSI timeout registry values on Windows. On Linux, they cover raising
noop_out_timeoutin/etc/iscsi/iscsid.conffrom 5 to 120.
Security
Microsoft hasn't changed the security model for ILR. Generating the script requires the same Azure role-based access permissions as a full VM or disk restore. The script is signed with Microsoft's Azure Backup certificate and must be run elevated with its password. It connects to the recovery point over iSCSI with mutual CHAP authentication inside a TLS tunnel. Access is read-only, file ACLs carry over, and the session expires after 12 hours unless you unmount sooner. That makes the script safe to hand around as a file, though anyone holding the password effectively has read access to the VM's data until the session ends.
Don't confuse it with GRS/CRR
Microsoft made geo-redundant storage (GRS) and Cross-Region Restore (CRR) generally available for Premium SSD v2 and Ultra VMs in October 2024. That is a separate feature with its own regional lists. The new ILR support is about getting files back, not about which region holds your backups.
Bottom line
This is a narrow update, but a useful one. Teams running SQL Server, SAP or other I/O-heavy workloads on Premium SSD v2 or Ultra disks can now recover a single dropped file the same way they do on older disk types. The 10 GB guideline and roughly 1 GB-per-hour speed still apply, so treat ILR as a quick fix for small losses and use disk restores for anything bigger.
References
- (Launched) Generally Available: Item Level Recovery for Azure VMs with Premium SSDv2 and Ultra Disks in Azure Backup Azure Updates · 2026-10-23T19:21:07Z
- Recover files and folders from Azure VM backup - Azure Backup learn.microsoft.com
- Support matrix for Azure VM backups - Azure Backup learn.microsoft.com