The methods here are still valid for a scenario of delivering under a single tenant, but the Contino requirement required a custom setup, covering the implementation with greater detail in a separate document HERE
_ ____ _ ___ / \ _____ _ _ __ ___ / ___| | |_ _| / _ \ |_ / | | | '__/ _ \ | | | | | / ___ \ / /| |_| | | | __/ |___| |___ | | /_/ \_\/___|\__,_|_| \___|\____|_____|___|
_____ __ |_ _|__ _ __ _ __ __ _ / _| ___ _ __ _ __ ___ | |/ _ \ '__| '__/ _` | |_ / _ \| '__| '_ ` _ \ | | __/ | | | | (_| | _| (_) | | | | | | | | |_|\___|_| |_| \__,_|_| \___/|_| |_| |_| |_|
_ ____ ___ __ ____ ____ / \ | _ \_ _| / / | _ \/ ___| / _ \ | |_) | | / / | |_) \___ \ / ___ \| __/| | / / | __/ ___) | /_/ \_\_| |___| /_/ |_| |____/
Check the :gh: Repository for complete scripts for the steps above and some examples
Check the :gh: Repository for basic to advanced terraform configurations - going from a simple run-local deployment up to remote state, service principal creation, subscription creation and integration plus some enhanced notifications options to ensure new subscription creation visibility
:terraform: azurerm/azurerm_ea_subscription
Check the :gh: and
for using the REST APIs - either calling directly or scripted
