-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Microsoft.Subscription
- Failed to create alias subscription
#21924
Comments
@ms-zhenhua We are looking into it and get back to you for any additional information. |
I'm also having this problem when deploying a bicep file. Initially, I created a subscription alias and it worked just fine. I then tried to check if subscriptions are idempotent and ran the deployment of the bicep file again with the exact same parameters a few minutes after it had completed, and everything worked: nothing changed with respect to the subscription (so I guess it's idempotent). I then went and worked on some other code for a while, then tried to deploy the bicep file again: Now I'm getting that same 429 error that just simply says:
I can deploy any of my other bicep files it should be noted. I can even move that initially created subscription to other management groups if I want. The weird thing is, when I deploy the bicep file via PowerShell, it just hangs for what looks like 30m and doesn't give any meaningful error result. I had to look in the portal under deployments for the management group the subscription was deployed to for details, which let me abort the deployment early. I also get the above if I try and deploy a new subscription via my bicep file with different parameters. I now seem to be stuck with being unable to make any via deployment. It should be noted I only have 2 active MCA subscriptions and 2 disabled MCA ones using the Microsoft Azure Plan. In case it's of any use, this is all that's in my create subscription bicep file (minus the parameter declarations):
And this is how I'm deploying the script with my admin account:
I then waited 2 hours or so and tried to manually make a subscription in the portal and was denied: I got the message " subscription is not created When viewing that link, it says for MCA customers you can have a max of 5 subscriptions in an MCA purchased directly through Azure.com: I have 4 as mentioned: 2 active, 2 disabled (can't delete them yet, need to wait 3 days). So if this really is a "you have made too many subscriptions" problem, should I still be able to create 1 more if the limit is 5? Furthermore, shouldn't the New-AzManagementGroupDeployment command not wait like half an hour and instead be able to see that 429 error (which I can almost immediately in the portal) and abort earlier and inform me of the same message that I see in the portal? Instead, if I let it run 30m or whatever, I get this incorrect error message:
|
Any updates on this? |
bump, this is a pretty serious issue, one that causes substantial roadblocks with development. If it's a bug, it should be fixed. If it's working as intended, it seems there could be better documentation on this topic as well as better error information, especially deploying the actual bicep file: instead of waiting 30m or so, like I originally mentioned, the portal seems to be able to detect a problem nearly instantly so the deployment program should be able to. And ideally the error output would be more meaningful to help diagnose. |
Yes... this is very unclear.
When deploying ACF templates, we need at least 4 clean subs to work with in the first place? |
Thanks for sharing that - seriously backwards by Azure... what on earth |
Hi, our customer got the following error when creating an alias subscription with the PUT API, could someone kindly help have a check?
The text was updated successfully, but these errors were encountered: