Merge pull request MicrosoftDocs#9745 from MicrosoftDocs/chrisda

CAB updates

Author: chrisda

exchange/docs-conceptual/basic-auth-connect-to-eop-powershell.md

@@ -61,7 +61,7 @@ The following introductory video shows you how to connect to and use Exchange On
 
 - WinRM needs to allow Basic authentication (it's enabled by default). We don't send the username and password combination, but the Basic authentication header is required to send the session's OAuth token, since the client-side WinRM implementation has no support for OAuth.
 
-  **Note**: You must temporarily enable WinRM to run the following commands. You can enable it by running the command: `winrm quickconfig`.
+  **Note**: The following commands require that WinRM is enabled. To enable WinRM, run the following command:  `winrm quickconfig`.
 
   To verify that Basic authentication is enabled for WinRM, run this command **in a Command Prompt** (not in Windows PowerShell):
 

exchange/docs-conceptual/basic-auth-connect-to-exo-powershell.md

@@ -64,7 +64,7 @@ The following introductory video shows you how to connect to and use Exchange On
 
 - WinRM needs to allow Basic authentication (it's enabled by default). We don't send the username and password combination, but the Basic authentication header is required to send the session's OAuth token, since the client-side WinRM implementation has no support for OAuth.
 
-  **Note**: You must temporarily enable WinRM to run the following commands. You can enable it by running the command: `winrm quickconfig`.
+  **Note**: You The following commands require that WinRM is enabled. To enable WinRM, run the following command:  `winrm quickconfig`.
 
   To verify that Basic authentication is enabled for WinRM, run this command **in a Command Prompt** (not in Windows PowerShell):
 

exchange/docs-conceptual/basic-auth-connect-to-scc-powershell.md

@@ -67,7 +67,7 @@ Security & Compliance PowerShell allows you to manage your Microsoft 365 Defende
 
 - WinRM needs to allow Basic authentication (it's enabled by default). We don't send the username and password combination, but the Basic authentication header is required to send the session's OAuth token, since the client-side WinRM implementation has no support for OAuth.
 
-  **Note** You must temporarily enable WinRM to run the following commands. You can enable it by running the command: `winrm quickconfig`.
+  **Note** The following commands require that WinRM is enabled. To enable WinRM, run the following command:  `winrm quickconfig`.
 
   To verify that Basic authentication is enabled for WinRM, run this command **in a Command Prompt** (not in Windows PowerShell):
 

exchange/docs-conceptual/exchange-online-powershell-v2.md

@@ -247,7 +247,7 @@ The EXO V2 module is supported in the following versions of Windows:
   To verify that Basic authentication is enabled for WinRM, run the following command in a **Command Prompt** or **Windows PowerShell**:
 
   > [!NOTE]
-  > You must temporarily enable WinRM to run the following WinRM commands. You can enable WinRM by running the command: `winrm quickconfig`.
+  > The following commands require that WinRM is enabled. To enable WinRM, run the following command:  `winrm quickconfig`.
 
   ```DOS
   winrm get winrm/config/client/auth

exchange/docs-conceptual/v1-module-mfa-connect-to-exo-powershell.md

@@ -44,7 +44,7 @@ If you want to use multi-factor authentication (MFA) to connect to Exchange Onli
 
 - WinRM needs to allow Basic authentication (it's enabled by default). We don't send the username and password combination, but the Basic authentication header is required to send the session's OAuth token, since the client-side WinRM implementation has no support for OAuth.
 
-  **Note**: You must temporarily enable WinRM to run the following commands. You can enable it by running the command: `winrm quickconfig`.
+  **Note**: The following commands require that WinRM is enabled. To enable WinRM, run the following command:  `winrm quickconfig`.
 
   To verify that Basic authentication is enabled for WinRM, run this command **in a Command Prompt** (not in Windows PowerShell):
 

exchange/docs-conceptual/v1-module-mfa-connect-to-scc-powershell.md

@@ -50,7 +50,7 @@ If your account uses multi-factor authentication (MFA) or federated authenticati
 
 - WinRM needs to allow Basic authentication (it's enabled by default). We don't send the username and password combination, but the Basic authentication header is required to send the session's OAuth token, since the client-side WinRM implementation has no support for OAuth.
 
-  **Note**: You must temporarily enable WinRM to run the following commands. You can enable it by running the command: `winrm quickconfig`.
+  **Note**: The following commands require that WinRM is enabled. To enable WinRM, run the following command:  `winrm quickconfig`.
 
   To verify that Basic authentication is enabled for WinRM, run this command **in a Command Prompt** (not in Windows PowerShell):
 

exchange/exchange-ps/exchange/New-MalwareFilterPolicy.md

@@ -525,19 +525,7 @@ This parameter is available only in the cloud-based service.
 
 The FileTypes parameter specifies the file types that are automatically blocked by common attachment blocking (also known as the Common Attachment Types Filter), regardless of content. The default values are:
 
-- ace
-- ani
-- app
-- cab
-- docm
-- exe
-- iso
-- jar
-- jnlp
-- reg
-- scr
-- vbe
-- vbs
+`ace, ani, apk, app, appx, arj, bat, cmd, com, deb, dex, dll, docm, elf, exe, hta, img, jar, kext, lha, lib, library, lnk, lzh, macho, msc, msi, msix, msp, mst, pif, ppa, ppam, reg, rev, scf, scr, sct, sys, uif, vb, vbe, vbs, vxd, wsc, wsf, wsh, xll, xz, z`
 
 You enable or disable common attachment blocking by using the EnableFileFilter parameter.
 

exchange/exchange-ps/exchange/Set-MalwareFilterPolicy.md

@@ -71,11 +71,11 @@ In on-premises Exchange, this example modifies the malware filter policy named C
 ### Example 2
 ```powershell
 $FileTypesAdd = Get-MalwareFilterPolicy -Identity Default | select -Expand FileTypes
-$FileTypesAdd += "com","bat"
+$FileTypesAdd += "dgz","mde"
 Set-MalwareFilterPolicy -Identity Default -EnableFileFilter $true -FileTypes $FileTypesAdd
 ```
 
-This example enables common attachment blocking in the malware filter policy named Default and adds the file types "com" and "bat" without affecting the other file type entries.
+This example enables common attachment blocking in the malware filter policy named Default and adds the file types "dgz" and "mde" without affecting the other file type entries.
 
 ### Example 3
 ```powershell
@@ -551,19 +551,7 @@ This parameter is available only in the cloud-based service.
 
 The FileTypes parameter specifies the file types that are automatically blocked by common attachment blocking (also known as the Common Attachment Types Filter), regardless of content. The default values are:
 
-- ace
-- ani
-- app
-- cab
-- docm
-- exe
-- iso
-- jar
-- jnlp
-- reg
-- scr
-- vbe
-- vbs
+`ace, ani, apk, app, appx, arj, bat, cmd, com, deb, dex, dll, docm, elf, exe, hta, img, jar, kext, lha, lib, library, lnk, lzh, macho, msc, msi, msix, msp, mst, pif, ppa, ppam, reg, rev, scf, scr, sct, sys, uif, vb, vbe, vbs, vxd, wsc, wsf, wsh, xll, xz, z`
 
 You enable or disable common attachment blocking by using the EnableFileFilter parameter.