You would think that with so much on the cloud and often nearly all within one ecosystem that de-bugging modern application connectivity and integrations would be a simple thing but you would be very, very wrong.
The huge level of complexity and granularity of control has just meant that de-bugging is now a multi person nightmare in any decent sized Corporation.
Successful debugging usually requires particularly gifted or knowledgeable people, and doing it can become an all consuming part of their jobs.
One of the most unexpectedly difficult parts of the process is the restricted nature of performing tests, running trace routes or even seeing logs and configurations.
This lack of transparency can quite literally cost you months of work trying to get to the right people to do something that should take 60 minutes as you try to get all the right people on one call, To fix this I personally recommend any large scale corporation have a general technical access group with a very good read level, it should span across all infrastructure and be able to see everything that is not implicitly secure (such as human user activity). It should be able to see the configuration to all aspects of your infrastructure: proxies, firewall or cloud objects. Everything that does not contain something that is justifiably secure.
This aids senior technicians in debugging so much it’s untrue. it is embarrassing the difference it can make to the speed of delivery of a feature. It also leads to far less finger pointing, Teflon shouldering and “oh it can’t be our part” excuses as you have log evidence.
Lastly and quite strangely different people can get hot and cross over the group name (I have no idea why) , so I have found the name:
“Resolver Read Access” seems to keep things calm and on point.