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
description: Learn how to configure Virtual Machines - Virtual Trusted Platform Module (vTPM).
4
4
ms.topic: how-to
5
5
ms.service: azure-vmware
6
-
ms.date: 11/22/2024
6
+
ms.date: 11/25/2024
7
7
ms.custom: engagement-fy25
8
8
---
9
9
@@ -13,9 +13,9 @@ This article demonstrates how to enable the virtual Trusted Platform Module (vTP
13
13
14
14
A virtual Trusted Platform Module (vTPM) in VMware vSphere is a virtual counterpart of a physical TPM 2.0 chip, utilizing VM Encryption. It provides the same functionalities as a physical TPM but operates within VMs. Each VM can have its own unique and isolated vTPM, which helps secure sensitive information and maintain system integrity. This setting enables VMs to apply security features like BitLocker disk encryption and authenticate virtual hardware devices, creating a more secure virtual environment.
15
15
16
-
## Pre-requisites
16
+
## Prerequisites
17
17
18
-
Before configuring vTPM on a VM in Azure VMware Solution, ensure the following pre-requisites are met:
18
+
Before configuring vTPM on a VM in Azure VMware Solution, ensure the following prerequisites are met:
19
19
20
20
- The virtual machine must use EFI firmware.
21
21
- The virtual machine must be at hardware version 14 or later.
@@ -24,6 +24,31 @@ Before configuring vTPM on a VM in Azure VMware Solution, ensure the following p
24
24
>[!IMPORTANT]
25
25
>Customers do not need to configure a key provider to use vTPM with Azure VMware Solution. Azure VMware Solution already provides and manages key providers for each environment.
26
26
27
+
## Trusted Launch for Azure VMware Solution
28
+
29
+
Trusted Launch is a comprehensive security solution that encompasses three key components: Secure Boot, Virtual Trusted Platform Module (vTPM), and Virtualization-based security (VBS). Each of these components plays a vital role in fortifying the security posture of VMs.
30
+
31
+
## Benefits
32
+
33
+
• Securely deploy VMs with verified boot loaders, operating system (OS) kernels, and drivers.
34
+
35
+
• Securely protect keys, certificates, and secrets in the VMs.
36
+
• Gain insights and confidence of the entire boot chain's integrity.
37
+
38
+
• Ensure that workloads are trusted and verifiable.
39
+
40
+
### Secure Boot
41
+
42
+
Secure Boot is the first line of defense in Trusted Launch. It establishes a "root of trust" for VMs by ensuring that only signed operating systems and drivers are allowed to boot. This prevents the installation of malware-based rootkits and bootkits, which can compromise the security of the entire system. With Secure Boot enabled, every aspect of the boot process, from the boot loader to the kernel and kernel drivers, must be digitally signed by trusted publishers. This creates a robust shield against unauthorized modifications and ensures that the VM starts in a secure and trusted state.
43
+
44
+
## Virtual Trusted Platform Module (vTPM)
45
+
46
+
The vTPM is a virtualized version of a hardware Trusted Platform Module (TPM) 2.0 device. It serves as a dedicated secure vault for storing keys, certificates, and secrets. What sets vTPM apart is its ability to operate in a secure environment outside the reach of any VM, making it tamper-resistant and highly secure. One of the key functions of vTPM is attestation. It measures the entire boot chain of a VM, including UEFI, OS, system components, and drivers, to certify that the VM booted securely. This attestation mechanism is invaluable for verifying the integrity of VMs and ensuring that they haven't been compromised.
47
+
48
+
## Virtualization-based Security (VBS)
49
+
50
+
VBS is the final piece of the Trusted Launch puzzle. It leverages the hypervisor to create isolated, secure memory regions within the VM. VBS uses virtualization to enhance system security by creating an isolated, hypervisor-restricted, specialized subsystem. It provides protection against unauthorized access of credential, prevents malware from running on windows system and ensures only trusted code runs from bootloader onwards.
51
+
27
52
## How to Configure vTPM
28
53
29
54
To configure vTPM on a VM in Azure VMware Solution, follow these steps:
@@ -43,7 +68,7 @@ To configure vTPM on a VM in Azure VMware Solution, follow these steps:
43
68
44
69
## Unsupported scenarios
45
70
46
-
Migration of VMs with vTPM may not be supported by some tools. Check the documentation of the migration tool. If it is not supported, you can follow VMware documentation to safely disable vTPM and re-enable it post-migration.
71
+
Migration of VMs with vTPM might not be supported by some tools. Check the documentation of the migration tool. If it isn't supported, you can follow VMware documentation to safely disable vTPM and re-enable it post-migration.
47
72
48
73
## More information
49
74
[Securing Virtual Machines with Virtual Trusted Platform Module](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-A43B6914-E5F9-4CB1-9277-448AC9C467FB.html)
Copy file name to clipboardExpand all lines: articles/event-grid/mqtt-overview.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
@@ -102,7 +102,7 @@ Event Grid allows you to route your MQTT messages to Azure services or webhooks
102
102
:::image type="content" source="media/mqtt-overview/routing-high-res.png" alt-text="Diagram of the MQTT message routing." border="false":::
103
103
104
104
### Edge MQTT broker integration
105
-
Event Grid integrates with [Azure IoT MQ](https://aka.ms/iot-mq) to bridge its MQTT broker capability on the edge with Azure Event Grid’s MQTT broker feature in the cloud. Azure IoT MQ is a new distributed MQTT broker for edge computing, running on Arc enabled Kubernetes clusters. It can connect to Event Grid MQTT broker with Microsoft Entra ID (formerly Azure Active Directory) authentication using system-assigned managed identity, which simplifies credential management. Azure IoT MQ provides high availability, scalability, and security for your IoT devices and applications. It's now available in [public preview](https://aka.ms/iot-mq-preview) as part of Azure IoT Operations. [Learn more about connecting Azure IoT MQ to Azure Event Grid's MQTT broker](https://aka.ms/iot-mq-eg-bridge).
105
+
Event Grid integrates with [Azure IoT Operations](https://aka.ms/iot-mq) to bridge its MQTT broker capability on the edge with Azure Event Grid’s MQTT broker feature in the cloud. Azure IoT Operations provides a new distributed MQTT broker for edge computing, running on Arc enabled Kubernetes clusters. It can connect to Event Grid MQTT broker with Microsoft Entra ID (formerly Azure Active Directory) authentication using system-assigned managed identity, which simplifies credential management. MQTT Broker provides high availability, scalability, and security for your IoT devices and applications. It's now available in [public preview](https://aka.ms/iot-mq-preview) as part of Azure IoT Operations. [Learn more about connecting Azure IoT Operations MQTT Broker to Azure Event Grid's MQTT broker](https://aka.ms/iot-mq-eg-bridge).
Copy file name to clipboardExpand all lines: articles/event-hubs/schema-registry-concepts.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
@@ -22,7 +22,7 @@ Schema group is a logical group of similar schemas based on your business criter
22
22
The security boundary imposed by the grouping mechanism help ensures that trade secrets don't inadvertently leak through metadata in situations where the namespace is shared among multiple partners. It also allows for application owners to manage schemas independent of other applications that share the same namespace.
23
23
24
24
### Schemas
25
-
Schemas define the contract between producers and consumers. A schema defined in an Event Hubs schema registry helps manage the contract outside of event data, thus removing the payload overhead. A schema has a name, type (example: record, array, and so on.), compatibility mode (none, forward, backward, full), and serialization type (only Avro for now). You can create multiple versions of a schema and retrieve and use a specific version of a schema.
25
+
Schemas define the contract between producers and consumers. A schema defined in an Event Hubs schema registry helps manage the contract outside of event data, thus removing the payload overhead. A schema has a name, type (example: record, array, and so on.), compatibility mode (none, forward, backward, full), and serialization type (both Avro and JSON). You can create multiple versions of a schema and retrieve and use a specific version of a schema.
26
26
27
27
### Schema formats
28
28
Schema formats are used to determine the manner in which a schema is structured and defined, with each format outlining specific guidelines and syntax for defining the structure of the events that will be used for event streaming.
Copy file name to clipboardExpand all lines: articles/fxt-edge-filer/add-nodes.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,9 @@ ms.date: 05/26/2021
10
10
11
11
# Tutorial: Add cluster nodes to an Azure FXT Edge Filer cluster
12
12
13
+
> [!NOTE]
14
+
> **Action Required:** Azure FXT Edge Filer will be retired on December 31, 2026. Please remove all Azure FXT Edge Filer resources by December 31, 2026. Visit https://aka.ms/fxtretirementfaq for more information.
15
+
13
16
A new Azure FXT Edge Filer cluster is created with only one node. You should add at least two more nodes and enable high availability before doing other configuration.
14
17
15
18
This tutorial explains how to add cluster nodes and enable the High Availability (HA) feature.
Copy file name to clipboardExpand all lines: articles/fxt-edge-filer/add-storage.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,9 @@ ms.date: 06/20/2019
10
10
11
11
# Tutorial: Add back-end storage and configure the virtual namespace
12
12
13
+
> [!NOTE]
14
+
> **Action Required:** Azure FXT Edge Filer will be retired on December 31, 2026. Please remove all Azure FXT Edge Filer resources by December 31, 2026. Visit https://aka.ms/fxtretirementfaq for more information.
15
+
13
16
This tutorial explains how to add back-edge storage for your cache and how to set up the client-facing virtual filesystem.
14
17
15
18
The cluster connects to back-end storage systems to access the data clients request, and to store changes more permanently than in the cache.
Copy file name to clipboardExpand all lines: articles/fxt-edge-filer/additional-doc.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,9 @@ ms.date: 06/20/2019
10
10
11
11
# Additional documentation for Azure FXT Edge Filer
12
12
13
+
> [!NOTE]
14
+
> **Action Required:** Azure FXT Edge Filer will be retired on December 31, 2026. Please remove all Azure FXT Edge Filer resources by December 31, 2026. Visit https://aka.ms/fxtretirementfaq for more information.
15
+
13
16
Other non-Microsoft resources might help you understand and work with your Microsoft Azure FXT Edge Filer hybrid cache.
Copy file name to clipboardExpand all lines: articles/fxt-edge-filer/cluster-create.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,9 @@ ms.date: 07/01/2019
10
10
11
11
# Tutorial: Create the Azure FXT Edge Filer cluster
12
12
13
+
> [!NOTE]
14
+
> **Action Required:** Azure FXT Edge Filer will be retired on December 31, 2026. Please remove all Azure FXT Edge Filer resources by December 31, 2026. Visit https://aka.ms/fxtretirementfaq for more information.
15
+
13
16
After you install and initialize the Azure FXT Edge Filer hardware nodes for your cache, use the FXT cluster software to create the cache cluster.
14
17
15
18
This tutorial walks you through the steps to configure your hardware nodes as a cluster.
0 commit comments