Skip to main content
NetApp Knowledge Base

Can one connector create private endpoints into 2 different Azure subscriptions?

Last Updated:

Applies to

  • Cloud Volumes ONTAP (CVO)
  • Microsoft Azure
  • Private Endpoints


  • No, a single connector cannot be used to create private endpoints into 2 different Azure subscriptions due to restrictions of the app.conf file.
  • Azure Private DNS is tied to the specific Azure subscription.
  • If using two different Azure subscriptions in different regions, and each has a different Private DNS Zone that is also in another Azure Resource Group, an example solution would be to:
  1. Create a connector to manage resources in the U.S. region
  2. Create a connector to manage resources in the Canada region
  3. If desired, create a third connector with Automatic Capacity Management mode disabled and use it to manage tasks like Snapmirroring between both regions.
NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.