fixing things

MashaMSFT · MashaMSFT · commit 8b4ae2a75b15 · 2020-05-14T14:16:44.000-07:00
diff --git a/articles/azure-sql/database/scripts/add-database-to-failover-group-powershell.md b/articles/azure-sql/database/scripts/add-database-to-failover-group-powershell.md
@@ -24,7 +24,7 @@ If you choose to install and use the PowerShell locally, this tutorial requires
 
 ## Sample scripts
 
-[!code-powershell-interactive[main](../../../../powershell_scripts/sql-database/failover-groups/add-single-db-to-failover-group-az-ps.ps1 "Add single database to a failover group")]
+[!code-powershell-interactive[main](../../../powershell_scripts/sql-database/failover-groups/add-single-db-to-failover-group-az-ps.ps1 "Add single database to a failover group")]
 
 ## Clean up deployment
 
diff --git a/articles/azure-sql/managed-instance/connect-vm-instance-configure.md b/articles/azure-sql/managed-instance/connect-vm-instance-configure.md
@@ -78,7 +78,7 @@ The easiest way to create a client virtual machine with all necessary tools is t
    | **Location** | The location for the resource group | This value is populated based on the resource group selected. |
    | **Virtual machine name**  | Any valid name | For valid names, see [Naming rules and restrictions](/azure/architecture/best-practices/resource-naming).|
    |**Admin Username**|Any valid username|For valid names, see [Naming rules and restrictions](/azure/architecture/best-practices/resource-naming). Don't use "serveradmin" as that is a reserved server-level role.<br>You use this username any time you [connect to the VM](#connect-to-virtual-machine).|
-   |**Password**|Any valid password|The password must be at least 12 characters long and meet the [defined complexity requirements](../virtual-machines/windows/faq.md#what-are-the-password-requirements-when-creating-a-vm).<br>You use this password any time you [connect to the VM](#connect-to-virtual-machine).|
+   |**Password**|Any valid password|The password must be at least 12 characters long and meet the [defined complexity requirements](../../virtual-machines/windows/faq.md#what-are-the-password-requirements-when-creating-a-vm).<br>You use this password any time you [connect to the VM](#connect-to-virtual-machine).|
    | **Virtual Machine Size** | Any valid size | The default in this template of **Standard_B2s** is sufficient for this quickstart. |
    | **Location**|[resourceGroup().location].| Don't change this value. |
    | **Virtual Network Name**|The virtual network in which you created the SQL Managed Instance.|
diff --git a/articles/azure-sql/managed-instance/how-to-content-reference-guide.md b/articles/azure-sql/managed-instance/how-to-content-reference-guide.md
@@ -78,7 +78,7 @@ In this article you can find a content reference to various guides, scripts, and
 
 ## Develop applications
 
-- [Connectivity](sql-database-libraries.md)
+- [Connectivity](../database/connect-query-content-reference-guide.md#libraries)
 - [Use Spark Connector](../../cosmos-db/spark-connector.md)
 - [Authenticate app](../database/application-authentication-get-client-id-keys.md)
 - [Use batching for better performance](../../sql-database/sql-database-use-batching-to-improve-performance.md)
diff --git a/articles/azure-sql/managed-instance/media/connect-application-instance/application-deployment-topologies.png b/articles/azure-sql/managed-instance/media/connect-application-instance/application-deployment-topologies.png
diff --git a/articles/azure-sql/managed-instance/media/connect-vm-instance-configure/ssms-connect.png b/articles/azure-sql/managed-instance/media/connect-vm-instance-configure/ssms-connect.png
diff --git a/articles/azure-sql/managed-instance/point-to-site-p2s-configure.md b/articles/azure-sql/managed-instance/point-to-site-p2s-configure.md
@@ -15,7 +15,7 @@ ms.date: 03/13/2019
 ---
 # Quickstart: Configure a point-to-site connection to Azure SQL Managed Instance from on-premises
 
-This quickstart demonstrates how to connect to Azure SQL Managed Instance using [SQL Server Management Studio](https://docs.microsoft.com/sql/ssms/sql-server-management-studio-ssms) (SSMS) from an on-premises client computer over a point-to-site connection. For information about point-to-site connections, see [About Point-to-Site VPN](../vpn-gateway/point-to-site-about.md)
+This quickstart demonstrates how to connect to Azure SQL Managed Instance using [SQL Server Management Studio](https://docs.microsoft.com/sql/ssms/sql-server-management-studio-ssms) (SSMS) from an on-premises client computer over a point-to-site connection. For information about point-to-site connections, see [About Point-to-Site VPN](../../vpn-gateway/point-to-site-about.md)
 
 ## Prerequisites
 
diff --git a/articles/azure-sql/managed-instance/scripts/create-configure-managed-instance-powershell.md b/articles/azure-sql/managed-instance/scripts/create-configure-managed-instance-powershell.md
@@ -26,7 +26,7 @@ If you choose to install and use the PowerShell locally, this tutorial requires
 
 ## Sample script
 
-[!code-powershell-interactive[main](../../../powershell_scripts/sql-database/managed-instance/create-and-configure-managed-instance.ps1 "Create managed instance")]
+[!code-powershell-interactive[main](../../../../powershell_scripts/sql-database/managed-instance/create-and-configure-managed-instance.ps1 "Create managed instance")]
 
 ## Clean up deployment
 
diff --git a/articles/azure-sql/managed-instance/scripts/transparent-data-encryption-byok-powershell.md b/articles/azure-sql/managed-instance/scripts/transparent-data-encryption-byok-powershell.md
@@ -33,7 +33,7 @@ If you are running PowerShell locally, you also need to run `Connect-AzAccount`
 
 ## Sample scripts
 
-[!code-powershell-interactive[main](../../../powershell_scripts/sql-database/transparent-data-encryption/setup-tde-byok-sqlmi.ps1 "Set up BYOK TDE for SQL Managed Instance")]
+[!code-powershell-interactive[main](../../../../powershell_scripts/sql-database/transparent-data-encryption/setup-tde-byok-sqlmi.ps1 "Set up BYOK TDE for SQL Managed Instance")]
 
 ## Next steps
 
diff --git a/articles/azure-sql/managed-instance/sql-managed-instance-paas-overview.md b/articles/azure-sql/managed-instance/sql-managed-instance-paas-overview.md
@@ -35,7 +35,7 @@ SQL Managed Instance combines the best features that are available both in Azure
 
 | **PaaS benefits** | **Business continuity** |
 | --- | --- |
-|No hardware purchasing and management <br>No management overhead for managing underlying infrastructure <br>Quick provisioning and service scaling <br>Automated patching and version upgrade <br>Integration with other PaaS data services |99.99% uptime SLA  <br>Built in [high-availability](../database/high-availability-sla.md) <br>Data protected with [automated backups](../database/automated-backups-overview.md) <br>Customer configurable backup retention period <br>User-initiated [backups](https://docs.microsoft.com/sql/t-sql/statements/backup-transact-sql?view=azuresqldb-mi-current) <br>[Point in time database restore](../azure-sql/database/recovery-using-backups.md#point-in-time-restore) capability |
+|No hardware purchasing and management <br>No management overhead for managing underlying infrastructure <br>Quick provisioning and service scaling <br>Automated patching and version upgrade <br>Integration with other PaaS data services |99.99% uptime SLA  <br>Built in [high-availability](../database/high-availability-sla.md) <br>Data protected with [automated backups](../database/automated-backups-overview.md) <br>Customer configurable backup retention period <br>User-initiated [backups](https://docs.microsoft.com/sql/t-sql/statements/backup-transact-sql?view=azuresqldb-mi-current) <br>[Point in time database restore](../database/recovery-using-backups.md#point-in-time-restore) capability |
 |**Security and compliance** | **Management**|
 |Isolated environment ([VNet integration](connectivity-architecture-overview.md), single tenant service, dedicated compute and storage) <br>[Transparent data encryption (TDE)](https://docs.microsoft.com/sql/relational-databases/security/encryption/transparent-data-encryption-azure-sql)<br>[Azure AD authentication](../database/aad-authentication-overview.md), single sign-on support <br> <a href="/sql/t-sql/statements/create-login-transact-sql?view=azuresqldb-mi-current">Azure AD server principals (logins)</a>  <br>Adheres to compliance standards same as Azure SQL Database <br>[SQL auditing](auditing-configure.md) <br>[Advanced Threat Protection](../../sql-database/sql-database-managed-instance-threat-detection.md) |Azure Resource Manager API for automating service provisioning and scaling <br>Azure portal functionality for manual service provisioning and scaling <br>Data Migration Service
 
@@ -308,7 +308,7 @@ Some key differences:
 - Specifying full physical paths is unsupported so all corresponding scenarios have to be supported differently: RESTORE DB does not support WITH MOVE, CREATE DB doesn't allow physical paths, BULK INSERT works with Azure Blobs only, etc.
 - SQL Managed Instance supports [Azure AD authentication](../database/aad-authentication-overview.md) as cloud alternative to Windows authentication.
 - SQL Managed Instance automatically manages XTP filegroup and files for databases containing In-Memory OLTP objects
-- SQL Managed Instance supports SQL Server Integration Services (SSIS) and can host SSIS catalog (SSISDB) that stores SSIS packages, but they are executed on a managed Azure-SSIS Integration Runtime (IR) in Azure Data Factory (ADF), see [Create Azure-SSIS IR in ADF](https://docs.microsoft.com/azure/data-factory/create-azure-ssis-integration-runtime). To compare the SSIS features, see [Compare SQL Database to SQL Managed Instance](../data-factory/create-azure-ssis-integration-runtime.md#comparison-of-a-azure-sql-database-elastic-pool-and-sql-managed-instance).
+- SQL Managed Instance supports SQL Server Integration Services (SSIS) and can host SSIS catalog (SSISDB) that stores SSIS packages, but they are executed on a managed Azure-SSIS Integration Runtime (IR) in Azure Data Factory (ADF), see [Create Azure-SSIS IR in ADF](https://docs.microsoft.com/azure/data-factory/create-azure-ssis-integration-runtime). To compare the SSIS features, see [Compare SQL Database to SQL Managed Instance](../../data-factory/create-azure-ssis-integration-runtime.md#comparison-of-a-azure-sql-database-elastic-pool-and-sql-managed-instance).
 
 ### Administration features
 
diff --git a/articles/azure-sql/managed-instance/tutorial-add-instance-failover-group.md b/articles/azure-sql/managed-instance/tutorial-add-instance-failover-group.md
@@ -1102,7 +1102,7 @@ This portion of the tutorial uses the following PowerShell cmdlet:
 ## Full script
 
 # [PowerShell](#tab/azure-powershell)
-[!code-powershell-interactive[main](../../powershell_scripts/sql-database/failover-groups/add-managed-instance-to-failover-group-az-ps.ps1 "Add SQL Managed Instance to a failover group")]
+[!code-powershell-interactive[main](../../../../powershell_scripts/sql-database/failover-groups/add-managed-instance-to-failover-group-az-ps.ps1 "Add SQL Managed Instance to a failover group")]
 
 This script uses the following commands. Each command in the table links to command specific documentation.
 
diff --git a/articles/azure-sql/managed-instance/tutorial-configure-aad-security.md b/articles/azure-sql/managed-instance/tutorial-configure-aad-security.md
@@ -32,7 +32,7 @@ In this tutorial, you learn how to:
 > - Use cross-database queries with Azure AD users
 > - Learn about security features, such as threat protection, auditing, data masking, and encryption
 
-To learn more, see the [Azure SQL Managed Instance overview](sql-database-managed-instance-index.yml) and [capabilities](sql-managed-instance-paas-overview.md) articles.
+To learn more, see the [Azure SQL Managed Instance overview](sql-managed-instance-paas-overview). 
 
 ## Prerequisites
 
diff --git a/articles/azure-sql/managed-instance/tutorial-configure-replication-two-instances-and-sql-server.md b/articles/azure-sql/managed-instance/tutorial-configure-replication-two-instances-and-sql-server.md
@@ -25,7 +25,7 @@ In this tutorial, you learn how to:
 
 This tutorial is intended for an experienced audience and assumes that the user is familiar with deploying and connecting to both managed instances, and SQL Server VMs within Azure. As such, certain steps in this tutorial are glossed over.
 
-To learn more, see the [Azure SQL Managed Instance overview](sql-database-managed-instance-index.yml), [capabilities](sql-managed-instance-paas-overview.md), and [SQL Transactional Replication](../database/transactional-replication-overview.md) articles.
+To learn more, see the [Azure SQL Managed Instance overview](sql-managed-instance-paas-overview.md), and [SQL Transactional Replication](../database/transactional-replication-overview.md) articles.
 
 To configure replication between a managed instance publisher and a managed instance subscriber, see [Configure transactional replication between two managed instances](tutorial-replication-between-two-instances-configure.md).
 
@@ -171,7 +171,7 @@ A private DNS zone allows DNS routing between the managed instances and the SQL
 
 ## 6 - Create Azure Storage Account
 
-[Create an Azure Storage Account](https://docs.microsoft.com/azure/storage/common/storage-create-storage-account#create-a-storage-account) for the working directory, and then create a [file share](../storage/files/storage-how-to-create-file-share.md) within the storage account.
+[Create an Azure Storage Account](https://docs.microsoft.com/azure/storage/common/storage-create-storage-account#create-a-storage-account) for the working directory, and then create a [file share](../../storage/files/storage-how-to-create-file-share.md) within the storage account.
 
 Copy the file share path in the format of:
 `\\storage-account-name.file.core.windows.net\file-share-name`
diff --git a/articles/azure-sql/managed-instance/tutorial-replication-between-two-instances-configure.md b/articles/azure-sql/managed-instance/tutorial-replication-between-two-instances-configure.md
@@ -45,7 +45,7 @@ Use the [Azure portal](https://portal.azure.com) to create a resource group with
 
 ## 2 - Create SQL Managed Instances
 
-Use the [Azure portal](https://portal.azure.com) to create two [SQL Managed Instances](sql-database-managed-instance-create-tutorial-portal.md) on the same virtual network and subnet. For example, name the two SQL Managed Instances:
+Use the [Azure portal](https://portal.azure.com) to create two [SQL Managed Instances](../../sql-database/sql-database-managed-instance-get-started.md) on the same virtual network and subnet. For example, name the two SQL Managed Instances:
 
 - `sql-mi-pub` (along with some characters for randomization)
 - `sql-mi-sub` (along with some characters for randomization)
diff --git a/articles/sql-database/sql-database-managed-instance-transact-sql-information.md b/articles/sql-database/sql-database-managed-instance-transact-sql-information.md
@@ -20,7 +20,7 @@ This article summarizes and explains the differences in syntax and behavior betw
 
 SQL Managed Instance provides high compatibility with the on-premises SQL Server Database Engine, and most features are supported in a SQL Managed Instance.
 
-![Migration](./media/sql-database-managed-instance/migration.png)
+![Migration](../azure-sql/managed-instance/media/sql-managed-instance-paas-overview/migration.png)
 
 There are some PaaS limitations that are introduced in SQL Managed Instance and some behavior changes compared to SQL Server. The differences are divided into the following categories: <a name="Differences"></a>
 
