Bug: bootstrap subscription set as target for telemetry

[jaredfholgate]

Is there an existing issue for this?

• I have searched the existing issues

Infrastructure as Code Type? (Required)

terraform

PowerShell Module Version (Optional)

latest

Bootstrap Module Version (Optional)

latest

Starter Module? (Required)

terraform - complete_multi_region

Starter Module Version (Optional)

latest

Input arguments of the ALZ-PowerShell-Module (Optional)

enable_telemetry: true

Debug Output/Panic Output (Optional)

No response

Expected Behaviour (Required)

Deployment is successful.

Actual Behaviour (Required)

By default, we set the bootstrap subscription as the target subscription. This results in the legacy telemetry provider trying to create a telemetry deployment to that subscription. This results in an error since it does not have the permissions required to do that if that subscription is not one of management, connectivity or identity.

Steps to Reproduce (Optional)

This is only an issue if a customer is using a 4 subscription model, rather than the standard 3 subscription model.

To resolve, we should point the default subscription to the management subscription. The deployment should not know about the bootstrap subscription anyway.

Alternative would be to apply perms, but not the correct approach.

Important Factoids (Optional)

No response

References (Optional)

No response