I'm implementing an always on database with a new Dynamics 365, on-premise deployment. The question at hand: is it possible to set it up so advanced finds and exports to Excel pull from the secondary node by default as to prevent potential performance hits? Or if this is impossible/unsupported without causing unwanted repercussions?
I know how to change the connection in Excel after the export for a dynamic one.
Thanks!
-Eric