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
I don't believe this is an issue with the image itself. However, I wanted to inform you that when attempting to purchase your product within the Azure Marketplace, we receive an HTTP 503 error when deploying your virtual machine
"statusCode": "InternalServerError",
"statusMessage": {
"error": {
"code": "InternalBillingError",
"message": "There was a problem communicating with the billing service. Diagnostic information: timestamp '20190308T202824Z'
I believe this is an issue on MS side of things. However, I wanted you all to be aware of the issue, if you weren't already.
The text was updated successfully, but these errors were encountered:
We believe it is to do with accepting the license agreement for market place purchases. This normally only needs to be done once, per subscription.
If anyone else comes across this, our issue was caused by a new (EA) subscription taking 48 hours to fully provision. Check your subscription quotas. In my experience, when you see them fully populated, you should be good to go.
Microsoft did give us this command to try and speed things up:
AZ CLI: Azure provider register -s <your_subscription> -n Microsoft.Network
(Keep the < and >)
Then you should be able to accept the agreement:
#List URNs
az vm image list --all --publisher $Publisher --offer $offer --sku $sku --query '[].urn
#Accept URN
az vm image accept-terms --urn paloaltonetworks:vmseries1:byol:9.0.1
PA Networks,
I don't believe this is an issue with the image itself. However, I wanted to inform you that when attempting to purchase your product within the Azure Marketplace, we receive an HTTP 503 error when deploying your virtual machine
I believe this is an issue on MS side of things. However, I wanted you all to be aware of the issue, if you weren't already.
The text was updated successfully, but these errors were encountered: