Skip to content

Commit b3188d2

Browse files
committed
Merge branch 'main' into release-arc-security
2 parents c6aaaaa + 8285147 commit b3188d2

10 files changed

Lines changed: 267 additions & 250 deletions

azure-sql/managed-instance/subnet-service-aided-configuration-enable.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Enable service-aided subnet configuration
2+
title: Service-aided subnet configuration
33
description: Learn how you can enable the service-aided subnet configuration for Azure SQL Managed Instance with subnet delegation.
44
author: zoran-rilak-msft
55
ms.author: zoranrilak
@@ -14,9 +14,7 @@ ms.custom:
1414
# Enable service-aided subnet configuration for Azure SQL Managed Instance
1515
[!INCLUDE [appliesto-sqlmi](../includes/appliesto-sqlmi.md)]
1616

17-
This article provides an overview of the service-aided subnet configuration and how to enable it with subnet delegation for Azure SQL Managed Instance.
18-
19-
Service-aided subnet configuration automates network configuration management for subnets that host managed instances, leaving the user fully in control of access to the data (TDS traffic flows) while the managed instance is responsible for ensuring uninterrupted flow of management traffic.
17+
This article provides an overview of service-aided subnet configuration and how it interacts with the subnets delegated to Azure SQL Managed Instance. Service-aided subnet configuration automates network configuration management for subnets that host managed instances, leaving the user fully in control of access to the data (TDS traffic flows) while the managed instance is responsible for ensuring uninterrupted flow of management traffic.
2018

2119
## Overview
2220

docs/database-engine/configure-windows/manage-certificates.md

Lines changed: 22 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Certificate management (SQL Server Configuration Manager)
33
description: Learn how to install certificates in various SQL Server configurations. Examples include single instances, failover clusters, and Always On availability groups.
44
author: rwestMSFT
55
ms.author: randolphwest
6-
ms.date: 06/20/2024
6+
ms.date: 08/09/2024
77
ms.service: sql
88
ms.subservice: configuration
99
ms.topic: conceptual
@@ -26,13 +26,17 @@ This article describes how to deploy and manage certificates across your [!INCLU
2626

2727
SSL/TLS certificates are widely used to secure access to [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)]. With earlier versions of [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)], organizations with large [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] estates had to spend considerable effort to maintain their [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] certificate infrastructure, often through developing scripts and running manual commands.
2828

29+
::: moniker range=">=sql-server-ver15"
30+
2931
With [!INCLUDE [sssql19-md](../../includes/sssql19-md.md)] and later versions, certificate management is integrated into the [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] Configuration Manager, which simplifies the following common tasks:
3032

3133
- View and validate certificates installed in a [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] instance.
3234
- Identify which certificates might be close to expiring.
33-
- Deploy certificates across AG machines from the node holding the primary replica.
35+
- Deploy certificates across AG machines from the node hosting the primary replica.
3436
- Deploy certificates across FCI machines from the active node.
3537

38+
::: moniker-end
39+
3640
You can use certificate management in [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] Configuration Manager with earlier versions of [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)], starting with [!INCLUDE [sql2008-md](../../includes/sql2008-md.md)].
3741

3842
::: moniker range=">=sql-server-ver15"
@@ -47,12 +51,14 @@ You can use certificate management in [!INCLUDE [ssnoversion-md](../../includes/
4751
> [!NOTE]
4852
> These instructions apply to [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] Configuration Manager for [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)] and earlier versions. For [!INCLUDE [sssql19-md](../../includes/sssql19-md.md)] and later versions, see [Certificate management (SQL Server 2019 Configuration Manager)](manage-certificates.md?view=sql-server-ver15&preserve-view=true).
4953
50-
::: moniker-end
54+
## <a id="provision-single-server-cert"></a> Install a certificate
5155

52-
## <a id="provision-single-server-cert"></a> Install a certificate for a single SQL Server instance
56+
::: moniker-end
5357

5458
::: moniker range=">=sql-server-ver15"
5559

60+
## <a id="provision-single-server-cert"></a> Install a certificate for a single SQL Server instance
61+
5662
1. In [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] Configuration Manager, in the console pane, expand **SQL Server Network Configuration**.
5763

5864
1. Right-click **Protocols for** *&lt;instance Name&gt;*, and then select **Properties**.
@@ -73,8 +79,17 @@ You can use certificate management in [!INCLUDE [ssnoversion-md](../../includes/
7379
1. Select a certificate from the **Certificate** dropdown list, and then select **Apply**.
7480

7581
1. Select **OK**.
82+
83+
### Install on failover cluster instance and availability group
84+
85+
For a failover cluster instance (FCI) configuration, complete these steps in the active node of the FCI. You must have administrator permissions on all the cluster nodes.
86+
87+
For an availability group (AG) configuration, complete these steps from the node hosting the AG primary replica. You must have administrator permissions on all the cluster nodes.
88+
7689
::: moniker-end
7790

91+
::: moniker range=">=sql-server-ver15"
92+
7893
## <a id="provision-failover-cluster-cert"></a> Install a certificate in a failover cluster instance configuration
7994

8095
1. In [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] Configuration Manager, in the console pane, expand **SQL Server Network Configuration**.
@@ -113,7 +128,9 @@ You can use certificate management in [!INCLUDE [ssnoversion-md](../../includes/
113128
1. Select **Next** to import the certificate on each node.
114129

115130
> [!NOTE]
116-
> Complete these steps from the node holding the AG primary replica. User must have administrator permissions on all the cluster nodes.
131+
> Complete these steps from the node hosting the AG primary replica. User must have administrator permissions on all the cluster nodes.
132+
133+
::: moniker-end
117134

118135
## Related content
119136

-20.4 KB
Loading
-19.3 KB
Loading
-53.5 KB
Loading
-18.2 KB
Loading
-16.4 KB
Loading

docs/sql-server/end-of-support/sql-server-extended-security-updates.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -134,12 +134,10 @@ You can either register a [single SQL Server instance](#single-sql-server-instan
134134

135135
1. Sign into the [Azure portal](https://portal.azure.com).
136136

137-
1. Navigate to **Azure Arc** and select **Infrastructure** > **SQL Servers**.
137+
1. Navigate to **Azure Arc** and select **Data services** > **SQL Server instances**.
138138

139139
1. To register a disconnected machine, select **Add** from the menu at the top of the screen.
140140

141-
:::image type="content" source="media/sql-server-extended-security-updates/extended-security-updates-empty-list.png" alt-text="Screenshot of an empty list of SQL Servers on the Azure Arc portal." lightbox="media/sql-server-extended-security-updates/extended-security-updates-empty-list.png":::
142-
143141
1. Select **Register Servers** to add a disconnected [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] instance.
144142

145143
:::image type="content" source="media/sql-server-extended-security-updates/extended-security-updates-add-connected-or-registered.png" alt-text="Screenshot of the two options for adding connected or registered servers." lightbox="media/sql-server-extended-security-updates/extended-security-updates-add-connected-or-registered.png":::
@@ -168,12 +166,10 @@ Multiple [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] instances ca
168166

169167
1. Sign into the [Azure portal](https://portal.azure.com).
170168

171-
1. Navigate to **Azure Arc** and select **Infrastructure** > **SQL Servers**.
169+
1. Navigate to **Azure Arc** and select **Data services** > **SQL Server instances**.
172170

173171
1. To register a disconnected machine, select **Add** from the menu at the top of the screen.
174172

175-
:::image type="content" source="media/sql-server-extended-security-updates/extended-security-updates-empty-list.png" alt-text="Screenshot of an empty list of SQL Servers on the Azure Arc portal." lightbox="media/sql-server-extended-security-updates/extended-security-updates-empty-list.png":::
176-
177173
1. Select **Register Servers** to add a disconnected [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] instance.
178174

179175
:::image type="content" source="media/sql-server-extended-security-updates/extended-security-updates-add-connected-or-registered.png" alt-text="Screenshot of the two options for adding connected or registered servers." lightbox="media/sql-server-extended-security-updates/extended-security-updates-add-connected-or-registered.png":::

0 commit comments

Comments
 (0)