Check your Azure Automation Accounts for Run As accounts before they are retired on Sept 30

pwshguy (mdowst)@programming.devM to

Powershell@programming.dev • 1 year ago

0 Comments

This script contains functions to help you identify potential runbooks still using Run As accounts.

gist.github.com

This script contains functions to help you identify potential runbooks still using Run As accounts. - Find-AutomationRunAsAccounts.ps1

Azure Automation Run As Account will retire on September 30, 2023 and will be replaced with Managed Identities. Before that date, you'll need to migrate your runbooks to use managed identities.

However, just the presence of a Run As account doesn’t mean a it is being used. Often these were just created during the automation account provisioning. This script help to determine if you are using the Run As account by search through the runbooks to find references to the Run As Account actually being called. Then finds the last time the runbook was executed. If no date is returned, then the runbook has not executed in the last 30 days.

You must log in or register to comment.

Chat

Powershell@programming.dev

powershell@programming.dev

Create a post

You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !powershell@programming.dev

PowerShell (POSH) is a a task automation command-line shell and scripting language created by Microsoft. It became part of the FOSS community in 2016 and is now available across Windows, Linux, and macOS

Resources:

Install PowerShell – Instructions for Windows, Linux, and macOS
PowerShell Galley Your one-stop shop community and Microsoft modules.
PowerShell Repository – View the PowerShell source code, report issues, or contribute to the project yourself.
PowerShell Community Call – Hear from and talk directly to the product team on the 3rd Thursday of every month
PowerShell in Visual Studio Code – It’s time to say goodbye to ISE

Rules:

Be civil (aka don’t be a jerk). Remember there are people from all walks of life, all with different levels of expertise. You can disagree with someone, but please be civil when doing so.
Adhere to the Lemmy Code of Conduct
Follow all programming.dev rules
Posts must relate to PowerShell or the PowerShell ecosystem.
Use code blocks to make things easier to read.
Memes and humorous posts are allowed but try not over do it. And keep them relevant to PowerShell
No discussion about piracy or hacking.
If someone provides an answer that solves your problem, please reply, so others know what the solution was. ^And ^so ^the ^person ^who ^suggested ^it ^gets ^that ^oh ^so ^sweet ^shot ^of ^dopamine.
If you find a solution to your problem by other means, please take your time to write down the steps you used to solve your problem in the original post. You can potentially help others having the same problem!

Self-promotion rules:

Self-promotion content must be marked as [OC]
Do not SPAM. Content must be PowerShell related.
Only 10% of your contributions can be self-promotion. In other words, 90% of your contribution must not be self-promotion.
Personal blogs are not considered self-promotion, at this time, as long as they are free to access and relevant. Please do not abuse this.

Visibility: Public

This community can be federated to other instances and be posted/commented in by their users.

1 user / day
1 user / week
1 user / month
1 user / 6 months
1 local subscriber
938 subscribers
35 Posts
1 Comment
Modlog