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
You can create a logical network using either the Azure Command-Line Interface (CLI) or by using the Azure portal.
46
+
You can create a logical network by using either the Azure CLI or the Azure portal.
47
47
48
48
# [Azure CLI](#tab/azurecli)
49
49
50
-
You can use the [`az stack-hci-vm network lnet create`](/cli/azure/stack-hci-vm/network/lnet#az-stack-hci-vm-network-lnet-create) cmdlet to create a logical network on the VM switch in Static IP configuration.
50
+
To create a logical network on the VM switch in a static IP configuration, you can use the [`az stack-hci-vm network lnet create`](/cli/azure/stack-hci-vm/network/lnet#az-stack-hci-vm-network-lnet-create) command:
51
+
52
+
```azurecli
53
+
az stack-hci-vm network lnet create \
54
+
--subscription $subscription \
55
+
--resource-group $resource_group \
56
+
--custom-location $customLocationID \
57
+
--name $lnetName \
58
+
--vm-switch-name $vmSwitchName \
59
+
--ip-allocation-method "Static" \
60
+
--address-prefixes $addressPrefixes \
61
+
--gateway $gateway \
62
+
--dns-servers $dnsServers \
63
+
--ip-pool-start $ipPoolStart \
64
+
--ip-pool-end $ipPoolEnd \
65
+
--vlan 10
66
+
```
51
67
52
68
For static IP, the required parameters are as follows:
53
69
@@ -57,17 +73,14 @@ For static IP, the required parameters are as follows:
57
73
|`--resource-group`| Name of the resource group where you create the logical network. |
58
74
|`--subscription`| Name or ID of the subscription where your Azure Local is deployed. |
59
75
|`--custom-location`| Provide the custom location associated with your Azure Local cluster where you're creating the logical network. |
60
-
|`--vm-switch-name`| The name of the VM switch. Usage: `--vm-switch-name "vm-switch-01"`. |
76
+
|`--vm-switch-name`| The name of the VM switch. Usage: `--vm-switch-name "vm-switch-01"`. |
61
77
|`--address-prefixes`| AddressPrefix for the network. Currently only 1 address prefix is supported. Usage: `--address-prefixes "10.220.32.16/24"`. |
62
-
|`--dns-servers`| Space-separated list of DNS server IP addresses. Usage: `--dns-servers 10.220.32.16 10.220.32.17`. |
78
+
|`--dns-servers`| Space-separated list of DNS server IP addresses. Usage: `--dns-servers 10.220.32.16 10.220.32.17`. |
63
79
|`--gateway`| Gateway. The gateway IP address must be within the scope of the address prefix. Usage: `--gateway 10.220.32.16`. |
64
-
|`--ip-allocation-method`| The IP address allocation method. Supported values are "Static". Usage: `--ip-allocation-method "Static"`. |
65
-
|`--ip-pool-start`| The start IP address of your IP pool. The address must be in range of the address prefix. Usage: `--ip-pool-start "10.220.32.18"`. |
80
+
|`--ip-allocation-method`| The IP address allocation method. Supported values are `Static`. Usage: `--ip-allocation-method "Static"`. |
81
+
|`--ip-pool-start`| The start IP address of your IP pool. The address must be in range of the address prefix. Usage: `--ip-pool-start "10.220.32.18"`. |
66
82
|`--ip-pool-end`| The end IP address of your IP pool. The address must be in range of the address prefix. Usage: `--ip-pool-end "10.220.32.38"`. |
|`--vlan`| The VLAN ID. Usage: `--vlan 10`. This parameter is required, otherwise the default value of 0 results in an AKS Arc cluster creation failure. |
71
84
72
85
# [Azure portal](#tab/azureportal)
73
86
@@ -77,11 +90,11 @@ Complete the following steps to create a logical network using the Azure portal:
@@ -17,44 +17,44 @@ This article describes the types of virtual machines (VMs) available on Azure Lo
17
17
18
18
Here are the different types of VMs that you can run on your Azure Local system:
19
19
20
-
-**Arc VMs:** Windows and Linux VMs hosted outside of Azure, on your corporate network, running on Azure Local.
21
-
- Are created using [Arc VM provisioning flow](../manage/create-arc-virtual-machines.md?tabs=azureportal), registered to [Arc Resource Bridge](/azure/azure-arc/resource-bridge/overview), and have the [Connected Machine agent](/azure/azure-arc/servers/agent-overview) installed.
20
+
-**Azure Local VMs enabled by Azure Arc:** Windows and Linux VMs hosted outside of Azure, on your corporate network, running on Azure Local.
21
+
- Are created using [Azure Local VM provisioning flow](../manage/create-arc-virtual-machines.md?tabs=azureportal), registered to [Azure Arc resource bridge](/azure/azure-arc/resource-bridge/overview), and have the [Connected Machine agent](/azure/azure-arc/servers/agent-overview) installed.
22
22
- Offer extensive management capabilities in the Azure portal, second only to native Azure VMs.
23
-
- Through Arc Resource Bridge, Arc VMs provide lifecycle management capabilities like starting, stopping, changing VM memory/vCPU, and adding or removing data disk and network interfaces.
24
-
- Through the Connected Machine agent, Arc VMs leverage Azure Arc extensions such as Microsoft Defender for Cloud and Azure Monitor to govern, protect, configure, and monitor virtual machines.
23
+
- Through Azure Arc resource bridge, Azure Local VMs provide lifecycle management capabilities like starting, stopping, changing VM memory/vCPU, and adding or removing data disk and network interfaces.
24
+
- Through the Connected Machine agent, Azure Local VMs leverage Azure Arc extensions such as Microsoft Defender for Cloud and Azure Monitor to govern, protect, configure, and monitor virtual machines.
25
25
- Can be managed through Azure.
26
26
27
27
-**[Arc-enabled servers](/azure/azure-arc/servers/overview):** Windows and Linux physical servers and virtual machines hosted outside of Azure, on your corporate network, or on other cloud providers with the Connected Machine agent installed.
28
28
- Arc-enabled servers run on Azure Local as virtual machines.
29
-
- Lack the lifecycle management capabilities that Arc VMs offer.
29
+
- Lack the lifecycle management capabilities that Azure Local VMs offer.
30
30
- Through the Connected Machine agent, Arc-enabled servers leverage Azure Arc extensions such as Microsoft Defender for Cloud and Azure Monitor to govern, protect, configure, and monitor virtual machines.
31
31
- Can be managed through Azure.
32
32
33
-
-**Non-Arc VMs:** Windows and Linux VMs created and hosted outside of Azure, on your corporate network, running on Azure Local.
33
+
-**Unmanaged VMs:** Windows and Linux VMs created and hosted outside of Azure, on your corporate network, running on Azure Local.
34
34
- Aren't connected to Azure.
35
35
- Can't be managed through Azure.
36
36
37
-
The following table compares the provisioning and management methods for the various types of Azure Local VM:
37
+
The following table compares the provisioning and management methods for the various types of VMs running on Azure Local:
38
38
39
-
| VM provisioning and management methods |Arc VMs | Arc-enabled servers |Non-Arc VMs |
39
+
| VM provisioning and management methods |Azure Local VMs enabled by Azure Arc | Arc-enabled servers |Unmanaged VMs |
40
40
| :---- | :---- | :---- | :---- |
41
-
| Provisioning method |[Arc VM provisioning flow](../manage/create-arc-virtual-machines.md?tabs=azureportal). Create Arc VMs using Azure CLI, Azure portal, or Azure Resource Manager template. Using ARM templates, you can also automate VM provisioning in a secure cloud environment. <br><br> [Azure Migrate flow](../migrate/migration-azure-migrate-overview.md). Migrate existing VMware and Hyper-V VMs as Arc VMs to Azure Local using the migration flow. | Connect these machines to Azure by [deploying the Connected Machine agent](/azure/azure-arc/servers/deployment-options)| On-premises provisioning flow. Use local tools like Failover Cluster Manager available in your on-premises environment, or use [Windows Admin Center](../manage/vm.md#create-a-new-vm), [System Center Virtual Machine Manager (SCVMM)](/system-center/vmm/provision-vms), or [PowerShell](../manage/vm-powershell.md#create-a-vm).|
42
-
| Management method | Via Azure. | Via Azure. See [Management and monitoring for Azure Arc-enabled servers](/azure/cloud-adoption-framework/scenarios/hybrid/arc-enabled-servers/eslz-management-and-monitoring-arc-server). | Via the local tools. Manage these VMs through the management consoles of the same local tools used for their creation. |
41
+
| Provisioning method |[Azure Local VMs provisioning flow](../manage/create-arc-virtual-machines.md?tabs=azureportal). Create Azure Local VMs using Azure CLI, Azure portal, or Azure Resource Manager (ARM) template. Using ARM templates, you can also automate VM provisioning in a secure cloud environment. <br><br> [Azure Migrate flow](../migrate/migration-azure-migrate-overview.md). Migrate existing VMware and Hyper-V VMs to Azure Local using the migration flow. | Connect these machines to Azure by [deploying the Connected Machine agent](/azure/azure-arc/servers/deployment-options)| On-premises provisioning flow. Use local tools like Failover Cluster Manager available in your on-premises environment, or use [Windows Admin Center](../manage/vm.md#create-a-new-vm), [System Center Virtual Machine Manager (SCVMM)](/system-center/vmm/provision-vms), or [PowerShell](../manage/vm-powershell.md#create-a-vm).|
42
+
| Management method |[Via Azure](../manage/manage-arc-virtual-machines.md). | Via Azure. See [Management and monitoring for Azure Arc-enabled servers](/azure/cloud-adoption-framework/scenarios/hybrid/arc-enabled-servers/eslz-management-and-monitoring-arc-server). | Via the local tools. Manage these VMs through the management consoles of the same local tools used for their creation. |
43
43
44
44
> [!NOTE]
45
-
> Currently, conversion of an Arc-enabled server or non-Arc VM to an Arc VM isn't supported.
45
+
> Currently, conversion of an Arc-enabled server or unmanaged VM to an Azure Local VM isn't supported.
46
46
47
47
## Compare VM management capabilities
48
48
49
-
The following table compares the management capabilities for Arc VMs, Arc-enabled servers, and non-Arc VMs across various operations and features available through the Azure portal:
49
+
The following table compares the management capabilities for Azure Local VMs, Arc-enabled servers, and unmanaged VMs across various operations and features available through the Azure portal:
50
50
51
51
> [!IMPORTANT]
52
52
> Keep in mind the following information when comparing VM management capabilities:
53
53
>- Microsoft Product Terms for your program override this section. For more information, see [Microsoft Azure Product Terms](https://www.microsoft.com/licensing/#products) and select your program to show the terms.
54
54
>- Some services, even if included in Azure Hybrid Benefits, may incur operational costs, such as storing log data. For more information, see [Azure Pricing calculator](https://azure.microsoft.com/pricing/calculator/).
55
55
>- Some key features are part of the Windows Server Management enabled by Azure Arc experience. For more information, see [Windows Server Management enabled by Azure Arc](/azure/azure-arc/servers/windows-server-management-overview?tabs=portal).
56
56
57
-
|Azure VM management capability|Arc VMs|Arc-enabled servers|Non-Arc VMs|
57
+
|Azure VM management capability|Azure Local VMs enabled by Azure Arc |Arc-enabled servers| Unmanaged VMs|
58
58
|:-----|:-----:|:-----:|:-----:|
59
59
|**Settings**|
60
60
| - Start|✅|❌|❌|
@@ -100,11 +100,6 @@ The following table compares the management capabilities for Arc VMs, Arc-enable
100
100
| - Export template |✅|❌|❌|
101
101
| - Resource health |❌ <br>(Use Alerts) |✅|❌|
102
102
103
-
104
-
<!--- 1: at additional costs.
105
-
- [^2]: included as part of Windows Server and SQL Server management capabilities enabled by Azure Arc. For more information, see [Azure Hybrid Benefits for Windows Server](/windows-server/get-started/azure-hybrid-benefit?tabs=azure).
106
-
- [^3]: included for VMs running on Azure and Azure Local instances.-->
107
-
108
103
<aname="1"></a>1: At additional costs.
109
104
110
105
<aname="2"></a>2: Included as part of Windows Server and SQL Server management capabilities enabled by Azure Arc. For more information, see [Azure Hybrid Benefits for Windows Server](/windows-server/get-started/azure-hybrid-benefit?tabs=azure).
@@ -113,4 +108,4 @@ The following table compares the management capabilities for Arc VMs, Arc-enable
113
108
114
109
## Next steps
115
110
116
-
- Review [Azure Arc VM management prerequisites](../manage/azure-arc-vm-management-prerequisites.md).
111
+
- Review [Azure Local VM management prerequisites](../manage/azure-arc-vm-management-prerequisites.md).
Copy file name to clipboardExpand all lines: azure-local/concepts/security-features.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
@@ -5,7 +5,7 @@ author: alkohli
5
5
ms.author: alkohli
6
6
ms.topic: conceptual
7
7
ms.service: azure-local
8
-
ms.date: 03/06/2025
8
+
ms.date: 03/24/2025
9
9
---
10
10
11
11
# Security features for Azure Local
@@ -193,5 +193,5 @@ For more information, see:
193
193
## Next steps
194
194
195
195
-[Assess deployment readiness via the Environment Checker](../manage/use-environment-checker.md).
196
-
-[Read the Azure Local security book](https://assetsprod.microsoft.com/mpn/azure-stack-hci-security-book.pdf).
196
+
-[Read the Azure Local security book](https://github.com/Azure-Samples/AzureLocal/blob/main/SecurityBook/Azure%20Local%20Security%20Book_01172025.pdf).
197
197
-[View the Azure Local security standards](/azure-stack/hci/assurance/azure-stack-security-standards).
0 commit comments