fix: MI provisioning time explanation

martdob · Sep 10, 2018 · 8ed833e · 8ed833e
1 parent 73d22b4
commit 8ed833e
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/101-sqlmi-new-vnet/README.md b/101-sqlmi-new-vnet/README.md
@@ -34,7 +34,7 @@ You can click the "Deploy to Azure" button at the beginning of this document or
 
 ## Important
 
-Usual deployment time is 3-6h but during the public preview deployment might take up to 48h. The reason why provisioning takes some time is that along the Managed Instance virtual cluster that hosts the instance is created. Each subsequent instance creation takes just about a few minutes.
+During the public preview deployment might take up to 48h (average time is 3-6h). This is because virtual cluster that hosts the instances needs some time to deploy. Each subsequent instance creation in the same virtual cluster takes just about a few minutes.
 
 After the last Managed Instance is deprovisioned, cluster stays a live for up to 24h. This is to avoid waiting for a new cluster to be provisioned in case that customer just wants to recreate the instance. During that period of time Resource Group and virtual network could not be deleted. This is a known issue and Managed Instance team is working on resolving it.
 

diff --git a/201-sqlmi-new-vnet-w-jumpbox/README.md b/201-sqlmi-new-vnet-w-jumpbox/README.md
@@ -36,7 +36,7 @@ You can click the "Deploy to Azure" button at the beginning of this document or
 
 ## Important
 
-Usual deployment time is 3-6h but during the public preview deployment might take up to 48h. The reason why provisioning takes some time is that the Managed Instance virtual cluster that hosts the instance is created. Each subsequent instance creation takes just about a few minutes.
+During the public preview deployment might take up to 48h (average time is 3-6h). This is because virtual cluster that hosts the instances needs some time to deploy. Each subsequent instance creation in the same virtual cluster takes just about a few minutes.
 
 After the last Managed Instance is deprovisioned, cluster stays a live for up to 24h. This is to avoid waiting for a new cluster to be provisioned in case that customer just wants to recreate the instance. During that period of time Resource Group and virtual network could not be deleted. This is a known issue and Managed Instance team is working on resolving it.
 

diff --git a/201-sqlmi-new-vnet-w-point-to-site-vpn/README.md b/201-sqlmi-new-vnet-w-point-to-site-vpn/README.md
@@ -61,7 +61,7 @@ You can click the "Deploy to Azure" button at the beginning of this document or
 
 ## Important
 
-Usual deployment time is 3-6h but during the public preview deployment might take up to 48h. The reason why provisioning takes some time is that the Managed Instance virtual cluster that hosts the instance is created. Each subsequent instance creation takes just about a few minutes.
+During the public preview deployment might take up to 48h (average time is 3-6h). This is because virtual cluster that hosts the instances needs some time to deploy. Each subsequent instance creation in the same virtual cluster takes just about a few minutes.
 
 After the last Managed Instance is deprovisioned, cluster stays a live for up to 24h. This is to avoid waiting for a new cluster to be provisioned in case that customer just wants to recreate the instance. During that period of time Resource Group and virtual network could not be deleted. This is a known issue and Managed Instance team is working on resolving it.