moved more files

Author: MashaMSFT

azure-sql/database/aad-authentication-configure.md

@@ -15,7 +15,7 @@ ms.date: 03/27/2020
 ---
 # Configure and manage Azure Active Directory authentication with SQL
 
-This article shows you how to create and populate Azure AD, and then use Azure AD with [Azure SQL Database](technical-overview.md), [Azure SQL Managed Instance](../../sql-database/sql-database-managed-instance.md), and [Azure Synapse Analytics (formerly Azure SQL Data Warehouse)](../../synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-what-is.md). For an overview, see [Azure Active Directory Authentication](aad-authentication-overview.md).
+This article shows you how to create and populate Azure AD, and then use Azure AD with [Azure SQL Database](technical-overview.md), [Azure SQL Managed Instance](../managed-instance/sql-managed-instance-paas-overview.md), and [Azure Synapse Analytics (formerly Azure SQL Data Warehouse)](../../synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-what-is.md). For an overview, see [Azure Active Directory Authentication](aad-authentication-overview.md).
 
 ## Azure AD authentication methods
 
@@ -107,7 +107,7 @@ To grant your SQL Managed Instance Azure AD read permission using the Azure port
 
     The process of changing the administrator may take several minutes. Then the new administrator appears in the Active Directory admin box.
 
-After provisioning an Azure AD admin for your SQL Managed Instance, you can begin to create Azure AD server principals (logins) with the <a href="/sql/t-sql/statements/create-login-transact-sql?view=azuresqldb-mi-current">CREATE LOGIN</a> syntax. For more information, see [SQL Managed Instance overview](../../sql-database/sql-database-managed-instance.md#azure-active-directory-integration).
+After provisioning an Azure AD admin for your SQL Managed Instance, you can begin to create Azure AD server principals (logins) with the <a href="/sql/t-sql/statements/create-login-transact-sql?view=azuresqldb-mi-current">CREATE LOGIN</a> syntax. For more information, see [SQL Managed Instance overview](../managed-instance/sql-managed-instance-paas-overview.md#azure-active-directory-integration).
 
 > [!TIP]
 > To later remove an Admin, at the top of the Active Directory admin page, select **Remove admin**, and then select **Save**.
@@ -351,7 +351,7 @@ You can meet these requirements by:
 
 ## Create contained users mapped to Azure AD identities
 
-Since SQL Managed Instance supports Azure AD server principals (logins), using contained database users is not required. Azure AD server principals (logins) enable you to create logins from Azure AD users, groups, or applications. This means that you can authenticate with your SQL Managed Instance using the Azure AD server login rather than a contained database user. For more information, see [SQL Managed Instance Overview](../../sql-database/sql-database-managed-instance.md#azure-active-directory-integration). For syntax on creating Azure AD server principals (logins), see <a href="/sql/t-sql/statements/create-login-transact-sql?view=azuresqldb-mi-current">CREATE LOGIN</a>.
+Since SQL Managed Instance supports Azure AD server principals (logins), using contained database users is not required. Azure AD server principals (logins) enable you to create logins from Azure AD users, groups, or applications. This means that you can authenticate with your SQL Managed Instance using the Azure AD server login rather than a contained database user. For more information, see [SQL Managed Instance Overview](../managed-instance/sql-managed-instance-paas-overview.md#azure-active-directory-integration). For syntax on creating Azure AD server principals (logins), see <a href="/sql/t-sql/statements/create-login-transact-sql?view=azuresqldb-mi-current">CREATE LOGIN</a>.
 
 However, using Azure Active Directory authentication with SQL Database and Azure Synapse requires using contained database users based on an Azure AD identity. A contained database user does not have a login in the master database, and maps to an identity in Azure AD that is associated with the database. The Azure AD identity can be either an individual user account or a group. For more information about contained database users, see [Contained Database Users- Making Your Database Portable](https://msdn.microsoft.com/library/ff929188.aspx).
 

azure-sql/database/aad-authentication-overview.md

@@ -14,7 +14,7 @@ ms.date: 04/23/2020
 ---
 # Use Azure Active Directory Authentication for authentication with Azure SQL
 
-Azure Active Directory authentication is a mechanism of connecting to [Azure SQL Database](technical-overview.md), [Azure SQL Managed Instance](../../sql-database/sql-database-managed-instance.md), and [Azure Synapse Analytics (formerly Azure SQL Data Warehouse)](../../synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-what-is.md) by using identities in Azure Active Directory (Azure AD).
+Azure Active Directory authentication is a mechanism of connecting to [Azure SQL Database](technical-overview.md), [Azure SQL Managed Instance](../managed-instance/sql-managed-instance-paas-overview.md), and [Azure Synapse Analytics (formerly Azure SQL Data Warehouse)](../../synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-what-is.md) by using identities in Azure Active Directory (Azure AD).
 
 > [!NOTE]
 > This article applies to Azure SQL Database, SQL Managed Instance, and Azure Synapse. For simplicity, Azure SQL is used when referring to all three.
@@ -110,8 +110,8 @@ To create a contained database user in Azure SQL Database, SQL Managed Instance,
 
 ### SQL Managed Instance
 
-- Azure AD server principals (logins) and users are supported for [SQL Managed Instance](../../sql-database/sql-database-managed-instance.md).
-- Setting Azure AD server principals (logins) mapped to an Azure AD group as database owner is not supported in [SQL Managed Instances](../../sql-database/sql-database-managed-instance.md).
+- Azure AD server principals (logins) and users are supported for [SQL Managed Instance](../managed-instance/sql-managed-instance-paas-overview.md).
+- Setting Azure AD server principals (logins) mapped to an Azure AD group as database owner is not supported in [SQL Managed Instances](../managed-instance/sql-managed-instance-paas-overview.md).
   - An extension of this is that when a group is added as part of the `dbcreator` server role, users from this group can connect to the SQL Managed Instance and create new databases, but will not be able to access the database. This is because the new database owner is SA, and not the Azure AD user. This issue does not manifest if the individual user is added to the `dbcreator` server role.
 - SQL Agent management and jobs execution are supported for Azure AD server principals (logins).
 - Database backup and restore operations can be executed by Azure AD server principals (logins).
@@ -154,7 +154,7 @@ The following authentication methods are supported for Azure AD server principal
 ## Next steps
 
 - To learn how to create and populate Azure AD, and then configure Azure AD with Azure SQL Database, SQL Managed Instance or Azure Synapse, see [Configure and manage Azure Active Directory authentication with SQL Database, SQL Managed Instance, or Azure Synapse](aad-authentication-configure.md).
-- For a tutorial of using Azure AD server principals (logins) with SQL Managed Instances, see [Azure AD server principals (logins) with SQL Managed Instances](../../sql-database/sql-database-managed-instance-aad-security-tutorial.md)
+- For a tutorial of using Azure AD server principals (logins) with SQL Managed Instances, see [Azure AD server principals (logins) with SQL Managed Instances](../managed-instance/tutorial-configure-aad-security.md)
 - For an overview of logins, users, database roles, and permissions in SQL Database, see [Logins, users, database roles, and permissions](logins-create-manage.md).
 - For more information about database principals, see [Principals](https://msdn.microsoft.com/library/ms181127.aspx).
 - For more information about database roles, see [Database roles](https://msdn.microsoft.com/library/ms189121.aspx).

azure-sql/database/auto-failover-group-configure.md

@@ -678,6 +678,6 @@ For detailed steps configuring a failover group, see the following tutorials:
 
 - [Add a single database to a failover group](tutorial-add-single-database-failover-group.md)
 - [Add an elastic pool to a failover group](tutorial-add-elastic-pool-failover-group.md)
-- [Add a managed instance to a failover group](../../sql-database/sql-database-managed-instance-failover-group-tutorial.md)
+- [Add a managed instance to a failover group](../managed-instance/tutorial-add-instance-failover-group.md)
 
 For an overview of Azure SQL Database high availability options, see [geo-replication](active-geo-replication-overview.md) and [auto-failover groups](auto-failover-group-overview.md).

azure-sql/database/auto-failover-group-overview.md

@@ -214,7 +214,7 @@ The following diagram illustrates a typical configuration of a geo-redundant clo
 ![auto failover](./media/auto-failover-group-overview/auto-failover-group-mi.png)
 
 > [!NOTE]
-> See [Add managed instance to a failover group](../../sql-database/sql-database-managed-instance-failover-group-tutorial.md) for a detailed step-by-step tutorial adding a SQL Managed Instance to use failover group.
+> See [Add managed instance to a failover group](../managed-instance/tutorial-add-instance-failover-group.md) for a detailed step-by-step tutorial adding a SQL Managed Instance to use failover group.
 
 If your application uses SQL Managed Instance as the data tier, follow these general guidelines when designing for business continuity:
 
@@ -225,7 +225,7 @@ To ensure non-interrupted connectivity to the primary SQL Managed Instance after
 > [!IMPORTANT]
 > First SQL Managed Instance created in the subnet determines DNS zone for all subsequent instances in the same subnet. This means that two instances from the same subnet cannot belong to different DNS zones.
 
-For more information about creating the secondary SQL Managed Instance in the same DNS zone as the primary instance, see [Create a secondary managed instance](../../sql-database/sql-database-managed-instance-failover-group-tutorial.md#3---create-a-secondary-sql-managed-instance).
+For more information about creating the secondary SQL Managed Instance in the same DNS zone as the primary instance, see [Create a secondary managed instance](../managed-instance/tutorial-add-instance-failover-group.md#3---create-a-secondary-sql-managed-instance).
 
 ### Enabling replication traffic between two instances
 
@@ -278,7 +278,7 @@ Let's assume that instance A is the primary instance, instance B is the existing
 
 1. Create instance C with same size as A and in the same DNS zone.
 2. Delete the failover group between instances A and B. At this point the logins will be failing because the SQL aliases for the failover group listeners have been deleted and the gateway will not recognize the failover group name. The secondary databases will be disconnected from the primaries and will become read-write databases.
-3. Create a failover group with the same name between instance A and C. Follow the instructions in [failover group with SQL Managed Instance tutorial](../../sql-database/sql-database-managed-instance-failover-group-tutorial.md). This is a size-of-data operation and will complete when all databases from instance A are seeded and synchronized.
+3. Create a failover group with the same name between instance A and C. Follow the instructions in [failover group with SQL Managed Instance tutorial](../managed-instance/tutorial-add-instance-failover-group.md). This is a size-of-data operation and will complete when all databases from instance A are seeded and synchronized.
 4. Delete instance B if not needed to avoid unnecessary charges.
 
 > [!NOTE]
@@ -291,7 +291,7 @@ Let's assume instance A is the primary instance, instance B is the existing seco
 1. Create instance C with same size as B and in the same DNS zone.
 2. Connect to instance B and manually failover to switch the primary instance to B. Instance A will become the new secondary instance automatically.
 3. Delete the failover group between instances A and B. At this point the logins will be failing because the SQL aliases for the failover group listeners have been deleted and the gateway will not recognize the failover group name. The secondary databases will be disconnected from the primaries and will become read-write databases.
-4. Create a failover group with the same name between instance A and C. Follow the instructions in the [failover group with managed instance tutorial](../../sql-database/sql-database-managed-instance-failover-group-tutorial.md). This is a size-of-data operation and will complete when all databases from instance A are seeded and synchronized.
+4. Create a failover group with the same name between instance A and C. Follow the instructions in the [failover group with managed instance tutorial](../managed-instance/tutorial-add-instance-failover-group.md). This is a size-of-data operation and will complete when all databases from instance A are seeded and synchronized.
 5. Delete instance A if not needed to avoid unnecessary charges.
 
 > [!CAUTION]
@@ -351,7 +351,7 @@ When you set up a failover group between primary and secondary SQL Managed Insta
 - The secondary SQL Managed Instance is configured with the correct DNS zone ID. DNS zone is a property of a SQL Managed Instance and underlying virtual cluster, and its ID is included in the host name address. The zone ID is generated as a random string when the first SQL Managed Instance is created in each VNet and the same ID is assigned to all other instances in the same subnet. Once assigned, the DNS zone cannot be modified. SQL Managed Instances included in the same failover group must share the DNS zone. You accomplish this by passing the primary instance's zone ID as the value of DnsZonePartner parameter when creating the secondary instance.
 
    > [!NOTE]
-   > For a detailed tutorial on configuring failover groups with SQL Managed Instance, see [add a SQL Managed Instance to a failover group](../../sql-database/sql-database-managed-instance-failover-group-tutorial.md).
+   > For a detailed tutorial on configuring failover groups with SQL Managed Instance, see [add a SQL Managed Instance to a failover group](../managed-instance/tutorial-add-instance-failover-group.md).
 
 ## Upgrading or downgrading a primary database
 
@@ -464,7 +464,7 @@ As discussed previously, auto-failover groups and active geo-replication can als
 - For detailed tutorials, see
   - [Add SQL Database to a failover group](tutorial-add-single-database-failover-group.md)
   - [Add an elastic pool to a failover group](tutorial-add-elastic-pool-failover-group.md)
-  - [Add a SQL Managed Instance to a failover group](../../sql-database/sql-database-managed-instance-failover-group-tutorial.md)
+  - [Add a SQL Managed Instance to a failover group](../managed-instance/tutorial-add-instance-failover-group.md)
 - For sample scripts, see:
   - [Use PowerShell to configure active geo-replication for Azure SQL Database](scripts/setup-geodr-and-failover-database-powershell.md)
   - [Use PowerShell to configure active geo-replication for a pooled database in Azure SQL Database](scripts/setup-geodr-and-failover-elastic-pool-powershell.md)

azure-sql/database/az-cli-script-samples-content-guide.md

@@ -68,6 +68,6 @@ The following table includes links to Azure CLI script examples for Azure SQL Ma
 
 For additional SQL Managed Instance examples, see the [create](https://blogs.msdn.microsoft.com/sqlserverstorageengine/20../../create-azure-sql-managed-instance-using-azure-cli/), [update](https://blogs.msdn.microsoft.com/sqlserverstorageengine/20../../modify-azure-sql-database-managed-instance-using-azure-cli/), [move a database](https://blogs.msdn.microsoft.com/sqlserverstorageengine/20../../cross-instance-point-in-time-restore-in-azure-sql-database-managed-instance/), [working with](https://medium.com/azure-sqldb-managed-instance/working-with-sql-managed-instance-using-azure-cli-611795fe0b44) scripts.
 
-Learn more about the [SQL Managed Instance Azure CLI API](../../sql-database/sql-database-managed-instance-create-manage.md#azure-cli-create-and-manage-managed-instances).
+Learn more about the [SQL Managed Instance Azure CLI API](../managed-instance/api-references-create-manage-instance.md#azure-cli-create-and-manage-managed-instances).
 
 ---

azure-sql/database/conditional-access-confugre.md

@@ -14,7 +14,7 @@ tag: azure-synpase
 ---
 # Conditional Access (MFA) with Azure SQL Database and Azure Synapse Analytics
 
-[Azure SQL Database](technical-overview.md), [Azure SQL Managed Instance](../../sql-database/sql-database-managed-instance.md), and [Azure Synapse Analytics](../../synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-what-is.md) support Microsoft Conditional Access.
+[Azure SQL Database](technical-overview.md), [Azure SQL Managed Instance](../managed-instance/sql-managed-instance-paas-overview.md), and [Azure Synapse Analytics](../../synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-what-is.md) support Microsoft Conditional Access.
 
 The following steps show how to configure Azure SQL Database, SQL Managed Instance, or Azure Synapse to enforce a Conditional Access (CA) policy.  
 

azure-sql/database/connect-query-dotnet-core.md

@@ -29,9 +29,9 @@ For this tutorial, you need:
   |:--- |:--- |:---|
   | Create| [Portal](quickstart-create-single-database.md) | [Portal](../../sql-database/sql-database-managed-instance-get-started.md) |
   || [CLI](scripts/create-and-configure-database-cli.md) | [CLI](https://medium.com/azure-sqldb-managed-instance/working-with-sql-managed-instance-using-azure-cli-611795fe0b44) |
-  || [PowerShell](scripts/create-and-configure-database-powershell.md) | [PowerShell](../../sql-database/scripts/sql-database-create-configure-managed-instance-powershell.md) |
-  | Configure | [Server-level IP firewall rule](quickstart-firewall-create-server-level-portal.md)| [Connectivity from a VM](../../sql-database/sql-database-managed-instance-configure-vm.md)|
-  |||[Connectivity from on-site](../../sql-database/sql-database-managed-instance-configure-p2s.md)
+  || [PowerShell](scripts/create-and-configure-database-powershell.md) | [PowerShell](../managed-instance/scripts/create-configure-managed-instance-powershell.md) |
+  | Configure | [Server-level IP firewall rule](quickstart-firewall-create-server-level-portal.md)| [Connectivity from a VM](../managed-instance/connect-vm-instance-configure.md)|
+  |||[Connectivity from on-site](../managed-instance/point-to-site-p2s-configure.md)
   |Load data|Adventure Works loaded per quickstart|[Restore Wide World Importers](../../sql-database/sql-database-managed-instance-get-started-restore.md)
   |||Restore or import Adventure Works from [BACPAC](database-import.md) file from [GitHub](https://github.com/Microsoft/sql-server-samples/tree/master/samples/databases/adventure-works)|
   |||