RunAs Account should not be required. #39
Description
In accordance with our mandated governance standards we do not create Run As accounts for automation accounts. We do not want to grant a Run As account contributor access to a subscription. Please note in Microsoft's documentation "Note that the creation of Run As accounts may affect the security of the subscription". We DO NOT want to have to run this with a Run As account because it will violate our security policies. We HAVE to get Az.Accounts updated to 2.2.8. This is preventing work from moving forward.
Microsoft provided this Automation service and removed the UX capability to update modules. This update script is absolutely terrible. We need to be able to update our modules and cannot. The documentation on this whole process is sparse and poorly written. Are we expected to add credentials to the code you wrote in order to simply update our modules in Azure automation? Then why are you even providing this service? Its easy to setup a similar infrastructure on premise yet here we are paying for a broken service....again.
Running the update module via a runbook this is what is returned
Failed
Connection 'AzureRunAsConnection' not found. (Connection 'AzureRunAsConnection' not found.)
RunAsAccount not found. To create this RunAsAccount, navigate to the RunAsAccount blade and create a RunAsAccount. Refer doc for more details (https://docs.microsoft.com/azure/automation/create-runas-account)
Logging in to Azure (AzureCloud)...
Connection 'AzureRunAsConnection' is incompatible type.