You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 8, 2019. It is now read-only.
I am having trouble with deploying solution to Azure. I cannot find the location/region that would support all the elements needed by myDriving AND MSDN subscription limitations.
Apparently MSDN Enterprise cannot provision sql instances everywhere.
MyDriving\scripts\PowerShell> .\deploy.ps1 "centralus" "IOT-4"
At first, multiple regions I tried did not support IoT or Streaming provisioning.
New-AzureRmResourceGroupDeployment : 14:27:04 - Error: Code=LocationNotAvailableForResourceType; Message=The provided location 'centralus' is not available for resource type 'Microsoft.Devices/IotHubs'. List of available regions for the resource type is 'westus,northeurope,eastasia,eastus,westeurope,southeastasia,japaneast,japanwest,australiaeast,australiasoutheast,westus2,westcentralus'.
New-AzureRmResourceGroupDeployment : 14:29:23 - Error: Code=LocationNotAvailableForResourceType; Message=The provided location 'westcentralus' is not available for resource type 'Microsoft.StreamAnalytics/streamingjobs'. List of available regions for the resource type is 'centralus,westeurope,eastus2,northeurope,japaneast,westus,southeastasia,southcentralus,eastasia,japanwest,northcentralus,eastus,australiaeast,australiasoutheast,brazilsout
h,centralindia'.
When I found one that did, I was greeted with this message:
New-AzureRmResourceGroupDeployment : 14:36:48 - Resource Microsoft.Sql/servers 'mydrivingdbserver-st4lihfvm5z5g' failed with message '{
"code": "45122",
"message": "'MSDN subscriptions are restricted from provisioning in this region. Please choose a different region. For exceptions to this rule please contact Microsoft Support.'",
"target": null,
The text was updated successfully, but these errors were encountered:
We have encountered similar issues when we were deploying to westeurope, so we deployed to northeurope. Not sure about the MSDN account restrictions as we have a different kind of subscription.
No, I did not succeed, I was able to almost deploy to westus when I edited script and changed hard-coded "centralus" to "westus" value for (I think) machine learning. (In script there was a comment that only centralus supports it, which is not true)
I am having trouble with deploying solution to Azure. I cannot find the location/region that would support all the elements needed by myDriving AND MSDN subscription limitations.
Apparently MSDN Enterprise cannot provision sql instances everywhere.
Below is my question from MSFT forums.
https://social.msdn.microsoft.com/Forums/azure/en-US/59535998-7fd9-4e41-9eae-60696768af59/cannot-deploy-mydriving-to-msdn-enterprise-subscription?forum=azureiothub
The text was updated successfully, but these errors were encountered: