Removing process scope

[20shivangi]

Task name: AzurePowerShellV4/V5

Description: Removing process scope from set-azcontext

[bergmeister]

I see this is a revert of #13336 , which caused PSJobs to inherit the authentication any more. Can you please prioritise the rollout of those new task versions @20shivangi @chshrikh @buckh as pipelines have been broken for several days now due to that.

[chshrikh]

@bergmeister sorry for the inconvenience, the roll back fix deployment is in-progress, it should get deployed in 3-4 days to all rings

[bergmeister]

@chshrikh Thank you for the update. However, I think 3-4 days are a very long time for a simple rollback that does not conflate with other changes, especially given that the bug has been in production for several days now. The impact is quite severe because for example existing scripts that use Az cmdlets in PowerShell Jobs are completely broken and according to issue #13329 it even seems that some cmdlets like Switch-AzWebAppSlot are broken because of that, that heavily affect production.
I understand why you want to have a slow ring deployment rollout concept but when it comes to a rollback just the last change, I do not see it as necessary to go through the same procedure and would warrant an expedited deployment. The whole concept of DevOps is to deploy often and in small amounts (which you do) but if things go wrong, then one also needs to be quick to rollback quickly, which I do not see. I would be an understanding if a rollback would also mean other changes would get rolled back but in this instance, it is a rollback of a single change that should be expedited.

[bergmeister]

@chshrikh I can see, the patched versions got deployed this morning, many thanks for expediting the rollback 😀
Please make sure there are regression test for this, especially using PowerShell jobs (which are process based) in the AzurePowerShell tasks.