You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
JEA transcripts are hard to read and not user-friendly #4094
JEA transcripts, unlike regular PowerShell session transcripts, output all of the session information unformatted. That means that auditors trying to read a JEA transcript have to parse together the output to understand what command a user invoked rather than just seeing exactly what the user ran. The request is to try and simplify the JEA transcript format so that it is similar to the standard transcript format.
Example of a standard transcript file for someone who ran Get-Service Dns:
PS C:\Users\Administrator> Get-Service Dns
Status Name DisplayName
------ ---- -----------
Running dns DNS Server
Example of a JEA transcript for the same command:
PS>CommandInvocation(Get-Service): "Get-Service"
>> ParameterBinding(Get-Service): name="Name"; value="Dns"
>> CommandInvocation(Out-Default): "Out-Default"
>> ParameterBinding(Out-Default): name="InputObject"; value="Dns"
Running Dns DNS Server
WG-Security:
Format-Table is not allowed in a basic JEA session, because the command is not considered secure. This effort would be to make the cmdlet secure (which is not trivial).
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
Reacted by Mr Beedell, Roke Julian Lockhart
microsoft-github-policy-service commented on Nov 23, 2023
Activity
PaulHigin commentedon Jun 21, 2021
WG-Security:
Format-Table is not allowed in a basic JEA session, because the command is not considered secure. This effort would be to make the cmdlet secure (which is not trivial).
microsoft-github-policy-service commentedon Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 23, 2023
This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes.
MatejKafka commentedon Sep 8, 2024
Ryan Yates (@kilasuit) Please reopen, still relevant.
soroshsabz commentedon Sep 25, 2026
Paul Higinbotham (@PaulHigin) any other plan to make more user friendly?
kilasuit commentedon Sep 26, 2026
soroshsabz Paul has long retired.
I can reopen this however priority is likely incredibly low for this and other JEA related items
soroshsabz commentedon Sep 28, 2026
Ryan Yates (@kilasuit) thanks
Do you accept PR for this?
kilasuit commentedon Sep 28, 2026
That would have to be up to the Security WG to decide about. I'm not part of that Group so I can't say I'm afraid soroshsabz
soroshsabz commentedon Oct 2, 2026
What is the name of the person who is a member of the Security WG?
Thanks :)
kilasuit commentedon Oct 4, 2026
This issue is marked for that working group to review, so they'll come back to this issue with a response, when they review it.
soroshsabz commentedon Oct 7, 2026
Start-Transcriptprevents prompts appearing. #26834 - check similar use case in remoting