The issue was logged as bug in Azure devops, and it was fixed. We hope we can get the uptake here. Details was sent via Email.