Azure Automation : Job Details showing as null in powershell

Kenneth 66 Reputation points
2022-09-06T19:49:46.163+00:00

While building with Azure Automation, I noticed that certain fields of the object returned by Get-AzAutomationJob in powershell are always null. Here is an example:

238344-image.png

The JobParameters and StartedBy fields always return null, regardless of the actual job implementation. If the job is scheduled, null. If the job is manually run, null. With or without parameters, still null. Is this by design, or is this a known issue?

Azure Automation
Azure Automation
An Azure service that is used to automate, configure, and install updates across hybrid environments.
0 comments No comments
{count} votes

Accepted answer
  1. Maxim Sergeev 6,586 Reputation points Microsoft Employee
    2022-09-06T22:07:49.39+00:00

    Hi @Kenneth

    Yes, this is an expected behavior.
    It resulted from the GDPR work that was done a few years back. At the time it was decided that Automation should not audit/store personal data as Activity Logs already provide auditing capabilities.


2 additional answers

Sort by: Most helpful
  1. Michael Seidl | au2mator 5 Reputation points MVP
    2025-08-06T04:57:35.1966667+00:00

    Hi, that is not correct, when you run the Get-AzAutomationJob with a specific ID like

    "Get-AZAutomationJob -AutomationAccountName $AutomationAccount -resourceGroupNAme $ResourceGroupName -JobID 8d64a149-bff1-484f-a436-f0b4f3665b68"

    You get all those Details you asked for

    User's image

    Michael Seidl
    au2mator

    1 person found this answer helpful.
    0 comments No comments

  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.