[AVM Module Issue]: Unable to create private endpoints for Private Link Scope when VNet is in different subscription

[JamesDawson]

Check for previous/existing GitHub issues

• I have checked for previous/existing GitHub issues

Issue Type?

Bug

Module Name

avm/res/insights/private-link-scope

(Optional) Module Version

0.5.2

Description

A deployment failure happens when the Private Link Scope resource is in a different subscription to the Virtual Network.

Generally the error is ResourceGroupNotFound on the private endpoint resource group (since it exists in a different subscription). If a resource group happens to exist with the same name in the PLS subscription, then the deployment produces an InvalidResourceReference.

Private Endpoints must be provisioned in the same subscription as the Virtual Network they are connected to. Whilst this module allows you to customise the resource group for the private endpoint, it currently assumes the same subscription as the Private Link Scope resource.

To avoid needing another parameter, perhaps the scope on this line should infer the subscription from the subnet resource ID?

bicep-registry-modules/avm/res/insights/private-link-scope/main.bicep

Line 160 in 8ee8adb

scope: resourceGroup(privateEndpoint.?resourceGroupName ?? '')

(Optional) Correlation Id

No response

[microsoft-github-policy-service]

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

[avm-team-linter]

@JamesDawson, thanks for submitting this issue for the avm/res/insights/private-link-scope module!

Important

A member of the @Azure/avm-res-insights-privatelinkscope-module-owners-bicep or @Azure/avm-res-insights-privatelinkscope-module-contributors-bicep team will review it soon!