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
+2-29Lines changed: 2 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -105,7 +105,7 @@ In Azure, virtual network peering and connected groups are two methods of establ
105
105
106
106
### Can I create exceptions to security admin rules?
107
107
108
-
Normally, security admin rules will be defined to block traffic across virtual networks. However, there are times when certain virtual networks and their resources need to allow traffic for management or other processes. For these scenarios,you can [create exceptions](./concept-enforcement.md#network-traffic-enforcement-and-exceptions-with-security-admin-rules) where needed. Learn how to [blocking high-risk ports with exceptions](how-to-block-high-risk-ports.md) for these types of scenarios.
108
+
Normally, security admin rules will be defined to block traffic across virtual networks. However, there are times when certain virtual networks and their resources need to allow traffic for management or other processes. For these scenarios,you can [create exceptions](./concept-enforcement.md#network-traffic-enforcement-and-exceptions-with-security-admin-rules) where needed. Learn how to [blocking high-risk ports with exceptions](how-to-block-high-risk-ports.md) for these types of scenarios.
109
109
110
110
### How can I deploy multiple security admin configurations to a region?
111
111
@@ -154,35 +154,8 @@ Certain services such as Azure SQL Managed Instance, Azure Databricks and Azure
154
154
155
155
### What are the service limitations of Azure Virtual Network Manager?
156
156
157
-
* A connected group can have up to 250 virtual networks. Virtual networks in a mesh topology are in a connected group, therefore a mesh configuration has a limit of 250 virtual networks.
157
+
For the most current limitations, see [Limitations with Azure Virtual Network Manager](concept-limitations.md).
158
158
159
-
* You can have network groups with or without direct connectivity enabled in the same hub-and-spoke configuration, as long as the total number of virtual networks peered to the hub **doesn't exceed 500** virtual networks.
160
-
* If the network group peered with the hub **has direct connectivity enabled**, these virtual networks are in a *connected group*, therefore the network group has a limit of 250 virtual networks.
161
-
* If the network group peered with the hub **doesn't have direct connectivity enabled**, the network group can have up to the total limit for a hub-and-spoke topology.
162
-
163
-
* A virtual network can be part of up to two connected groups.
164
-
165
-
**Example:**
166
-
* A virtual network can be part of two mesh configurations.
167
-
* A virtual network can be part of a mesh topology and a network group that has direct connectivity enabled in a hub-and-spoke topology.
168
-
* A virtual network can be part of two network groups with direct connectivity enabled in the same or different hub-and-spoke configuration.
169
-
170
-
* You can have virtual networks with overlapping IP spaces in the same connected group. However, communication to an overlapped IP address is dropped.
171
-
172
-
* The maximum number of IP prefixes in all admin rules combined is 1000.
173
-
174
-
* The maximum number of admin rules in one level of Azure Virtual Network Manager is 100.
175
-
176
-
* Azure Virtual Network Manager doesn't have cross-tenant support in the public preview.
177
-
178
-
* Customers with more than 15,000 Azure subscriptions can apply Azure Virtual Network Policy only at the subscription and resource group scopes. Management groups can't be applied over the 15 k subscription limit.
179
-
* If this is your scenario, you would need to create assignments at lower level management group scope that have less than 15,000 subscriptions.
180
-
181
-
* Virtual networks can't be added to a network group when the Azure Virtual Network Manager custom policy `enforcementMode` element is set to `Disabled`.
182
-
183
-
* Azure Virtual Network Manager policies don't support the standard policy compliance evaluation cycle. For more information, see [Evaluation triggers](../governance/policy/how-to/get-compliance-data.md#evaluation-triggers).
184
-
185
-
* The current preview of connected group has a limitation where traffic from a connected group can't communicate with a private endpoint in this connected group if it has NSG enabled on it. However, this limitation will be removed once the feature is generally available.
186
159
## Next steps
187
160
188
161
Create an [Azure Virtual Network Manager](create-virtual-network-manager-portal.md) instance using the Azure portal.
Copy file name to clipboardExpand all lines: articles/virtual-network-manager/overview.md
+15-5Lines changed: 15 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,10 +43,20 @@ Next, you create connectivity and/or security configuration(s) applied to those
43
43
44
44
For current information on the regions where Azure Virtual Network Manager is available, see [Azure Virtual Network Manager regions](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=virtual-network-manager).
45
45
46
+
## Pricing
47
+
For pricing details, see [Azure Virtual Network Manager pricing](https://azure.microsoft.com/pricing/details/virtual-network-manager/).
48
+
49
+
## FAQs
50
+
For FAQs, see [Azure Virtual Network Manager FAQs](faq.md).
51
+
52
+
## Limits
53
+
For limits, see [Azure Virtual Network Manager limits](faq.md#what-are-the-service-limitations-of-azure-virtual-network-manager).
54
+
55
+
## Service Level Agreement
56
+
For SLA, see [SLA for Azure Virtual Network Manager](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1)
57
+
46
58
## Next steps
47
59
48
-
- Create an [Azure Virtual Network Manager](create-virtual-network-manager-portal.md) instance using the Azure portal.
49
-
- Deploy an [Azure Virtual Network Manager](create-virtual-network-manager-terraform.md) instance using Terraform.
50
-
- Learn more about [network groups](concept-network-groups.md) in Azure Virtual Network Manager.
51
-
- Learn what you can do with a [connectivity configuration](concept-connectivity-configuration.md).
52
-
- Learn more about [security admin configurations](concept-security-admins.md).
60
+
> [!div class="nextstepaction"]
61
+
> [Create an Azure Virtual Network Manager instance using the Azure portal](create-virtual-network-manager-portal.md).
0 commit comments