Hi Ed,
Based on this Github thread, it looks like you got a response to your question after opening a support ticket. Posting your response here to help others who might come across the same issue. Thanks for sharing your response with the rest of the community.
"After opening a ticket, it transpires that some of our app service plans were being deployed to stamps (clusters of servers within datacenters) within East US 2 which didn't support the new preview integration feature. Some stamps do support it, some don't. Hence the inconsistency in our deployment results!
The docs list one of the limitations as:
The feature is only available from newer App Service scale units that support PremiumV2 App Service plans.
However, the only way you can ensure you're on this new infrastructure is if you initially deploy your app service plan as P1v2, P2v2, or P3v2. You can then scale it back down to a standard SKU, if you wish. There's no way to say "I want a Standard sku which supports scaling to a Premium V2 sku."
We've opted to deploy as a P1v2 initially, then use PowerShell to scale back down straight after. You could also use another ARM template, of course, or just do it manually in the portal :)"