Yes, I just recently upgraded to 8.0U3.
Original Message:
Sent: Aug 19, 2024 05:52 PM
From: einstein-a-go-go
Subject: Microsoft Entra ID
Is this using 8.0U3 ?
I have come across another three sites which have this issue so we are not alone, so I'm glad it's not just me!
Someone told me if you refresh the page they are able to login - but that didn't work for me!
Original Message:
Sent: Aug 19, 2024 05:31 PM
From: Perry Balacuit
Subject: Microsoft Entra ID
I'm at the same spot as you are with the Access Denied screen after successfully configuring/testing the connections.
I followed the instructions to create an internal scim from this KB (https://knowledge.broadcom.com/external/article?legacyId=94182). The attachment PDF file shows step by step on how to configure using Microsoft Entra Connect Provisioning Agent.
I'm hoping someone has a solution/workaround.
I've added my VMware Users AD group to the Administrators group in the vCenter. It takes my SSO login then prompts the ACCESS DENIED screen.
Original Message:
Sent: Aug 18, 2024 06:02 AM
From: einstein-a-go-go
Subject: Microsoft Entra ID
We did create a SCIM, but we didn't like to idea of direct contact with vCenter Server in a public space, so we created our internal SCIM
We are going to try with 8.0U2 and check it's an issue with the update.
Original Message:
Sent: Aug 15, 2024 03:01 PM
From: Larry Si
Subject: Microsoft Entra ID
Hello, did you ever figure out the issue. We are in the process of doing the same. Moving to Entra ID and received the same error. Did you configure SCIM? In adfs we did not do that. Not sure if its mandatory for entra id. Thanks
Original Message:
Sent: Aug 07, 2024 12:33 PM
From: einstein-a-go-go
Subject: Microsoft Entra ID
vCenter Server 8.0U3 - Provider changed to Microsoft Entra ID
All seems to be configured correctly, Azure provisions the users for the domain, Azure states in the log the users have been correctly Authenticated against Entra ID, the users are present in vCenter Server.
These users have been allocated correct permissions in vCenter Server
BUT
this appears!

We are not using Workspace One, of have any configuration or anything to do with Workspace One!
So puzzled ?