26808 - Feature - Add support to allow Private DNS Zone VNet Linking for Spoke VNets

[4pplied]

Overview/Summary

Adding support to allow Private DNS Zone VNet Linking for Spoke VNets through HubPeeredSpoke orchestration module and a new Private Dns Zone Linking module.

AB#26808

This PR fixes/adds/changes/removes

1. Added feature to HubPeeredSpoke orchestration module to allow Private DNS Zone Linking to Spoke VNets.
2. Added new module for Private DNS Zone Linking.

Breaking Changes

1. N/A

Testing Evidence

Evidence to be posted.

As part of this Pull Request I have

• Read the Contribution Guide and ensured this PR is compliant with the guide
• Ensured the resource API versions in .bicep file/s I am adding/editing are using the latest API version possible
• Checked for duplicate Pull Requests
• Associated it with relevant GitHub Issues
• (ALZ Bicep Core Team Only) Associated it with relevant ADO Items
• Ensured my code/branch is up-to-date with the latest changes in the main branch
• Performed testing and provided evidence.
• Updated one or more of the following tests (if required)
  • Unit
  • Linting
  • E2E (End-To-End)
  • ValidateAzCloud (Base validation in Azure Cloud)
  • ValidateMcCloud (Base validation in Azure China Cloud)
• Updated relevant and associated documentation (e.g. Contribution Guide, Module READMEs, Wiki Docs etc.)
• If relevant, created or updated Code Tours here

[4pplied]

/azp run validateazcloud

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[4pplied]

/azp run e2e

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jtracey93]

LGTM