We’ll definitely do this
Thanks for this suggestion! Our team can look into this.
Please add support for this, team. Thank you!
Thanks for the feedback!
This kind of information is sometimes essential, depending on the purpose of the Runbook. Any kind of "meta" Runbooks might need access to these fields:
- The Resource Group Name that the Automation Account belongs to
- The Automation Account that the Runbook belongs to
- The name of the Runbook
- The execution time of the Runbook
- The current Runbook instance's Job ID
- The Azure subscription ID, and name, that the Runbook belongs to
Microsoft MVP: PowerShell
1 vote0 comments · Log Analytics » Agent Management (OnPrem components) / Connectivity / Setup · Flag idea as inappropriate… · Admin →
4 votes0 comments · Networking » Security (ACLs, Firewalls, Intrusion Detection) · Flag idea as inappropriate… · Admin →
Thanks for the feedback, we’ll consider this improvement for future
We can definitely look into this.
Yes, sorry if I wasn't clear enough with my step by step suggestion.
Today, when you open a Resource Group blade, you would potentially do so using the blade that simply lists Resource Groups. When you click on a [source] Resource Group, the Resource Group blade would open, but you'd still have the list of Resource Groups open, to the left.
That would enable you to drag resource(s) from the "source" Resource Group, to a different "destination" Resource Group on the Resource Group list blade, that you started with.
Where can I post a video to demonstrate what I'm after?
We’ve talked about doing this. We’d love to hear more about shortcuts you’re looking for.
Thank you for taking the time to vote on this idea. Could you please provide more details on your ask here as this can be accomplished today.
112 votesunder review · 2 comments · Azure portal » Resource management · Flag idea as inappropriate… · Admin →
Makes sense. For now, you can do this by clicking and dragging on the menu bar that appears when you hover over the tile.