The Azure Subscription Builder project allows an Enterprise Account owner to quickly deploy secure, policy compliant, Azure Subscriptions. The solution consists of a Front End HTTP trigger, a Logic App Workflow, Azure Automation Account/Runbooks, Blueprints, and CosmosDB. The front end passes variables to the Logic App workflow URI via HTTP Post, details are covered in a dedicated section below. Currently, a sample static web front end is defined as an option in this project. Since the solution leverages a RESTful HTTP trigger, you can bring your own front end such as a PowerApp or a Github Action. The Logic App then takes the variables and passes them as parameters when invoking a set of Azure Automation Runbooks. The first runbook called create-mgmt-group creates a management group (if it already does not exist) to place the subscriptions under. The second runbook called create-subscription creates the subscriptions and places them under the previously created management group. The last runbook called assign-blueprintassigns the desired blueprint to the newly created subscriptions. This helps to ensure that proper policy and governance is enforced on new subscriptions at the time of build
MIT License
24
stars
19
forks
source link
Subscription Create API rate limiting (status code 429) #15
when increasing volumes of requests are sent, the create subscription API is throwing a 429 (rate limiting). we need to incorporate retry and exponential backoff
elnica6-zz
commented
4 years ago
when increasing volumes of requests are sent, the create subscription API is throwing a 429 (rate limiting). we need to incorporate retry and exponential backoff