So I was told that the Q4 date was incorrect - in fact there is currently no ETA for when this issue will be fixed. It's considered lower priority by Databricks as not enough customers are impacted or have raised this type of an issue. I would recommend @Ememel that you try and raise this issue through your Databricks support team or Microsoft so it increases the priority?