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
Creating a Enterprise Dev/Test subscription with New-AzSubscription with Operation: Badrequest #13600
Comments
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @anuragdalmia, @ShilpiGautam, @ramaganesan-rg. Issue DetailsRun this from an ADO pipeline on our release server: That give this error: Normal enteprise agreements with offertype MS-AZR-0017P don't fail and succeeded in creating. We are using version 0.7.3 of the Az.Subscription module, because the cmdlet is missing is 0.8.0. By the way, I don't get the reason behinding changing the New-AzSubscription command, because New-AzSubscription worked perfect for us.
|
@guidovbrakel , could you share your debug log? You can enable it via |
See below 2020-11-30T09:45:43.2346868Z |
We fixed it ourselves, we granted the enrollment the necessary permissions and now it works |
@guidovbrakel can you provide some context of what necessary permissions you added? |
Run this from an ADO pipeline on our release server:
New-AzSubscription -OfferType MS-AZR-0148P -Name $Sub.SubscriptionName -EnrollmentAccountObjectId $EnrollAccObjId -OwnerObjectId $OwnerObjId
That give this error:
2020-11-27T12:12:45.1499038Z ##[error]Operation returned an invalid status code 'BadRequest'
2020-11-27T12:12:45.3506619Z ##[error]PowerShell exited with code '1'.
Normal enteprise agreements with offertype MS-AZR-0017P don't fail and succeeded in creating.
We are using version 0.7.3 of the Az.Subscription module, because the cmdlet is missing is 0.8.0. By the way, I don't get the reason behinding changing the New-AzSubscription command, because New-AzSubscription worked perfect for us.
The text was updated successfully, but these errors were encountered: