No, these changes were to allow a user to specify an affinity group and virtual network when provisioning a vm with Vagrant. The affinity group code was already there, but didn't function properly so I fixed it (see the commit comments). I added the virtual network piece because I needed it. 

Js

Sent from my iPhone

> On May 6, 2014, at 12:24 AM, Ramakrishnan <notifications@github.com> wrote:
> 
> In lib/vagrant-azure/action/run_instance.rb:
> 
> >  
> > +          options[:virtual_network_name] = config.virtual_network_name unless \
> > +            config.virtual_network_name.nil?
> > +          options[:affinity_group_name] = config.vm_affinity_group unless \
> > +            config.vm_affinity_group.nil?
> Is this change made to fix any issues with chef-solo?
> 
> —
> Reply to this email directly or view it on GitHub.