You could get an inspiration from https://spiffe.io/ https://spiffe.io/ to name things. I would look out how centralized you want things to behave and if you i

You could get an inspiration from https://spiffe.io/ https://spiffe.io/ to name things. I would look out how centralized you want things to behave and if you introduce roadblocks for each team since they can’t work independently any more. Maybe not the team name should be part of your naming but the business case which it is solving. Try to keep an evolutionary architecture. Also ask the question why you have so many shared resources divided by multiple teams. Is there actually another team boundary implicitly defined in your organization by these shared resources?