CMDB — 1 CI but multiple change approver groups
In CMDB, they say there has to be 1 CI for 1 instance.
For example, lets say Azure Databricks.
It can have multiple instances owned by many different teams but there should be only 1 CI - Azure Databricks.
Now, different teams are saying they each need to be change approver group on this CI, so they are asking us to create multiple Azure Databricks entries but we know this goes against general CMDB principles.
So, 1 CI but multiple change approver groups.
How do we resolve this dilemma?
Edit - Adding more info below
There is Azure Databricks. There are many teams in the org that use it - Team A, Team B, Team C and so on ............
On Azure Databricks the CI itself, we can specify who is the Change Approver Group.
If Team A is specified as the Change Approver Group, and if you submit a change request with CI field populated as Azure Databricks, then change goes to Team A
The problem is, Team B and Team C are saying we want to submit change request for AZure Databricks, but its going to Team A, so , create another CI and make our team Change Approver Group so that we can approve it.
But, creating multiple CI's for Azure Databricks is not a good idea is what the architect told me. We need to have just 1 CI. Also, our change management process owner had told us we won't run into this situation.1 CI will have 1 team as approver is what they said
How do I deal with this?