O365 PowerShell Integration - Long Delay to Allow Device ID

[jeremygould]

We are in the process of configuring PowerShell integration with O365 to migrate from our existing on-prem Exchange/SEG setup. I have noticed that when registering a device it is taking a long time for the Active Sync device ID to become Allowed in O365 (up to 20 minutes). Wondering if this is typical or if there is a way to speed this process up? Thanks.

[talavital]

Did you set your AirWatch environment so Powershell commands will go through your ACC server ?

[sarndt]

This is fairly normal behavior.  The workaround we've put in place is to allow the Boxer client IDs at the Exchange level.  Since we know Boxer will be coming in as managed (both in MDM and standalone scenarios), this is approved from our security team.

[LukeDC]

Yep completely normal. The denial process is immediate in the cloud, but moving back to allow takes awhile. It's like using a credit card, they take your money quick and immediate but a refund takes its sweet time to process