Why is it not possible to update extension attributes of former hybrid users via Graph API?

Lehmann, Oliver 20 Reputation points
2024-07-31T10:36:48.5166667+00:00

We want to update extension attributes (extensionAttribute1 … extensionAttribute15) via Graph API but on a specific set of users we get the following error message:

User's image

In our tenant are two different types of users:

  • Native cloud users
  • Former hybrid users that were fully migrated to cloud users (approved by Microsoft support)

The latter look like this in Entra ID and their extension attributes can not be updated via Graph API:
User's image

According to Graph API documentation: "If a cloud-only user was previously synced from on-premises Active Directory, these properties can't be managed via the Microsoft Graph API. Instead, they can be managed through the Exchange Admin Center or the Exchange Online V2 module in PowerShell."
https://learn.microsoft.com/en-us/graph/api/resources/onpremisesextensionattributes?view=graph-rest-1.0

So there is a workaround but you have to use another module (Exchange Online V2) and manually check each user before updating if they are native cloud users or former hybrid users.

Why does this limitation exist for fully migrated cloud users? Should these users not act like native cloud users? Is it possible to remove this limitation so we can handle all cloud users (native and migrated) identically?

Thank you very much in advance for an answer.

Kind regards

Microsoft Graph
Microsoft Graph
A Microsoft programmability model that exposes REST APIs and client libraries to access data on Microsoft 365 services.
13,296 questions
0 comments No comments
{count} votes

Accepted answer
  1. Vasil Michev 115.6K Reputation points MVP
    2024-07-31T17:46:15.6133333+00:00

    "Because Microsoft hasn't put the work into enabling this scenario" is the best answer I can give you. The are several hybrid/source of authority scenarios they need to address, but progress on that front is being made very slowly (it is a complex task).

    In addition, said attributes have traditionally been part of the Exchange schema, thus are not "native" to Entra/Graph API. So for the time being, you need to use ExO PowerShell to manage them.


1 additional answer

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.