Workspace Role

Great question — this is one of those areas where behavior and documentation can feel a bit out of sync.

You're right that the official documentation states that modifying Spark pool settings requires Admin role in the workspace. You can find that here:
🔗Microsoft Learn 

However, in practice, Contributor role can sometimes modify Spark pool settings if the workspace permissions are loosely scoped or inherited from broader Fabric-level permissions. This might explain why you were able to make changes with Contributor access.

That said, relying on Contributor for this task isn't guaranteed or recommended. Microsoft enforces role-based access control (RBAC) strictly in some environments, especially in enterprise tenants. So while it might work now, it could break later if policies are tightened.

To be safe and compliant with best practices:

• Use Admin role for Spark pool configuration.
• Use Contributor for pipeline, notebook, and dataset development.

Also, here's another helpful doc on Fabric roles and permissions:
🔗 Microsoft Learn 

Let me know if you want to test this behavior in a controlled setup or need help checking your workspace's permission inheritance.

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.

This response was assisted by AI for translation and formatting purposes.