Skip to content

Commit 14d7d63

Browse files
authored
Merge pull request #108138 from srdan-bozovic-msft/patch-1
fix link
2 parents a323f7b + daca40a commit 14d7d63

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/sql-database/sql-database-managed-instance-enabling-service-aided-subnet-configuration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Automatically configured network security groups and route table rules are visib
1919
Service-aided configuration is enabled automatically once you turn on [subnet-delegation](../virtual-network/subnet-delegation-overview.md) for `Microsoft.Sql/managedInstances` resource provider.
2020

2121
> [!IMPORTANT]
22-
> Once subnet-delegation is turned on you could not turn it off until you remove last virtual cluster from the subnet. For more details on how to delete virtual cluster see the following [article](sql-database-managed-instance-delete-virtual-cluster.md#delete-virtual-> cluster-from-the-azure-portal).
22+
> Once subnet-delegation is turned on you could not turn it off until you remove last virtual cluster from the subnet. For more details on how to delete virtual cluster see the following [article](sql-database-managed-instance-delete-virtual-cluster.md#delete-virtual-cluster-from-the-azure-portal).
2323
2424
> [!NOTE]
2525
> As service-aided subnet configuration is essential feature for maintaining SLA, starting May 1st 2020, it won't be possible to deploy managed instances in subnets that are not delegated to managed instance resource provider. On July 1st 2020 all subnets containing managed instances will be automatically delegated to managed instance resource provider.

0 commit comments

Comments
 (0)