🪲 Bug Report - Creating subscriptions without networking resources causes management group placement and sub tags etc. to not be deployed/created

[jtracey93]

Describe the bug

Creating subscriptions without networking resources causes management group placement and sub tags etc. to not be deployed/created

To Reproduce

Steps to reproduce the behaviour:

Below example will create subscription fine, but will not move to corp MG or tag the subscription

targetScope = 'managementGroup'

module sub001 'br/public:lz/sub-vending:1.1.1' = {
  name: 'sub001'
  params: {
    subscriptionAliasEnabled: true
    subscriptionBillingScope: '/providers/Microsoft.Billing/billingAccounts/1234567/enrollmentAccounts/123456'
    subscriptionAliasName: 'sub-test-001'
    subscriptionDisplayName: 'sub-test-001'
    subscriptionTags: {
      example: 'true'
    }
    subscriptionWorkload: 'Production'
    subscriptionManagementGroupAssociationEnabled: true
    subscriptionManagementGroupId: 'corp'
  }
}

Expected behaviour

Above example should tag and move sub to correct MG