I've just received confirmation from MS support that this is indeed a bug in serverless. I believe a fix is in the works no ETA or further information about the scope.
Supposedly there might be a back end fix that can remediated but you need to work with MS Support to enable.