vSphere 8.x
VCF 9.x
When configuring vCenter Server Identity Provider Federation with Microsoft Entra ID, the MFA requirement is applied to all users by default. Because non-interactive service accounts cannot respond to MFA prompts, these integrations may fail to authenticate.
To maintain functionality and security, use one of the following methods:
Conditional Access Policies (Recommended): Create an exclusion policy in the Microsoft Entra admin center targeting the vCenter application to explicitly exclude service accounts from the MFA requirement.
Note: With this method, service accounts still authenticate through Entra ID. If Entra ID experiences an outage or there is an internet connectivity issue, these accounts will fail to authenticate.
Dedicated Local Accounts: If organizational policies restrict Conditional Access exclusions, or if service accounts must remain functional during an Entra ID outage, create dedicated local vCenter accounts on the vsphere.local domain with the minimum necessary privileges. These accounts authenticate locally and are not impacted by Entra ID availability.
Note: Management of accounts created invsphere.localwill need to be maintained in vCenter. In VCF 9 when vCenter Linking is being used instead of ELM, thenvsphere.locallocal service accounts will need to be maintained per vCenter.vsphere.localwill not replicate when vCenter Linking is used.
Note: Ensure proper security hardening. After configuring Entra ID as a valid identity source, logging in via the Sign in with local account option can potentially allow users to bypass Entra ID SSO.