I was able to fix the provisioning problem by (re)starting the VM from the Compute Infrastructure blade rather than the DevTest Lab environment.

It seems that creating the SAS URL "confuses" the managed DevTest Lab environment. Starting the VM manually from the Compute Infrastructure environment seems to have updated and "resynced" the managed DevTest Lab environment.