Fabric identities - Confusion between Object_ID and Service Principal ID ?

[vivien57]

Hello everyone,

We are starting to use Workspace Identity, but we have just noticed something strange.

What is listed in the "Service Principal ID" column is the "Object_ID" when we look in Entra ID.

So it seems that since Fabric, we no longer have access to the "Service Principal ID".

Are you experiencing the same issue?

Thank you in advance for your feedback,

Have a nice day,

Vivien

[V-yubandi-msft]

Hi @vivien57 ,

Thank you for reaching out to the Microsoft Fabric Community. With the current design of Fabric Workspace Identity, this behavior is expected.

For workspace identities, Fabric sets up a managed service principal in Microsoft Entra ID and uses the Object ID for authorization and RBAC. That’s why the Service Principal ID matches the Object ID in Entra ID.

The Application (Client) ID isn’t shown in the Fabric UI for workspace identities since it’s not needed in these cases. In most scenarios, such as assigning permissions to ADLS Gen2 or SQL, the Object ID is the correct identifier to use. If you need to find the Application (Client) ID, you can view it in Entra ID under Enterprise Applications by searching for the workspace identity.

I hope this clarifies the situation. Please let me know if I’ve misunderstood anything, and feel free to ask if you have any additional questions.

[vivien57]

Hello @V-yubandi-msft ,

Thank you for your feedback. Yes, I understand.

However, for example, when granting authorisation on Dataverse (D365), the object_id does not work. And we do not always have the necessary rights on Entra ID to retrieve the "Service Principal ID".

However, shouldn't the column still be called ‘Object ID’ to avoid confusion?

Is there a plan in the roadmap to display the ‘Service Principal ID’ as visible in Entra ID, in Fabric ?

Thank you in advance,

Vivien

[V-yubandi-msft · Accepted solution]

Hi @vivien57 ,

Thank you for clarifying. I understand your concern, and it makes sense.

For services like Dataverse, permissions use the Application (Client) ID rather than the Object ID. In these cases, the Workspace Identity value shown in Fabric isn’t usable, which is a current limitation especially if you can’t access Entra ID to find it.

I also agree about the column name. Since it shows the Object ID, calling it Service Principal ID can be misleading. 

Currently, there’s no public update about showing the Application (Client) ID in the Fabric UI for Workspace Identities. The only way to access it remains through Entra ID, typically with an Entra adminsassistance.

Regards,

Yugandhar.

[vivien57]

Thank you, i have created an idea : https://community.fabric.microsoft.com/t5/Fabric-Ideas/Fabric-Identities-Making-the-Service-Principa...