ILB Issue with new VNets created after Azure rolling updates that occurred the last few days

1. We are deploying a cloud service with 2 web role instances and 2 worker role instances.
2. The 2 worker role instances are configured with endpoints on an ILB
3. If we deploy our cloud service to an existing VNet, before the Azure rolling updates the last few days, it works fine.
4. If we deploy our cloud service  to a newly created VNet, after the Azure Rolling Updates the last few days, we get the following error:

VERBOSE: 4:32:26 PM - Begin Operation: Get-AzureDeployment

VERBOSE: 4:32:26 PM - Completed Operation: Get-AzureDeployment

VERBOSE: 4:32:29 PM - Begin Operation: New-AzureDeployment

New-AzureDeployment : BadRequest : Internal Load Balancer usage not allowed for this deployment.

At C:\apps\DeploymentScripts\DeployAzureApplication.ps1:297 char:29

+             $DeployResult = New-AzureDeployment -Verbose -ServiceName $ServiceNa ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : CloseError: (:) [New-AzureDeployment], CloudException

    + FullyQualifiedErrorId : Microsoft.WindowsAzure.Commands.ServiceManagement.HostedServices.NewAzureDeploymentCommand

1. We have tried VNets created with Affinity and Resource Groups same error

Charlie