Skip to content

Commit c195a0e

Browse files
authored
Merge pull request #178310 from duongau/patch-3
AVNM FAQ - add SQLMI question and update limits
2 parents b0dbc0b + c2dd7ef commit c195a0e

File tree

1 file changed

+25
-4
lines changed
  • articles/virtual-network-manager

1 file changed

+25
-4
lines changed

articles/virtual-network-manager/faq.md

Lines changed: 25 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -84,23 +84,44 @@ You can view Azure Virtual Network Manager settings under **Network Manager** fo
8484

8585
Yes, you can choose to override or delete an existing peering already created.
8686

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.
90+
91+
#### Inbound rules
92+
93+
| Port | Protocol | Source | Destination | Action |
94+
| ---- | -------- | ------ | ----------- | ------ |
95+
| 9000, 9003, 1438, 1440, 1452 | TCP | SqlManagement | **VirtualNetwork** | Allow |
96+
| 9000, 9003 | TCP | CorpnetSaw | **VirtualNetwork** | Allow |
97+
| 9000, 9003 | TCP | CorpnetPublic | **VirtualNetwork** | Allow |
98+
| Any | Any | **VirtualNetwork** | **VirtualNetwork** | Allow |
99+
| Any | Any | **AzureLoadBalancer** | **VirtualNetwork** | Allow |
100+
101+
#### Outbound rules
102+
103+
| Port | Protocol | Source | Destination | Action |
104+
| ---- | -------- | ------ | ----------- | ------ |
105+
| 443, 12000 | TCP | **VirtualNetwork** | AzureCloud | Allow |
106+
| Any | Any | **VirtualNetwork** | **VirtualNetwork** | Allow |
107+
87108
## Limits
88109

89110
### What are the service limitation of Azure Virtual Network Manager?
90111

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.
92113

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 can have up to 250 virtual networks.
94115

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.
96117

97118
* The maximum number of IP prefixes in all admin rules combined is 1000.
98119

99120
* The maximum number of admin rules in one level of Azure Virtual Network Manager is 100.
100121

101122
* Azure Virtual Network Manager doesn't have cross-tenant support in the public preview.
102123

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.
104125

105126
## Next steps
106127

0 commit comments

Comments
 (0)