@Lee Thornton - Based on the issue we can suggest the details below please refer and let us know if it helps here.
please confirm in the Azure portal that each managed disk attached to the VM shows the new size (e.g., if you have set a total of 10TB across disks the portal should reflect this per disk)
If possible, stop (deallocate) the VM completely in the Azure portal and then start it again. This ensures disk size changes propagate to the VM OS. (If it's prod server please consider doing in off hours)
Log in to the VM via RDP.
- Open Disk Management (diskmgmt.msc).
- Check the status and capacity of each disk.
- You should see the expanded disk size reflected as unallocated space outside the current partitions.
Right-click on the volume(s) (e.g., F: drive) you want to expand. Select "Extend Volume" to allocate the unallocated space and If disks are part of a storage pool or striped volume, extending may require adding additional disks or using the Storage Pools management console.
Additionally, please refer the Microsoft documentation for details:
Configure storage for SQL Server on Azure VMs : https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/storage-configuration?view=azuresql&tabs=windows2016
For Expanding virtual hard disks attached to a Windows virtual machine: https://learn.microsoft.com/en-us/azure/virtual-machines/windows/expand-disks
Performance best practices for SQL Server on Azure VMs : https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-storage?view=azuresql
I’ve sent you a private message requesting some details related to your subscription to ensure your privacy is protected. Please check your messages and let me know if you have any questions or need further clarification.