This is currently a known issue with Storage Policy based management, when we attach a shared virtual disk to another VM it assumes the default policy name of the target VM instead of enforcing existing policy name of the VMDK which was already created with a policy.