I'm trying to deploy multiple python runbooks using Azure Automation Account, the python packages used are the same between the runbooks but every runbook corresponds to a different project or initiative. And I'm looking for some architecture design advise here.
So, my question is: Should I create different automation accounts (cause there's not max limit of automation accounts) for every project, in order to maintain the logics separated?
Or should I use the same Automation Account and create different runbooks inside, and try to group similar runbooks logics into the automation account? (the advantage of the latter is that the python packages are loaded only once in one automation account)
Important note: the access permissions will be the same on every runbook, so, permissions wise, there is not problem in creating different or use the same automation account.
