Why does Az Powershell require change of varying contexts (e.g. Subscription, Vaults, etc.) where the Portal does not?

[mcdonamw]

Why does Az Powershell require change of varying contexts (e.g. Subscription, Vaults, etc.) where the Portal does not?

I'm trying to move to doing my Azure work via Powershell but I'm finding it a bit annoying, to say the least. Constantly having to switch my subscription context, or vault context to manage backups, etc., is time consuming and adds a lot of code to avoid having to do this if not necessary.

Why is this required in Az Powershell whereas the Portal can simply perform actions without seemingly doing any of this. I can perform an operation regardless of context and it does so very quickly. I assume either way is using the same Azure APIs so wondering why Az Powershell is more limited in this way.

[vidai-msft]

Hi @mcdonamw do you often work under cross-subscription scenarios? If so, we'd like to uderstand your use case. Thanks in advance!