Cross Subscription Network_swift_connection throws error

This refers to the issue being discussed in:

This is a fairly significant issue that has gone unaddressed for quite a while.

Large enterprises need to secure their paths to on-prem, so those subnets are in different subscriptions with different permission levels. Elastic Premium Functions are typically managed by developers who do not have privileges to manage those vnet subscriptions and deploy into a different set of subscriptions in their DevOps pipelines.

The inability to delegate Functions into vNETs in other subscriptions without Terraform deploy throwing an error is a growing in need and a critical one, but there is little feedback on this issue.

I was able to do what I needed with a nodejs SDK script in my pipeline, but this is by no means a stable, long-term fix.

Do we know when will this issue be addressed?