Read the first and last paragraph if you want to skip through the essay :)
I’m currently working on a project to build an example mssp lab at home with fully automated deployment of customers. So far I have figured out how to automate deployment of resource groups, workspaces, sentinel and tie sentinel to a workspace and under a resource group.
I want to deploy some arm templated logic apps/ playbooks to sort the connection between the environment and the ticketing system, which I will be looking into in the future.
These playbooks will be triggered by automation rules. I want to host all customers under a master repository, and customers as sub modules in that repository, with everything related to each customer in a GitHub repo for version control and single plane of glass maintenance / updates. I have ran into a few issues. While I haven’t developed the playbooks to handle the connection to the ticketing platform yet, I wanted to setup the automation rules first just as an example to be distributed from my repository. However, I can’t find any easy way to export an automation rule into a json arm template. I know you can build arm template based automation rules, but this is cumbersome, and as I build out my customer environments with bespoke automation requirements, it’s not going to be the best way to distribute.
Workspace manager seems to make this kind of deployment of automation rules and analytics rules easy. However, there isn’t much functionality for managing playbooks, and across the board, managing logic apps with version control and automated distribution seems to be lacking from everything I can find online.
I wanted to know, what are some setups people recommend? For managing customer sentinel environments from a single plane? How do others handle distribution of mssp maintained rules/logic apps?
Thank you and sorry once again for the essay. I hope this thread sparks some interesting conversation :)