added note to other fci docs

Author: MashaMSFT

articles/azure-sql/virtual-machines/windows/failover-cluster-instance-premium-file-share-manually-configure.md

@@ -117,6 +117,15 @@ After you've configured the failover cluster, you can create the SQL Server FCI.
 
 1. In **Failover Cluster Manager**, make sure that all the core cluster resources are on the first virtual machine. If necessary, move all resources to this virtual machine.
 
+1. If the version of the operating system is Windows Server 2019 and the Windows Cluster was created using the default [**Distributed Network Name (DNN)**](https://blogs.windows.com/windows-insider/2018/08/14/announcing-windows-server-2019-insider-preview-build-17733/), then the FCI installation for SQL Server 2017 and below will fail with the error `The given key was not present in the dictionary`. 
+
+    During installation, SQL Server setup queries for the existing Virtual Network Name (VNN) and doesn't recognize the Windows Cluster DNN. The issue has been fixed in SQL Server 2019 setup. For SQL Server 2017 and below, follow these steps to avoid the installation error:
+     
+    - In Failover Cluster Manager, connect to the cluster, right-click  **Roles** and select **Create Empty Role**.
+    - Right-click the newly created empty role, select **Add Resource** and select **Client Access Point**.
+    - Enter any name and complete the wizard to create the **Client Access Point**. 
+    - After the SQL Server FCI installation completes, the role containing the temporary **Client Access Point** can be deleted. 
+
 1. Locate the installation media. If the virtual machine uses one of the Azure Marketplace images, the media is located at `C:\SQLServer_<version number>_Full`. 
 
 1. Select **Setup**.

articles/azure-sql/virtual-machines/windows/failover-cluster-instance-storage-spaces-direct-manually-configure.md

@@ -144,6 +144,15 @@ After you've configured the failover cluster and all cluster components, includi
 
 1. In **Failover Cluster Manager**, make sure all core cluster resources are on the first virtual machine. If necessary, move all resources to that virtual machine.
 
+1. If the version of the operating system is Windows Server 2019 and the Windows Cluster was created using the default [**Distributed Network Name (DNN)**](https://blogs.windows.com/windows-insider/2018/08/14/announcing-windows-server-2019-insider-preview-build-17733/), then the FCI installation for SQL Server 2017 and below will fail with the error `The given key was not present in the dictionary`. 
+
+    During installation, SQL Server setup queries for the existing Virtual Network Name (VNN) and doesn't recognize the Windows Cluster DNN. The issue has been fixed in SQL Server 2019 setup. For SQL Server 2017 and below, follow these steps to avoid the installation error:
+     
+    - In Failover Cluster Manager, connect to the cluster, right-click  **Roles** and select **Create Empty Role**.
+    - Right-click the newly created empty role, select **Add Resource** and select **Client Access Point**.
+    - Enter any name and complete the wizard to create the **Client Access Point**. 
+    - After the SQL Server FCI installation completes, the role containing the temporary **Client Access Point** can be deleted. 
+
 1. Locate the installation media. If the virtual machine uses one of the Azure Marketplace images, the media is located at `C:\SQLServer_<version number>_Full`. Select **Setup**.
 
 1. In **SQL Server Installation Center**, select **Installation**.