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
Copy file name to clipboardExpand all lines: articles/virtual-network-manager/faq.md
+25-4Lines changed: 25 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -84,23 +84,44 @@ You can view Azure Virtual Network Manager settings under **Network Manager** fo
84
84
85
85
Yes, you can choose to override or delete an existing peering already created.
86
86
87
+
### How can I explicitly allow SQLMI traffic before having deny rules?
88
+
89
+
Azure SQL Managed Instance has some network requirements. If your security admin rules can block the network requirements, you can use the below sample rules to allow SQLMI traffic with higher priority than the deny rules that can block the traffic of SQL Managed Instance.
| Any | Any |**VirtualNetwork**|**VirtualNetwork**| Allow |
107
+
87
108
## Limits
88
109
89
110
### What are the service limitation of Azure Virtual Network Manager?
90
111
91
-
* A hub in a hub-and-spoke topology can be peered up to 500 spokes.
112
+
* A hub in a hub-and-spoke topology can be peered up to 250 spokes.
92
113
93
-
*The subnets in a virtual network can't talk to each other if they have the same address space in a mesh configuration.
114
+
*A mesh topology canhave up to 250 virtual networks.
94
115
95
-
*Azure Virtual Network Manager allows only 500 virtual network peering connections across all connectivity configuration for a given virtual network. You can also manage legacy peering on their own.
116
+
*The subnets in a virtual network can't talk to each other if they have the same address space in a mesh configuration.
96
117
97
118
* The maximum number of IP prefixes in all admin rules combined is 1000.
98
119
99
120
* The maximum number of admin rules in one level of Azure Virtual Network Manager is 100.
100
121
101
122
* Azure Virtual Network Manager doesn't have cross-tenant support in the public preview.
102
123
103
-
* A virtual network can be part of up to five mesh configurations.
124
+
* A virtual network can be part of up to two mesh configurations.
0 commit comments