MLZ Configuration Resources (TF State, Key Vaults) are always created in the Hub subscription

[glennmusa]

Description
Should I try a multi-subscription deployment with a subscription for MLZ configuration other than the hub like below, applying Terraform via deploy.sh will fail because it will always look in the hub subscription for the Terraform state storage account:

src/scripts/deploy.sh -s {config_sub_id} \
-u {hub_sub_id} \
-0 {t0_sub_id} \
-1 {t1_sub_id} \
-2 {t2_sub_id} \
-3 {t3_sub_id}

Steps to Reproduce
Steps to reproduce the behavior:

1. Run deploy.sh with a configuration subscription -s as a subscription other than the Hub subscription -u
2. You'll receive this error: Terraform State Resource Group '{the tf state account}' does not exist...validate config.vars file and re-run script

Expected behavior
I can deploy the MLZ configuration resources into whatever subscription I want

Actual behavior
MLZ configuration resources always end up in the Hub subscription.

[glennmusa]

+@RKauf00