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: articles/azure-vmware/azure-vmware-solution-platform-updates.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,14 +4,20 @@ description: Learn about the platform updates to Azure VMware Solution.
4
4
ms.topic: reference
5
5
ms.custom: "references_regions, engagement-fy23"
6
6
ms.service: azure-vmware
7
-
ms.date: 09/12/2025
7
+
ms.date: 03/09/2026
8
8
# Customer intent: "As an Azure VMware Solution user, I want to stay informed about platform updates and maintenance schedules, so that I can ensure my workloads remain optimized and secure during transitions."
9
9
---
10
10
11
11
# What's new in Azure VMware Solution
12
12
13
13
Microsoft regularly applies important updates to the Azure VMware Solution for new features and software lifecycle management. You should receive a notification through Azure Service Health that includes the timeline of the maintenance. For more information, see [Host maintenance and lifecycle management](azure-vmware-solution-private-cloud-maintenance.md#host-maintenance-and-lifecycle-management).
14
14
15
+
## March 2026
16
+
17
+
**Microsoft Entra ID integration for Azure VMware Solution**
18
+
19
+
Microsoft Entra ID intergration for Azure VMware Solution is now Generally Available (GA). This feature enables customers to utilize Microsoft Entra ID an an external identity source for vCenter, providing greater security and integration into Azure. [Learn More](configure-identity-source-vcenter.md#microsoft-entra-id-as-an-identity-source).
Copy file name to clipboardExpand all lines: articles/azure-vmware/configure-identity-source-vcenter.md
+20-1Lines changed: 20 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: Set an external identity source for vCenter Server
3
3
description: Learn how to set Windows Server Active Directory over LDAP or LDAPS for VMware vCenter Server as an external identity source.
4
4
ms.topic: how-to
5
5
ms.service: azure-vmware
6
-
ms.date: 10/22/2025
6
+
ms.date: 03/9/2026
7
7
ms.custom: engagement-fy23
8
8
# Customer intent: "As a system administrator, I want to configure Windows Server Active Directory as an external identity source for vCenter Server, so that I can authenticate users and manage role-based access efficiently."
9
9
---
@@ -46,6 +46,25 @@ In this article, you learn how to:
46
46
> [!NOTE]
47
47
> For more information about LDAPS and certificate issuance, contact your security team or your identity management team.
48
48
49
+
## Microsoft Entra ID as an Identity Source
50
+
51
+
Integrating Microsoft Entra ID as your external identity provider for Azure VMware Solution vCenter transforms your administrative security and operational efficiency. While Azure VMware Solution traditionally relies on Windows Server Active Directory via LDAPS, native Entra ID federation (using OIDC in vSphere 8.0 U2+) offers a modernized approach. The primary advantage is centralized identity management, which breaks down authentication silos between your cloud and on-premises environments.
52
+
53
+
By relying on Entra ID, you can natively enforce advanced security policies—such as Multi-Factor Authentication (MFA) and Conditional Access—without deploying additional infrastructure. Because this is a federated model, vCenter never directly handles or stores user credentials; instead, it trusts Entra ID's validation. This protects credentials, ensures a seamless Single Sign-On (SSO) experience for your administrators, and provides centralized audit trails for better compliance.
54
+
55
+
Azure VMware Solution is a managed service, standard CloudAdmin accounts do not have the elevated native vCenter permissions required to manage external identity provider directly. To bridge this gap, you must use Run Commands—specifically packaged PowerShell cmdlets executed directly through the Azure portal.
56
+
57
+
| Category | Component/Feature | Description |
58
+
| --- | --- | --- |
59
+
|**Security Benefits**| MFA & Conditional Access | Enforces native Entra ID security policies to protect vCenter Access. |
60
+
|| Credential Protection | Federated authentication ensures vCenter never sees raw credentials. |
61
+
|**Run Commands**| Add-VCenterCloudAdminRoleVcIdentityProvidersManagePrivilege | Add required permission for external identity provider to Cloudadmin account. |
62
+
|| Remove-AVSIdentityProviderEntraId | Deletes the configured Entra ID from vCenter Server. |
63
+
|**Permissions**| VcIdentityProviders.Manage | vCenter privilege required to create, update, or delete external identiy providers. |
64
+
65
+
> [!NOTE]
66
+
> Use Microsoft Entra ID or LDAPS authentication for external identity sources with vCenter. Azure VMware Solution supports both options.
67
+
49
68
## Export the certificate for LDAPS authentication (Optional)
50
69
51
70
First, verify that the certificate that's used for LDAPS is valid. If you don't have a certificate, complete the steps to [create a certificate for LDAPS](../active-directory-domain-services/tutorial-configure-ldaps.md#create-a-certificate-for-secure-ldap) before you continue.
0 commit comments