Update: a wonderful mobility tech from my company helped out with some back-end configuration changes to help solve this issue for time being. :-). Seems that the consensus is that the latest Android OS version has some security built in which contradicts the Airwatch Intelligent Hub process. Perhaps the next OS version will solve it, or perhaps not. But this is now a verified issue outside of Pixel phone, as Samsung Galaxy Note users are experiencing it. Thus far, Google & Airwatch have not provided any assistance, so your local IT group will likely have to solve it. I do not have the tech details on how this was solved, unfortunately. Thanks for reading!
Any chance you can get me in contact with them? I can send you my email through message if you can. I'm still fighting this issue and can figure out a fix for it.