Skip to content

Add notes about TypeData and FormatData commands #13094

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sdwheeler wants to merge 2 commits into
base: main
Choose a base branch
from
+36 −8
Open

Add notes about TypeData and FormatData commands #13094

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f2bb6f4
Add notes about TypeData and FormatData commands
sdwheeler Jun 17, 2026
335452c
Apply suggestions from code review
sdwheeler Jun 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 11 additions & 5 deletions reference/7.4/Microsoft.PowerShell.Utility/Update-FormatData.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
external help file: Microsoft.PowerShell.Commands.Utility.dll-Help.xml
Locale: en-US
Module Name: Microsoft.PowerShell.Utility
ms.date: 12/12/2022
ms.date: 06/17/2026
online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/update-formatdata?view=powershell-7.4&WT.mc_id=ps-gethelp
schema: 2.0.0
title: Update-FormatData
Expand Down Expand Up @@ -192,10 +192,16 @@ This cmdlet returns no output.

## NOTES

- `Update-FormatData` also updates the formatting data for commands in the session that were
imported from modules. If the formatting file for a module changes, you can run an
`Update-FormatData` command to update the formatting data for imported commands. You do not need
to import the module again.
`Update-FormatData` also updates the formatting data for commands in the session that were imported
from modules. If the formatting file for a module changes, you can run an `Update-FormatData`
command to update the formatting data for imported commands. You do not need to import the module
again.

> [!WARNING]
> Restricted endpoints, such as JEA, must not expose the `Update-FormatData` command. This command
> allows you to add **ScriptBlock** elements to the formatting for a type. The **ScriptBlock** is
> evaluated in `FullLanguage` mode, even when the session is configured to use a more restrictive
> language mode.

## RELATED LINKS

Expand Down
8 changes: 7 additions & 1 deletion reference/7.4/Microsoft.PowerShell.Utility/Update-TypeData.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
external help file: Microsoft.PowerShell.Commands.Utility.dll-Help.xml
Locale: en-US
Module Name: Microsoft.PowerShell.Utility
ms.date: 01/18/2026
ms.date: 06/17/2026
online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/update-typedata?view=powershell-7.4&WT.mc_id=ps-gethelp
schema: 2.0.0
title: Update-TypeData
Expand Down Expand Up @@ -900,6 +900,12 @@ This cmdlet returns no output.

## NOTES

> [!WARNING]
> Restricted endpoints, such as JEA, must not expose the `Update-TypeData` command. This command
> allows you to add **ScriptProperty** members to types. The **ScriptProperty** members are
> evaluated in `FullLanguage` mode, even when the session is configured to use a more restrictive
> language mode.

## RELATED LINKS

[about_Types.ps1xml](../Microsoft.PowerShell.Core/About/about_Types.ps1xml.md)
Expand Down
10 changes: 9 additions & 1 deletion reference/docs-conceptual/security/remoting/jea/security-considerations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
description: >-
Since JEA allows these users to run administrative commands without having full administrator
access, you can then remove those users from highly privileged security groups.
ms.date: 01/26/2026
ms.date: 06/17/2026
title: JEA Security Considerations
---
# JEA Security Considerations
Expand Down Expand Up @@ -199,6 +199,14 @@ configured session.
> PowerShell. Don't allow any commands that would run via the Windows Compatibility feature. The
> `*-Job` cmdlets can create new runspaces without the restrictions.

### Don't allow commands that add TypeData or FormatData

Restricted endpoints must not expose the `Update-TypeData`, `Remove-TypeData`, or
`Update-FormatData` commands. The `*-TypeData` commands allow you to add **ScriptProperty** members
to types. The `Update-FormatData` command allows you to add **ScriptBlock** definitions to create
custom formatting. The **ScriptProperty** and **ScriptBlock** members are evaluated in
`FullLanguage` mode, even when the session is configured to use a more restrictive language mode.

### Don't allow the `Trace-Command` cmdlet.

> [!WARNING]
Expand Down
10 changes: 9 additions & 1 deletion reference/docs-conceptual/security/securing-restricted-sessions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
description: This article explains how to secure a restricted PowerShell session that is used for secure remote access.
ms.date: 01/26/2026
ms.date: 06/17/2026
title: Securing a restricted PowerShell remoting session
---
# Securing a restricted PowerShell remoting session
Expand Down Expand Up @@ -43,6 +43,14 @@ restricted session implementation.
> PowerShell. Don't allow any commands that would run via the Windows Compatibility feature. The
> `*-Job` cmdlets can create new runspaces without the restrictions.

### Don't allow commands that add TypeData or FormatData

Restricted endpoints must not expose the `Update-TypeData`, `Remove-TypeData`, or
`Update-FormatData` commands. The `*-TypeData` commands allow you to add **ScriptProperty** members
to types. The `Update-FormatData` command allows you to add **ScriptBlock** definitions to create
custom formatting. The **ScriptProperty** and **ScriptBlock** members are evaluated in
`FullLanguage` mode, even when the session is configured to use a more restrictive language mode.

### Don't allow the `Trace-Command` cmdlet.

> [!WARNING]
Expand Down