[AutoPublish] main to live - 08/05 20:07 PDT | 08/06 08:37 IST

exchange/docs-conceptual/client-advanced-settings.md

@@ -317,11 +317,11 @@ Use this advanced setting in conjunction with *ScannerMinCPU* to limit CPU consu
 
 - Value: \<number>**
 
-The value is set to **100** by default, which means there is no limit of maximum CPU consumption. In this case, the scanner process will try to use all available CPU time to maximize your scan rates.
+The value is set to **100** by default, which means there is no limit of maximum CPU consumption. In this case, the scanner process tries to use all available CPU time to maximize your scan rates.
 
-If you set **ScannerMaxCPU** to less than 100, the scanner will monitor the CPU consumption over the last 30 minutes. If the average CPU crossed the limit you set, it will start to reduce the number of threads allocated for new files.
+If you set **ScannerMaxCPU** to less than 100, the scanner monitors the CPU consumption over the last 30 minutes. If the average CPU crossed the limit you set, it starts to reduce the number of threads allocated for new files.
 
-The limit on the number of threads will continue as long as CPU consumption is higher than the limit set for **ScannerMaxCPU**.
+The limit on the number of threads continues as long as CPU consumption is higher than the limit set for **ScannerMaxCPU**.
 
 ## ScannerMinCPU
 
@@ -334,7 +334,7 @@ Used only if *ScannerMaxCPU* is not equal to 100, and cannot be set to a number
 
 We recommend keeping **ScannerMinCPU** set at least 15 points lower than the value of *ScannerMaxCPU*.
 
-The value is set to **50** by default, which means that if CPU consumption in the last 30 minutes when lower than this value, the scanner will start adding new threads to scan more files in parallel, until the CPU consumption reaches the level you have set for *ScannerMaxCPU*-15.
+The value is set to **50** by default, which means that if CPU consumption in the last 30 minutes when lower than this value, the scanner starts adding new threads to scan more files in parallel, until the CPU consumption reaches the level you have set for *ScannerMaxCPU*-15.
 
 ## ScannerConcurrencyLevel
 
@@ -361,17 +361,17 @@ Set-LabelPolicy -Identity Scanner -AdvancedSettings @{ScannerConcurrencyLevel="8
 
 By default, the information protection scanner scans all relevant files. However, you might want to define specific files to be skipped, such as for archived files or files that have been moved.
 
-Enable the scanner to skip specific files based on their file attributes by using the **ScannerFSAttributesToSkip** advanced setting. In the setting value, list the file attributes that will enable the file to be skipped when they are all set to **true**. This list of file attributes uses the AND logic.
+Enable the scanner to skip specific files based on their file attributes by using the **ScannerFSAttributesToSkip** advanced setting. In the setting value, list the file attributes that enable the file to be skipped when they are all set to **true**. This list of file attributes uses the AND logic.
 
 Example PowerShell commands, where your label policy is named "Global".
 
-**Skip files that are both read-only and archived**
+**Skip files that are both read-only and archived**:
 
 ```PowerShell
 Set-LabelPolicy -Identity Global -AdvancedSettings @{ ScannerFSAttributesToSkip =" FILE_ATTRIBUTE_READONLY, FILE_ATTRIBUTE_ARCHIVE"}
 ```
 
-**Skip files that are either read-only or archived**
+**Skip files that are either read-only or archived**:
 
 To use an OR logic, run the same property multiple times. For example:
 

exchange/docs-conceptual/connect-exo-powershell-managed-identity.md

@@ -68,7 +68,7 @@ The first command in the PowerShell runbook must be the `Connect-ExchangeOnline.
 Connect-ExchangeOnline -ManagedIdentity -Organization contoso.onmicrosoft.com
 ```
 
-After that, as a test, you can start with as simple, low-impact command in the runbook before moving on to more complex commands or scripts. For example:
+After that, as a test, you can start with as simple, low risk command in the runbook before moving on to more complex commands or scripts. For example:
 
 ```powershell
 Get-AcceptedDomain | Format-Table Name
@@ -118,7 +118,7 @@ Connect-ExchangeOnline -ManagedIdentity -Organization contoso.onmicrosoft.com -M
 
 You get the ManagedIdentityAccount value from [Step 3: Store the user-assigned managed identity in a variable](#step-3-store-the-user-assigned-managed-identity-in-a-variable).
 
-After that, as a test, you can start with as simple, low-impact command in the runbook before moving on to more complex commands or scripts. For example:
+After that, as a test, you can start with as simple, low risk command in the runbook before moving on to more complex commands or scripts. For example:
 
 ```powershell
 Get-AcceptedDomain | Format-Table Name
@@ -285,7 +285,7 @@ To verify that the module imported successfully, run the following command:
 Get-AzAutomationModule -ResourceGroupName ContosoRG -AutomationAccountName ContosoAzAuto1 -Name ExchangeOnlineManagement
 ```
 
-During the import, the ProvisioningState property will have the value Creating. When the module import is complete, the value will change to Succeeded.
+During the import, the ProvisioningState property has the value Creating. When the module import is complete, the value changes to Succeeded.
 
 For detailed syntax and parameter information, see [New-AzAutomationModule](/powershell/module/az.automation/new-azautomationmodule).
 

exchange/docs-conceptual/connect-to-exo-powershell-c-sharp.md

@@ -207,7 +207,7 @@ void ParallelConnectionsToExchangeOnline()
 
         // Set the ThreadOptions to reuse the same threads for the runspaces so that
 
-        // the Exchange Online cmdlets will be available after running Connect-ExchangeOnline in each runspace.
+        // the Exchange Online cmdlets are available after running Connect-ExchangeOnline in each runspace.
 
         pool.ThreadOptions = PSThreadOptions.ReuseThread;
 

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

@@ -591,7 +591,7 @@ Unless otherwise noted, the current release of the Exchange Online PowerShell mo
 - **Get-VivaModuleFeature** now returns information about ParentFeature, ChildFeature, and PolicyModes. These values represent parent and child features of a Viva app feature along with available enablement modes for future policies.  
 - New parameters _IsUserOptedInByDefault_ on the **Add-VivaModuleFeaturePolicy** and **Update-VivaModuleFeaturePolicy** cmdlets and the corresponding property value in all **\*-VivaModuleFeaturePolicy** cmdlets. The value indicates if users are opted in or out by the policy, as long as the user doesn't set a preference.
 
-  You can use this parameter to keep the feature enabled in your organization while opting out the impacted users by default, effectively soft disabling the feature for those users.
+  You can use this parameter to keep the feature enabled in your organization while opting out the affected users by default, effectively soft disabling the feature for those users.
 
 - Deprecated the **Get-VivaFeatureCategory** cmdlet, all category-related parameters, and return values (_CategoryId_, _IsCategoryEnabled_).
 

exchange/docs-conceptual/filter-properties.md

@@ -532,7 +532,7 @@ For example, `Get-CASMailbox -Filter 'EcpEnabled -eq $false'`.
 
 For example, `Get-Recipient -Filter "EmailAddresses -like 'marketing*'"`.
 
-When you use a complete email address, you don't need to account for the `smtp:` prefix. If you use wildcards, you do. For example, if `"EmailAddresses -eq '[email protected]'"` returns a match, `"EmailAddresses -like 'lila*'"` won't return a match, but or `"EmailAddresses -like 'smtp:lila*'"` will return a match.
+When you use a complete email address, you don't need to account for the `smtp:` prefix. If you use wildcards, you do. For example, if `"EmailAddresses -eq '[email protected]'"` returns a match, `"EmailAddresses -like 'lila*'"` won't return a match, but `"EmailAddresses -like 'smtp:lila*'"` returns a match.
 
 Although this property is multi-valued, the filter returns a match if the property _contains_ the specified value.
 
@@ -640,7 +640,7 @@ For example, `Get-Recipient -Filter 'ExternalDirectoryObjectId -ne $null'`.
 
 For example, `Get-Recipient -Filter "ExternalEmailAddress -like '@fabrikam.com*'"`.
 
-When you use a complete email address, you don't need to account for the `smtp:` prefix. If you use wildcards, you do. For example, if `"ExternalEmailAddress -eq '[email protected]'"` returns a match, `"ExternalEmailAddress -like 'lila*'"` won't return a match, but `"ExternalEmailAddress -like 'smtp:lila*'"` will return a match.
+When you use a complete email address, you don't need to account for the `smtp:` prefix. If you use wildcards, you do. For example, if `"ExternalEmailAddress -eq '[email protected]'"` returns a match, `"ExternalEmailAddress -like 'lila*'"` won't return a match, but `"ExternalEmailAddress -like 'smtp:lila*'"` returns a match.
 
 ## ExternalOofOptions
 
@@ -684,7 +684,7 @@ To find the distinguished name of a forwarding recipient, replace _\<RecipientId
 
 For example, `Get-Mailbox -Filter "ForwardingSmtpAddress -like '@fabrikam.com*'"`.
 
-When you use a complete email address, you don't need to account for the `smtp:` prefix. If you use wildcards, you do. For example, if `"ForwardingSmtpAddress -eq '[email protected]'"` returns a match, `"ForwardingSmtpAddress -like 'lila*'"` won't return a match, but `"ForwardingSmtpAddress -like 'smtp:lila*'"` will return a match.
+When you use a complete email address, you don't need to account for the `smtp:` prefix. If you use wildcards, you do. For example, if `"ForwardingSmtpAddress -eq '[email protected]'"` returns a match, `"ForwardingSmtpAddress -like 'lila*'"` doesn't return a match, but `"ForwardingSmtpAddress -like 'smtp:lila*'"` returns a match.
 
 ## GeneratedOfflineAddressBooks
 
@@ -734,7 +734,7 @@ For example, `Get-UnifiedGroup -Filter "GroupExternalMemberCount -gt 0"`.
 
 Distribution groups have the value `Universal`, and mail-enabled security groups have the value `Universal, SecurityEnabled`. You can specify multiple values separated by commas, and the order doesn't matter. For example, `Get-DistributionGroup -Filter "GroupType -eq 'Universal,SecurityEnabled'"` returns the same results as `Get-DistributionGroup -Filter "GroupType -eq 'SecurityEnabled,Universal'"`.
 
-This multivalued property will only return a match if the property _equals_ the specified value.
+This multivalued property returns a match only if the property _equals_ the specified value.
 
 ## Guid
 
@@ -978,7 +978,7 @@ This property is named **Languages** in the properties of a mailbox, and it cont
 
 You can specify multiple values separated by commas, but the order matters. For example, `Get-Mailbox -Filter "LanguagesRaw -eq 'en-US,es-MX'"` returns different results than `Get-Mailbox -Filter "LanguagesRaw -eq 'es-MX,en-US'"`.
 
-For single values, this multivalued property will return a match if the property _contains_ the specified value.
+For single values, this multivalued property returns a match only if the property _contains_ the specified value.
 
 ## LastExchangeChangedTime
 
@@ -1058,7 +1058,7 @@ For example, `Get-Mailbox -Filter "MailboxMoveFlags -ne 'None'"`.
 
 You can specify multiple values separated by commas, and the order doesn't matter. For example, `Get-Recipient -Filter "MailboxMoveFlags -eq 'IntraOrg,Pull'"` returns the same results as `Get-Recipient -Filter "MailboxMoveFlags -eq 'Pull,IntraOrg'"`.
 
-This multivalued property will only return a match if the property _equals_ the specified value.
+This multivalued property returns a match only if the property _equals_ the specified value.
 
 ## MailboxMoveRemoteHostName
 
@@ -1514,7 +1514,7 @@ For example, `Get-User -Filter 'PreviousRecipientTypeDetails -ne $null'`.
 |---|---|---|
 |n/a|**Get-CASMailbox** <br/> **Get-DistributionGroup** <br/> **Get-DynamicDistributionGroup** <br/> **Get-Mailbox** <br/> **Get-MailContact** <br/> **Get-MailPublicFolder** <br/> **Get-MailUser** <br/> **Get-Recipient** <br/> **Get-RemoteMailbox** <br/> **Get-UMMailbox** <br/> **Get-UnifiedGroup**|String (wildcards accepted)|
 
-Don't use the _PrimarySmtpAddress_ property; use the _EmailAddresses_ property instead. Any filter that uses the _PrimarySmtpAddress_ property will also search values in the _EmailAddresses_ property. For example, if a mailbox has the primary email address [email protected], and the additional proxy addresses [email protected] and [email protected], all of the following filters will return that mailbox in the result: `"PrimarySmtpAddress -eq '[email protected]'"`, `"PrimarySmtpAddress -eq '[email protected]'"`, or `"PrimarySmtpAddress -eq '[email protected]'"`.
+Don't use the _PrimarySmtpAddress_ property; use the _EmailAddresses_ property instead. Any filter that uses the _PrimarySmtpAddress_ property also searchs values in the _EmailAddresses_ property. For example, if a mailbox has the primary email address [email protected], and the additional proxy addresses [email protected] and [email protected], all of the following filters return that mailbox in the result: `"PrimarySmtpAddress -eq '[email protected]'"`, `"PrimarySmtpAddress -eq '[email protected]'"`, or `"PrimarySmtpAddress -eq '[email protected]'"`.
 
 ## ProhibitSendQuota
 
@@ -2085,7 +2085,7 @@ For example, `Get-User -Filter "UserAccountControl -eq 'NormalAccount'"`.
 
 You can specify multiple values separated by commas, but the order matters. For example, `Get-User -Filter "UserAccountControl -eq 'AccountDisabled,NormalAccount'"` returns different results than `Get-User -Filter "UserAccountControl -eq 'NormalAccount,AccountDisabled'"`.
 
-This multivalued property will only return a match if the property _equals_ the specified value.
+This multivalued property returns a match only if the property _equals_ the specified value.
 
 ## UserPrincipalName
 

exchange/docs-conceptual/recipientfilter-properties.md

@@ -117,7 +117,7 @@ The recipient properties that have been *confirmed* to work with the _RecipientF
 |_EwsApplicationAccessPolicy_|_msExchEwsApplicationAccessPolicy_|`EnforceAllowList` or `EnforceBlockList`.||
 |_EwsEnabled_|_msExchEwsEnabled_|Integer||
 |_ExchangeGuid_|_msExchMailboxGuid_|String (wildcards accepted).||
-|_ExchangeUserAccountControl_|_msExchUserAccountControl_|For valid values, see [ADS_USER_FLAG_ENUM enumeration](/windows/win32/api/iads/ne-iads-ads_user_flag_enum). The integer values will work as described. Most of the text values won't work as described (even if you remove `ADS_UF` and all underscores).||
+|_ExchangeUserAccountControl_|_msExchUserAccountControl_|For valid values, see [ADS_USER_FLAG_ENUM enumeration](/windows/win32/api/iads/ne-iads-ads_user_flag_enum). The integer values work as described. Most of the text values don't work as described (even if you remove `ADS_UF` and all underscores).||
 |_ExchangeVersion_|_msExchVersion_|Dynamic distribution groups: String (wildcards accepted). <br> Others: `ExchangeObjectVersion` values.||
 |_ExpansionServer_|_msExchExpansionServerName_|String (wildcards accepted).||
 |_ExtensionCustomAttribute1_ to _ExtensionCustomAttribute5_|_msExchExtensionCustomAttribute1_ to _msExchExtensionCustomAttribute5_|String (wildcards accepted).|Currently, these attributes aren't useable as filters in Exchange Online. For more information, see [Microsoft Entra Connect Sync: Attributes synchronized to Microsoft Entra ID](/entra/identity/hybrid/connect/reference-connect-sync-attributes-synchronized).|
@@ -223,7 +223,7 @@ The recipient properties that have been *confirmed* to work with the _RecipientF
 |_PostOfficeBox_|_postOfficeBox_|String (wildcards accepted).||
 |_PreviousRecipientTypeDetails_|_msExchPreviousRecipientTypeDetails_|For valid values, see the description of the _RecipientTypeDetails_ parameter in [Get-Recipient](/powershell/module/exchangepowershell/get-recipient).||
 |_PrimaryGroupId_|_primaryGroupId_|Integer|For ___domain users, the value of this property is typically 513, which corresponds to the Domain Users group.|
-|_PrimarySmtpAddress_|n/a|String (wildcards accepted).|Don't use the _PrimarySmtpAddress_ property; use the _EmailAddresses_ property instead. Any filter that uses the _PrimarySmtpAddress_ property will also search values in the _EmailAddresses_ property. For example, if a mailbox has the primary email address [email protected], and the additional proxy addresses [email protected] and [email protected], all of the following filters will return that mailbox in the result: `"PrimarySmtpAddress -eq '[email protected]'"`, `"PrimarySmtpAddress -eq '[email protected]'"`, or `"PrimarySmtpAddress -eq '[email protected]'"`.|
+|_PrimarySmtpAddress_|n/a|String (wildcards accepted).|Don't use the _PrimarySmtpAddress_ property; use the _EmailAddresses_ property instead. Any filter that uses the _PrimarySmtpAddress_ property also searches values in the _EmailAddresses_ property. For example, if a mailbox has the primary email address `[email protected]`, and the additional proxy addresses `[email protected]` and `[email protected]`, all of the following filters return that mailbox in the result: `"PrimarySmtpAddress -eq '[email protected]'"`, `"PrimarySmtpAddress -eq '[email protected]'"`, or `"PrimarySmtpAddress -eq '[email protected]'"`.|
 |_ProhibitSendQuota_|_mDBOverQuotaLimit_|Dynamic distribution groups: A byte quantified size value (for example, `50MB` or `1.5GB`). Unqualified values are treated as bytes. <br> Others: Blank or non-blank.||
 |_ProhibitSendReceiveQuota_|_mDBOverHardQuotaLimit_|Dynamic distribution groups: A byte quantified size value (for example, `50MB` or `1.5GB`). Unqualified values are treated as bytes. <br> Others: Blank or non-blank.||
 |_ProtocolSettings_|_protocolSettings_|String (wildcards accepted).||

exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md

@@ -64,9 +64,9 @@ Add-ADPermission [[-Identity] <ADRawEntryIdParameter>] -Instance <ADAcePresentat
 ```
 
 ## DESCRIPTION
-The ADPermission cmdlets can be used to directly modify Active Directory access control lists (ACLs). Although some Microsoft Exchange features may continue to use the ADPermission cmdlets to manage permissions (for example Send and Receive connectors), Exchange 2013 and later versions no longer use customized ACLs to manage administrative permissions. If you want to grant or deny administrative permissions in Exchange 2013 or later, you need to use Role Based Access Control (RBAC). For more information about RBAC, see [Permissions in Exchange Server](https://learn.microsoft.com/Exchange/permissions/permissions).
+The ADPermission cmdlets can be used to directly modify Active Directory access control lists (ACLs). Although some Microsoft Exchange features might continue to use the ADPermission cmdlets to manage permissions (for example Send and Receive connectors), Exchange 2013 and later versions no longer use customized ACLs to manage administrative permissions. If you want to grant or deny administrative permissions in Exchange 2013 or later, you need to use Role Based Access Control (RBAC). For more information about RBAC, see [Permissions in Exchange Server](https://learn.microsoft.com/Exchange/permissions/permissions).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES