You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Placing domain controllers in an Identity subscription would require a transient network for VMs in other spoke vnets to reach them.
Best practise is not to have peerings between spoke vnets.
Is the transient network included in the blueprint?
Wouldn't it in a hybrid senario generally make sense to have the domain controllers in the Hub Connectivity subscriptipn or in the corp sub together with the domain joined VMs?
Cheers
Seb
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi
Placing domain controllers in an Identity subscription would require a transient network for VMs in other spoke vnets to reach them.
Best practise is not to have peerings between spoke vnets.
Is the transient network included in the blueprint?
Wouldn't it in a hybrid senario generally make sense to have the domain controllers in the Hub Connectivity subscriptipn or in the corp sub together with the domain joined VMs?
Cheers
Seb
Beta Was this translation helpful? Give feedback.
All reactions