A pooled AVD host pool uses FSLogix Profile Containers stored on an Azure Files share. After a storage networking outage, users reported being unexpectedly logged on with brand-new temporary local profiles instead of receiving an error, which caused confusion and lost work. To prevent this behavior in the future so that users are instead prevented from signing in (or shown a failure) when their Profile Container cannot be attached, which FSLogix registry setting under HKLM\SOFTWARE\FSLogix\Profiles should you configure?