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/concepts/compare-windows-server.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 @@ ms.topic: conceptual
5
5
author: alkohli
6
6
ms.author: alkohli
7
7
ms.service: azure-local
8
-
ms.date: 03/28/2025
8
+
ms.date: 04/08/2025
9
9
---
10
10
11
11
# Compare Azure Local to Windows Server
@@ -18,7 +18,7 @@ When replacing a datacenter primarily running VMware, Azure Local is typically n
18
18
19
19
## When to use Azure Local
20
20
21
-
Azure Local is Microsoft's premier hyperconverged infrastructure platform for running VMs or virtual desktops on-premises with connections to Azure hybrid services. Azure Local can help to modernize and secure your datacenters and branch offices, and achieve industry-best performance with low latency and data sovereignty.
21
+
Azure Local is Microsoft's premier hyperconverged infrastructure platform for running virtual machines (VMs) or virtual desktops on-premises with connections to Azure hybrid services. Azure Local can help to modernize and secure your datacenters and branch offices, and achieve industry-best performance with low latency and data sovereignty.
22
22
23
23
:::image type="content" source="media/compare-windows-server/hci-scenarios.png" alt-text="When to use Azure Local over Windows Server 2019" border="false" lightbox="media/compare-windows-server/hci-scenarios.png":::
24
24
@@ -41,7 +41,7 @@ Windows Server is a highly versatile, multi-purpose operating system with dozens
41
41
42
42
Use Windows Server for:
43
43
44
-
- A guest operating system inside of virtual machines (VMs) or containers
44
+
- A guest operating system inside of VMs or containers
45
45
- As the runtime server for a Windows application
46
46
- To use one or more of the built-in server roles such as Active Directory, file services, DNS, DHCP, or Internet Information Services (IIS)
47
47
- As a traditional server, such as a bare-metal domain controller or SQL Server installation
@@ -119,7 +119,7 @@ The following table compares the management options for Azure Local and Windows
119
119
| Azure portal > Windows Admin Center integration (preview) | Yes | Azure VMs only <sup>1</sup>|
120
120
| Azure portal > Multi-cluster monitoring for Azure Local | Yes | No |
121
121
| Azure portal > Azure Resource Manager integration for clusters | Yes | No |
122
-
| Azure portal > Arc VM management| Yes | No |
122
+
| Azure portal > Management of Azure Local VMs enabled by Arc| Yes | No |
123
123
| Desktop experience | No | Yes |
124
124
125
125
<sup>1</sup> Requires manually installing the Arc-git statusConnected Machine agent on every machine.
Copy file name to clipboardExpand all lines: azure-local/concepts/observability.md
+31-1Lines changed: 31 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Azure Local observability
3
3
description: Learn about observability in Azure Local.
4
4
author: alkohli
5
5
ms.author: alkohli
6
-
ms.date: 10/18/2024
6
+
ms.date: 04/25/2025
7
7
ms.topic: conceptual
8
8
ms.service: azure-local
9
9
---
@@ -109,6 +109,36 @@ The following table describes the types of data, their storage location, default
109
109
| Metrics | Metrics are numerical values collected at regular intervals, describing aspects of a system. | Metrics data is sent to the respective region in which resource is deployed. | Enabled by default and can be disabled anytime. | Platform metrics are stored for 93 days, however, you can only query (in the Metrics tile) for a maximum of 30 days' worth of data on any single chart. | You can use metrics explorer to interactively analyze the data in your metric database. |
110
110
| Billing and census | Billing data includes the system ID and the number of physical cores and hours used. Census data is required to enable basic management from Azure and includes system information (system name and ID, system connection status, storage pool ID, trial days remaining and billing model), machine information (number of machines, machine name, OS version, machine manufacturer, model and serial number, number of physical cores and memory size), and basic configuration such as, enablement of Azure verification for VMs, Azure managed identity and diagnostics level setting. | Billing and census data is sent to the respective resource region where the customer registered the device. | Billing is always enabled as it is required to charge for Azure Local usage. Census data is also always enabled, as it includes the minimal information required to manage Azure Local from Azure. | Data is deleted when the resource is deleted, except for billing data, which is retained. | To view billing data, navigate to the Azure Local system resource page in Azure portal, select **Overview** in the left pane, in the Essentials section select the **Billing status** link, followed by **View Cost Management**. To view census data, select **JSON View** located in the top right corner of the Essentials section. |
111
111
112
+
## Crash dump collection
113
+
114
+
Crash dump collection is a feature in Azure Local that allows for the automatic collection, analysis, and debugging of crashes. The data collected from a crash, referred to as the crash dump, is used for analysis and debugging.
115
+
116
+
### Key features
117
+
118
+
Here are the key features of crash dump collection for Azure Local:
119
+
120
+
-**Automatic collection and analysis.** Automatically gathers data from Azure Local crashes and analyzes it to pinpoint the root causes of failures, aiding in quick diagnosis and resolution. This minimizes downtime and enhances service reliability.
121
+
-**Compliance and security.** Ensures crash data is handled securely and in compliance with data protection regulations across all Azure regions and national clouds.
122
+
-**Customizable settings.** Enabled by default for optimal performance and reliability, but can be disabled using specific commands if necessary. However, we recommend to keep it enabled to benefit from its diagnostic capabilities.
123
+
124
+
### Prerequisites
125
+
126
+
To use the crash dump collection feature, install the `AzureEdgeTelemetryAndDiagnostics` extension, version 2.0.18 or later. For information about the extension, see [Azure Local telemetry and diagnostics extension overview](./telemetry-and-diagnostics-overview.md).
127
+
128
+
### Disable crash dump collection
129
+
130
+
To disable the crash dump collection capability, use the following command:
131
+
132
+
```powershell
133
+
Set-EdgeCrashDumpCollection -SetState Disable
134
+
```
135
+
136
+
To re-enable it, use the following command:
137
+
138
+
```powershell
139
+
Set-EdgeCrashDumpCollection -SetState Enable
140
+
```
141
+
112
142
## Next steps
113
143
114
144
-[Azure Local telemetry and diagnostics extension](./telemetry-and-diagnostics-overview.md)
Copy file name to clipboardExpand all lines: azure-local/deploy/single-server.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ Currently you can't use Windows Admin Center to deploy Azure Stack HCI on a sing
23
23
24
24
## Prerequisites
25
25
26
-
- A server from the [Azure Stack HCI Catalog](https://hcicatalog.azurewebsites.net/#/catalog) certified for use as a single-node cluster and configured with all NVMe or all SSD drives.
26
+
- A server from the [Azure Stack HCI Catalog](https://azurelocalsolutions.azure.microsoft.com/#/catalog) certified for use as a single-node cluster and configured with all NVMe or all SSD drives.
27
27
- For network, hardware and other requirements, see [Azure Stack HCI network and domain requirements](../deploy/operating-system.md#determine-hardware-and-network-requirements).
28
28
- Optionally, [install Windows Admin Center](/windows-server/manage/windows-admin-center/deploy/install) to register and manage the server after it's deployed.
Copy file name to clipboardExpand all lines: azure-local/faq.yml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ metadata:
6
6
author: cosmosdarwin
7
7
ms.author: cosdar
8
8
ms.service: azure-local
9
-
ms.date: 02/03/2025
9
+
ms.date: 04/08/2025
10
10
title: Azure Local FAQ
11
11
summary: The Azure Local FAQ provides information about Azure Local connectivity with the cloud, and how Azure Local relates to Windows Server.
12
12
@@ -54,7 +54,7 @@ sections:
54
54
answer: |
55
55
While your connection is down, all host infrastructure and VMs continue to run normally, and you can use edge-local tools for management. However, you wouldn't be able to use features that directly rely on cloud services. Information in the Azure portal may also become out-of-date until Azure Local is able to sync again.
56
56
57
-
Configuration changes made to Arc VMs using edge-local tools won't automatically sync with Azure.
57
+
Configuration changes made to Azure Local VMs enabled by Arc using edge-local tools won't automatically sync with Azure.
58
58
59
59
- question: How long can Azure Local run with the connection down?
0 commit comments