Pool provisioning DSC Extension error ... again

Hi wilsonosorio -

I can't remember my exact scenario now, but this is what it boiled down to for me.

As I was deploying the HostPool, it needs to access the 'azurexxx.net' FQDN that shows up during that DSC extension step.  If there's no name resolution in the subscription, that step will fail.

If you have anything other than an empty subscription (as in, you've been messing with networking settings), then you could have problems as well.  I'm almost positive this is what happened in my original post.  I had a subscription with multiple systems in it:

- couple of networks

- application network gateway

- static IPs on other VMs already in the subscription

- tunneling between this sub and another (before I learned about vnet peering)

I just didn't have a default route defined for the subnet I was using for WVD hostpools.

I've set up multiple hostpools since this time, and it's always worked just fine (with no extra configuration in the subscription for routing/etc).