Hi najshahid-san, thank you for providing additional guidance on this matter.
However, it seems that some of the information I am looking for is still missing. Would it be possible to get answers to the following questions?
Scope: All users signing into Azure portal, CLI, PowerShell, or Terraform to administer Azure resources are within the scope of this enforcement.
Specifically, how will it be implemented?
- Through control functions on the Azure side or Entra ID managed conditional access?
Timeline: Beginning July 2024, a gradual rollout of this enforcement for portal only will commence. Once we have completed the rollout for portal, a similar gradual rollout will start for CLI, PowerShell and Terraform. We understand the impact this enforcement could have on automated scripts using user identities and thus are prioritizing enforcement for Azure portal to provide additional time to adapt if needed.
What I need is not a gradual "forced" rollout, but a control option to enable it myself when needed.
Do you plan to provide such a feature?