Skip to content

Commit fd4877e

Browse files
authored
Merge pull request #189088 from urosmil/patch-6
Updated no ip address section
2 parents 9faa77c + eb8dd5f commit fd4877e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-sql/managed-instance/frequently-asked-questions-faq.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -335,7 +335,7 @@ sections:
335335
336336
### What if there are not enough IP addresses for performing instance update operation?
337337
338-
In case there are not enough [IP addresses](connectivity-architecture-overview.md#network-requirements) in the subnet where your managed instance is provisioned, you will have to create a new subnet and a new managed instance inside it. We also suggest that the new subnet is created with more IP addresses allocated so future update operations will avoid similar situations. After the new instance is provisioned, you can manually back up and restore data between the old and new instances or perform cross-instance [point-in-time restore](point-in-time-restore.md?tabs=azure-powershell).
338+
In case there are not enough [IP addresses](connectivity-architecture-overview.md#network-requirements) in the subnet where your managed instance is provisioned, you will have to create a new subnet and move the managed instance to it. We also suggest that the new subnet is created with more IP addresses allocated so future update operations will avoid similar situations. Learn how to [move Azure SQL Managed Instance across subnets](./vnet-subnet-move-instance.md).
339339
340340
### Do I need an empty subnet to create a Managed Instance?
341341

0 commit comments

Comments
 (0)