Import certificates created by publish settings
When downloading the publish settings file certificates are created in all of my subscriptions. I can import and use them in the shell, but why cannot I use them as automation assets?
Updating this to be reviewed.
To be transparent, since we are moving to Azure Resource Manager which doesn’t support publish settings files, we will be unlikely to take this request. If this is a real blocker for you, please respond with a bit more detail so we can take a closer look.
Darko Aleksic commented
We have a workaround - everyone can run the script from their local machine.
The idea was to have a runbook that can be run from the automation account (and scheduled if needed). We cannot create a service account and cannot use credentials due to MFA (both by policy), so certificates looked like the only way to use the runbook. Because publish settings already creates certificates in each subscription, why not use those in automation?
If the functionality was there, we would not need the script in the first place - we are trying to reboot all instance of a role (given subscription/service/role). The script uses the update/upgrade domains, similar to Windows Update. If Windows Update can do it, why can't we?
Why would one need to reboot all instances? Good question, but we do :)