ManoharLakkoju-MSFT
commented
10 months ago @helplessJ Thanks for your feedback! We will investigate and update as appropriate.
Closed helplessJ closed 10 months ago
ManoharLakkoju-MSFT
commented
10 months ago @helplessJ Thanks for your feedback! We will investigate and update as appropriate.
AjayBathini-MSFT
commented
10 months ago @helplessJ
Thank you for your question.
Regarding the use of ADF Managed Private Link with multisubnetfailover, it is possible to configure the Private Link Service to support multisubnetfailover. This involves configuring the Private Link Service to use a load balancer with multiple backend pools, each containing a different subnet. The DNS server can then respond with multiple private IP addresses, and the load balancer will route traffic to the correct endpoint that supports write-intent.
It is important to note that configuring multisubnetfailover for ADF Managed Private Link requires careful planning and configuration to ensure that it is set up correctly and works as expected. You should consult the Azure documentation and work with a qualified Azure engineer to ensure that your configuration is correct and meets your requirements.
I hope this answers your question. Let me know if you have any further questions or concerns.
moodoovoodoo
commented
10 months ago Would this then be a VNN AG?
Edit: Additionally, I keep seeing that multiple subnets are called for, but I've never seen why. This makes sense for on-prem where you want distinct failure domains, but in Azure with software-defined networking this shouldn't be an issue. Would you be able to elaborate on that?
helplessJ
commented
10 months ago Thank you AjayBathini-MSFT. It sounds like a DNN AG Cluster isn't supported in this instance since: a) it does not require a load balancer or separate Subnets for the cluster nodes b) the dns server responds with the ip addresses of all nodes (some ip's are read-only intenet in our case) c) ADF Managed Private Link server entry only supports FQDN,Port (does not look possible to add multisubnetfailover=true to the connection string; but the ADF UI obfuscates this -- so this is unknown)
AjayBathini-MSFT
commented
10 months ago @helplessJ & @moodoovoodoo Thank you for your feedback! Since this issue isn't directly related to improving our docs, and to gain a better understanding of your issue, I'd recommend working closer with our support team via an [Azure support request] (https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request). Or you can leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds. [Teams Q&A forum] (https://docs.microsoft.com/en-us/answers/topics/46488/office-teams-windows-itpro.html) for technical questions about the configuration and administration of Microsoft Teams on Windows. [Microsoft Teams Community forum] (https://answers.microsoft.com/en-us/msteams/forum?sort=LastReplyDate&dir=Desc&tab=All&status=all&mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&isFilterExpanded=false&page=1) Thank you for your time and patience throughout this issue.
helplessJ
commented
10 months ago The only reason I'm here is because this very basic information is missing from the docs. Thank you for taking the time to reply.
With respect to the matrix of choices to consider when choosing the proper ADF IR for 'Azure integration runtime with managed virtual network' does the ADF Managed Private Link using a Private Link Service support multisubnetfailover ? IE, can the dns server respond with multiple private ip's and the service connects to the correct endpoint that supports write-intent?
"401b1322-0468-7eb2-f022-9d33eec90b4b" source in question: https://learn.microsoft.com/en-us/azure/data-factory/choose-the-right-integration-runtime-configuration#comparison-of-different-types-of-integration-runtimes
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.