Session
Hitchhiker's Guide to Multitenant environments
There are very few things more annoying in scripting than wanting to deploy into subscription/tenant A and instead deploying into subscription/tenant B.
When managing Azure Resources in multiple tenants or just in multiple subscriptions for your in-house infrastructure or your own public SaaS offering it is important to only execute commands or scripts in the right context.
With the combination of terminal profiles, PowerShell startup conditions, and customized environment variables we can add guardrails to our everyday working environment to make sure we *not* running our scripts against the wrong environment.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top