For 11th Gen Intel mobile processor machines, you’ll need to create your SmartDeploy boot media or deployment package with just the platform pack for the model selected in the Media Wizard. That will add the new Intel VMD RAID driver into the boot environment and allow the internal storage to show up.
This has shown up more on Dell machines as they somewhat uniquely ship all their machines with RAID on, whereas other manufacturers don’t. It certainly makes the deployment more complex, versus just using the native controller on the NVMe drive, and the Windows 10 inbox stornvme.sys driver, which is how other manufactures have it. So, a workaround is to turn RAID off in the BIOS.
The problem happens because when a boot critical driver gets added, it must be staged so that it’s ready for use at boot, not just for Plug-n-Play. That means the binaries are copied directly into C:\Windows\System32\Drivers folder. Intel’s older RAID driver and newer RAID driver share files that have the same file name but are not the same files (picture). Whichever driver would get added last is the one that would have its correct set of files and work. The other driver that got added first would have had its same filename files overwritten and won’t work.
Until Intel changes this to either share the same identical files, or use different file names, the best that can be done is to have boot media that supports 10th Gen and older machines, and separate boot media that supports 11th Gen machines.