Not able to see the Tempdb and configure button in SQL virtual machine under storage --> Management under drive

Sunil 20 Reputation points
2026-05-18T17:29:50.47+00:00

Not able to see TempDB under SQL virtual machine -->Storage -->Management--> under drives..See below screen shot. I think I did some stupid thing, Initial when IaaS extension setup I'm able to see the tempdb their but I mistakenly configure the large size of tempdb data files so I try to revert the size, I did I click NO to "configure tempdb data files" and click NO to "manage tempdb database folders on restart" thought that it will remove the tampdb from there so I can re-setup again but now tempdb it is not showing their. How to bring the tempdb back their ??

User's image

SQL Server on Azure Virtual Machines
Answer accepted by question author
Pilladi Padma Sai Manisha 11,715 Reputation points Microsoft External Staff Moderator
2026-05-20T07:13:42.3433333+00:00

Hi Sunil,

Looks like by clicking No on both the “Configure tempdb data files” and “Manage tempdb database folders on restart” prompts, the SQL IaaS Agent no longer shows the tempdb drive in the storage blade. To get that back you basically need to re-enable the storage configuration for tempdb. Here’s how:

  1. Verify your SQL IaaS Agent extension is healthy
  2. Ensure you’re using a supported Marketplace image with managed Premium SSD disks
    • Storage Configuration (including tempdb) only works on SQL Server VMs deployed from Azure Marketplace gallery images with managed Premium SSDs.
    • Unmanaged disks or custom images won’t show the Configure/Extend options.
  3. Make sure your storage pool and volume names are the defaults
    • If you’ve customized your Storage Spaces pool or renamed volumes, the portal won’t detect them. Default naming conventions are: • Storage Pools: SQLVMStoragePool1, 2, 3 • Virtual Disks: SQLVMVirtualDisk1, 2, 3 • Volumes: SQLVMDATA1, SQLVMLOG, SQLVMTEMPDB
    • Check Disk Management inside the VM and rename the tempdb volume to SQLVMTEMPDB if needed.
  4. Re-run the Storage Configuration blade
    • In the Azure Portal navigate to your SQL virtual machine resource → Storage tab → click Configure at the top.
    • You should now see a TempDB card with a Configure button.
    • Toggle Configure tempdb data files to Yes, select your settings, and also toggle Manage tempdb database folders on restart to Yes.
    • Save and then restart the SQL Server service (or the entire VM) to have the IaaS Agent recreate the tempdb folders and files on that volume.

If you still don’t see the tempdb section, let me know:

• Which marketplace image and SQL version you’re running?

• Your disk types (Premium SSD / Standard HDD / unmanaged)?

• Whether you’ve ever customized the storage pool or renamed volumes?

Reference list:

• Configure Storage for existing VMs (incl. tempdb):

https://docs.microsoft.com/azure/azure-sql/virtual-machines/windows/storage-configuration#existing-vms

• IaaS Agent extension install/remove:

https://docs.microsoft.com/azure/azure-sql/virtual-machines/windows/sql-agent-extension-manually-register-single-vm?tabs=bash%2Cazure-cli

• Known issues & naming requirements:

https://learn.microsoft.com/azure/azure-sql/virtual-machines/windows/storage-configuration?view=azuresql&tabs=windows2016#known-issues

Hope that helps get your tempdb drive and Configure button back!

Was this answer helpful?

1 person found this answer helpful.
0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Amira Bedhiafi 43,046 Reputation points MVP Volunteer Moderator
    2026-05-18T19:54:53.0233333+00:00

    Hello Sunil !

    Thank you for posting on MS Learn Q&A.

    I think you have an issue in the config of SQL IaaS Agent extension lost/disabled the managed TempDB configuration.

    Drive is not found in the volumes list means the SQL VM resource still has some TempDB or storage metadata but the drive it expects is no longer mapped to a detected Windows volume.

    First verify where SQL Server thinks TempDB is located :

    SELECT
    name,
    physical_name,
    size * 8 / 1024 AS size_mb,
    growth,
    is_percent_growth
FROM sys.master_files
WHERE database_id = 2;

    Check whether the files are pointing to something like:

    D:\SQLTemp\
T:\SQLTemp\
G:\...

    Then RDP to the VM and confirm that the drive and folder actually exist.

    You can enable TempDB management from the SQL VM, so go to SQL virtual machine resource then Storage configuration then tempdb the configure then :

    Configure tempdb data files = Yes

    Manage tempdb database folders on restart = Yes

    Then enter the correct path, file count, initial size and growth values. This way Azure manages the TempDB configuration, folders and permissions at SQL Server service start. Then restart.

    If the TempDB Configure option is no longer visible you need to check the SQL IaaS Agent extension health.

    If it is unhealthy, failed or stuck, repair it.

    If TempDB is on the Azure temporary or local SSD drive, usually D:\ be careful. That storage is ephemeral. The SQL IaaS Agent extension recreates the required TempDB folders and permissions for Marketplace SQL VM images but if management is disabled or SQL Server was installed manually you must handle that startup logic yourself.

    If you disabled Manage tempdb database folders on restart then SQL Server may fail to start after a reboot if the TempDB folder no longer exists.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.