Skip to content

Commit 3596d3a

Browse files
authored
Added in location of intent policy and best practice for routing
have added in the location of the network intent policies and also best practice guidance around routing between Auto faliover MI instances
1 parent 717decc commit 3596d3a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-sql/managed-instance/connectivity-architecture-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ Deploy SQL Managed Instance in a dedicated subnet inside the virtual network. Th
102102
- **Sufficient IP addresses:** The SQL Managed Instance subnet must have at least 32 IP addresses. For more information, see [Determine the size of the subnet for SQL Managed Instance](vnet-subnet-determine-size.md). You can deploy managed instances in [the existing network](vnet-existing-add-subnet.md) after you configure it to satisfy [the networking requirements for SQL Managed Instance](#network-requirements). Otherwise, create a [new network and subnet](virtual-network-subnet-create-arm-template.md).
103103

104104
> [!IMPORTANT]
105-
> When you create a managed instance, a network intent policy is applied on the subnet to prevent noncompliant changes to networking setup. After the last instance is removed from the subnet, the network intent policy is also removed. Rules below are for the informational purposes only, and you should not deploy them using ARM template / PowerShell / CLI. If you want to use the latest official template you could always [retrieve it from the portal](../../azure-resource-manager/templates/quickstart-create-templates-use-the-portal.md).
105+
> When you create a managed instance, a network intent policy is applied on the subnet to prevent noncompliant changes to networking setup, this policy is a hidden resource located in the Virtual Network Resrouce Group. After the last instance is removed from the subnet, the network intent policy is also removed. Rules below are for the informational purposes only, and you should not deploy them using ARM template / PowerShell / CLI. If you want to use the latest official template you could always [retrieve it from the portal](../../azure-resource-manager/templates/quickstart-create-templates-use-the-portal.md). When deploying Auto Failover groups please ensure replication traffic goes direct between the two MI instances and not through a hub network
106106
107107
### Mandatory inbound security rules with service-aided subnet configuration
108108

0 commit comments

Comments
 (0)