-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
azurerm_private_dns_zone_virtual_network_link fails when linking to Virtual Network in a different subscription #24724
Comments
Hi @captainhook , This seems to be an API issue rather than a provider bug. Can you cross-link different subscriptions in the Portal? |
Hi @wuxu92, yes, I can create the vnet link through the Azure portal. I have tested through Azure Portal and Terraform using the same user accounts, so same rights (full). |
So I recreated everything with new subscriptions, and it works fine:
I then recreated the spoke vnet and it's all suddenly working fine... there must be something weird with that old vnet or I did something wrong in handling/importing it. No bug in Terraform - lovely day! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Is there an existing issue for this?
Community Note
Terraform Version
1.7.1
AzureRM Provider Version
3.89.0
Affected Resource(s)/Data Source(s)
azurerm_private_dns_zone_virtual_network_link
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
It should successfully create a virtual network link associated with the virtual network in a different subscription to the private DNS zones.
Actual Behaviour
Fails with 'LinkedAuthorizationFailed' error.
Steps to Reproduce
terraform apply
Important Factoids
No response
References
#21350 - may be the same but it is not reported as a bug
#5172
#23238
The text was updated successfully, but these errors were encountered: