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: azure-local/manage/connect-arc-vm-using-ssh.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
@@ -5,7 +5,7 @@ author: alkohli
5
5
ms.author: alkohli
6
6
ms.topic: how-to
7
7
ms.service: azure-local
8
-
ms.date: 02/11/2025
8
+
ms.date: 02/18/2025
9
9
10
10
#customer intent: As a Senior Content Developer, I want to provide customers with the highest level of content for using disconneced operations to deploy and manage their Azure Local instances.
11
11
---
@@ -61,7 +61,7 @@ Before you begin, ensure that you:
61
61
$resourceGroup="<your resource group>"
62
62
$serverName = "<your server name>"
63
63
$location = "<your location>"
64
-
$localUser = "Administrator" # Use a local admin account for testing
64
+
$localUser = "<your username>" # Use a local admin account for testing
65
65
```
66
66
67
67
e. Install the `OpenSSH` Arc Extension:
@@ -107,7 +107,7 @@ Before you begin, ensure that you:
107
107
108
108
:::image type="content" source="./media/connect-arc-vm-using-ssh/azure-portal-extensions-list-view-3.png" alt-text="Screenshot of Azure portal Extensions list view." lightbox="./media/connect-arc-vm-using-ssh/azure-portal-extensions-list-view-3.png":::
109
109
110
-
## Use SSH to connect to Azure Local
110
+
## Use SSH to connect to an Arc VM on Azure Local
111
111
112
112
> [!NOTE]
113
113
> You may be asked to allow Arc SSH to set up port 22 for SSH.
@@ -124,7 +124,7 @@ Use the following steps to connect to Azure Local.
124
124
125
125
:::image type="content" source="./media/connect-arc-vm-using-ssh/server-connection-6.png" alt-text="Screenshot of server connection over SSH." lightbox="./media/connect-arc-vm-using-ssh/server-connection-6.png":::
126
126
127
-
## Use RDP over SSH to connect to Azure Local
127
+
## Use RDP over SSH to connect an Arc VM on Azure Local
128
128
129
129
1. To sign into Azure Local using RDP over SSH, run the following command with the RDP parameter:
Copy file name to clipboardExpand all lines: azure-local/manage/manage-security-post-upgrade.md
+18-18Lines changed: 18 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: alkohli
5
5
ms.author: alkohli
6
6
ms.topic: how-to
7
7
ms.service: azure-local
8
-
ms.date: 02/03/2025
8
+
ms.date: 02/18/2025
9
9
---
10
10
11
11
# Manage security after upgrading Azure Local
@@ -41,31 +41,31 @@ Each of these steps is described in detail in the following sections.
41
41
A new deployment of Azure Local introduces two baselines documents injected by the security management layer, while the upgraded cluster doesn't.
42
42
43
43
> [!IMPORTANT]
44
-
> After applying the security baseline documents, a new mechanism is used to apply and maintain the[Security baseline settings](https://aka.ms/hci-securitybase).
44
+
> After you apply the security baseline documents, a new mechanism is used to apply and maintain [Security baseline settings](https://aka.ms/hci-securitybase).
45
45
46
46
1. If your servers inherit baseline settings through mechanisms such as GPO, DSC, or scripts, we recommend that you:
47
47
48
48
- Remove these duplicate settings from such mechanisms.
49
-
- Alternatively, after applying the security baseline, [Disable the drift control mechanism](./manage-secure-baseline.md).
49
+
- Alternatively, after you apply the security baseline, [Disable the drift control mechanism](./manage-secure-baseline.md).
50
50
51
-
The new security posture of your servers will combine the previous settings, the new settings, and the overlapping settings with updated values.
51
+
The new security posture of your servers combines previous settings, new settings, and overlapping settings with updated values.
52
52
53
53
> [!NOTE]
54
-
> Microsoft tests and vaildates the Azure Local security settings. We strongly recommend that you keep these settings. Use of custom settings can potentially lead to system instability, incompatibility with the new product scenarios, and could require extensive testing and troubleshooting on your part.
54
+
> Microsoft tests and vaildates the Azure Local security settings. We strongly recommend that you keep these settings. Use of custom settings can potentially lead to system instability, incompatibility with new product scenarios, and could require extensive testing and troubleshooting on your part.
55
55
56
-
1. When running the followign commands, you'll find the documents aren't in place. These cmdlets won't return any output.
56
+
1. When running the following commands, you'll find the documents aren't in place. These cmdlets won't return any output.
57
57
58
-
```powershell
59
-
Get-AzSSecuritySettingsConfiguration
60
-
Get-AzSSecuredCoreConfiguration
61
-
```
58
+
```powershell
59
+
Get-ASOSConfigSecuredCoreDoc
60
+
Get-ASOSConfigSecuritySettingsDoc
61
+
```
62
62
63
63
1. To enable the baselines, go to each of the nodes you upgraded. Run the following commands locally or remotely using a privileged administrator account:
64
64
65
-
```powershell
66
-
Start-AzSSecuritySettingsConfiguration
67
-
Start-AzSSecuredCoreConfiguration
68
-
```
65
+
```powershell
66
+
Start-AzSSecuritySettingsConfiguration
67
+
Start-AzSSecuredCoreConfiguration
68
+
```
69
69
70
70
1. Reboot the nodes in a proper sequence for the new settings to become effective.
You'll get an output for each cmdlet with the baseline information.
81
+
You get an output for each cmdlet with baseline information.
82
82
83
-
Here is an example of the baseline output:
83
+
Here's an example of the baseline output:
84
84
85
85
```powershell
86
86
OsConfiguration": {
@@ -108,7 +108,7 @@ If you need to enable BitLocker on any of your volumes, see [Manage BitLocker en
108
108
109
109
Application control for business (formerly known as Windows Defender Application Control or WDAC) provides a great layer of defense against running untrusted code.
110
110
111
-
After you upgrade your system, consider enabling Application Control. This can be disruptive if the necessary measures aren't taken for proper validation of existing third party software already existing on the servers.
111
+
After you upgrade your system, consider enabling Application Control. This can be disruptive if the necessary measures aren't taken for proper validation of existing non-Microsoft software already existing on the servers.
112
112
113
113
For new deployments, Application Control is enabled in *Enforced* mode (blocking nontrusted binaries), whereas for upgraded systems we recommend that you follow these steps:
114
114
@@ -118,7 +118,7 @@ For new deployments, Application Control is enabled in *Enforced* mode (blocking
118
118
1. Repeat steps #2 and #3 as necessary until no further audit events are observed. Switch to *Enforced* mode.
119
119
120
120
> [!WARNING]
121
-
> Failure to create the necessary AppControl policies to enable additional third party software will prevent that software from running.
121
+
> Failure to create the necessary AppControl policies to enable non-Microsoft software may prevent that software from running.
122
122
123
123
For instructions to enable in *Enforced* mode, see [Manage Windows Defender Application Control for Azure Local](./manage-wdac.md#switch-application-control-policy-modes).
0 commit comments