Skip to content

JEA transcripts are hard to read and not user-friendly #4094

Open

Description

@rpsqrd

Note: Ported from bug 9318376

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

Activity

  1. added
    Issue-Enhancementthe issue is more of a feature request than a bug
    and removed
    Needs-TriageThe issue is new and needs to be triaged by a work group.
    on Mar 9, 2021
  2. PaulHigin commented on Jun 21, 2021

    @PaulHigin
    Contributor

    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).

  3. microsoft-github-policy-service commented on Nov 16, 2023

    @microsoft-github-policy-service
    Contributor

    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.

  4. microsoft-github-policy-service commented on Nov 16, 2023

    @microsoft-github-policy-service
    Contributor

    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.

  5. microsoft-github-policy-service commented on Nov 23, 2023

    @microsoft-github-policy-service
    Contributor

    This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes.

  6. MatejKafka commented on Sep 8, 2024

    @MatejKafka
    Contributor

    Ryan Yates (@kilasuit) Please reopen, still relevant.

  7. soroshsabz commented on Sep 25, 2026

    @soroshsabz

    Paul Higinbotham (@PaulHigin) any other plan to make more user friendly?

  8. kilasuit commented on Sep 26, 2026

    @kilasuit
    Collaborator

    soroshsabz Paul has long retired.

    I can reopen this however priority is likely incredibly low for this and other JEA related items

  9. soroshsabz commented on Sep 28, 2026

    @soroshsabz

    Ryan Yates (@kilasuit) thanks

    Do you accept PR for this?

  10. kilasuit commented on Sep 28, 2026

    @kilasuit
    Collaborator

    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

  11. soroshsabz commented on Oct 2, 2026

    @soroshsabz

    What is the name of the person who is a member of the Security WG?

    Thanks :)

  12. kilasuit commented on Oct 4, 2026

    @kilasuit
    Collaborator

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue-Enhancementthe issue is more of a feature request than a bugWG-NeedsReviewNeeds a review by the labeled Working GroupWG-Securitysecurity related areas such as JEA

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions