Update 24-10-2022: I’ve got word from Microsoft that the issue discussed here has been solved in version v21 (2022 wave 2). The way it has been solved is that now
Update 24-10-2022: I’ve got word from Microsoft that the issue discussed here has been solved in version v21 (2022 wave 2). The way it has been solved is that now