Restrict Support Case Creation by Cloud Account or Service
I noticed that there is currently no way to limit which cloud accounts or services a user can create support cases for.
For example, in an organization with multiple teams:
A user from Team A should only be able to create support cases for the cloud accounts or services owned by Team A.
However, today, that same user can open support cases for any cloud account or service across the organization.
While DoiT Organizations can scope access for Cloud Analytics, this scoping does not apply to Support, and there is currently no workaround. As a result, users can unintentionally or incorrectly create support cases for resources they do not own.
This capability would be especially valuable for enterprise customers, where governance and compliance are critical. Beyond controlling what actions users can take, there is also a strong need to control what resources they can see and interact with. Proper segregation of duties is a common compliance requirement, and this feature would help organizations meet those standards more effectively.
Having the ability to restrict support case creation by cloud account and/or service would greatly improve governance, reduce confusion, and align better with enterprise operational models.
Min Htet Htet
shared this idea
We'll work on this idea and then prioritize.