Skip to content

Commit 0ad67c7

Browse files
committed
Feeback edits
1 parent 588434a commit 0ad67c7

6 files changed

Lines changed: 23 additions & 13 deletions

File tree

reference/7.4/Microsoft.PowerShell.Core/About/about_Language_Modes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
description: Explains language modes and their effect on PowerShell sessions.
33
Locale: en-US
4-
ms.date: 01/23/2026
4+
ms.date: 01/26/2026
55
no-loc: [FullLanguage, ConstrainedLanguage, RestrictedLanguage, NoLanguage]
66
online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_language_modes?view=powershell-7.4&WT.mc_id=ps-gethelp
77
schema: 2.0.0

reference/7.5/Microsoft.PowerShell.Core/About/about_Language_Modes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
description: Explains language modes and their effect on PowerShell sessions.
33
Locale: en-US
4-
ms.date: 01/23/2026
4+
ms.date: 01/26/2026
55
no-loc: [FullLanguage, ConstrainedLanguage, RestrictedLanguage, NoLanguage]
66
online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_language_modes?view=powershell-7.5&WT.mc_id=ps-gethelp
77
schema: 2.0.0

reference/7.6/Microsoft.PowerShell.Core/About/about_Language_Modes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
description: Explains language modes and their effect on PowerShell sessions.
33
Locale: en-US
4-
ms.date: 01/23/2026
4+
ms.date: 01/26/2026
55
no-loc: [FullLanguage, ConstrainedLanguage, RestrictedLanguage, NoLanguage]
66
online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_language_modes?view=powershell-7.6&WT.mc_id=ps-gethelp
77
schema: 2.0.0

reference/docs-conceptual/security/app-control/application-control.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
description: This article explains the features of Application Control that can be used to secure your PowerShell environment.
3-
ms.date: 12/09/2025
3+
ms.date: 01/26/2026
44
title: Use App Control to secure PowerShell
55
---
66
# Use App Control to secure PowerShell
@@ -26,11 +26,13 @@ following name format:
2626
- `$Env:TEMP/__PSScriptPolicyTest_<random-8dot3-name>.ps1`
2727
- `$Env:TEMP/__PSScriptPolicyTest_<random-8dot3-name>.psm1`
2828

29-
App Control for Business is the preferred application control system for Windows. App Control
30-
provides APIs that allow you to discover the policy configuration. App Control is designed as a
31-
security feature under the servicing criteria defined by the Microsoft Security Response Center
32-
(MSRC). For more information, see [Application Controls for Windows][04] and
33-
[App Control and AppLocker feature availability][02].
29+
App Control for Business is the preferred application control system for Windows. App Control puts
30+
the system into System Lockdown mode. System Lockdown mode is the feature that detects the policies
31+
and determines if a context needs to be initialized or changed to a specific language mode.
32+
33+
App Control is designed as a security feature under the servicing criteria defined by the Microsoft
34+
Security Response Center (MSRC). For more information, see [Application Controls for Windows][04]
35+
and [App Control and AppLocker feature availability][02].
3436

3537
> [!NOTE]
3638
> When [choosing between App Control or AppLocker][03], we recommend that you implement application

reference/docs-conceptual/security/remoting/jea/security-considerations.md

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
description: >-
33
Since JEA allows these users to run administrative commands without having full administrator
44
access, you can then remove those users from highly privileged security groups.
5-
ms.date: 10/10/2023
5+
ms.date: 01/26/2026
66
title: JEA Security Considerations
77
---
88
# JEA Security Considerations
@@ -102,8 +102,16 @@ access to all mapped users. For example, a JEA session configured using the foll
102102
grants full access to `CONTOSO\JEA_Lev1` and `CONTOSO\JEA_Lev2`.
103103

104104
```powershell
105-
$roles = @{ 'CONTOSO\JEA_Lev1' = 'Lev1Role'; 'CONTOSO\JEA_Lev2' = 'Lev2Role' }
106-
New-PSSessionConfigurationFile -Path '.\jea.pssc' -SessionType RestrictedRemoteServer -RoleDefinitions $roles -RunAsVirtualAccount
105+
$newPSSessionConfigurationFileSplat = @{
106+
Path = '.\jea.pssc'
107+
SessionType = 'RestrictedRemoteServer'
108+
RoleDefinitions = @{
109+
'CONTOSO\JEA_Lev1' = 'Lev1Role'
110+
'CONTOSO\JEA_Lev2' = 'Lev2Role'
111+
}
112+
RunAsVirtualAccount = $true
113+
}
114+
New-PSSessionConfigurationFile @newPSSessionConfigurationFileSplat
107115
Register-PSSessionConfiguration -Path '.\jea.pssc' -Name 'MyJEAEndpoint'
108116
```
109117

reference/docs-conceptual/security/securing-restricted-sessions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
description: This article explains how to secure a restricted PowerShell session that is used for secure remote access.
3-
ms.date: 10/10/2023
3+
ms.date: 01/26/2026
44
title: Securing a restricted PowerShell remoting session
55
---
66
# Securing a restricted PowerShell remoting session

0 commit comments

Comments
 (0)