You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-sql/database/connectivity-settings.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ The connectivity settings are accessible from the **Firewalls and virtual networ
30
30
31
31
In the Azure portal, when the **Deny public network access** setting is set to **Yes**, only connections via private endpoints are allowed. When this setting is set to **No**, clients can connect using the private or public endpoint.
32
32
33
-
Customers can connect to SQL Database using public endpoints (IP-based firewall rules, VNET based firewall rules) or private endpoints (using Private Link) as outlined in the [network access overview](sql-database-networkaccess-overview.md).
33
+
Customers can connect to SQL Database using public endpoints (IP-based firewall rules, VNET based firewall rules) or private endpoints (using Private Link) as outlined in the [network access overview](network-access-controls-overview.md).
34
34
35
35
When **Deny public network access** setting is set to **Yes**, only connections via private endpoints are allowed and all connections via public endpoints are denied with an error message similar to:
36
36
@@ -85,7 +85,7 @@ At present we support TLS 1.0, 1.1 and 1.2. Setting a Minimal TLS Version ensure
85
85
86
86
For customers with applications that rely on older versions of TLS, we recommend setting the Minimal TLS Version per the requirements of your applications. For customers that rely on applications to connect using an unencrypted connection, we recommend not setting any Minimal TLS Version.
87
87
88
-
For more information, see [TLS considerations for SQL Database connectivity](sql-database-connect-query.md#tls-considerations-for-sql-database-connectivity).
88
+
For more information, see [TLS considerations for SQL Database connectivity](connect-query-content-reference-guide.md#tls-considerations-for-sql-database-connectivity).
89
89
90
90
After setting the Minimal TLS Version, login attempts from clients that are using a TLS version lower than the Minimal TLS Version of the server will fail with following error:
Copy file name to clipboardExpand all lines: articles/data-factory/how-to-use-sql-managed-instance-with-ir.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,13 +23,13 @@ You can now move your SQL Server Integration Services (SSIS) projects, packages,
23
23
-[Execute SSIS packages by Azure SQL Managed Instance Agent job](how-to-invoke-ssis-package-managed-instance-agent.md)
24
24
-[Clean up SSISDB logs by Azure SQL Managed Instance Agent job](#clean-up-ssisdb-logs)
25
25
-[Azure-SSIS IR failover with Azure SQL Database Managed Instance](configure-bcdr-azure-ssis-integration-runtime.md#azure-ssis-ir-failover-with-a-sql-database-managed-instance)
26
-
-[Migrate on-premises SSIS workloads to SSIS in ADF with Azure SQL Database managed instance as database workload destination](scenario-ssis-migration-overview.md#azure-sql-database-managed-instance-as-database-workload-destination)
26
+
-[Migrate on-premises SSIS workloads to SSIS in ADF with Azure SQL Database managed instance as database workload destination](scenario-ssis-migration-overview.md#azure-sql-managed-instance-as-database-workload-destination)
27
27
28
-
## Provision Azure-SSIS IR with SSISDB hosted by Azure SQL Database managed instance
28
+
## Provision Azure-SSIS IR with SSISDB hosted by Azure SQL Managed Instance
29
29
30
30
### Prerequisites
31
31
32
-
1.[Enable Azure Active Directory (Azure AD) on Azure SQL Database managed instance](enable-aad-authentication-azure-ssis-ir.md#configure-azure-ad-authentication-for-azure-sql-database-managed-instance), when choosing Azure Active Directory authentication.
32
+
1.[Enable Azure Active Directory (Azure AD) on Azure SQL Database managed instance](enable-aad-authentication-azure-ssis-ir.md#configure-azure-ad-authentication-for-azure-sql-managed-instance), when choosing Azure Active Directory authentication.
33
33
34
34
1. Choose how to connect SQL managed instance, over private endpoint or over public endpoint:
35
35
@@ -142,7 +142,7 @@ You can now move your SQL Server Integration Services (SSIS) projects, packages,
For more info about how to enable Azure AD authentication, see [Enable Azure AD on Azure SQL Database managed instance](enable-aad-authentication-azure-ssis-ir.md#configure-azure-ad-authentication-for-azure-sql-database-managed-instance).
145
+
For more info about how to enable Azure AD authentication, see [Enable Azure AD on Azure SQL Database managed instance](enable-aad-authentication-azure-ssis-ir.md#configure-azure-ad-authentication-for-azure-sql-managed-instance).
146
146
147
147
1. Join Azure-SSIS IR to the virtual network when applies.
Copy file name to clipboardExpand all lines: articles/data-factory/v1/data-factory-data-processing-using-batch.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ With the Batch service, you define Azure compute resources to execute your appli
34
34
If you aren't familiar with Batch, the following articles help you understand the architecture/implementation of the solution described in this article:
35
35
36
36
*[Basics of Batch](../../azure-sql/database/sql-database-paas-overview.md)
0 commit comments