diff --git a/exchange/docs-conceptual/client-advanced-settings.md b/exchange/docs-conceptual/client-advanced-settings.md index 965318b2df..4ef196f94f 100644 --- a/exchange/docs-conceptual/client-advanced-settings.md +++ b/exchange/docs-conceptual/client-advanced-settings.md @@ -317,11 +317,11 @@ Use this advanced setting in conjunction with *ScannerMinCPU* to limit CPU consu - Value: \** -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: diff --git a/exchange/docs-conceptual/connect-exo-powershell-managed-identity.md b/exchange/docs-conceptual/connect-exo-powershell-managed-identity.md index 5266f57d04..8baf75ef9f 100644 --- a/exchange/docs-conceptual/connect-exo-powershell-managed-identity.md +++ b/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). diff --git a/exchange/docs-conceptual/connect-to-exo-powershell-c-sharp.md b/exchange/docs-conceptual/connect-to-exo-powershell-c-sharp.md index f34a86b8d1..f372350e60 100644 --- a/exchange/docs-conceptual/connect-to-exo-powershell-c-sharp.md +++ b/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; diff --git a/exchange/docs-conceptual/exchange-online-powershell-v2.md b/exchange/docs-conceptual/exchange-online-powershell-v2.md index f149901408..0f362ffe35 100644 --- a/exchange/docs-conceptual/exchange-online-powershell-v2.md +++ b/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_). diff --git a/exchange/docs-conceptual/filter-properties.md b/exchange/docs-conceptual/filter-properties.md index c351b83884..12f17e81b9 100644 --- a/exchange/docs-conceptual/filter-properties.md +++ b/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 'lila@fabrikam.com'"` 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 'lila@fabrikam.com'"` 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 'lila@fabrikam.com'"` 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 'lila@fabrikam.com'"` 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 _\ **Get-DistributionGroup**
**Get-DynamicDistributionGroup**
**Get-Mailbox**
**Get-MailContact**
**Get-MailPublicFolder**
**Get-MailUser**
**Get-Recipient**
**Get-RemoteMailbox**
**Get-UMMailbox**
**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 dario@contoso.com, and the additional proxy addresses dario2@contoso.com and dario3@contoso.com, all of the following filters will return that mailbox in the result: `"PrimarySmtpAddress -eq 'dario@contoso.com'"`, `"PrimarySmtpAddress -eq 'dario2@contoso.com'"`, or `"PrimarySmtpAddress -eq 'dario3@contoso.com'"`. +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 dario@contoso.com, and the additional proxy addresses dario2@contoso.com and dario3@contoso.com, all of the following filters return that mailbox in the result: `"PrimarySmtpAddress -eq 'dario@contoso.com'"`, `"PrimarySmtpAddress -eq 'dario2@contoso.com'"`, or `"PrimarySmtpAddress -eq 'dario3@contoso.com'"`. ## 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 diff --git a/exchange/docs-conceptual/recipientfilter-properties.md b/exchange/docs-conceptual/recipientfilter-properties.md index f94d2a8186..6e2a411bad 100644 --- a/exchange/docs-conceptual/recipientfilter-properties.md +++ b/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).
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 dario@contoso.com, and the additional proxy addresses dario2@contoso.com and dario3@contoso.com, all of the following filters will return that mailbox in the result: `"PrimarySmtpAddress -eq 'dario@contoso.com'"`, `"PrimarySmtpAddress -eq 'dario2@contoso.com'"`, or `"PrimarySmtpAddress -eq 'dario3@contoso.com'"`.| +|_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 `dario@contoso.com`, and the additional proxy addresses `dario2@contoso.com` and `dario3@contoso.com`, all of the following filters return that mailbox in the result: `"PrimarySmtpAddress -eq 'dario@contoso.com'"`, `"PrimarySmtpAddress -eq 'dario2@contoso.com'"`, or `"PrimarySmtpAddress -eq 'dario3@contoso.com'"`.| |_ProhibitSendQuota_|_mDBOverQuotaLimit_|Dynamic distribution groups: A byte quantified size value (for example, `50MB` or `1.5GB`). Unqualified values are treated as bytes.
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.
Others: Blank or non-blank.|| |_ProtocolSettings_|_protocolSettings_|String (wildcards accepted).|| diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md index 0f883fb2c0..9b7f139ea5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md @@ -64,9 +64,9 @@ Add-ADPermission [[-Identity] ] -Instance -ForestNam ## DESCRIPTION In Exchange Online, you need to run the New-AvailabilityConfig cmdlet before you run the Add-AvailabilityAddressSpace cmdlet. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md b/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md index 6065a9815c..7e7cef98c9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md @@ -32,7 +32,7 @@ Add-ContentFilterPhrase [-Phrase] -Influence ## DESCRIPTION The Add-ContentFilterPhrase cmdlet adds phrases to the Allow or Block phrases list. -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 @@ -41,7 +41,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Add-ContentFilterPhrase -Phrase "Free credit report" -Influence BadWord ``` -This example adds the phrase Free credit report to the Block phrase list. Any messages that contain this phrase will be marked as spam by the Content Filtering agent. +This example adds the phrase Free credit report to the Block phrase list. Any messages that contain this phrase are marked as spam by the Content Filtering agent. ## PARAMETERS @@ -67,7 +67,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The Influence parameter specifies whether the phrase being added will cause the messages that contain the phrase to be allowed or blocked. Valid values are GoodWord and BadWord. +The Influence parameter specifies whether the phrase being added cause messages that contain the phrase to be allowed or blocked. Valid values are GoodWord and BadWord. A message that contains a custom word or phrase that has an Influence value of GoodWord is automatically assigned a spam confidence level (SCL) rating of 0 and therefore bypasses downstream spam processing. A message that contains a custom word or phrase that has an Influence value of BadWord is automatically assigned an SCL rating of 9 and therefore is treated as spam. diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md b/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md index 897bf7a61f..8773c97f8a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md @@ -37,7 +37,7 @@ To add a Mailbox server to a DAG, the Mailbox server must be running the Windows To add the first server to a DAG and create a computer object for the DAG, the Exchange Windows Permissions security group must have the appropriate rights to add computer accounts to the domain. Alternatively, a computer account can be created and disabled prior to adding the server. Adding the first server to the DAG enables the computer account for the DAG. Thus, the account used for the task doesn't need permissions to add a computer account to the domain. If you're pre-creating the computer account, the name of the account must match the name for the DAG. For example, if the DAG is named DAG1, the computer account must be named DAG1. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md index b87a4f59b9..7b4aa8a16e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md @@ -13,7 +13,7 @@ title: Add-DistributionGroupMember # Add-DistributionGroupMember ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Add-DistributionGroupMember cmdlet to add a single recipient to distribution groups and mail-enabled security groups. To replace all members, use the Update-DistributionGroupMember cmdlet. @@ -32,7 +32,7 @@ Add-DistributionGroupMember [-Identity] ``` ## DESCRIPTION -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 @@ -147,7 +147,7 @@ The Member parameter specifies the recipient that you want to add to the group. - Email address - GUID -Although it isn't required, it's a good idea to add only security principals (for example, mailboxes and mail users with user accounts or other mail-enabled security groups) to mail-enabled security groups. If you assign permissions to a mail-enabled security group, any members that aren't security principals (for example, mail contacts or distribution groups) won't have the permissions assigned. +Although it isn't required, it's a good idea to add only security principals (for example, mailboxes and mail users with user accounts or other mail-enabled security groups) to mail-enabled security groups. If you assign permissions to a mail-enabled security group, any members that aren't security principals (for example, mail contacts or distribution groups) don't have the permissions assigned. ```yaml Type: RecipientWithAdUserGroupIdParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md index 25568ab2fa..a955e3dbaa 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md @@ -36,7 +36,7 @@ You can add any registered Internet domain to the federated organization identif For more details, see [Federation](https://learn.microsoft.com/exchange/federation-exchange-2013-help). -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md index 7cdc6eb202..8a81090517 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md @@ -44,7 +44,7 @@ Add-GlobalMonitoringOverride [-Identity] -ItemType Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The Identity parameter specifies the identity of the probe, monitor, or responder. This parameter uses the syntax `HealthSetName\MonitoringItemName[\TargetResource]`. Note that the values are case sensitive. For example, use `AD\ActiveDirectoryConnectivityServerReboot`, not `ad\activedirectoryconnectivityserverreboot`. +The Identity parameter specifies the identity of the probe, monitor, or responder. This parameter uses the syntax `HealthSetName\MonitoringItemName[\TargetResource]`. The values are case sensitive. For example, use `AD\ActiveDirectoryConnectivityServerReboot`, not `ad\activedirectoryconnectivityserverreboot`. ```yaml Type: String diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListEntry.md b/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListEntry.md index 8aeb4bef69..a084014efb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListEntry.md @@ -147,7 +147,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The ExpirationTime parameter specifies a day and time when the IP Allow list entry that you're creating will expire. If you specify a time only and you don't specify a date, the current day is assumed. +The ExpirationTime parameter specifies a day and time when the IP Allow list entry expires. If you specify a time only and you don't specify a date, the current day is assumed. Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM". diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListEntry.md b/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListEntry.md index c121c4bd15..5507b123be 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListEntry.md @@ -146,7 +146,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The ExpirationTime parameter specifies a day and time when the IP Block list entry that you're creating will expire. If you specify a time only and you don't specify a date, the current day is assumed. +The ExpirationTime parameter specifies a day and time when the IP Block list entry expires. If you specify a time only and you don't specify a date, the current day is assumed. Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM". diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxDatabaseCopy.md index e255aaa90a..c76c4e5760 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxDatabaseCopy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxDatabaseCopy.md @@ -41,11 +41,11 @@ To use the Add-MailboxDatabaseCopy cmdlet to add a mailbox database copy, the fo - The specified Mailbox server must be in the same database availability group (DAG), and the DAG must have quorum and be healthy. - The specified Mailbox server must not already host a copy of the specified mailbox database. - The database path used by the specified database must also be available on the specified Mailbox server, because all copies of a database must use the same path. -- If you're adding the second copy of a database (for example, adding the first passive copy of the database), circular logging must not be enabled for the specified mailbox database. If circular logging is enabled, you must first disable it. After the mailbox database copy has been added, circular logging can be enabled. After enabling circular logging for a replicated mailbox database, continuous replication circular logging (CRCL) is used instead of JET circular logging. If you're adding the third or subsequent copy of a database, CRCL can remain enabled. +- If you're adding the second copy of a database (for example, adding the first passive copy of the database), circular logging must not be enabled for the specified mailbox database. If circular logging is enabled, you must first disable it. After the mailbox database copy is added, circular logging can be enabled. After enabling circular logging for a replicated mailbox database, continuous replication circular logging (CRCL) is used instead of JET circular logging. If you're adding the third or subsequent copy of a database, CRCL can remain enabled. After running the Add-MailboxDatabaseCopy cmdlet, the new copy remains in a Suspended state if the SeedingPostponed parameter is specified. When the database copy status is set to Suspended, the SuspendMessage is set to "Replication is suspended for database copy '{0}' because database needs to be seeded." -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 @@ -98,7 +98,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The MailboxServer parameter specifies the name of the server that will host the database copy. This server must be a member of the same DAG and must not already host a copy of the database. +The MailboxServer parameter specifies the name of the server that hosts the database copy. This server must be a member of the same DAG and must not already host a copy of the database. ```yaml Type: MailboxServerIdParameter @@ -136,7 +136,7 @@ Accept wildcard characters: False The ConfigurationOnly switch allows database copies to be added without invoking automatic seeding. You don't need to specify a value with this switch. -The source database does not need to be online or present when using this parameter. It will create a new database in Active Directory without contacting the target server. This parameter may be useful in situations where the target server is down for maintenance and the new database copy does not yet exist on the target server. +The source database does not need to be online or present when using this parameter. It creates a new database in Active Directory without contacting the target server. This parameter might be useful in situations where the target server is down for maintenance and the new database copy does not yet exist on the target server. ```yaml Type: SwitchParameter @@ -199,7 +199,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h The default value is 24:00:00 (24 hours). To disable deferred lagged copy play down, specify the value 00:00:00. -Note that when the disk is running out of space, the value of this parameter is ignored and lagged copy play down occurs without delay. +When the disk is running out of space, the value of this parameter is ignored and lagged copy play down occurs without delay. ```yaml Type: EnhancedTimeSpan @@ -257,7 +257,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The TruncationLagTime parameter specifies the amount of time that the Microsoft Exchange Replication service waits before truncating log files that have replayed into a copy of the database. The time period begins after the log has been successfully replayed into the copy of the database. +The TruncationLagTime parameter specifies the amount of time that the Microsoft Exchange Replication service waits before truncating log files that have replayed into a copy of the database. The time period begins after the log is successfully replayed into the copy of the database. To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds. diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxFolderPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxFolderPermission.md index 721fa3fe78..93f7798c11 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxFolderPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxFolderPermission.md @@ -13,7 +13,7 @@ title: Add-MailboxFolderPermission # Add-MailboxFolderPermission ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Add-MailboxFolderPermission cmdlet to add folder-level permissions for users in mailboxes. @@ -34,7 +34,7 @@ Add-MailboxFolderPermission [-Identity] -AccessRights ## DESCRIPTION To modify the permissions that are assigned to the user on a mailbox folder, use the Set-MailboxFolderPermission cmdlet. To remove all permissions that are assigned to a user on a mailbox folder, use the Remove-MailboxFolderPermission cmdlet. -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 @@ -229,10 +229,10 @@ Accept wildcard characters: False This parameter is available only in the cloud-based service. -The SendNotificationToUser parameter specifies whether to send a sharing invitation to the user when you add calendar permissions for them. The message will be a normal calendar sharing invitation that can be accepted by the recipient. Valid values are: +The SendNotificationToUser parameter specifies whether to send a sharing invitation to the user when you add calendar permissions for them. The message is a normal calendar sharing invitation that can be accepted by the recipient. Valid values are: - $true: A sharing invitation is sent. -- $false: No sharing invitation is sent. This is the default value. +- $false: No sharing invitation is sent. This value is the default. This parameter only applies to calendar folders and can only be used with the following AccessRights parameter values: @@ -261,8 +261,8 @@ This parameter is available only in the cloud-based service. The SharingPermissionFlags parameter assigns calendar delegate permissions. This parameter only applies to calendar folders and can only be used when the AccessRights parameter value is Editor. Valid values are: -- None: Has no effect. This is the default value. -- Delegate: The user is made a calendar delegate, which includes receiving meeting invites and responses. If there are no other delegates, this value will create the meeting message rule. If there are existing delegates, the user is added to the meeting message rule without changing how delegate messages are sent. +- None: Has no effect. This value is the default. +- Delegate: The user is made a calendar delegate, which includes receiving meeting invites and responses. If there are no other delegates, this value creates the meeting message rule. If there are existing delegates, the user is added to the meeting message rule without changing how delegate messages are sent. - CanViewPrivateItems: The user can access private items on the calendar. You must use this value with the Delegate value. You can specify multiple values separated by commas. diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md index accc016d50..e3d74dcb35 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md @@ -13,7 +13,7 @@ title: Add-MailboxPermission # Add-MailboxPermission ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Add-MailboxPermission cmdlet to add permissions to a mailbox or to an Exchange Server 2016, Exchange Server 2019, or Exchange Online mail user. @@ -67,7 +67,7 @@ Add-MailboxPermission [[-Identity] ] -Instance [!NOTE] > You can use this cmdlet to add a maximum of 500 permission entries (ACEs) to a mailbox. To grant permissions to more than 500 users, use security groups instead of individual users for the User parameter. Security groups contain many members, but only count as one entry. -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 @@ -165,7 +165,7 @@ Accept wildcard characters: False This parameter is available only in on-premises Exchange. -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: MailboxAcePresentationObject @@ -228,7 +228,7 @@ The User parameter specifies who gets the permissions on the mailbox. You can sp - Mail users - Mail-enabled security groups (non-mail-enabled security groups are selectable, but they don't work) -**Note**: When a mail-enabled security group is used to specify Full Access permissions, the auto-mapping feature won't automatically add the mailbox in Outlook for the group member. For more information, see [Mailboxes to which your account has full access aren't automapped to Outlook profile](https://learn.microsoft.com/outlook/troubleshoot/profiles-and-accounts/full-access-mailbox-not-automapped-outlook-profile). +**Note**: When a mail-enabled security group is used to specify Full Access permissions, the auto-mapping feature doesn't automatically add the mailbox in Outlook for the group member. For more information, see [Mailboxes to which your account has full access aren't automapped to Outlook profile](https://learn.microsoft.com/outlook/troubleshoot/profiles-and-accounts/full-access-mailbox-not-automapped-outlook-profile). For the best results, we recommend using the following values: @@ -266,9 +266,9 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online -The AutoMapping parameter includes or excludes the mailbox from the auto-mapping feature in Microsoft Outlook. Auto-mapping uses Autodiscover to automatically add mailboxes to a user's Outlook profile if the user has Full Access permission to the mailbox. However, Autodiscover won't enumerate security groups that are given Full Access permission to the mailbox. Valid values are: +The AutoMapping parameter includes or excludes the mailbox from the auto-mapping feature in Microsoft Outlook. Auto-mapping uses Autodiscover to automatically add mailboxes to a user's Outlook profile if the user has Full Access permission to the mailbox. However, Autodiscover doesn't enumerate security groups that have Full Access permission to the mailbox. Valid values are: -- $true: The mailbox is automatically added to the user's Outlook profile if the user has Full Access permission. This is the default value. +- $true: The mailbox is automatically added to the user's Outlook profile if the user has Full Access permission. This value is the default. - $false: The mailbox is not automatically added to the user's Outlook profile if the user has Full Access permission. **Note**: To disable auto-mapping for a mailbox where the user was already assigned Full Access permission, you need to remove the user's Full Access permission by using the Remove-MailboxPermission cmdlet, and then reassign the user Full Access permission on the mailbox using the AutoMapping parameter with the value $false. diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md b/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md index c356ae0e7b..ae6c6b0762 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md @@ -13,7 +13,7 @@ title: Add-ManagementRoleEntry # Add-ManagementRoleEntry ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Add-ManagementRoleEntry cmdlet to add management role entries to an existing management role. @@ -50,11 +50,11 @@ Add-ManagementRoleEntry [-ParentRoleEntry] -Role - ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md index e65cd078af..8bfbcd9ac9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md @@ -13,7 +13,7 @@ title: Add-PublicFolderClientPermission # Add-PublicFolderClientPermission ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Add-PublicFolderClientPermission cmdlet to add permissions to public folders. @@ -31,7 +31,7 @@ Add-PublicFolderClientPermission [-Identity] -AccessRi ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-RecipientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-RecipientPermission.md index 2a629a5a0d..e1708d0560 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-RecipientPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-RecipientPermission.md @@ -31,7 +31,7 @@ Add-RecipientPermission [-Identity] -AccessRights -StartTime ``` ## DESCRIPTION -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 @@ -171,7 +171,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019 -The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, ""). +The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, ""). ```yaml Type: String diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md index 4b06eb4397..a700deba46 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md @@ -13,7 +13,7 @@ title: Add-RoleGroupMember # Add-RoleGroupMember ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Add-RoleGroupMember cmdlet to add members to a management role group. @@ -33,13 +33,13 @@ Add-RoleGroupMember [-Identity] -Member -ItemType Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The Identity parameter specifies the identity of the monitoring item that you want to override. This parameter uses the syntax `HealthSet\MonitoringItemName[\TargetResource]`. Note that the values are case sensitive. For example, use `AD\ActiveDirectoryConnectivityConfigDCServerReboot`, not `ad\activedirectoryconnectivityconfigdcserverreboot`. +The Identity parameter specifies the identity of the monitoring item that you want to override. This parameter uses the syntax `HealthSet\MonitoringItemName[\TargetResource]`. The values are case sensitive. For example, use `AD\ActiveDirectoryConnectivityConfigDCServerReboot`, not `ad\activedirectoryconnectivityconfigdcserverreboot`. You can use Get-ServerHealth to find the correct object for the monitoring item you want to override. diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-UnifiedGroupLinks.md b/exchange/exchange-ps/ExchangePowerShell/Add-UnifiedGroupLinks.md index a4786f7f64..4e1ade63bf 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Add-UnifiedGroupLinks.md +++ b/exchange/exchange-ps/ExchangePowerShell/Add-UnifiedGroupLinks.md @@ -36,9 +36,9 @@ Add-UnifiedGroupLinks [-Identity] -Links ## DESCRIPTION The Clear-TextMessagingAccount cmdlet clears all of a user's text messaging settings, including communication and notification settings. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md b/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md index 1eb6f7ca40..83845e82d0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md +++ b/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md @@ -13,7 +13,7 @@ title: Compare-TextMessagingVerificationCode # Compare-TextMessagingVerificationCode ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Compare-TextMessagingVerificationCode cmdlet to verify the text messaging verification code that the user specified as part of configuring text message notifications on the mailbox. @@ -34,7 +34,7 @@ The Compare-TextMessagingVerificationCode cmdlet returns the value true if the c When text messaging notifications are enabled on a mailbox, you can configure calendar notifications, voice mail notifications, and email notifications using an inbox rule. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md index a47891ea77..a8ed9f625e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md @@ -13,7 +13,7 @@ title: Complete-MigrationBatch # Complete-MigrationBatch ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Complete-MigrationBatch cmdlet to finalize a migration batch for a local move, cross-forest move, or remote move migration that has successfully finished initial synchronization. @@ -40,13 +40,13 @@ After a migration batch for a local or cross-forest move has successfully run an - Configures the user's Microsoft Outlook profile to point to the new target domain. - Converts the source mailbox to a mail-enabled user in the source domain. -In the cloud-based service, this cmdlet sets the value of CompleteAfter to the current time. It is important to remember that any CompleteAfter setting that has been applied to the individual users within the batch will override the setting on the batch, so the completion for some users may be delayed until their configured time. +In the cloud-based service, this cmdlet sets the value of CompleteAfter to the current time. It is important to remember that any CompleteAfter setting applied to the individual users within the batch overrides the setting on the batch, so the completion for some users might be delayed until their configured time. When the finalization process is complete, you can remove the batch by using the Remove-MigrationBatch cmdlet. If a migration batch has a status of Completed with Errors, you can re-attempt to finalize the failed users. In Exchange Online, use the Start-MigrationBatch cmdlet to retry migration for failed users. In Exchange 2013 or Exchange 2016, use the Complete-MigrationBatch to retry these failed users. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Connect-ExchangeOnline.md b/exchange/exchange-ps/ExchangePowerShell/Connect-ExchangeOnline.md index 04e48a420d..b424b12ca1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Connect-ExchangeOnline.md +++ b/exchange/exchange-ps/ExchangePowerShell/Connect-ExchangeOnline.md @@ -740,7 +740,7 @@ Accept wildcard characters: False The ShowProgress parameter specifies whether to show or hide the progress bar of imported cmdlets when you connect. Valid values are: -- $true: The progress bar is displayed. This is the default value. +- $true: The progress bar is displayed. This value is the default. - $false: Currently, this value has no effect. ```yaml @@ -785,7 +785,7 @@ Accept wildcard characters: False **Note**: This parameter is available in version 3.3.0 or later of the module. -In version 3.7.0-Preview1 or later, this parameter is replaced by the LoadCmdletHelp parameter. The SkipLoadingCmdletHelp parameter is no longer required and no longer does anything, because cmdlet help files are no longer downloaded by default. Eventually, this parameter will be retired, so remove it from any scripts. +In version 3.7.0-Preview1 or later, this parameter is replaced by the LoadCmdletHelp parameter. The SkipLoadingCmdletHelp parameter is no longer required and no longer does anything, because cmdlet help files are no longer downloaded by default. The SkipLoadingCmdletHelp switch prevents downloading the cmdlet help files for the Get-Help cmdlet in REST API connections. You don't need to specify a value with this switch. @@ -811,7 +811,7 @@ Accept wildcard characters: False The SkipLoadingFormatData switch prevents downloading the format data for REST API connections. You don't need to specify a value with this switch. -When you use this switch, the output of any Exchange cmdlet will be unformatted. +When you use this switch, the output of any Exchange cmdlet is unformatted. Use this switch to avoid errors when connecting to Exchange Online PowerShell from within a Windows service or the Windows PowerShell SDK. @@ -836,7 +836,7 @@ Accept wildcard characters: False The TrackPerformance parameter measures additional events (for example, CPU load and memory consumed). Valid values are: - $true: Performance tracking is enabled. -- $false: Performance tracking is disabled. This is the default value. +- $false: Performance tracking is disabled. This value is the default. This parameter works only when logging is enabled. @@ -858,8 +858,8 @@ Accept wildcard characters: False The UseMultithreading parameter specifies whether to disable or enable multi-threading in the Exchange Online PowerShell module. Valid values are: -- $true: Enable multi-threading. This is the default value. -- $false: Disable multi-threading. This value will degrade the performance of the nine exclusive **Get-EXO\*** cmdlets in the module. +- $true: Enable multi-threading. This value is the default. +- $false: Disable multi-threading. This value degrades the performance of the nine exclusive **Get-EXO\*** cmdlets in the module. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md index cb4c8cfa49..8d4f60535b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md @@ -116,7 +116,7 @@ Connect-Mailbox [-Identity] [-Database] Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The ValidateOnly switch tells the cmdlet to evaluate the conditions and requirements necessary to perform the operation and then reports whether the operation will succeed or fail. You don't need to specify a value with this switch. +The ValidateOnly switch specifies whether to evaluate the potential success or failure of the command without making changes. You don't need to specify a value with this switch. No changes are made when you use this switch. diff --git a/exchange/exchange-ps/ExchangePowerShell/Delete-QuarantineMessage.md b/exchange/exchange-ps/ExchangePowerShell/Delete-QuarantineMessage.md index 4fb377a2a5..eaa566a1f2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Delete-QuarantineMessage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Delete-QuarantineMessage.md @@ -45,7 +45,7 @@ Delete-QuarantineMessage -Identity ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-ATPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-ATPProtectionPolicyRule.md index 8352e7a409..55e5a4c0fd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-ATPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-ATPProtectionPolicyRule.md @@ -33,7 +33,7 @@ The State property in rules that are associated with preset security policies in For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md b/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md index eaf4c603a6..c525408a82 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md @@ -29,7 +29,7 @@ Disable-AddressListPaging [-Confirm] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-AntiPhishRule.md index e736bcd2b3..3773a17e34 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-AntiPhishRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-AntiPhishRule.md @@ -29,7 +29,7 @@ Disable-AntiPhishRule [-Identity] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-App.md b/exchange/exchange-ps/ExchangePowerShell/Disable-App.md index b2ff60ea45..c176a7102c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-App.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-App.md @@ -13,7 +13,7 @@ title: Disable-App # Disable-App ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Disable-App cmdlet to disable (turn off) a specific app for a specific user. @@ -31,11 +31,11 @@ Disable-App [-Identity] ``` ## DESCRIPTION -The Disable-App cmdlet requires that the specified app has already been installed (for example, that the app has been installed with the New-App cmdlet, or that it's a default app for Microsoft Outlook). +The Disable-App cmdlet requires that the specified app has already been installed (for example, that the app is installed with the New-App cmdlet, or that it's a default app for Microsoft Outlook). For more information, see [Manage user access to add-ins for Outlook in Exchange Server](https://learn.microsoft.com/Exchange/manage-user-access-to-add-ins-exchange-2013-help) and [Manage deployment of add-ins in the Microsoft 365 admin center](https://learn.microsoft.com/office365/admin/manage/manage-deployment-of-add-ins). -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md b/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md index 950d45cb73..1ba7f512d3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md @@ -34,7 +34,7 @@ Cmdlet extension agents are used by Exchange cmdlets in Exchange Server 2010 and When you disable a cmdlet extension agent, the agent is disabled for the entire organization. When an agent is disabled, it's not made available to cmdlets. Cmdlets can no longer use the agent to perform additional operations. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md index 1bf77a6557..81854c040f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md @@ -33,7 +33,7 @@ Disable-DistributionGroup [-Identity] ## DESCRIPTION The Disable-DistributionGroup cmdlet mail-disables existing mail-enabled security groups and distribution groups by removing the email attributes that are required by Exchange. Mail-disabled groups are invisible to the \*-DistributionGroup cmdlets (with the exception of Enable-DistributionGroup). All groups (mail-enabled or not) are visible to the Get-Group and Set-Group cmdlets. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-DnssecForVerifiedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Disable-DnssecForVerifiedDomain.md index d6bba5f7e1..41c64fcc70 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-DnssecForVerifiedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-DnssecForVerifiedDomain.md @@ -31,7 +31,7 @@ Disable-DnssecForVerifiedDomain [-DomainName] ## DESCRIPTION For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works). -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-EOPProtectionPolicyRule.md index df608cff7f..0a8a006a20 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-EOPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-EOPProtectionPolicyRule.md @@ -33,7 +33,7 @@ The State property in rules that are associated with preset security policies in For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-HostedContentFilterRule.md index 7630a48749..bc31eef052 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-HostedContentFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-HostedContentFilterRule.md @@ -29,7 +29,7 @@ Disable-HostedContentFilterRule [-Identity] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-HostedOutboundSpamFilterRule.md index 9a3ea41209..4b73d2012f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-HostedOutboundSpamFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-HostedOutboundSpamFilterRule.md @@ -29,7 +29,7 @@ Disable-HostedOutboundSpamFilterRule [-Identity] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-IPv6ForAcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Disable-IPv6ForAcceptedDomain.md index 3e0dadb098..799ceca694 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-IPv6ForAcceptedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-IPv6ForAcceptedDomain.md @@ -32,7 +32,7 @@ Use the Get-AcceptedDomain cmdlet to return accepted domains in the Exchange Onl If IPv6 is enabled for an accepted domain in Exchange Online, IPv4 and IPv6 addresses are returned in DNS queries for mail flow records of the domain. If IPv6 is disabled, only IPv4 addresses are returned in DNS queries for mail flow records of the domain. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md index 63aca8800c..dde3d20511 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md @@ -13,7 +13,7 @@ title: Disable-InboxRule # Disable-InboxRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Disable-InboxRule cmdlet to disable existing Inbox rules in mailboxes. @@ -35,7 +35,7 @@ Disable-InboxRule [-Identity] ## DESCRIPTION When you create, modify, remove, enable, or disable an Inbox rule in Exchange PowerShell, any client-side rules created by Microsoft Outlook are removed. -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 @@ -140,7 +140,7 @@ The Force switch hides warning or confirmation messages. You don't need to speci You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate. -A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules will be removed by the actions of this cmdlet. +A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules are removed by the actions of this cmdlet. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-JournalArchiving.md b/exchange/exchange-ps/ExchangePowerShell/Disable-JournalArchiving.md index cc3806b3c5..e8dfd114a9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-JournalArchiving.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-JournalArchiving.md @@ -36,7 +36,7 @@ The Disable-JournalArchiving cmdlet removes the mail user and converts the journ In hybrid organizations that use DirSync, this cmdlet doesn't remove the mail user. Removal of the mail user is handled by DirSync. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md index d3a8397ba1..c2e684786c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md @@ -13,7 +13,7 @@ title: Disable-JournalRule # Disable-JournalRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Disable-JournalRule cmdlet to disable a journal rule on a Mailbox server. @@ -32,7 +32,7 @@ Disable-JournalRule -Identity ## DESCRIPTION You can enable or disable specific journal rules in your organization at any time using the Disable-JournalRule and Enable-JournalRule cmdlets. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md index 3f7988f388..66d3cc5e91 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md @@ -33,7 +33,7 @@ Disable-MailContact [-Identity] ## DESCRIPTION The Disable-MailContact cmdlet mail-disables existing mail contacts by removing the email attributes that are required by Exchange. Mail-disabled contacts are invisible to the \*-MailContact cmdlets (with the exception of Enable-MailContact). All contacts (mail-enabled or not) are visible to the Get-Contact and Set-Contact cmdlets. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md index e3f87cb3ae..19e6f06e0d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md @@ -13,7 +13,7 @@ title: Disable-MailPublicFolder # Disable-MailPublicFolder ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Disable-MailPublicFolder cmdlet to mail-disable a public folder. @@ -31,7 +31,7 @@ Disable-MailPublicFolder [-Identity] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md index c2a47e5857..3bc30aea90 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md @@ -34,7 +34,7 @@ Disable-MailUser [-Identity] ## DESCRIPTION The Disable-MailUser cmdlet mail-disables existing mail users by removing the email attributes that are required by Exchange. Mail-disabled users are invisible to the \*-MailUser cmdlets (with the exception of Enable-MailUser). All users (mail-enabled or not) are visible to the Get-User and Set-User cmdlets. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md index 57ce870b95..ffd3bd0dd9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md @@ -13,7 +13,7 @@ title: Disable-Mailbox # Disable-Mailbox ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Disable-Mailbox cmdlet to disable the mailbox of existing users who already have mailboxes. For this cmdlet, a user could also be a public folder mailbox or an InetOrgPerson object. The user account that's associated with the mailbox remains, but it's no longer associated with a mailbox. @@ -77,9 +77,9 @@ The Disable-Mailbox cmdlet removes the mailbox's Exchange attributes from Active The Disable-Mailbox cmdlet also performs the clean-up task on the individual mailbox, so the mailbox is disconnected immediately after this task completes. -Under normal circumstances, a mailbox is marked as disconnected immediately after the Disable-Mailbox or Remove-Mailbox command completes. However, if the mailbox was disabled or removed while the Exchange Information Store service was stopped, or if it was disabled or removed by an external means other than Exchange management interfaces, the status of the mailbox object in the Exchange mailbox database won't be marked as disconnected. +Under normal circumstances, a mailbox is marked as disconnected immediately after the Disable-Mailbox or Remove-Mailbox command completes. However, if the mailbox was disabled or removed while the Exchange Information Store service was stopped, or if it was disabled or removed by an external means other than Exchange management interfaces, the status of the mailbox object in the Exchange mailbox database isn't marked as disconnected. -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 @@ -313,7 +313,7 @@ The PermanentlyDisable switch specifies whether to permanently disable the mailb **Notes**: - You can only use this switch on user mailboxes that aren't licensed and aren't on hold. -- When the Exchange Online license is removed from a mailbox without following other deprovisioning steps, this may leave the mailbox in a hard-deleted state. In this case, this parameter is not useful. You can use it, for example, in hybrid Exchange environments. +- When the Exchange Online license is removed from a mailbox without following other deprovisioning steps, this might leave the mailbox in a hard-deleted state. In this case, this parameter is not useful. You can use it, for example, in hybrid Exchange environments. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md index 1bb4f37eb4..69bd293167 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md @@ -68,9 +68,9 @@ Disable-MailboxQuarantine -Server ``` ## DESCRIPTION -Mailboxes are quarantined when they affect the availability of the mailbox database. Typically a software fix from Microsoft is required before releasing a mailbox from quarantine. If a fix isn't deployed before releasing the mailbox, the quarantine on the mailbox will be re-enabled if the condition recurs. The default quarantine duration is 24 hours. +Mailboxes are quarantined when they affect the availability of the mailbox database. Typically a software fix from Microsoft is required before releasing a mailbox from quarantine. If a fix isn't deployed before releasing the mailbox, the quarantine on the mailbox is re-enabled if the condition recurs. The default quarantine duration is 24 hours. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md index 44824fbe35..3135c19f76 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md @@ -13,7 +13,7 @@ title: Disable-MalwareFilterRule # Disable-MalwareFilterRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Disable-MalwareFilterRule cmdlet to disable malware filter rules in your organization. @@ -30,7 +30,7 @@ Disable-MalwareFilterRule [-Identity] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md index 3d4485454e..cff0f8762f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md @@ -29,7 +29,7 @@ Disable-MetaCacheDatabase -Server ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookAnywhere.md b/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookAnywhere.md index 8cfbf56343..2be4362dad 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookAnywhere.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookAnywhere.md @@ -44,9 +44,9 @@ Enabling Outlook Anywhere on the Client Access server prevents the server from a When you run this cmdlet, it can take as long as an hour for the settings to become effective, depending on how long it takes for Active Directory to replicate. -After the Client Access server is disabled for Outlook Anywhere, you may want to remove the RPC over HTTP proxy Windows networking component. +After the Client Access server is disabled for Outlook Anywhere, you might want to remove the RPC over HTTP proxy Windows networking component. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md index 17ffbc57db..f294454b97 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md @@ -15,7 +15,7 @@ title: Disable-OutlookProtectionRule ## SYNOPSIS **Note**: This cmdlet is no longer supported in the cloud-based service. -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Disable-OutlookProtectionRule cmdlet to disable an existing Microsoft Outlook protection rule. @@ -36,7 +36,7 @@ Outlook protection rules are administrator-created rules applied before a user s For more information, see [Outlook protection rules](https://learn.microsoft.com/exchange/outlook-protection-rules-exchange-2013-help). -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md b/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md index 069b955360..45364575b0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md @@ -30,7 +30,7 @@ Disable-PushNotificationProxy [-Confirm] ## DESCRIPTION The push notification proxy relays event notifications (for example, new email or calendar updates) for on-premises mailboxes through Microsoft 365 to Outlook on the web for devices on the user's device. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md index 3549b91ef4..ce5291ee76 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md @@ -35,7 +35,7 @@ Disable-RemoteMailbox [-Identity] ## DESCRIPTION Use the Disable-RemoteMailbox cmdlet to perform the following actions: -- Remove a cloud-based mailbox but keep the associated on-premises user account. To do this, you first need to remove the Exchange Online license for the mailbox. Otherwise, the mailbox won't be removed. The on-premises mail user is automatically converted to a regular user object. You can mail-enable the on-premises user object using the Enable-MailUser cmdlet. +- Remove a cloud-based mailbox but keep the associated on-premises user account. To do this, you first need to remove the Exchange Online license for the mailbox. Otherwise, the mailbox isn't removed. The on-premises mail user is automatically converted to a regular user object. You can mail-enable the on-premises user object using the Enable-MailUser cmdlet. - Disconnect a cloud-based archive mailbox from a cloud-based mailbox. The cloud-based mailbox and the associated on-premises mail user are preserved. If you want to remove both the cloud-based mailbox and the associated on-premises mail user, use the Remove-RemoteMailbox cmdlet. @@ -44,10 +44,10 @@ Directory synchronization must be configured correctly for a mailbox to be remov **Notes**: -- If you are deprovisioning a cloud mailbox and its associated online archive, you must first disable the online archive with the command `Disable-RemoteMailbox -Archive` and then perform a directory synchronization prior to disabling the remote mailbox. Attempting to disable both the online archive and cloud mailbox without a sync between them may result in an ArchiveGuid mismatch and validation error. +- If you are deprovisioning a cloud mailbox and its associated online archive, you must first disable the online archive with the command `Disable-RemoteMailbox -Archive` and then perform a directory synchronization prior to disabling the remote mailbox. Attempting to disable both the online archive and cloud mailbox without a sync between them might result in an ArchiveGuid mismatch and validation error. - Due to the current service architecture, you need to convert shared mailboxes to user mailboxes prior to running the Disable-RemoteMailbox cmdlet. -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 @@ -56,14 +56,14 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Disable-RemoteMailbox "Kim Akers" ``` -This example removes the cloud-based mailbox that's associated with the on-premises mail user named Kim Akers. The mail user is automatically converted to a regular user. This example assumes that you've already removed the Exchange Online license for the mailbox, and that directory synchronization has been configured. +This example removes the cloud-based mailbox that's associated with the on-premises mail user named Kim Akers. The mail user is automatically converted to a regular user. This example assumes that you've already removed the Exchange Online license for the mailbox, and that directory synchronization is configured. ### Example 2 ```powershell Disable-RemoteMailbox "David Strome" -Archive ``` -This example removes the cloud-based archive mailbox but keeps the cloud-based mailbox that's associated with the on-premises mail user named David Strome. This example assumes directory synchronization has been configured. +This example removes the cloud-based archive mailbox but keeps the cloud-based mailbox that's associated with the on-premises mail user named David Strome. This example assumes directory synchronization is configured. ## PARAMETERS diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-ReportSubmissionRule.md index 1fbb643e5a..95727eff23 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-ReportSubmissionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-ReportSubmissionRule.md @@ -29,7 +29,7 @@ Disable-ReportSubmissionRule [-Identity] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-SafeAttachmentRule.md index 953b770117..ee21f6286e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-SafeAttachmentRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-SafeAttachmentRule.md @@ -31,7 +31,7 @@ Disable-SafeAttachmentRule [-Identity] ## DESCRIPTION Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about). -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-SafeLinksRule.md index 3327a72700..24f062ac31 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-SafeLinksRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-SafeLinksRule.md @@ -31,7 +31,7 @@ Disable-SafeLinksRule [-Identity] ## DESCRIPTION Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md b/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md index 4e82617c25..66799f5106 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md @@ -32,7 +32,7 @@ Disable-ServiceEmailChannel [-Identity] ## DESCRIPTION The Disable-ServiceEmailChannel cmdlet deletes the receive folder in the user's mailbox under the root folder. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-SmtpDaneInbound.md b/exchange/exchange-ps/ExchangePowerShell/Disable-SmtpDaneInbound.md index 658111797e..9c28890fee 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-SmtpDaneInbound.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-SmtpDaneInbound.md @@ -31,7 +31,7 @@ Disable-SmtpDaneInbound [-DomainName] ## DESCRIPTION For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works). -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md index 95de0ed658..5049dce174 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md @@ -13,7 +13,7 @@ title: Disable-SweepRule # Disable-SweepRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Disable-SweepRule cmdlet to disable Sweep rules in mailboxes. @@ -31,7 +31,7 @@ Disable-SweepRule [-Identity] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md index dde2c3a4c3..675098e0b9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md @@ -31,7 +31,7 @@ Disable-TransportAgent [-Identity] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md index 1921db70e4..72a6cd1f6e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md @@ -13,7 +13,7 @@ title: Disable-TransportRule # Disable-TransportRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Disable-TransportRule cmdlet to disable transport rules (mail flow rules) in your organization. @@ -32,7 +32,7 @@ Disable-TransportRule [-Identity] ## DESCRIPTION To enable rules that are disabled, use the Enable-TransportRule cmdlet. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMAutoAttendant.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMAutoAttendant.md index 1ef66ad50b..55d93cb30b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMAutoAttendant.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMAutoAttendant.md @@ -32,9 +32,9 @@ Disable-UMAutoAttendant [-Identity] ## DESCRIPTION The Disable-UMAutoAttendant cmdlet disables an existing UM auto attendant that's currently enabled. The Disable-UMAutoAttendant cmdlet disables the UM auto attendant by modifying its status variable. The Disable-UMAutoAttendant cmdlet can't disable the UM auto attendant if it's linked or associated to the UM hunt group associated with the default UM dial plan. -After this task is completed, the UM auto attendant is disabled and won't accept incoming calls. +After this task is completed, the UM auto attendant is disabled and doesn't accept incoming calls. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMCallAnsweringRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMCallAnsweringRule.md index 28f9e0bd91..83930d80a6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMCallAnsweringRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMCallAnsweringRule.md @@ -15,7 +15,7 @@ title: Disable-UMCallAnsweringRule ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Disable-UMCallAnsweringRule cmdlet to disable a call answering rule that has been created within a UM-enabled mailbox. +Use the Disable-UMCallAnsweringRule cmdlet to disable a call answering rule that is created within a UM-enabled mailbox. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -35,7 +35,7 @@ The Disable-UMCallAnsweringRule cmdlet disables the call answering rule by modif When the call answering rule is created, you should disable the call answering rule when you're setting up conditions and actions. This prevents the call answering rule from being processed when an incoming call is received until you've correctly configured the call answering rule. After this task is completed, the cmdlet sets the parameters and the values specified. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMIPGateway.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMIPGateway.md index a715ac322d..99d701cbe6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMIPGateway.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMIPGateway.md @@ -33,7 +33,7 @@ Disable-UMIPGateway [-Identity] ## DESCRIPTION The status variable for a UM IP gateway can be used to enable or disable call answering destined for the IP gateway. The Disable-UMIPGateway cmdlet disables a UM IP gateway in Active Directory by modifying its status variable. After this task is completed, the UM IP gateway no longer answers incoming calls or makes outgoing calls. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMMailbox.md index ea3727bee6..de6a75d801 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMMailbox.md @@ -34,7 +34,7 @@ Disable-UMMailbox [-Identity] ## DESCRIPTION After the mailbox is disabled for Unified Messaging, the user can no longer use the UM features that are included in Microsoft Exchange and the Microsoft Exchange Unified Messaging service no longer handle calls for the associated extension number. The mailbox continues to function normally for all other operations that are unrelated to Unified Messaging. -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 @@ -144,7 +144,7 @@ Accept wildcard characters: False The KeepProperties parameter specifies whether to keep or remove the UM properties for the mailbox. Valid values are: -- $true: The UM properties are retained on the mailbox. This is the default value. +- $true: The UM properties are retained on the mailbox. This value is the default. - $false: The UM properties are removed from the mailbox. ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMServer.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMServer.md index a4713a795f..090daef048 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMServer.md @@ -31,7 +31,7 @@ Disable-UMServer [-Identity] ``` ## DESCRIPTION -The Disable-UMServer cmdlet sets the status of a Unified Messaging server. A UM server has a logical status variable controlled using the enable and disable cmdlets. A UM server won't process any new calls unless it's in the enabled state. With this status variable, you can start or stop call processing on a UM server so the UM server can be brought online or taken offline in a controlled way. +The Disable-UMServer cmdlet sets the status of a Unified Messaging server. A UM server has a logical status variable controlled using the enable and disable cmdlets. A UM server doesn't process any new calls unless it's in the enabled state. With this status variable, you can start or stop call processing on a UM server so the UM server can be brought online or taken offline in a controlled way. After this task is completed, the UM server can no longer: @@ -40,7 +40,7 @@ After this task is completed, the UM server can no longer: - Be used to manage UM-enabled mailboxes - Be queried when a diagnostic task is used -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMService.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMService.md index f712294833..f3f2b6c64a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMService.md @@ -33,7 +33,7 @@ Disable-UMService [-Identity] ``` ## DESCRIPTION -The Disable-UMService cmdlet sets the status of a UM server. A UM server has a logical status variable controlled using the enable and disable cmdlets. A UM server won't process any new calls unless it's in the enabled state. With this status variable, you can start or stop call processing on a UM server so the UM server can be brought online or taken offline in a controlled way. +The Disable-UMService cmdlet sets the status of a UM server. A UM server has a logical status variable controlled using the enable and disable cmdlets. A UM server doesn't process any new calls unless it's in the enabled state. With this status variable, you can start or stop call processing on a UM server so the UM server can be brought online or taken offline in a controlled way. After this task is completed, the UM server can no longer: @@ -42,7 +42,7 @@ After this task is completed, the UM server can no longer: - Be used to manage UM-enabled mailboxes. - Be queried when a diagnostic task is used. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md b/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md index f71b315592..27e96b01a7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md +++ b/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md @@ -30,7 +30,7 @@ Dismount-Database [-Identity] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md b/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md index caf85044ed..0ec91c54ca 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md +++ b/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md @@ -43,11 +43,11 @@ Dump-ProvisioningCache [-Server] -Application ``` ## DESCRIPTION -The Dump-ProvisioningCache cmdlet is for diagnostic purposes only and is rarely used. Exchange administrators or Microsoft support personnel may need to run this cmdlet to troubleshoot problems resulting from incorrect links or properties stamped on newly provisioned recipients, which can be caused by stale data in the provisioning cache. +The Dump-ProvisioningCache cmdlet is for diagnostic purposes only and is rarely used. Exchange administrators or Microsoft support personnel might need to run this cmdlet to troubleshoot problems resulting from incorrect links or properties stamped on newly provisioned recipients, which can be caused by stale data in the provisioning cache. The Dump-ProvisioningCache cmdlet displays a list of the Windows PowerShell provisioning cache keys. Use the value of these cache keys with the Reset-ProvisioningCache cmdlet to reset provisioning cache data. -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 @@ -184,7 +184,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -The Organizations parameter specifies the organizations that the provisioning cache will be reset. This parameter is used in multi-tenant deployments. +The Organizations parameter specifies the organizations where the provisioning cache is reset. This parameter is used in multi-tenant deployments. ```yaml Type: MultiValuedProperty diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ATPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ATPProtectionPolicyRule.md index c62fb63b78..58eda1bbbf 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-ATPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ATPProtectionPolicyRule.md @@ -33,7 +33,7 @@ The State property in rules that are associated with preset security policies in For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md b/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md index 7cf35a1dd4..bb39c286cd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md @@ -31,7 +31,7 @@ Enable-AddressListPaging [-Confirm] ## DESCRIPTION The Enable-AddressListPaging cmdlet creates the Address List container in Active Directory. Recipient cmdlets, such as Get-Recipient, use the information written to the container to quickly retrieve recipient data. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-AntiPhishRule.md index 418b53848b..9cd62cc3f6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-AntiPhishRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-AntiPhishRule.md @@ -29,7 +29,7 @@ Enable-AntiPhishRule [-Identity] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-App.md b/exchange/exchange-ps/ExchangePowerShell/Enable-App.md index fe719c307f..5379a54dbe 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-App.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-App.md @@ -13,7 +13,7 @@ title: Enable-App # Enable-App ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Enable-App cmdlet to enable (turn on) a specific app for a specific user. @@ -31,11 +31,11 @@ Enable-App [-Identity] ``` ## DESCRIPTION -The Enable-App cmdlet requires that the specified app has already been installed (for example, that it has been installed with the New-App cmdlet, or that it's a default app for Microsoft Outlook). +The Enable-App cmdlet requires that the specified app has already been installed (for example, that it is installed with the New-App cmdlet, or that it's a default app for Microsoft Outlook). For more information, see [Manage user access to add-ins for Outlook in Exchange Server](https://learn.microsoft.com/Exchange/manage-user-access-to-add-ins-exchange-2013-help) and [Manage deployment of add-ins in the Microsoft 365 admin center](https://learn.microsoft.com/office365/admin/manage/manage-deployment-of-add-ins). -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md b/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md index b954efdd4a..fa6ec7a67a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md @@ -34,9 +34,9 @@ Cmdlet extension agents are used by Exchange cmdlets in Exchange Server 2010 and When you enable a cmdlet extension agent, the agent is run on every Exchange server in the organization. When an agent is enabled, it's made available to cmdlets that can then use the agent to perform additional operations. -Before you enable agents, be sure that you're aware of how the agent works and what impact the agent will have on your organization. +Before you enable agents, be sure that you're aware of how the agent works and what effect the agent can have on your organization. -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 @@ -45,7 +45,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi Enable-CmdletExtensionAgent "Scripting Agent" ``` -This example enables the cmdlet extension agent named Scripting Agent. Before you enable the Scripting Agent, you need to configure the %ExchangeInstallPath%Bin\\CmdletExtensionAgents\\ScriptingAgentConfig.xml.sample file and rename it to ScriptingAgentConfig.xml on all the Exchange servers in your organization. If you don't, all non-Get cmdlets will fail. +This example enables the cmdlet extension agent named Scripting Agent. Before you enable the Scripting Agent, you need to configure the `%ExchangeInstallPath%Bin\CmdletExtensionAgents\ScriptingAgentConfig.xml.sample` file and rename it to `ScriptingAgentConfig.xml` on all the Exchange servers in your organization. If you don't configure the file, all non-Get cmdlets will fail. ## PARAMETERS diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ComplianceTagStorage.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ComplianceTagStorage.md index a28f12032f..7eaaed4768 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-ComplianceTagStorage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ComplianceTagStorage.md @@ -30,7 +30,7 @@ Enable-ComplianceTagStorage ``` ## DESCRIPTION -You can check the status by running the following command: `Get-ComplianceTagStorage | Format-List Enabled,DistributionStatus`. The value True for the Enabled property and the value Success for the DistributionStatus property indicates the Enable-ComplianceTagStorage cmdlet has already been run in the organization, and you don't need to run it again. If you run the cmdlet unnecessarily, you'll get a warning, and the DistributionStatus property changes to the value Pending for a few minutes before returning to the value Success. +You can check the status by running the following command: `Get-ComplianceTagStorage | Format-List Enabled,DistributionStatus`. The value True for the Enabled property and the value Success for the DistributionStatus property indicates the Enable-ComplianceTagStorage cmdlet has already been run in the organization, and you don't need to run it again. If you run the cmdlet unnecessarily, you get a warning, and the DistributionStatus property changes to the value Pending for a few minutes before returning to the value Success. To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md index 2b0bca1bab..3c3963ce8a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md @@ -35,7 +35,7 @@ Enable-DistributionGroup [-Identity] ## DESCRIPTION The Enable-DistributionGroup cmdlet mail-enables existing universal security groups and universal distribution groups by adding the email attributes that are required by Exchange. Mail-enabled security groups and distribution groups are visible to the other \*-DistributionGroup cmdlets and to the \*-DistributionGroupMember cmdlets. -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). In Exchange Server, the [CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216) InformationVariable and InformationAction don't work. @@ -172,7 +172,7 @@ Accept wildcard characters: False The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient. -By default, the primary SMTP address is generated based on the default email address policy and the value of the Alias parameter or the Name property. If you use the PrimarySmtpAddress parameter to specify the primary email address, the EmailAddressPolicyEnabled property is set to the value False, which means the email addresses of the group won't be automatically updated by email address policies. +By default, the primary SMTP address is generated based on the default email address policy and the value of the Alias parameter or the Name property. If you use the PrimarySmtpAddress parameter to specify the primary email address, the EmailAddressPolicyEnabled property is set to the value False, which means the email addresses of the group aren't automatically updated by email address policies. ```yaml Type: SmtpAddress diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-DnssecForVerifiedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Enable-DnssecForVerifiedDomain.md index ba66a7d906..d538718ea9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-DnssecForVerifiedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-DnssecForVerifiedDomain.md @@ -33,7 +33,7 @@ The output of this cmdlet is an MX record value that you need to add to DNS for For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works). -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-EOPProtectionPolicyRule.md index 55ab46f3c3..a71a9634b9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-EOPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-EOPProtectionPolicyRule.md @@ -33,7 +33,7 @@ The State property in rules that are associated with preset security policies in For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md index 8ac543b37b..1d42298bb7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md @@ -57,7 +57,7 @@ There are many factors to consider when you configure certificates for Transport Secure Sockets Layer (SSL) is being replaced by Transport Layer Security (TLS) as the protocol that's used to encrypt data sent between computer systems. They're so closely related that the terms "SSL" and "TLS" (without versions) are often used interchangeably. Because of this similarity, references to "SSL" in Exchange topics, the Exchange admin center, and the Exchange Management Shell have often been used to encompass both the SSL and TLS protocols. Typically, "SSL" refers to the actual SSL protocol only when a version is also provided (for example, SSL 3.0). For more information, see [Exchange Server TLS configuration best practices](https://learn.microsoft.com/Exchange/exchange-tls-configuration). -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 @@ -135,7 +135,7 @@ You can specify multiple values separated by commas. The values that you specify with this parameter are additive. When you enable a certificate for one or more services, any existing services remain in the Services property and you can't remove the existing services. Instead, configure another certificate for the services and then remove the certificate that you don't want to use. -Different services have different certificate requirements. For example, some services may require a server name in the certificate's Subject Name or Subject Alternative Name fields, but other services may require an FQDN. Verify that the certificate supports the services that you want to configure. +Different services have different certificate requirements. For example, some services might require a server name in the certificate's Subject Name or Subject Alternative Name fields, but other services might require an FQDN. Verify that the certificate supports the services that you want to configure. ```yaml Type: AllowedServices diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-HostedContentFilterRule.md index 2e2746777a..3bed2ac086 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-HostedContentFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-HostedContentFilterRule.md @@ -29,7 +29,7 @@ Enable-HostedContentFilterRule [-Identity] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-HostedOutboundSpamFilterRule.md index ea9fd1312b..4db53e86eb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-HostedOutboundSpamFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-HostedOutboundSpamFilterRule.md @@ -29,7 +29,7 @@ Enable-HostedOutboundSpamFilterRule [-Identity] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-IPv6ForAcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Enable-IPv6ForAcceptedDomain.md index 742bc1c935..faceb49a5d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-IPv6ForAcceptedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-IPv6ForAcceptedDomain.md @@ -32,7 +32,7 @@ Use the Get-AcceptedDomain cmdlet to return accepted domains in the Exchange Onl If IPv6 is enabled for an accepted domain in Exchange Online, IPv4 and IPv6 addresses are returned in DNS queries for mail flow records of the domain. If IPv6 is disabled, only IPv4 addresses are returned in DNS queries for mail flow records of the domain. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md index d1680d3778..6c3673325b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md @@ -13,7 +13,7 @@ title: Enable-InboxRule # Enable-InboxRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Enable-InboxRule cmdlet to enable an Inbox rule. Inbox rules are used to process messages in the Inbox based on conditions specified and take actions such as moving a message to a specified folder or deleting a message. @@ -35,7 +35,7 @@ Enable-InboxRule [-Identity] ## DESCRIPTION When you create, modify, remove, enable, or disable an Inbox rule in Exchange PowerShell, any client-side rules created by Microsoft Outlook are removed. -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 @@ -138,7 +138,7 @@ The Force switch hides warning or confirmation messages. You don't need to speci You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate. -A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules will be removed by the actions of this cmdlet. +A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules are removed by the actions of this cmdlet. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md index 9cfd07daa1..244d0391ce 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md @@ -13,7 +13,7 @@ title: Enable-JournalRule # Enable-JournalRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Enable-JournalRule cmdlet to enable an existing journal rule on a Mailbox server. @@ -32,7 +32,7 @@ Enable-JournalRule [-Identity] ## DESCRIPTION You can enable or disable specific journal rules in your organization at any time using the Enable-JournalRule and Disable-JournalRule cmdlets. For more information, see [Journaling in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/journaling/journaling). -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md index 14a850f520..2b9a9f8fda 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md @@ -39,7 +39,7 @@ Enable-MailContact [-Identity] -ExternalEmailAddress ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md index 431b7b0427..ceb3f644e4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md @@ -55,7 +55,7 @@ The Enable-MailUser cmdlet mail-enables existing users by adding the email attri Mail users have email addresses and accounts in the Exchange organization, but they don't have Exchange mailboxes. Email messages sent to mail users are delivered to the specified external email address. -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 @@ -208,7 +208,7 @@ Accept wildcard characters: False The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are: -- BinHex (This is the default value) +- BinHex (default value) - UuEncode - AppleSingle - AppleDouble @@ -238,7 +238,7 @@ The MessageBodyFormat parameter specifies the message body format for messages s - Text - Html -- TextAndHtml (This is the default value) +- TextAndHtml (default value) The MessageFormat and MessageBodyFormat parameters are interdependent: @@ -264,7 +264,7 @@ Accept wildcard characters: False The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are: - Text -- Mime (This is the default value) +- Mime (default value) The MessageFormat and MessageBodyFormat parameters are interdependent: @@ -314,7 +314,7 @@ Accept wildcard characters: False The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are: - $true: Messages sent to the mail user or mail contact use the message format that's configured for the mail user or mail contact. -- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value. +- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md index dc154ed3be..4ca227e302 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md @@ -13,7 +13,7 @@ title: Enable-Mailbox # Enable-Mailbox ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Enable-Mailbox cmdlet to create mailboxes for existing users who don't already have mailboxes. You can also use this cmdlet to create In-Place archives for existing mailboxes. @@ -273,7 +273,7 @@ The Enable-Mailbox cmdlet mailbox-enables existing users, public folders, or Ine When mailbox-enabling an existing user, beware of non-supported characters in the user account or Name property. If you don't specify an Alias value when you mailbox-enable the user, Exchange converts all non-supported characters to question marks (?). To avoid question marks in the Alias, verify that the user account and Name properties have only supported ASCII or Unicode characters or specify an Alias value when you mailbox-enable the user. -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). In Exchange Server, the [CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216) InformationVariable and InformationAction don't work. @@ -894,7 +894,7 @@ The HoldForMigration switch specifies whether to prevent any client or user, exc You need to use this switch when you create the first public folder, which is called the hierarchy mailbox, in your organization. -Use this switch only if you plan to migrate legacy Exchange 2010 public folders to Exchange 2016. If you use this switch but don't have legacy public folders to migrate, you won't be able to create any public folders. +Use this switch only if you plan to migrate legacy Exchange 2010 public folders to Exchange 2016. If you use this switch but don't have legacy public folders to migrate, you can't create any public folders. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md index cf97201621..d539c0c031 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md @@ -54,7 +54,7 @@ Enable-MailboxQuarantine -Database -StoreMailboxIdentity < ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md index b323fd1b21..c8d9f1432e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md @@ -13,7 +13,7 @@ title: Enable-MalwareFilterRule # Enable-MalwareFilterRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Enable-MalwareFilterRule cmdlet to enable malware filter rules in your organization. @@ -30,7 +30,7 @@ Enable-MalwareFilterRule [-Identity] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md index e498da9e61..860be7f17a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md @@ -29,7 +29,7 @@ Enable-MetaCacheDatabase -Server ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-OrganizationCustomization.md b/exchange/exchange-ps/ExchangePowerShell/Enable-OrganizationCustomization.md index 0737dacb31..92019b3cd6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-OrganizationCustomization.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-OrganizationCustomization.md @@ -15,7 +15,7 @@ title: Enable-OrganizationCustomization ## SYNOPSIS This cmdlet is available only in the cloud-based service. -You may be prompted to run the EnableOrganizationCustomization cmdlet before you create or modify objects in your Exchange Online organization. +You might be prompted to run the EnableOrganizationCustomization cmdlet before you create or modify objects in your Exchange Online organization. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -28,7 +28,7 @@ Enable-OrganizationCustomization [-Confirm] ``` ## DESCRIPTION -In the Microsoft datacenters, certain objects are consolidated to save space. When you use Exchange Online PowerShell or the Exchange admin center to modify one of these objects for the first time, you may encounter an error message that tells you to run the Enable-OrganizationCustomization cmdlet. +In the Microsoft datacenters, certain objects are consolidated to save space. When you use Exchange Online PowerShell or the Exchange admin center to modify one of these objects for the first time, you might encounter an error message that tells you to run the Enable-OrganizationCustomization cmdlet. Here are some examples of when you might see this: @@ -39,11 +39,11 @@ Here are some examples of when you might see this: - Creating a new retention policy or modifying a built-in retention policy. - Enabling preset security policies in the Microsoft Defender portal. -Note that you are only required to run the Enable-OrganizationCustomization cmdlet once in your Exchange Online organization. If you attempt to run the cmdlet again, you'll get an error. +You are only required to run the Enable-OrganizationCustomization cmdlet once in your Exchange Online organization. If you attempt to run the cmdlet again, you get an error. -Whether or not this command has been previously run in an organization is available in the IsDehydrated property of the Get-OrganizationConfig cmdlet: False ($false) = the command has already been run; True ($true) = the command has never been run. +Whether or not this command is previously run in an organization is available in the IsDehydrated property of the Get-OrganizationConfig cmdlet: False ($false) = the command has already been run; True ($true) = the command has never been run. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookAnywhere.md b/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookAnywhere.md index f3108d903a..300964c824 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookAnywhere.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookAnywhere.md @@ -57,7 +57,7 @@ When you run this cmdlet, it can take as long as an hour for the settings to bec For more information about the different authentication methods that you can see in this article, see [Understanding HTTP Authentication](https://learn.microsoft.com/dotnet/framework/wcf/feature-details/understanding-http-authentication). -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 @@ -95,7 +95,7 @@ The ClientAuthenticationMethod parameter specifies the authentication method tha This parameter must be specified if you don't use the DefaultAuthenticationMethod parameter. When you use this parameter without specifying the IISAuthenticationMethods parameter, IISAuthenticationMethods parameter is set to both NTLM and Basic. -Although this parameter only allows setting one authentication method, the command won't return an error if you include multiple values. +Although this parameter only allows setting one authentication method, the command doesn't return an error if you include multiple values. ```yaml Type: AuthenticationMethod @@ -217,9 +217,9 @@ The ExtendedProtectionFlags parameter is used to customize the options you use i - None: Default setting. - Proxy: Specifies that a proxy is terminating the SSL channel. A Service Principal Name (SPN) must be registered in the ExtendedProtectionSPNList parameter if proxy mode is configured. -- ProxyCoHosting: Specifies that both HTTP and HTTPS traffic may be accessing the Client Access server and that a proxy is located between at least some of the clients and the Client Access server. +- ProxyCoHosting: Specifies that both HTTP and HTTPS traffic might be accessing the Client Access server and that a proxy is located between at least some of the clients and the Client Access server. - AllowDotlessSPN: Specifies whether you want to support valid SPNs that aren't in the fully qualified domain name (FQDN) format, for example ContosoMail. You specify valid SPNs with the ExtendedProtectionSPNList parameter. This option makes extended protection less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel. -- NoServiceNameCheck: Specifies that the SPN list won't be checked to validate a channel binding token. This option makes Extended Protection for Authentication less secure. We generally don't recommend this setting. +- NoServiceNameCheck: Specifies that the SPN list isn't checked to validate a channel binding token. This option makes Extended Protection for Authentication less secure. We generally don't recommend this setting. ```yaml Type: MultiValuedProperty @@ -241,7 +241,7 @@ The ExtendedProtectionSPNList parameter specifies a list of valid Service Princi The possible values are: -- Null This is the default value. +- Null This value is the default. - Single SPN or comma delimited list of valid SPNs By default, you must specify the fully qualified domain name (FQDN) (for example mail.contoso.com) for each SPN. If you want to add an SPN that's not an FQDN (for example, ContosoMail), you must also use the ExtendedProtectionTokenChecking parameter with the AllowDotlessSPN value. You specify the domain in SPN format. The SPN format is `Protocol\FQDN` (for example, `HTTP/mail.contoso.com`). ```yaml @@ -262,14 +262,11 @@ Accept wildcard characters: False The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the specified Exchange virtual directory. Extended Protection for Authentication isn't enabled by default. The available settings are: -- None Extended Protection for Authentication won't be used. Connections between the client and Exchange won't use Extended Protection for Authentication on this virtual directory. This is the default setting. -- Allow Extended Protection for Authentication will be used for connections between the client and Exchange on this virtual directory if both the client and server support Extended Protection for Authentication. Connections that don't support Extended Protection for Authentication on the client and server will work, but may not be as secure as a connection using Extended Protection for Authentication. +- None Extended Protection for Authentication isn't used. Connections between the client and Exchange don't use Extended Protection for Authentication on this virtual directory. This is the default setting. +- Allow Extended Protection for Authentication is used for connections between the client and Exchange on this virtual directory if both the client and server support Extended Protection for Authentication. Connections that don't support Extended Protection for Authentication on the client and server work, but might not be as secure as a connection using Extended Protection for Authentication. +- Require Extended Protection for Authentication is used for all connections between clients and Exchange servers for this virtual directory. If either the client or server doesn't support Extended Protection for Authentication, the connection between the client and server will fail. If you set this option, you must also set a value for the ExtendedProtectionSPNList parameter. -If you have a proxy server between the client and the Client Access server that's configured to terminate the client-to-proxy SSL channel, you must also configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. - -- Require Extended Protection for Authentication will be used for all connections between clients and Exchange servers for this virtual directory. If either the client or server doesn't support Extended Protection for Authentication, the connection between the client and server will fail. If you set this option, you must also set a value for the ExtendedProtectionSPNList parameter. - -If you have a proxy server between the client and the Client Access server that's configured to terminate the client-to-proxy SSL channel, you must also configure one or more SPNs using the parameter ExtendedProtectionSPNList. +**Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter. To learn more about Extended Protection for Authentication, see [Understanding Extended Protection for Authentication](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/ff459225(v=exchg.141)). @@ -291,7 +288,7 @@ Accept wildcard characters: False The IISAuthenticationMethods parameter specifies the authentication method that's enabled on the /rpc virtual directory in IIS. You can set the virtual directory to allow Basic authentication or NTLM authentication. Alternatively, you can also set the virtual directory to allow both Basic and NTLM authentication. All other authentication methods are disabled. -You may want to enable both Basic and NTLM authentication if you're using the IIS virtual directory with multiple applications that require different authentication methods. +You might want to enable both Basic and NTLM authentication if you're using the IIS virtual directory with multiple applications that require different authentication methods. When you configure this setting using the IIS interface, you can enable as many authentication methods as you want. diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md index 1224f593ff..46b914e2ec 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md @@ -15,7 +15,7 @@ title: Enable-OutlookProtectionRule ## SYNOPSIS **Note**: This cmdlet is no longer supported in the cloud-based service. -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Enable-OutlookProtectionRule cmdlet to enable an existing Outlook protection rule. @@ -34,7 +34,7 @@ Enable-OutlookProtectionRule [-Identity] ## DESCRIPTION Outlook protection rules are used to automatically Information Rights Management (IRM)-protect messages using a Rights Management Services (RMS) template before the message is sent. However, Outlook protection rules don't inspect message content. To rights-protect messages based on message content, use transport protection rules. For more information, see [Outlook protection rules](https://learn.microsoft.com/exchange/outlook-protection-rules-exchange-2013-help). -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md b/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md index 468851c7ae..79a0e49acc 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md @@ -34,7 +34,7 @@ Enable-PushNotificationProxy [-Confirm] ## DESCRIPTION The push notification proxy relays event notifications (for example, new email or calendar updates) for on-premises mailboxes through Microsoft 365 to Outlook on the web for devices on the user's device. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md index a6256027c7..26f49783c0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md @@ -102,7 +102,7 @@ Directory synchronization must be configured correctly for a mailbox to be creat The policies that you apply to recipients in the on-premises Exchange organization, such as Unified Messaging or compliance policies, aren't applied to mailboxes in the service. You must configure policies in the service if you want policies to be applied to recipients in the service. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ReportSubmissionRule.md index 56e3f4dd50..8cb09e07a1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-ReportSubmissionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ReportSubmissionRule.md @@ -29,7 +29,7 @@ Enable-ReportSubmissionRule [-Identity] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-SafeAttachmentRule.md index f90229ee73..352b045c45 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-SafeAttachmentRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-SafeAttachmentRule.md @@ -31,7 +31,7 @@ Enable-SafeAttachmentRule [-Identity] ## DESCRIPTION Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about). -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-SafeLinksRule.md index c328540126..a488f199df 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-SafeLinksRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-SafeLinksRule.md @@ -31,7 +31,7 @@ Enable-SafeLinksRule [-Identity] ## DESCRIPTION Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ServiceEmailChannel.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ServiceEmailChannel.md index 2e4d132aa7..d4a9119467 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-ServiceEmailChannel.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ServiceEmailChannel.md @@ -32,7 +32,7 @@ Enable-ServiceEmailChannel [-Identity] ## DESCRIPTION The .NET service channel enables Microsoft Exchange to store information that it later forwards to applications or devices that aren't permanently connected to the server running Exchange. This cmdlet creates a receive folder in the user's mailbox under the root folder named Service E-mail. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-SmtpDaneInbound.md b/exchange/exchange-ps/ExchangePowerShell/Enable-SmtpDaneInbound.md index 98ea3d22e8..0198844e56 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-SmtpDaneInbound.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-SmtpDaneInbound.md @@ -31,7 +31,7 @@ Enable-SmtpDaneInbound [-DomainName] ## DESCRIPTION For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works). -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-SweepRule.md index db15150448..da7cacb624 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-SweepRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-SweepRule.md @@ -13,7 +13,7 @@ title: Enable-SweepRule # Enable-SweepRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Enable-SweepRule cmdlet to enable Sweep rules in mailboxes. @@ -31,7 +31,7 @@ Enable-SweepRule [-Identity] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Enable-TransportAgent.md index 1c9fd5b5c9..3b13e5f06b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-TransportAgent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-TransportAgent.md @@ -31,7 +31,7 @@ Enable-TransportAgent [-Identity] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md index fad19405e6..a5df89ce00 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md @@ -13,7 +13,7 @@ title: Enable-TransportRule # Enable-TransportRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Enable-TransportRule cmdlet to enable transport rules (mail flow rules) in your organization. @@ -33,7 +33,7 @@ Enable-TransportRule [-Identity] ## DESCRIPTION To disable rules that are enabled, use the Disable-TransportRule cmdlet. -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 @@ -124,11 +124,11 @@ Accept wildcard characters: False The Mode parameter specifies how the rule operates after it's enabled. Valid values are: -- Audit: The actions that the rule would have taken are written to the message tracking log, but no any action is taken on the message that would impact delivery. +- Audit: The actions that the rule would have taken are written to the message tracking log, but no any action is taken on the message that would affect delivery. - AuditAndNotify: The rule operates the same as in Audit mode, but notifications are also enabled. - Enforce: All actions specified in the rule are taken. -The value that has already been set in the rule will be persevered, unless -Mode parameter is specified. +If you don't use this parameter, the value already set in the rule is persevered. ```yaml Type: RuleMode diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMAutoAttendant.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMAutoAttendant.md index fdf6d70163..6738fa8dca 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMAutoAttendant.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMAutoAttendant.md @@ -32,7 +32,7 @@ Enable-UMAutoAttendant [-Identity] ## DESCRIPTION The Enable-UMAutoAttendant cmdlet enables the UM auto attendant by modifying its status variable. When you create a UM auto attendant, it isn't enabled by default. For the auto attendant to answer incoming calls, you must first enable it. After this task is completed, the UM auto attendant answers incoming calls. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMCallAnsweringRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMCallAnsweringRule.md index 1d442c6278..d5f4e06300 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMCallAnsweringRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMCallAnsweringRule.md @@ -15,7 +15,7 @@ title: Enable-UMCallAnsweringRule ## SYNOPSIS This cmdlet is available only in on-premises Exchange. -Use the Enable-UMCallAnsweringRule cmdlet to enable a call answering rule that has been created within a UM-enabled mailbox. +Use the Enable-UMCallAnsweringRule cmdlet to enable a call answering rule that is created within a UM-enabled mailbox. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -35,7 +35,7 @@ The Enable-UMCallAnsweringRule cmdlet enables the call answering rule by modifyi After this task is completed, the cmdlet sets the parameters and values specified. When you enable a call answering rule, the call answering rule is processed when an incoming call is received. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMIPGateway.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMIPGateway.md index a26ffb5377..257616fe21 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMIPGateway.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMIPGateway.md @@ -34,7 +34,7 @@ The status variable for a UM IP gateway can be used to enable or disable call an After this task is completed, the UM IP gateway answers incoming calls and makes outgoing calls through the IP gateway or IP Private Branch eXchange (PBX). -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMMailbox.md index 67cdd97fb3..702bc96be8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMMailbox.md @@ -63,7 +63,7 @@ Enable-UMMailbox [-Identity] ## DESCRIPTION When the mailbox is enabled for Unified Messaging, the settings from a UM mailbox policy are applied to the mailbox. After the mailbox is enabled for Unified Messaging, the user can use the UM features that are included in Microsoft Exchange. -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 @@ -140,7 +140,7 @@ Accept wildcard characters: False The AutomaticSpeechRecognitionEnabled parameter specifies whether to enable Automatic Speech Recognition (ASR) for the UM mailbox. Valid values are: -- $true: ASR is enabled for the mailbox. This is the default value. ASR is available only if the user's specified preferred language is installed. +- $true: ASR is enabled for the mailbox. This value is the default. ASR is available only if the user's specified preferred language is installed. - $false: ASR is disabled for the mailbox. ```yaml @@ -336,7 +336,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016 -The SendWelcomeMail parameter specifies whether you want to send a welcome message after the mailbox has been enabled for UM. Valid values are: +The SendWelcomeMail parameter specifies whether you want to send a welcome message after the mailbox is enabled for UM. Valid values are: - $true: Send the welcome to UM message. - $false: Don't send the welcome to UM message. @@ -375,7 +375,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016 -The ValidateOnly switch tells the cmdlet to evaluate the conditions and requirements necessary to perform the operation and then reports whether the operation will succeed or fail. You don't need to specify a value with this switch. +The ValidateOnly switch specifies whether to evaluate the potential success or failure of the command without making changes. You don't need to specify a value with this switch. No changes are made when the ValidateOnly switch is used. diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMServer.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMServer.md index 8ee6d80f46..44f9f235b6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMServer.md @@ -30,11 +30,11 @@ Enable-UMServer [-Identity] ``` ## DESCRIPTION -The Enable-UMServer cmdlet sets the status of a Unified Messaging server. A UM server has a logical status variable controlled using the enable and disable cmdlets. A UM server won't process any new calls unless it's in the enabled state. With the status variable, you can start or stop call processing on a UM server so the UM server can be brought online or taken offline in a controlled way. +The Enable-UMServer cmdlet sets the status of a Unified Messaging server. A UM server has a logical status variable controlled using the enable and disable cmdlets. A UM server doesn't process any new calls unless it's in the enabled state. With the status variable, you can start or stop call processing on a UM server so the UM server can be brought online or taken offline in a controlled way. After this task is completed, the Unified Messaging server is available to answer incoming calls. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMService.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMService.md index 3207726463..9804245e88 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMService.md @@ -32,11 +32,11 @@ Enable-UMService [-Identity] ``` ## DESCRIPTION -The Enable-UMService cmdlet sets the status of an Exchange server running the Unified Messaging server role. A UM server has a logical status variable controlled using the enable and disable cmdlets. A UM server won't process any new calls unless it's in the enabled state. With the status variable, you can start or stop call processing on a UM server so the UM server can be brought online or taken offline in a controlled way. +The Enable-UMService cmdlet sets the status of an Exchange server running the Unified Messaging server role. A UM server has a logical status variable controlled using the enable and disable cmdlets. A UM server doesn't process any new calls unless it's in the enabled state. With the status variable, you can start or stop call processing on a UM server so the UM server can be brought online or taken offline in a controlled way. After this task is completed, the UM server is available to answer incoming calls. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Execute-AzureADLabelSync.md b/exchange/exchange-ps/ExchangePowerShell/Execute-AzureADLabelSync.md index 3868bcd8ea..2290b1aed6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Execute-AzureADLabelSync.md +++ b/exchange/exchange-ps/ExchangePowerShell/Execute-AzureADLabelSync.md @@ -35,7 +35,7 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned Execute-AzureADLabelSync ``` -This example will initialize the synchronization of sensitivity labels into Microsoft Entra ID. +This example initializes the synchronization of sensitivity labels into Microsoft Entra ID. ## PARAMETERS diff --git a/exchange/exchange-ps/ExchangePowerShell/Expedite-Delicensing.md b/exchange/exchange-ps/ExchangePowerShell/Expedite-Delicensing.md index f490e9a900..349d748c48 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Expedite-Delicensing.md +++ b/exchange/exchange-ps/ExchangePowerShell/Expedite-Delicensing.md @@ -27,7 +27,7 @@ Expedite-Delicensing [-Identity] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-ActiveSyncLog.md b/exchange/exchange-ps/ExchangePowerShell/Export-ActiveSyncLog.md index 044fde6d46..cce74c131a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Export-ActiveSyncLog.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-ActiveSyncLog.md @@ -37,7 +37,7 @@ Export-ActiveSyncLog -Filename ## DESCRIPTION The Export-ActiveSyncLog cmdlet parses the IIS log files and returns information about Exchange ActiveSync usage. This cmdlet can export the output to a file or display it in the Exchange Management Shell. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-ActivityExplorerData.md b/exchange/exchange-ps/ExchangePowerShell/Export-ActivityExplorerData.md index 9da4987e32..83eee07bc7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Export-ActivityExplorerData.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-ActivityExplorerData.md @@ -179,7 +179,7 @@ This example exports a maximum of 5000 records for the specified date range in J Export-ActivityExplorerData -StartTime "07/08/2022 07:15 AM" -EndTime "07/08/2022 11:08 AM" -OutputFormat Json ``` -This example exports up to 100 records for the specified date range in Json format. If more than 100 records are available, the value of the LastPage property in the command output will be False. Use the value of the Watermark property as the value of the PageCookie parameter in a new query to get the next set of records. +This example exports up to 100 records for the specified date range in Json format. If more than 100 records are available, the value of the LastPage property in the command output is False. Use the value of the Watermark property as the value of the PageCookie parameter in a new query to get the next set of records. ### Example 3 ```powershell @@ -431,7 +431,7 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable ## NOTES The date-time field exported via this cmdlet is in Coordinated Universal Time (UTC). -The cmdlet exports following data columns. However, not all columns will be present for each activity. For details on exported column for different activities, we recommend checking the activities in [Activity Explorer](https://learn.microsoft.com/purview/data-classification-activity-explorer). +The cmdlet exports following data columns. However, not all columns are present for each activity. For details on exported column for different activities, we recommend checking the activities in [Activity Explorer](https://learn.microsoft.com/purview/data-classification-activity-explorer). - Activity - Application diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-AutoDiscoverConfig.md b/exchange/exchange-ps/ExchangePowerShell/Export-AutoDiscoverConfig.md index b0ec8af14a..c347036561 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Export-AutoDiscoverConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-AutoDiscoverConfig.md @@ -34,9 +34,9 @@ Export-AutoDiscoverConfig -TargetForestDomainController ``` ## DESCRIPTION -The Autodiscover Service Connection Point pointer resides Active Directory in the user account forest and includes the LDAP URL of the resource forest that the client will use to locate the Autodiscover service in the resource forest. +The Autodiscover Service Connection Point pointer resides Active Directory in the user account forest. The pointer includes the LDAP URL of the resource forest that the client uses to locate the Autodiscover service in the resource forest. -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 @@ -62,7 +62,7 @@ This example specifies that Exchange is deployed in more than one Active Directo The TargetForestDomainController parameter specifies the forest or domain controller that you want to export the Autodiscover configuration to. -If the target domain controller requires signing, you'll get the error: "A more secure authentication method is required for this server". Domain controllers that require signing aren't supported. +If the target domain controller requires signing, you get the error: "A more secure authentication method is required for this server". Domain controllers that require signing aren't supported. ```yaml Type: String @@ -140,7 +140,7 @@ Accept wildcard characters: False The MultipleExchangeDeployments parameter specifies whether multiple Exchange deployments exist. Valid values are: - $true: Exchange is deployed in more than one Active Directory forest, and the forests are connected. The list of authoritative accepted domains for the source forest is written to the Autodiscover service connection point object. Outlook clients use this object to select the most appropriate forest to search for the Autodiscover service. -- $False: Multiple Exchange deployments aren't used. This is the default value. +- $False: Multiple Exchange deployments aren't used. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-DlpPolicyCollection.md b/exchange/exchange-ps/ExchangePowerShell/Export-DlpPolicyCollection.md index fd15f00128..63d707a6a2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Export-DlpPolicyCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-DlpPolicyCollection.md @@ -13,7 +13,7 @@ title: Export-DlpPolicyCollection # Export-DlpPolicyCollection ## SYNOPSIS -**Note**: This cmdlet has been retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). +**Note**: This cmdlet is retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). This cmdlet is functional only in on-premises Exchange. @@ -34,7 +34,7 @@ Export-DlpPolicyCollection [[-Identity] ] ## DESCRIPTION The Export-DlpPolicyCollection cmdlet exports the settings of the DLP policies and the associated transport rules. You use the Import-DlpPolicyCollection to import the DLP policy collection into your organization. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Export-ExchangeCertificate.md index 0d42ee0899..46aae8392f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Export-ExchangeCertificate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-ExchangeCertificate.md @@ -57,7 +57,7 @@ The Export-ExchangeCertificate cmdlet creates the following types of files: Typically, you export a certificate request file if you need to resubmit the certificate request to the certification authority. You can't import an exported certificate request on another server. -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 @@ -161,7 +161,7 @@ Accept wildcard characters: False The BinaryEncoded switch encodes the exported certificate or certificate request file by using Distinguished Encoding Rules (DER). You don't need to specify a value with this switch. -Typically, you use this switch when you export a certificate, because you can store the certificate and its private key or chain of trust in a single binary file when you also use the Password parameter. If you don't use this switch, the exported certificate file is Base64 encoded, and you'll need to export any intermediate or root certificates in the chain of trust separately. +Typically, you use this switch when you export a certificate, because you can store the certificate and its private key or chain of trust in a single binary file when you also use the Password parameter. If you don't use this switch, the exported certificate file is Base64 encoded, and you need to export any intermediate or root certificates in the chain of trust separately. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-JournalRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Export-JournalRuleCollection.md index 88844ce4ba..556b223c09 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Export-JournalRuleCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-JournalRuleCollection.md @@ -33,7 +33,7 @@ Export-JournalRuleCollection [[-Identity] ] ## DESCRIPTION You can use the Export-JournalRuleCollection cmdlet to export journal rules in your organization to create a backup copy of your rules. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-MailboxDiagnosticLogs.md b/exchange/exchange-ps/ExchangePowerShell/Export-MailboxDiagnosticLogs.md index fac4b1dd30..98b784d811 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Export-MailboxDiagnosticLogs.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-MailboxDiagnosticLogs.md @@ -13,7 +13,7 @@ title: Export-MailboxDiagnosticLogs # Export-MailboxDiagnosticLogs ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Export-MailboxDiagnosticLogs cmdlet to export diagnostic data from user and system mailboxes in your organization. @@ -51,7 +51,7 @@ Export-MailboxDiagnosticLogs [-Identity] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-Message.md b/exchange/exchange-ps/ExchangePowerShell/Export-Message.md index 4046ba538f..c550e5f436 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Export-Message.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-Message.md @@ -31,7 +31,7 @@ Export-Message [-Identity] ## DESCRIPTION The Export-Message cmdlet copies messages from the Delivery queue, the Unreachable queue, or the poison message queue on Mailbox server or an Edge Transport server to a specified file path. Before you export a message, you must first suspend the message. Messages in the poison message queue are already suspended. You can use the Export-Message cmdlet to copy messages to the Replay directory of another Mailbox server for delivery. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-MigrationReport.md b/exchange/exchange-ps/ExchangePowerShell/Export-MigrationReport.md index 98abe6ceae..f01bf9c014 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Export-MigrationReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-MigrationReport.md @@ -13,7 +13,7 @@ title: Export-MigrationReport # Export-MigrationReport ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. The Export-MigrationReport is used by the Exchange migration process to enable an administrator to download a CSV file that contains migration errors for a selected migration batch. This cmdlet isn't run by an administrator in Windows PowerShell. @@ -42,7 +42,7 @@ Export-MigrationReport [-Identity] -RowCount ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-RecipientDataProperty.md b/exchange/exchange-ps/ExchangePowerShell/Export-RecipientDataProperty.md index be24b3e0be..f7ded90650 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Export-RecipientDataProperty.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-RecipientDataProperty.md @@ -42,7 +42,7 @@ Export-RecipientDataProperty [-Identity] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-TransportRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Export-TransportRuleCollection.md index 18d538f220..733a9c53f1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Export-TransportRuleCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-TransportRuleCollection.md @@ -13,7 +13,7 @@ title: Export-TransportRuleCollection # Export-TransportRuleCollection ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Export-TransportRuleCollection cmdlet to export the transport rules in your organization. @@ -36,7 +36,7 @@ The Export-TransportRuleCollection cmdlet can be used to export the transport ru Exporting the rules collection is a two-step process. You first export the rules collection to a variable, and then use the Set-Content cmdlet to write the data to an XML file. For more information, see [Set-Content](https://learn.microsoft.com/powershell/module/microsoft.powershell.management/set-content). -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-UMCallDataRecord.md b/exchange/exchange-ps/ExchangePowerShell/Export-UMCallDataRecord.md index 0b1bb2fb95..2cae15c5ab 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Export-UMCallDataRecord.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-UMCallDataRecord.md @@ -36,7 +36,7 @@ The Export-UMCallDataRecord cmdlet exports Unified Messaging call data records f After this task is completed, a report is generated that contains Unified Messaging call data records. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-UMPrompt.md b/exchange/exchange-ps/ExchangePowerShell/Export-UMPrompt.md index 99782c9c33..3e7bdb2f80 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Export-UMPrompt.md +++ b/exchange/exchange-ps/ExchangePowerShell/Export-UMPrompt.md @@ -44,7 +44,7 @@ The Export-UMPrompt cmdlet exports prompts that belong to existing UM dial plan After this task is completed, the UM prompts are displayed or saved. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ADPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-ADPermission.md index d946553a7a..bb70e13cd8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ADPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ADPermission.md @@ -38,9 +38,9 @@ Get-ADPermission [-Identity] ``` ## 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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ADServerSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ADServerSettings.md index 60f17efd20..d34e36afaa 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ADServerSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ADServerSettings.md @@ -26,7 +26,7 @@ Get-ADServerSettings [] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ADSite.md b/exchange/exchange-ps/ExchangePowerShell/Get-ADSite.md index fd05d2e031..6849e8bdc0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ADSite.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ADSite.md @@ -30,7 +30,7 @@ Get-ADSite [[-Identity] ] ## DESCRIPTION Exchange uses Active Directory sites and the costs assigned to the Active Directory site links to make message routing decisions. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ADSiteLink.md b/exchange/exchange-ps/ExchangePowerShell/Get-ADSiteLink.md index ed22b0467f..cc1b89a208 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ADSiteLink.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ADSiteLink.md @@ -28,7 +28,7 @@ Get-ADSiteLink [[-Identity] ] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ATPBuiltInProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ATPBuiltInProtectionRule.md index 1ff7c3140b..2cb22176b0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ATPBuiltInProtectionRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ATPBuiltInProtectionRule.md @@ -28,7 +28,7 @@ Get-ATPBuiltInProtectionRule [[-Identity] ] [-Stat ## DESCRIPTION For more information about preset security policies, see [Preset security policies in EOP and Microsoft Defender for Office 365](https://learn.microsoft.com/defender-office-365/preset-security-policies). -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ATPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ATPProtectionPolicyRule.md index 1463a2e760..963826fe7e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ATPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ATPProtectionPolicyRule.md @@ -30,7 +30,7 @@ Get-ATPProtectionPolicyRule [[-Identity] ] ## DESCRIPTION For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ATPTotalTrafficReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-ATPTotalTrafficReport.md index 75b267a41d..75dddf8e56 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ATPTotalTrafficReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ATPTotalTrafficReport.md @@ -56,7 +56,7 @@ If the tenant had Safe Attachments or Safe Links policies, the messages would ha By default, the command returns data for the last 14 days. Data for the last 90 days is available. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-AcceptedDomain.md index 9ba5ea4926..7748fcd4fb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AcceptedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AcceptedDomain.md @@ -13,7 +13,7 @@ title: Get-AcceptedDomain # Get-AcceptedDomain ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-AcceptedDomain cmdlet to view the configuration information for the accepted domains in your organization. @@ -29,7 +29,7 @@ Get-AcceptedDomain [[-Identity] ] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AccessToCustomerDataRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-AccessToCustomerDataRequest.md index b2043007fa..995c951c19 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AccessToCustomerDataRequest.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AccessToCustomerDataRequest.md @@ -31,7 +31,7 @@ Get-AccessToCustomerDataRequest [-ApprovalStatus ] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDevice.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDevice.md index ddefef7cd4..38fa08786f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDevice.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDevice.md @@ -13,7 +13,7 @@ title: Get-ActiveSyncDevice # Get-ActiveSyncDevice ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-ActiveSyncDevice cmdlet to retrieve the list of devices in your organization that have active Exchange ActiveSync partnerships. @@ -50,7 +50,7 @@ Get-ActiveSyncDevice [[-Identity] ] ## DESCRIPTION The Get-ActiveSyncDevice cmdlet returns identification, configuration and status information for each device. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAccessRule.md index d5102b012a..969dff3485 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAccessRule.md @@ -13,7 +13,7 @@ title: Get-ActiveSyncDeviceAccessRule # Get-ActiveSyncDeviceAccessRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-ActiveSyncDeviceAccessRule cmdlet to retrieve an access group of Exchange mobile devices along with their access level. @@ -30,7 +30,7 @@ Get-ActiveSyncDeviceAccessRule [[-Identity] ] ## DESCRIPTION You can use this cmdlet to view a list of mobile phones or devices by type. For example, you can return a list of all Android mobile digital devices in the organization or all Windows Phone devices in the organization. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceStatistics.md index c79c8576e2..08446a5d56 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceStatistics.md @@ -13,7 +13,7 @@ title: Get-ActiveSyncDeviceStatistics # Get-ActiveSyncDeviceStatistics ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-ActiveSyncDeviceStatistics cmdlet to retrieve the list of mobile devices configured to synchronize with a specified user's mailbox and return a list of statistics about the mobile devices. @@ -46,7 +46,7 @@ Get-ActiveSyncDeviceStatistics -Mailbox ## DESCRIPTION The Get-ActiveSyncDeviceStatistics cmdlet returns a list of statistics about each mobile device. Additionally, it allows you to retrieve logs and send those logs to a recipient for troubleshooting purposes. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncMailboxPolicy.md index 13cdaabfc9..daa6a942b5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncMailboxPolicy.md @@ -13,7 +13,7 @@ title: Get-ActiveSyncMailboxPolicy # Get-ActiveSyncMailboxPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-ActiveSyncMailboxPolicy cmdlet to retrieve the Mobile Device mailbox policy settings for a specific Mobile Device mailbox policy. @@ -32,7 +32,7 @@ Get-ActiveSyncMailboxPolicy [[-Identity] ] ## DESCRIPTION A Mobile Device mailbox policy is a group of settings that specifies how mobile devices enabled for Microsoft Exchange ActiveSync connect to the computer running Exchange. Exchange supports multiple Mobile Device mailbox policies. The Get-ActiveSyncMailboxPolicy cmdlet displays all the policy settings for the specified policy. These settings include password settings, file access settings and attachment settings. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncOrganizationSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncOrganizationSettings.md index c6cd6f96fa..a8b91cba75 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncOrganizationSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncOrganizationSettings.md @@ -13,7 +13,7 @@ title: Get-ActiveSyncOrganizationSettings # Get-ActiveSyncOrganizationSettings ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-ActiveSyncOrganizationSettings cmdlet to view the Microsoft Exchange ActiveSync settings for your organization. @@ -28,7 +28,7 @@ Get-ActiveSyncOrganizationSettings [[-Identity] ] ## DESCRIPTION Microsoft Exchange servers have a default virtual directory that Exchange ActiveSync mobile devices use to synchronize with the server. You can create multiple virtual directories and assign different devices to different directories. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AddressBookPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AddressBookPolicy.md index 48627a19bd..14bcfbf882 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AddressBookPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AddressBookPolicy.md @@ -13,7 +13,7 @@ title: Get-AddressBookPolicy # Get-AddressBookPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-AddressBookPolicy cmdlet to return address book policies that match the specified conditions. @@ -30,7 +30,7 @@ Get-AddressBookPolicy [[-Identity] ] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Get-AddressList.md index 7eacd33705..16fd763848 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AddressList.md @@ -13,7 +13,7 @@ title: Get-AddressList # Get-AddressList ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-AddressList cmdlet to view address lists. @@ -47,7 +47,7 @@ Get-AddressList [-SearchText ] ## DESCRIPTION You can pipe the output from the Get-AddressList cmdlet to the Remove-AddressList, Set-AddressList, Update-AddressList and Move-AddressList cmdlets instead of using the Identity parameter with each of those cmdlets. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AdminAuditLogConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-AdminAuditLogConfig.md index 98e1a44545..975a94075f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AdminAuditLogConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AdminAuditLogConfig.md @@ -13,7 +13,7 @@ title: Get-AdminAuditLogConfig # Get-AdminAuditLogConfig ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-AdminAuditLogConfig cmdlet to view the administrator audit logging configuration settings. @@ -29,7 +29,7 @@ Get-AdminAuditLogConfig [-DomainController ] ## DESCRIPTION To check the UnifiedAuditLogIngestionEnabled value in the output of this cmdlet, run the command in Exchange Online PowerShell. The value in Security & Compliance PowerShell is always False and the Set-AdminAuditLogConfig cmdlet (and the UnifiedAuditLogIngestionEnabled parameter) is not available to change it. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AdministrativeUnit.md b/exchange/exchange-ps/ExchangePowerShell/Get-AdministrativeUnit.md index d1db51fb3f..9a605c829e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AdministrativeUnit.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AdministrativeUnit.md @@ -32,7 +32,7 @@ Get-AdministrativeUnit [[-Identity] ] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AgentLog.md b/exchange/exchange-ps/ExchangePowerShell/Get-AgentLog.md index 7cc4bd9fa0..5c34512eea 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AgentLog.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AgentLog.md @@ -30,7 +30,7 @@ Get-AgentLog [-EndDate ] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AggregateZapReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-AggregateZapReport.md index fe08151188..1a7944c6c3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AggregateZapReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AggregateZapReport.md @@ -37,7 +37,7 @@ For the reporting period you specify, the cmdlet returns the following informati - EventType - ZapActionCount -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishPolicy.md index 86ea27c33c..819eba076b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishPolicy.md @@ -30,7 +30,7 @@ Get-AntiPhishPolicy [-Identity ] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishRule.md index d21b4063d9..729fd881f2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishRule.md @@ -28,7 +28,7 @@ Get-AntiPhishRule [[-Identity] ] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-App.md b/exchange/exchange-ps/ExchangePowerShell/Get-App.md index a1ade6001f..4dfc80bbfd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-App.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-App.md @@ -13,7 +13,7 @@ title: Get-App # Get-App ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-App cmdlet to view installed apps. @@ -33,7 +33,7 @@ Get-App [[-Identity] ] ## DESCRIPTION The Get-App cmdlet returns information about all installed apps or the details of a specific installed app. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AppRetentionCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AppRetentionCompliancePolicy.md index a945fa35af..bf1ee91fe5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AppRetentionCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AppRetentionCompliancePolicy.md @@ -30,7 +30,7 @@ Get-AppRetentionCompliancePolicy [[-Identity] ] ``` ## DESCRIPTION -\*-AppRetentionCompliance\* cmdlets are used for policies with adaptive policy scopes and all static policies that cover Teams private channels, Viva Engage chats, and Viva Engage community messages. Eventually, you'll use these cmdlets for most retention locations and policy types. The \*-RetentionCompliance\* cmdlets will continue to support Exchange and SharePoint locations primarily. For policies created with the \*-AppRetentionCompliance\* cmdlets, you can only set the list of included or excluded scopes for all included workloads, which means you'll likely need to create one policy per workload. +\*-AppRetentionCompliance\* cmdlets are used for policies with adaptive policy scopes and all static policies that cover Teams private channels, Viva Engage chats, and Viva Engage community messages. Eventually, you'll use these cmdlets for most retention locations and policy types. The \*-RetentionCompliance\* cmdlets will continue to support Exchange and SharePoint locations primarily. For policies created with the \*-AppRetentionCompliance\* cmdlets, you can only set the list of included or excluded scopes for all included workloads, which means you likely need to create one policy per workload. To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ApplicationAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ApplicationAccessPolicy.md index 83a5b541f3..e2c7f08d47 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ApplicationAccessPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ApplicationAccessPolicy.md @@ -29,7 +29,7 @@ Get-ApplicationAccessPolicy [[-Identity] ] ## DESCRIPTION This feature applies only to apps connecting to the Microsoft Graph API for Outlook resources. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ArcConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-ArcConfig.md index 49101ba1b4..b85c65bf0f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ArcConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ArcConfig.md @@ -28,7 +28,7 @@ Get-ArcConfig [] ## DESCRIPTION Services that modify message content in transit before delivery can invalidate DKIM email signatures and affect the authentication of the message. These services can use ARC to provide details of the original authentication before the modifications occurred. Your organization can then trust these details to help authenticate the message. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AtpPolicyForO365.md b/exchange/exchange-ps/ExchangePowerShell/Get-AtpPolicyForO365.md index 6af619e308..4ab8b7aacd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AtpPolicyForO365.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AtpPolicyForO365.md @@ -37,7 +37,7 @@ Safe Documents scans documents and files that are opened in Protected View. For Safe Attachments for SharePoint, OneDrive, and Microsoft Teams prevents users from opening and downloading files that are identified as malicious. For more information, see [Safe Attachments for SharePoint, OneDrive, and Microsoft Teams](https://learn.microsoft.com/defender-office-365/safe-attachments-for-spo-odfb-teams-about). -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuditLogSearch.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuditLogSearch.md index eb76ab1d68..1074a5cee0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AuditLogSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuditLogSearch.md @@ -13,7 +13,7 @@ title: Get-AuditLogSearch # Get-AuditLogSearch ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-AuditLogSearch cmdlet to return a list of current audit log searches that were created with the New-AdminAuditLogSearch or New-MailboxAuditLogSearch cmdlets. The Get-AuditLogSearch cmdlet also returns audit log searches that are initiated whenever an administrator uses the Exchange admin center (EAC) to export audit logs. @@ -31,9 +31,9 @@ Get-AuditLogSearch [[-Identity] ] ``` ## DESCRIPTION -Run the Get-AuditLogSearch cmdlet to return a list of pending audit log searches. If an audit log search has been completed, it won't be displayed in the list of audit log searches. +Run the Get-AuditLogSearch cmdlet to return a list of pending audit log searches. If an audit log search has completed, it isn't displayed in the list of audit log searches. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthConfig.md index 0274db23b5..9f1e7d1fa9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthConfig.md @@ -27,7 +27,7 @@ Get-AuthConfig [-DomainController ] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthRedirect.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthRedirect.md index 51703adc07..2fd82357b2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthRedirect.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthRedirect.md @@ -30,7 +30,7 @@ Get-AuthRedirect [[-Identity] ] ## DESCRIPTION Exchange 2010 Client Access servers don't support OAuth authentication requests. OAuth redirection objects redirect OAuth authentication requests to Exchange servers that are running later versions of Exchange. This cmdlet is only useful if your organization has Exchange 2010 Client Access servers. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthServer.md index 169457a4a0..18a995e5e5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthServer.md @@ -13,7 +13,7 @@ title: Get-AuthServer # Get-AuthServer ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-AuthServer cmdlet to view the settings of authorization servers in the Exchange organization. @@ -30,7 +30,7 @@ Get-AuthServer [[-Identity] ] ## DESCRIPTION An authorization server is a server or service that issues tokens trusted by Microsoft Exchange for access by partner applications. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md index 5c142396b0..0cc8f2ce52 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md @@ -13,7 +13,7 @@ title: Get-AuthenticationPolicy # Get-AuthenticationPolicy ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-AuthenticationPolicy cmdlet to view authentication policies in your organization. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -28,7 +28,7 @@ Get-AuthenticationPolicy [[-Identity] ] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelPolicy.md index 5f3b883571..11abe41196 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelPolicy.md @@ -91,7 +91,7 @@ Accept wildcard characters: False The ForceValidate parameter specifies whether to include details related to the AdminUnits of users, groups, or sites in the policy. Valid values are: - $true: Various properties in the policy include details of the AdminUnits that are associated with current set of selected users, groups, or sites. -- $false: The output doesn't contain the information. This is the default value. +- $false: The output doesn't contain the information. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelRule.md index 1c816823d5..4db72e7ae3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelRule.md @@ -111,7 +111,7 @@ Accept wildcard characters: False The IncludeExecutionRuleGuids parameter specifies whether to include the execution rule GUID in the rule details. Valid values are: - $true: Include the execution rule GUID in the rule details. -- $false: Don't include the execution rule GUID in the rule details. This is the default value. +- $false: Don't include the execution rule GUID in the rule details. This value is the default. ```yaml Type: Boolean @@ -132,7 +132,7 @@ Accept wildcard characters: False The IncludeExecutionRuleInformation parameter specifies whether to include the execution rule information in the rule details. Valid values are: - $true: Include the execution rule information in the rule details. -- $false: Don't include the execution rule information in the rule details. This is the default value. +- $false: Don't include the execution rule information in the rule details. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-AutodiscoverVirtualDirectory.md index e37a13db48..9427b28c13 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AutodiscoverVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AutodiscoverVirtualDirectory.md @@ -40,7 +40,7 @@ Get-AutodiscoverVirtualDirectory [[-Identity] ] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityAddressSpace.md b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityAddressSpace.md index ee7c097c2e..dd98d48602 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityAddressSpace.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityAddressSpace.md @@ -13,7 +13,7 @@ title: Get-AvailabilityAddressSpace # Get-AvailabilityAddressSpace ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-AvailabilityAddressSpace cmdlet to view existing availability address space objects that are used to share free/busy data across Exchange organizations. @@ -30,7 +30,7 @@ Get-AvailabilityAddressSpace [[-Identity] ] ## DESCRIPTION In on-premises Exchange organizations, you run the Remove-AvailabilityAddressSpace cmdlet on Exchange servers that have the Client Access server role installed. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityConfig.md index 92f1bd5067..41769cda65 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityConfig.md @@ -13,7 +13,7 @@ title: Get-AvailabilityConfig # Get-AvailabilityConfig ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-AvailabilityConfig cmdlet to view information about the sharing of free/busy information between organizations: @@ -31,7 +31,7 @@ Get-AvailabilityConfig [[-Identity] ] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityReportOutage.md b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityReportOutage.md index 3bcdbbc750..34915d7e93 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityReportOutage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityReportOutage.md @@ -30,7 +30,7 @@ Get-AvailabilityReportOutage [[-Identity] ] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-BlockedConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-BlockedConnector.md index 9004e6d029..e32648d522 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-BlockedConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-BlockedConnector.md @@ -26,7 +26,7 @@ Get-BlockedConnector [-ConnectorId ] [] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-BlockedSenderAddress.md b/exchange/exchange-ps/ExchangePowerShell/Get-BlockedSenderAddress.md index 92c889fdec..8a230bbf7a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-BlockedSenderAddress.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-BlockedSenderAddress.md @@ -15,7 +15,7 @@ title: Get-BlockedSenderAddress ## SYNOPSIS This cmdlet is available only in the cloud-based service. -Use the Get-BlockedSenderAddress cmdlet to view users in your Microsoft 365 organization that are impacted by the protection system. These users sent multiple messages that were classified as spam, so they're blocked from sending messages. +Use the Get-BlockedSenderAddress cmdlet to view users in your Microsoft 365 organization that are affected by the protection system. These users sent multiple messages that were classified as spam, so they're blocked from sending messages. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -27,7 +27,7 @@ Get-BlockedSenderAddress [-SenderAddress ] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CASMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-CASMailbox.md index a742383485..01bae9325f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-CASMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-CASMailbox.md @@ -13,7 +13,7 @@ title: Get-CASMailbox # Get-CASMailbox ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-CASMailbox cmdlet to view the Client Access settings that are configured on mailboxes. @@ -66,7 +66,7 @@ Get-CASMailbox [[-Identity] ] ## DESCRIPTION This cmdlet returns a variety of client access settings for one or more mailboxes. These settings include options for Outlook on the web, Exchange ActiveSync, POP3, and IMAP4. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CASMailboxPlan.md b/exchange/exchange-ps/ExchangePowerShell/Get-CASMailboxPlan.md index 6f9a965d48..b18ba0fbd9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-CASMailboxPlan.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-CASMailboxPlan.md @@ -35,7 +35,7 @@ Get-CASMailboxPlan [[-Identity] ] ## DESCRIPTION A CAS mailbox plan is tied to the corresponding mailbox plan that has the same name (and display name). Like mailbox plans, CAS mailbox plans correspond to license types, and are applied to a mailbox when you license the user. The availability of a CAS mailbox plan is determined by your selections when you enroll in the service and the age of your organization. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticAnalysis.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticAnalysis.md index ed3b0dc62d..254a8bc41d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticAnalysis.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticAnalysis.md @@ -60,7 +60,7 @@ The following properties of the calendar item are returned in the default output - SenderEmailAddress - SentRepresentingDisplayName -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 @@ -155,7 +155,7 @@ Accept wildcard characters: False The DetailLevel parameter specifies the level of detail you want to see in the analysis output. Valid values are: -- Basic: This is the default value. The calendar item properties that are returned are listed in the Detailed Description. +- Basic: This value is the default. The calendar item properties that are returned are listed in the Detailed Description. - Advanced: 37 additional calendar item properties are returned. You should use this value only for detailed debugging information. ```yaml @@ -196,7 +196,7 @@ Accept wildcard characters: False The OutputAs parameter specifies the output format of the command. Valid values are: -- CSV (This is the default value) +- CSV (default value) - HTML - XML diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticLog.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticLog.md index 5de9699698..381a1fe665 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticLog.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticLog.md @@ -65,7 +65,7 @@ Get-CalendarDiagnosticLog [-Identity] -LogLocation ## DESCRIPTION The output of this cmdlet contains the following information: -- IsFileLink: Indicates whether the calendar item has been exported to a .msg file by using the LogLocation parameter. Values are True or False. +- IsFileLink: Indicates whether the calendar item is exported to a .msg file by using the LogLocation parameter. Values are True or False. - Identity: Identifies the mailbox that holds the calendar item. An example value is: excallog://laura@contoso.com/?id=RgAAAACF/h/dHTTkQbdPrk7z+G4SBwCoatc7EmnEQq1iF35p17stAAAAAAFEAACoatc7EmnEQq1iF35p17stAAAAABEIAAAP. - LogDate: The date-time that the calendar item was logged. - NormalizedSubject: The Subject field of the calendar item. @@ -73,7 +73,7 @@ The output of this cmdlet contains the following information: After you run the Get-CalendarDiagnosticLog cmdlet, you can analyze the calendar data using the Get-CalendarDiagnosticAnalysis cmdlet. For more information, see [Get-CalendarDiagnosticAnalysis](https://learn.microsoft.com/powershell/module/exchangepowershell/get-calendardiagnosticanalysis). -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 @@ -299,9 +299,9 @@ Accept wildcard characters: False The ExactMatch parameter specifies whether to use an exact match or a partial match for text values that you specify for the Subject parameter. Valid values are: - $true: The subject search uses an exact match and searches all calendar items in the mailbox. For example, if you search for "budget", the search looks for items that have "budget" anywhere in the subject, but not "budgeting". -- $false: The subject search uses a partial match and searches a maximum of 1000 calendar items in the mailbox. For example, if you search for "budget", the search looks for items that have "budget" and "budgeting" anywhere in the subject. This is the default value. +- $false: The subject search uses a partial match and searches a maximum of 1000 calendar items in the mailbox. For example, if you search for "budget", the search looks for items that have "budget" and "budgeting" anywhere in the subject. This value is the default. -A partial subject match search may not return all of the relevant calendar items. Try using an exact subject match search for more accurate results. +A partial subject match search might not return all of the relevant calendar items. Try using an exact subject match search for more accurate results. You only use this parameter with the Subject parameter. diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticObjects.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticObjects.md index 27ba38654a..8971b36801 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticObjects.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticObjects.md @@ -49,7 +49,7 @@ Get-CalendarDiagnosticObjects [-Identity] ## DESCRIPTION Some of the more interesting properties that are returned in the results are: -- AppointmentState: 1 = The appointment is a meeting, 2 = The appointment has been received, 4 = The appointment has been cancelled, and 8 = the appointment is a forwarded appointment. +- AppointmentState: 1 = The appointment is a meeting, 2 = The appointment is received, 4 = The appointment is cancelled, and 8 = the appointment is a forwarded appointment. - CalendarLogTriggerAction: The action that's taken on the item (for example, Create or Update). - ClientInfoString: The entity that made the change (for example, `Client=OWA;`, `Client=WebServices;`;, or `Client=TBA;Service=MSExchangeMailboxAssistants;Action=ELCAssistant;`). - MeetingRequestType: 1 = The meeting message is a meeting request, 65536 = The meeting message is a full update to an existing meeting, 131072 = The meeting message is an informational update to an existing meeting, 262144 = The meeting message is a silent update, 524288 = The update is outdated, or 1048576 = The meeting message is forwarded to a delegate, and the copy is marked as informational. @@ -57,7 +57,7 @@ Some of the more interesting properties that are returned in the results are: - ResponseType: 0 = The organizer hasn't received a response, 1 = The organizer's copy of the meeting, 2 = Tentative, 3 = Accept, 4 = Decline, or 5 = The attendee hasn't responded. - ResponsibleUserName: The LegacyExchangeDN value of the user who made the change (for example, `/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=BN6PR11MB1587/cn=Microsoft System Attendant` or `/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=696eea97d3c449eab648920d03385efb-admin`). -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 @@ -259,9 +259,9 @@ Accept wildcard characters: False The ExactMatch parameter specifies whether to use an exact match or a partial match for text values that you specify for the Subject parameter. Valid values are: - $true: The subject search uses an exact match and searches all calendar items in the mailbox. For example, if you search for "budget", the search looks for items that have "budget" anywhere in the subject, but not "budgeting". -- $false: The subject search uses a partial match and searches a maximum of 1000 calendar items in the mailbox. For example, if you search for "budget", the search looks for items that have "budget" and "budgeting" anywhere in the subject. This is the default value. +- $false: The subject search uses a partial match and searches a maximum of 1000 calendar items in the mailbox. For example, if you search for "budget", the search looks for items that have "budget" and "budgeting" anywhere in the subject. This value is the default. -A partial subject match search may not return all of the relevant calendar items. Try using an exact subject match search for more accurate results. +A partial subject match search might not return all of the relevant calendar items. Try using an exact subject match search for more accurate results. You only use this parameter with the Subject parameter. @@ -394,7 +394,7 @@ Accept wildcard characters: False The ShouldBindToItem parameter specifies whether to truncate large streamable property values (for example, AppointmentRecurrenceBlob). Valid values are: - $true: The values of large streamable properties aren't truncated, so the full value is returned. -- $false: The values of large streamable properties are truncated. This is the default value. +- $false: The values of large streamable properties are truncated. This value is the default. ```yaml Type: Boolean @@ -451,7 +451,7 @@ Accept wildcard characters: False The ShouldFetchRecurrenceExceptions parameter specifies whether to include exceptions to recurring meetings. Valid values are: - $true: Include exceptions to recurring meetings. When you use this value, you also need to use the ItemIds parameter. -- $false: Don't Include exceptions to recurring meetings. This is the default value. +- $false: Don't Include exceptions to recurring meetings. This value is the default. ```yaml Type: Boolean diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarNotification.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarNotification.md index 1f56a01412..8805d48276 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarNotification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarNotification.md @@ -17,7 +17,7 @@ This cmdlet is available only in on-premises Exchange. Use the Get-CalendarNotification cmdlet to view calendar text message notification settings for a mailbox. -**Note**: This cmdlet has been deprecated in Exchange Online PowerShell. The text message notification service has been discontinued in Microsoft 365. +**Note**: This cmdlet is deprecated in Exchange Online PowerShell. The text message notification service is discontinued in Microsoft 365. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -35,7 +35,7 @@ Get-CalendarNotification [-Identity] ## DESCRIPTION The Get-CalendarNotification cmdlet retrieves and displays the rules that trigger the calendar agenda notification, reminder notification, or update notification text messages. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarProcessing.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarProcessing.md index 87199882e2..7e0d1c3a47 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarProcessing.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarProcessing.md @@ -13,9 +13,9 @@ title: Get-CalendarProcessing # Get-CalendarProcessing ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. -Use the Get-CalendarProcessing cmdlet to view the calendar processing options for resource mailboxes, which include the Calendar Attendant, resource booking assistant and calendar configuration. Note that the settings returned by this cmdlet are editable only on resource mailboxes. +Use the Get-CalendarProcessing cmdlet to view the calendar processing options for resource mailboxes, which include the Calendar Attendant, resource booking assistant and calendar configuration. The settings returned by this cmdlet are editable only on resource mailboxes. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -32,7 +32,7 @@ Get-CalendarProcessing [-Identity] ## DESCRIPTION For details about the properties that are returned in the output of this cmdlet, see [Set-CalendarProcessing](https://learn.microsoft.com/powershell/module/exchangepowershell/set-calendarprocessing). -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CaseHoldPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-CaseHoldPolicy.md index 6f2f8b1488..e1c850af72 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-CaseHoldPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-CaseHoldPolicy.md @@ -102,7 +102,7 @@ Accept wildcard characters: False The DistributionDetail switch returns detailed policy distribution information on the case hold policy. You don't need to specify a value with this switch. -If you don't use this switch, the command won't return information about the current deployment status, and the DistributionStatus property will only show as "Pending". +If you don't use this switch, the command doesn't return information about the current deployment status, and the DistributionStatus property shows as "Pending". The following properties are affected by this switch: diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClassificationRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClassificationRuleCollection.md index eb41942aba..d193a9e80d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ClassificationRuleCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClassificationRuleCollection.md @@ -13,7 +13,7 @@ title: Get-ClassificationRuleCollection # Get-ClassificationRuleCollection ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-ClassificationRuleCollection cmdlet to view the classification rule collections in your organization. @@ -30,7 +30,7 @@ Get-ClassificationRuleCollection [[-Identity] [!NOTE] > Beginning in October 2022, client access rules were deprecated for all Exchange Online organizations that weren't using them. Client access rules will be deprecated for all remaining organizations on September 1, 2025. If you choose to turn off client access rules before the deadline, the feature will be disabled in your organization. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809). -This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-ClientAccessRule cmdlet to view client access rules. Client access rules help you control access to your cloud-based organization based on the properties of the connection. @@ -35,7 +35,7 @@ Get-ClientAccessRule [[-Identity] ] ## DESCRIPTION Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessServer.md index ae619fa9f7..09650e1a71 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessServer.md @@ -32,7 +32,7 @@ Get-ClientAccessServer [[-Identity] ] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessService.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessService.md index 75380355de..0bc4dd10e3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessService.md @@ -30,7 +30,7 @@ Get-ClientAccessService [[-Identity] ] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Clutter.md b/exchange/exchange-ps/ExchangePowerShell/Get-Clutter.md index 7ecfb68037..726b83b98e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-Clutter.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-Clutter.md @@ -28,7 +28,7 @@ Get-Clutter -Identity ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CmdletExtensionAgent.md b/exchange/exchange-ps/ExchangePowerShell/Get-CmdletExtensionAgent.md index bf76f861a0..2de9f2d0a0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-CmdletExtensionAgent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-CmdletExtensionAgent.md @@ -39,7 +39,7 @@ Get-CmdletExtensionAgent [[-Identity] ] ## DESCRIPTION Cmdlet extension agents are used by Exchange cmdlets in Exchange Server 2010 and later. Cmdlets provided by other Microsoft or non-Microsoft products can't use cmdlet extension agents. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceCase.md b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceCase.md index d0e22b0d1d..b28065f954 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceCase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceCase.md @@ -97,7 +97,7 @@ The CaseType parameter specifies the type of compliance case that you want to vi - ComplianceWorkspace: This value is reserved for internal Microsoft use. - DataInvestigation: Data investigation cases are used to investigate data spillage incidents. In the Microsoft Purview compliance portal, Data investigation cases are displayed on the **Data investigations** page. - DSR: Data Subject Request (DSR) cases are used to manage General Data Protection Regulation (GDPR) DSR investigations. In the Microsoft Purview compliance portal, DSR cases are displayed under **Data privacy** \> **Data subject requests**. -- eDiscovery: eDiscovery (also called eDiscovery Standard) cases are used to manage legal or other types of investigations. In the Microsoft Purview compliance portal, eDiscovery Standard cases are displayed under **eDiscovery** \> **Standard**. This is the default value. +- eDiscovery: eDiscovery (also called eDiscovery Standard) cases are used to manage legal or other types of investigations. In the Microsoft Purview compliance portal, eDiscovery Standard cases are displayed under **eDiscovery** \> **Standard**. This value is the default. - InsiderRisk: Insider risk cases are used to manage insider risk management cases. In the Microsoft Purview compliance portal, insider risk cases are displayed under **Insider risk management** \> **Cases**. Typically, insider risk management cases are manually created in the Microsoft Purview compliance portal to further investigate activity based on a risk alert. - InternalInvestigation: This value is reserved for internal Microsoft use. - SupervisionPolicy: This type of case corresponds to communication compliance policy. In the Microsoft Purview compliance portal, communication compliance policies are displayed under **Communication compliance** \> **Policies**. diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEventType.md b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEventType.md index eaa1c7f19c..a20b6d4bff 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEventType.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEventType.md @@ -28,7 +28,7 @@ Get-ComplianceRetentionEventType [-Identity ] ``` ## DESCRIPTION -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 @@ -76,7 +76,7 @@ Accept wildcard characters: False The LoadTag switch specifies whether to show the compliance tags that are associated with the retention event types. You don't need to specify a value with this switch. -If you don't use this switch, the ComplianceTag property will always appear empty in the results. +If you don't use this switch, the ComplianceTag property always appears empty in the results. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearch.md index 92d5c4ff7f..9ae15ddfbb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearch.md @@ -13,7 +13,7 @@ title: Get-ComplianceSearch # Get-ComplianceSearch ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-ComplianceSearch cmdlet to view estimate compliance searches in Exchange Server 2016 or later and in the Microsoft Purview compliance portal. After you use the New-ComplianceSearchAction cmdlet to define a preview action for the compliance search, use the Get-ComplianceSearchAction cmdlet to view the results of the compliance search. @@ -30,7 +30,7 @@ Get-ComplianceSearch [[-Identity] ] ``` ## DESCRIPTION -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). In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group. diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearchAction.md b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearchAction.md index bb1a32696a..b21f4a1973 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearchAction.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearchAction.md @@ -13,7 +13,7 @@ title: Get-ComplianceSearchAction # Get-ComplianceSearchAction ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-ComplianceSearchAction cmdlet to view information about compliance search actions. @@ -72,7 +72,7 @@ Get-ComplianceSearchAction [-Export] ## DESCRIPTION After you create and run a compliance search using the New-ComplianceSearch cmdlet, and start the search using the Start-ComplianceSearch cmdlet, you assign a search action using the New-ComplianceSearchAction cmdlet. You use the Get-ComplianceSearchAction cmdlet to track the progress of the compliance search action. -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). In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group. diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserAggregateReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserAggregateReport.md index 5f7e8ed48b..265f55aab4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserAggregateReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserAggregateReport.md @@ -38,7 +38,7 @@ This cmdlet returns the following information: - UserCount - Action -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserDetailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserDetailReport.md index 5b8fba0918..762a182473 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserDetailReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserDetailReport.md @@ -38,7 +38,7 @@ This cmdlet returns the following information: - UserCount - Action -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ConfigAnalyzerPolicyRecommendation.md b/exchange/exchange-ps/ExchangePowerShell/Get-ConfigAnalyzerPolicyRecommendation.md index 3d946278f6..4b2485cfbf 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ConfigAnalyzerPolicyRecommendation.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ConfigAnalyzerPolicyRecommendation.md @@ -35,11 +35,11 @@ The output of this cmdlet only returns settings that fall below the value that y The output contains the following information for each setting: -- PolicyGroup: The type of policy. The value will be Anti-Spam, Anti-Phishing, Anti-Malware, ATP Safe Links, or ATP Safe Attachments +- PolicyGroup: The type of policy. The value is Anti-Spam, Anti-Phishing, Anti-Malware, ATP Safe Links, or ATP Safe Attachments - SettingName: The name of the setting in the policy. - SettingNameDescription: A description of the setting. - Policy: The name of the policy. -- AppliedTo: The number of users or domains that the policy applies to. If the policy isn't applied to anyone (for example, it's disabled), this value will be blank. +- AppliedTo: The number of users or domains that the policy applies to. If the policy isn't applied to anyone (for example, it's disabled), this value is blank. - CurrentConfiguration: The current value of the setting. - LastModified: When the policy was last modified. - Recommendation: The recommended Standard or Strict value for the setting. @@ -49,7 +49,7 @@ If a setting is configured at or better than the Standard or Strict protection p This cmdlet returns the following output for each setting in each policy that falls below the recommended value. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Contact.md b/exchange/exchange-ps/ExchangePowerShell/Get-Contact.md index 1fc5354a8a..2869b21596 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-Contact.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-Contact.md @@ -13,7 +13,7 @@ title: Get-Contact # Get-Contact ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-Contact cmdlet to view existing contact objects in your organization. This cmdlet returns contacts and mail contacts. @@ -52,7 +52,7 @@ Get-Contact [[-Identity] ] ## DESCRIPTION The Get-Contact cmdlet returns no mail-related properties for mail contacts. Use the Get-MailContact to view mail-related properties for mail contacts. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterConfig.md index 6a8e1dbce8..fc479a47c6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterConfig.md @@ -27,7 +27,7 @@ Get-ContentFilterConfig [-DomainController ] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterPhrase.md b/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterPhrase.md index 9b20ec8f22..2e50b904e8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterPhrase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterPhrase.md @@ -36,7 +36,7 @@ Get-ContentFilterPhrase [-Phrase ] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoAggregateReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoAggregateReport.md index 0769430b82..58abe6daed 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoAggregateReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoAggregateReport.md @@ -42,7 +42,7 @@ For the specified reporting period, the cmdlet returns the following information By default, the command returns data for the last 14 days. Data for the last 90 days is available. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoDetailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoDetailReport.md index ce69c30ab3..e50714762a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoDetailReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoDetailReport.md @@ -44,7 +44,7 @@ For the specified reporting period, the cmdlet returns the following information By default, the command returns data for the last 14 days. Data for the last 30 days is available. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DataClassification.md b/exchange/exchange-ps/ExchangePowerShell/Get-DataClassification.md index 271b48a173..00d4186107 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DataClassification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DataClassification.md @@ -15,7 +15,7 @@ title: Get-DataClassification ## SYNOPSIS This cmdlet is functional only in on-premises Exchange. -In Exchange Online, this cmdlet has been replaced by the [Get-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchangepowershell/get-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell. +In Exchange Online, this cmdlet is replaced by the [Get-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchangepowershell/get-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell. Use the Get-DataClassification cmdlet to view the data classification rules in your organization. This cmdlet shows built-in data classification rules and rules that you created that use document fingerprints. @@ -40,7 +40,7 @@ Get-DataClassification [[-Identity] ] ## DESCRIPTION Classification rule packages are used by data loss prevention (DLP) to detect sensitive content in messages. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DataClassificationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-DataClassificationConfig.md index 39e8fca684..582c99fd75 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DataClassificationConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DataClassificationConfig.md @@ -26,7 +26,7 @@ Get-DataClassificationConfig [] ``` ## DESCRIPTION -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DataEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-DataEncryptionPolicy.md index e21fd13b90..a1d0a13841 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DataEncryptionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DataEncryptionPolicy.md @@ -34,7 +34,7 @@ Data encryption policy cmdlets are the Exchange Online part of Customer Key. For You can assign a data encryption policy to a mailbox by using the DataEncryptionPolicy parameter on the Set-Mailbox cmdlet in Exchange Online PowerShell. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroup.md index 4077072041..4b2ad570fd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroup.md @@ -39,7 +39,7 @@ In addition to obtaining a list of DAG members, the Get-DatabaseAvailabilityGrou Use the Status parameter with the command to include the values for these listed properties. Without the Status parameter, the values returned for these properties are blank. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroupNetwork.md b/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroupNetwork.md index 20964115f3..06b82d75b5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroupNetwork.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroupNetwork.md @@ -48,7 +48,7 @@ Valid states for network interfaces - Unavailable: The network interface isn't enabled for replication or use by the DAG, or the DAG member associated with this network interface is inactive or unavailable.The network interface isn't enabled for replication or use by the DAG, or the DAG member associated with this network interface is inactive or unavailable. - Unknown: The system was unable to determine the state of the network interface. -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 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md index 5fe36fb545..158918e113 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md @@ -30,7 +30,7 @@ Get-DeliveryAgentConnector [[-Identity] ] ## DESCRIPTION Delivery agent connectors are used to route messages addressed to foreign systems that don't use the SMTP protocol. When a message is routed to a delivery agent connector, the associated delivery agent performs the content conversion and message delivery. Delivery agent connectors allow queue management of foreign connectors, thereby eliminating the need for storing messages on the file system in Drop and Pickup directories. For more information, see [Delivery agents and Delivery Agent connectors](https://learn.microsoft.com/exchange/delivery-agents-and-delivery-agent-connectors-exchange-2013-help). -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DetailZapReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-DetailZapReport.md index 0c93ed0d8a..259eb9844a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DetailZapReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DetailZapReport.md @@ -48,7 +48,7 @@ If you append the command with ` | Format-List`, the following additional inform - Delivery Status - Detection Technology -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md index f04bcdd675..ba5338a4a8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md @@ -32,7 +32,7 @@ Get-DetailsTemplate [[-Identity] ] ## DESCRIPTION The Get-DetailsTemplate cmdlet retrieves the attributes for one or more details templates. Wildcard characters can be used when specifying the type and language of the details templates. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md index 5603596725..19775f1e8f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md @@ -13,7 +13,7 @@ title: Get-DistributionGroup # Get-DistributionGroup ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-DistributionGroup cmdlet to view existing distribution groups or mail-enabled security groups. To view the members of a group, use the Get-DistributionGroupMember cmdlet. @@ -85,7 +85,7 @@ Get-DistributionGroup [-Credential ] ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md index 1d9b8bb4fd..9bd3ff56a4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md @@ -13,7 +13,7 @@ title: Get-DistributionGroupMember # Get-DistributionGroupMember ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-DistributionGroupMember cmdlet to view the members of distribution groups and mail-enabled security groups. @@ -33,9 +33,9 @@ Get-DistributionGroupMember [-Identity] ``` ## DESCRIPTION -If your organization has multiple Active Directory domains, you may need to run the Set-ADServerSettings cmdlet with the ViewEntireForest parameter set to $true before running the Get-DistributionGroupMember cmdlet to view the entire forest. For more information, see Example 2. +If your organization has multiple Active Directory domains, you might need to run the Set-ADServerSettings cmdlet with the ViewEntireForest parameter set to $true before running the Get-DistributionGroupMember cmdlet to view the entire forest. For more information, see Example 2. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DkimSigningConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-DkimSigningConfig.md index f26a3f5385..89e4889084 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DkimSigningConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DkimSigningConfig.md @@ -29,7 +29,7 @@ Get-DkimSigningConfig [[-Identity] ] ## DESCRIPTION DKIM in Microsoft 365 is an email authentication method that uses a public key infrastructure (PKI), message headers and CNAME records in DNS to authenticate the message sender, which is stamped in the DKIM-Signature header field. DKIM helps prevent forged sender email addresses (also known as spoofing) by verifying that the domain in the From address matches the domain in the DKIM-Signature header field. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetailReport.md index 9b5a04d968..1aad6efd02 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetailReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetailReport.md @@ -13,7 +13,7 @@ title: Get-DlpDetailReport # Get-DlpDetailReport ## SYNOPSIS -**Note**: This cmdlet has been retired. Use the [Export-ActivityExplorerData](https://learn.microsoft.com/powershell/module/exchangepowershell/export-activityexplorerdata) cmdlet to view DLP information. Data from Export-ActivityExplorerData is the same as the retired Get-DlpIncidentDetailReport cmdlet. +**Note**: This cmdlet is retired. Use the [Export-ActivityExplorerData](https://learn.microsoft.com/powershell/module/exchangepowershell/export-activityexplorerdata) cmdlet to view DLP information. Data from Export-ActivityExplorerData is the same as the retired Get-DlpIncidentDetailReport cmdlet. This cmdlet is available only in the cloud-based service. @@ -61,7 +61,7 @@ The Get-DlpDetailReport cmdlet returns detailed information about specific DLP r To see DLP detection data that's aggregated per day, use the [Get-DlpDetectionsReport](https://learn.microsoft.com/powershell/module/exchangepowershell/get-dlpdetectionsreport) cmdlet. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetectionsReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetectionsReport.md index 2668fc6b73..5d9632faf6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetectionsReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetectionsReport.md @@ -53,7 +53,7 @@ To see all of these columns (width issues), write the output to a file. For exam To see detailed information about each DLP rule match, use the Get-DlpDetailReport cmdlet. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpIncidentDetailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpIncidentDetailReport.md index b5aa6eac36..6b5f5fb3b1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpIncidentDetailReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpIncidentDetailReport.md @@ -66,7 +66,7 @@ The output of the Get-DlpIncidentDetailReport cmdlet includes the following prop - SensitiveInformationCountList - SensitiveInformationConfidenceList -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md index d8452dfc15..65c660582f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md @@ -13,7 +13,7 @@ title: Get-DlpPolicy # Get-DlpPolicy ## SYNOPSIS -**Note**: This cmdlet has been retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). Use the Get-DlpCompliancePolicy and Get-DlpComplianceRule cmdlets instead. +**Note**: This cmdlet is retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). Use the Get-DlpCompliancePolicy and Get-DlpComplianceRule cmdlets instead. This cmdlet is functional only in on-premises Exchange. @@ -30,7 +30,7 @@ Get-DlpPolicy [[-Identity] ] ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md index c43bb97aac..b3260543ef 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md @@ -13,7 +13,7 @@ title: Get-DlpPolicyTemplate # Get-DlpPolicyTemplate ## SYNOPSIS -**Note**: This cmdlet has been retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). +**Note**: This cmdlet is retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). This cmdlet is functional only in on-premises Exchange. @@ -30,7 +30,7 @@ Get-DlpPolicyTemplate [[-Identity] ] ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DnssecStatusForVerifiedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-DnssecStatusForVerifiedDomain.md index 36ca1bd7a8..282963d2eb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DnssecStatusForVerifiedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DnssecStatusForVerifiedDomain.md @@ -34,7 +34,7 @@ Get-DnssecStatusForVerifiedDomain [-DomainName] ## DESCRIPTION For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works). -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md b/exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md index 7a52528003..5ef1c821e9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md @@ -40,7 +40,7 @@ Get-DomainController [-DomainName ] The Get-DomainController cmdlet is used by the Exchange admin center to populate fields that display domain controller information. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md index 87c60a02f3..85d20b7657 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md @@ -13,7 +13,7 @@ title: Get-DynamicDistributionGroup # Get-DynamicDistributionGroup ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-DynamicDistributionGroup cmdlet to view existing dynamic distribution groups. @@ -90,7 +90,7 @@ Get-DynamicDistributionGroup [-ManagedBy ] ## DESCRIPTION A dynamic distribution group queries mail-enabled objects and builds the group membership based on the results. The group membership is recalculated whenever an email message is sent to the group. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroupMember.md index 0f7bc5f3fe..73b6f4ac35 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroupMember.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroupMember.md @@ -32,7 +32,7 @@ Get-DynamicDistributionGroupMember [-Identity] ] ## DESCRIPTION For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell). -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxFolderPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxFolderPermission.md index 5cbf8ec31b..f4ab5fa2a7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxFolderPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxFolderPermission.md @@ -152,7 +152,7 @@ The User parameter filters the results by the specified mailbox, mail user, or m - Email address - GUID -**Note**: If you specify a user that doesn't have permission to access the mailbox folder, the command will throw an exception. +**Note**: If you specify a user that doesn't have permission to access the mailbox folder, the command returns an error. ```yaml Type: String @@ -170,7 +170,7 @@ Accept wildcard characters: False > Applicable: Exchange Online -The UserPrincipalName parameter identifies the mailbox that you want to view by UPN (for example, navin@contoso.onmicrosoft.com). +The UserPrincipalName parameter identifies the mailbox that you want to view by UPN (for example, `navin@contoso.onmicrosoft.com`). You can't use this parameter with the ExternalDirectoryObjectId, Identity, or PrimarySmtpAddress parameters. diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxPermission.md index d52f055125..65358472d3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxPermission.md @@ -54,7 +54,7 @@ By default, the following permissions are assigned to user mailboxes: - FullAccess and ReadPermission are directly assigned to NT AUTHORITY\SELF. This entry gives a user permission to their own mailbox. - FullAccess is denied to Administrator, Domain Admins, Enterprise Admins and Organization Management. These inherited permissions prevent these users and group members from opening other users' mailboxes. -- ChangeOwner, ChangePermission, DeleteItem, and ReadPermission are allowed for Administrator, Domain Admins, Enterprise Admins and Organization Management. Note that these inherited permission entries also appear to allow FullAccess. However, these users and groups do not have FullAccess to the mailbox because the inherited Deny permission entries override the inherited Allow permission entries. +- ChangeOwner, ChangePermission, DeleteItem, and ReadPermission are allowed for Administrator, Domain Admins, Enterprise Admins and Organization Management. These inherited permission entries also appear to allow FullAccess. However, these users and groups do not have FullAccess to the mailbox because the inherited Deny permission entries override the inherited Allow permission entries. - FullAccess is inherited by NT AUTHORITY\SYSTEM and ReadPermission is inherited by NT AUTHORITY\NETWORK. - FullAccess and ReadPermission are inherited by Exchange Servers, ChangeOwner, ChangePermission, DeleteItem, and ReadPermission are inherited by Exchange Trusted Subsystem and ReadPermission is inherited by Managed Availability Servers. diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EXORecipient.md b/exchange/exchange-ps/ExchangePowerShell/Get-EXORecipient.md index eac17545ab..b4f3f62b24 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-EXORecipient.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EXORecipient.md @@ -374,7 +374,7 @@ The RecipientTypeDetails parameter filters the results by the specified recipien You can specify multiple values separated by commas. -The value of the RecipientType parameter affects the values that you can use for this parameter. For example, if you use the RecipientType value MailContact, you can't use the value UserMailbox for this parameter. You'll receive the error: None of the specified RecipientTypeDetails are included in any specified recipient type. +The value of the RecipientType parameter affects the values that you can use for this parameter. For example, if you use the RecipientType value MailContact, you can't use the value UserMailbox for this parameter. You get the error: None of the specified RecipientTypeDetails are included in any specified recipient type. ```yaml Type: String[] diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EXORecipientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-EXORecipientPermission.md index 41c27a1675..ec3795b475 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-EXORecipientPermission.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EXORecipientPermission.md @@ -43,7 +43,7 @@ Get-EXORecipientPermission [[-Identity] ] ``` ## DESCRIPTION -This cmdlet is used to view/manage information about SendAs permissions that are configured for users in a cloud-based organization. Send As permission allows delegates to use the mailbox to send messages. After this permission is assigned to a delegate, any message that the delegate sends from the mailbox will appear to have been sent by the mailbox owner. However, this permission doesn't allow a delegate to sign in to the user's mailbox. It only allows users to open the mailbox. If this permission is assigned to a group, a message sent by the delegate will appear to have been sent by the group. +This cmdlet is used to view/manage information about SendAs permissions that are configured for users in a cloud-based organization. Send As permission allows delegates to use the mailbox to send messages. After this permission is assigned to a delegate, any message that the delegate sends from the mailbox appears to be sent by the mailbox owner. However, this permission doesn't allow a delegate to sign in to the user's mailbox. It only allows users to open the mailbox. If this permission is assigned to a group, a message sent by the delegate appears to be sent by the group. ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md index 250dab85ba..a892d29bdf 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md @@ -42,7 +42,7 @@ Get-EcpVirtualDirectory [[-Identity] ] ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md index 75362938ad..0bcc05c3a9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md @@ -30,7 +30,7 @@ Get-EdgeSubscription [[-Identity] ] ## DESCRIPTION Run the Get-EdgeSubscription cmdlet on an Exchange server in your organization. This cmdlet retrieves the list of Edge Subscriptions. Each Edge Transport server that's subscribed to the Exchange organization has a separate Edge Subscription. You can use this cmdlet to view the Edge Subscription information for a specific Edge Transport server. You can also use this cmdlet to view the Edge Subscription information for all Edge Transport servers subscribed to Active Directory sites. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md index 0f9ce42282..d10d31d535 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md @@ -29,7 +29,7 @@ Get-EdgeSyncServiceConfig [[-Identity] ] ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md b/exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md index dabfa9610d..85571cd4b0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md @@ -38,7 +38,7 @@ Get-EligibleDistributionGroupForMigration [-ManagedBy ] ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EmailTenantSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-EmailTenantSettings.md index 8fa56a3fe5..48232a093d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-EmailTenantSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EmailTenantSettings.md @@ -26,7 +26,7 @@ Get-EmailTenantSettings [[-Identity] ] [] ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md b/exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md index e44116bb97..0e6199f755 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md @@ -36,7 +36,7 @@ Get-EventLogLevel [[-Identity] ] ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EventsFromEmailConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-EventsFromEmailConfiguration.md index 739c0aca33..25832eb908 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-EventsFromEmailConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-EventsFromEmailConfiguration.md @@ -29,7 +29,7 @@ Get-EventsFromEmailConfiguration [-Identity] ## DESCRIPTION **Note**: The following output properties have been deprecated: EventReservationProcessingLevel, FoodEstablishmentReservationProcessingLevel, InvoiceProcessingLevel, and ServiceReservationProcessingLevel. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md index 6935ba187f..ab03c82edf 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md @@ -28,7 +28,7 @@ Get-ExchangeAssistanceConfig [[-Identity] ] ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md index fea0c58a77..0931257c1a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md @@ -51,7 +51,7 @@ Get-ExchangeCertificate [[-Thumbprint] ] By default, this cmdlet returns the following certificate properties in the summary list view: - Thumbprint: The unique digest of the certificate data. An example thumbprint value is 78E1BE82F683EE6D8CB9B9266FC1185AE0890C41. -- Services: The Exchange services that the certificate is assigned to by using the Enable-ExchangeCertificate cmdlet. Values are None, Federation, IIS, IMAP, POP, SMTP, UM, and UMCallRouter. You'll see the value None in certificates that aren't used with Exchange (for example, the `WMSvc-` certificate that's used for the IIS Web Management Service). +- Services: The Exchange services that the certificate is assigned to by using the Enable-ExchangeCertificate cmdlet. Values are None, Federation, IIS, IMAP, POP, SMTP, UM, and UMCallRouter. You see the value None in certificates that aren't used with Exchange (for example, the `WMSvc-` certificate that's used for the IIS Web Management Service). - Subject: Contains the X.500 value in the certificate's Subject Name field. The important part is the CN= value. If you append ` | Format-List` to the command, the cmdlet returns these additional certificate properties: @@ -92,7 +92,7 @@ If you append ` | Format-List *` to the command, the cmdlet returns these additi - SubjectName: Typically, this value is System.Security.Cryptography.X509Certificates.X500DistinguishedName. - Version: Typically, this value is 3. -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'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). ## EXAMPLES @@ -122,7 +122,7 @@ This example returns all available information for the specified certificate. Get-ExchangeCertificate -DomainName mail.contoso.com ``` -This example shows which certificate Exchange will select for the domain name mail.contoso.com. A Send connector or Receive connector selects the certificate to use based on the fully qualified domain name (FQDN) of the connector. If you have multiple certificates with the same FQDN, you can see which certificate Exchange will select by using the DomainName parameter to specify the FQDN. The first certificate returned is the certificate that Exchange will select. +This example shows which certificate Exchange selects for the domain name mail.contoso.com. A Send connector or Receive connector selects the certificate to use based on the fully qualified domain name (FQDN) of the connector. If you have multiple certificates with the same FQDN, you can see which certificate Exchange selects by using the DomainName parameter to specify the FQDN. The first certificate returned is the certificate that Exchange selects. ## PARAMETERS @@ -213,7 +213,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 -This parameter has been deprecated and is no longer used. +This parameter is deprecated and no longer used. ```yaml Type: X509Certificate2 diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md index 26ef51e172..f0d225dc85 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md @@ -31,7 +31,7 @@ Get-ExchangeDiagnosticInfo [-Argument ] ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md index 124cbe2406..66aa3b8ac0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md @@ -31,7 +31,7 @@ Get-ExchangeFeature [-Identity ] ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md index 5bbf2d4944..0765cedd81 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md @@ -42,7 +42,7 @@ Get-ExchangeServer [[-Identity] ] ## DESCRIPTION The ExchangeVersion attribute returned is the minimum version of Microsoft Exchange that you can use to manage the returned object. This attribute isn't the same as the version of Exchange displayed in the Exchange admin center when you select Server Configuration. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md index 1663316338..3bb1ee430a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md @@ -33,7 +33,7 @@ The Get-ExchangeServerAccessLicense cmdlet returns a collection of these license - Exchange Server Standard Edition - Exchange Server Enterprise Edition -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md index 4c452c27b0..eb7f39eb5d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md @@ -29,7 +29,7 @@ Get-ExchangeServerAccessLicenseUser -LicenseName ## DESCRIPTION The Get-ExchangeServerAccessLicenseUser cmdlet returns a collection of unique users for the specified license name. The list of unique users represents an estimate of your licenses when you run this cmdlet. Each object contains the FQDN or primary SMTP address of the mailbox and the license name to which it's associated. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md index 23cefad71d..d1d449f8f3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md @@ -40,7 +40,7 @@ Get-ExchangeSettings [[-Identity] ] ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierPolicy.md index 593507275d..c7bf951bbb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierPolicy.md @@ -26,7 +26,7 @@ Get-ExoInformationBarrierPolicy [[-Identity] ] [-ShowF ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierRelationship.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierRelationship.md index a21fb872a1..77602601cd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierRelationship.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierRelationship.md @@ -27,7 +27,7 @@ Get-ExoInformationBarrierRelationship -RecipientId1 -Reci ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierSegment.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierSegment.md index 2133d84497..b66215c355 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierSegment.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierSegment.md @@ -26,7 +26,7 @@ Get-ExoInformationBarrierSegment [[-Identity] ] ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExoSecOpsOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExoSecOpsOverrideRule.md index 6a7a7b3409..3d42a3cbcf 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExoSecOpsOverrideRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExoSecOpsOverrideRule.md @@ -31,7 +31,7 @@ Get-ExoSecOpsOverrideRule [[-Identity] ] ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExternalInOutlook.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExternalInOutlook.md index 8da1e93597..b33e844ca7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ExternalInOutlook.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExternalInOutlook.md @@ -31,7 +31,7 @@ The important properties that are returned in the output of this cmdlet are: - Enabled: True means the feature is enabled; False means the feature is disabled. - AllowList: The list of exceptions. Messages received from the specified senders or senders in the specified domains don't receive the External icon in the area of subject line. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md b/exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md index 509c2fe2d2..e86dea6e67 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md @@ -71,7 +71,7 @@ After a new filter is installed, only new messages with attachments of the type The cmdlet output provides details about items in a mailbox that couldn't be indexed, including an error code and the reason for failure. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md index 6e8cafa070..4fe0da6daa 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md @@ -31,7 +31,7 @@ Get-FederatedDomainProof -DomainName ## DESCRIPTION The Get-FederatedDomainProof cmdlet generates a cryptographically secure string for the domain used for federated sharing. The resulting string is used to manually configure a text (TXT) record in the Domain Name System (DNS) zone for the domain used by the administrator when running the cmdlet. A TXT record needs to be added to DNS for all accepted domains used for federated sharing. If the thumbprint of a certificate isn't provided, the task generates strings for all the certificates currently configured for the federation trust. Upon initial configuration of federated sharing, the proof string generated for the current certificate needs to be put into the TXT record for the federated domain in DNS. We recommend you update the TXT records whenever a new certificate is configured for the federation trust. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md index 9e34d46c14..47e2fce1d9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md @@ -13,7 +13,7 @@ title: Get-FederatedOrganizationIdentifier # Get-FederatedOrganizationIdentifier ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-FederatedOrganizationIdentifier cmdlet to retrieve the Exchange organization's federated organization identifier and related details, such as federated domains, organization contact and status. @@ -31,7 +31,7 @@ Get-FederatedOrganizationIdentifier [[-Identity] ] ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md index 3d86985c9a..c270d36671 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md @@ -13,7 +13,7 @@ title: Get-FederationInformation # Get-FederationInformation ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-FederationInformation cmdlet to get federation information from an external Exchange organization. @@ -35,7 +35,7 @@ Get-FederationInformation -DomainName ## DESCRIPTION The Get-FederationInformation cmdlet retrieves federation information from the specified domain, which should have federation enabled. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md index e4bb95f38d..56f0ba4831 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md @@ -13,7 +13,7 @@ title: Get-FederationTrust # Get-FederationTrust ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-FederationTrust cmdlet to view the federation trust configured for the Exchange organization. @@ -28,7 +28,7 @@ Get-FederationTrust [[-Identity] ] ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FocusedInbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-FocusedInbox.md index 5ffb9ea050..b1f7e2b8ea 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-FocusedInbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FocusedInbox.md @@ -30,7 +30,7 @@ Get-FocusedInbox -Identity ## DESCRIPTION Focused Inbox is a replacement for Clutter that separates the Inbox into the Focused and Other tabs in Outlook on the web and newer versions of Outlook. Important emails are on the Focused tab while the rest are on the Other tab. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md index 7abc2d7b28..6aa7779b61 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md @@ -28,7 +28,7 @@ Get-ForeignConnector [[-Identity] ] ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md b/exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md index 2c21f00765..0e1874937a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md @@ -30,7 +30,7 @@ Get-FrontendTransportService [[-Identity] ] ## DESCRIPTION The Front End Transport service acts as a stateless proxy for all inbound and outbound external SMTP traffic for the Exchange organization. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md index 6725543d75..71b37b5867 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md @@ -13,7 +13,7 @@ title: Get-GlobalAddressList # Get-GlobalAddressList ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-GlobalAddressList cmdlet to view a global address list (GAL) or a set of GALs. @@ -40,7 +40,7 @@ Get-GlobalAddressList [[-Identity] ] ## DESCRIPTION The Get-GlobalAddressList cmdlet is mainly used to populate the GAL property pages in the Exchange admin center. This command doesn't provide a filtering capability. If filtering is required, you should use a WHERE clause with the command. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md index 83d6144720..5b523b365d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md @@ -27,7 +27,7 @@ Get-GlobalMonitoringOverride [-DomainController ] ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Group.md b/exchange/exchange-ps/ExchangePowerShell/Get-Group.md index dbaaa4b176..7a8fd3d370 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-Group.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-Group.md @@ -13,7 +13,7 @@ title: Get-Group # Get-Group ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-Group cmdlet to view existing group objects in your organization. In all environments, this cmdlet returns mail-enabled security groups, distribution groups, role groups, and room lists. For details about other supported group types in on-premises Exchange environments, see the RecipientTypeDetails parameter description. @@ -54,7 +54,7 @@ Get-Group [[-Identity] ] ## DESCRIPTION The Get-Group cmdlet returns no mail-related properties for distribution groups or mail-enabled security groups, and no role group-related properties for role groups. To view the object-specific properties for a group, you need to use the corresponding cmdlet based on the object type (for example, Get-DistributionGroup or Get-RoleGroup). -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md index e95ba742ac..b729e36b53 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md @@ -41,7 +41,7 @@ The following list contains the health values that are returned: - Functional - Unavailable -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HistoricalSearch.md b/exchange/exchange-ps/ExchangePowerShell/Get-HistoricalSearch.md index 27051147bd..97064d9895 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-HistoricalSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HistoricalSearch.md @@ -29,7 +29,7 @@ Get-HistoricalSearch [-JobId ] ## DESCRIPTION A historical search provides message trace and report details in a comma-separated value (CSV) file for messages that are less than 90 days old. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HoldCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-HoldCompliancePolicy.md index 78c781ef0f..13535a450a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-HoldCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HoldCompliancePolicy.md @@ -17,7 +17,7 @@ This cmdlet is available only in Security & Compliance PowerShell. For more info Use the Get-HoldCompliancePolicy to view existing preservation policies in the Microsoft Purview compliance portal. -**Note**: The Get-HoldCompliancePolicy cmdlet has been replaced by the Get-RetentionCompliancePolicy cmdlet. If you have scripts that use Get-HoldCompliancePolicy, update them to use Get-RetentionCompliancePolicy. +**Note**: The Get-HoldCompliancePolicy cmdlet is replaced by the Get-RetentionCompliancePolicy cmdlet. If you have scripts that use Get-HoldCompliancePolicy, update them to use Get-RetentionCompliancePolicy. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HoldComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-HoldComplianceRule.md index 6f68eb4b30..7885973ffc 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-HoldComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HoldComplianceRule.md @@ -17,7 +17,7 @@ This cmdlet is available only in Security & Compliance PowerShell. For more info Use the Get-HoldComplianceRule to view preservation rules in the Microsoft Purview compliance portal. -**Note**: The Get-HoldComplianceRule cmdlet has been replaced by the Get-RetentionComplianceRule cmdlet. If you have scripts that use Get-HoldComplianceRule, update them to use Get-RetentionComplianceRule. +**Note**: The Get-HoldComplianceRule cmdlet is replaced by the Get-RetentionComplianceRule cmdlet. If you have scripts that use Get-HoldComplianceRule, update them to use Get-RetentionComplianceRule. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HostedConnectionFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-HostedConnectionFilterPolicy.md index 3b9e5bdaac..9207a2a0e7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-HostedConnectionFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HostedConnectionFilterPolicy.md @@ -27,7 +27,7 @@ Get-HostedConnectionFilterPolicy [[-Identity] ] ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterPolicy.md index 20ca00576b..3259b337b8 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterPolicy.md @@ -27,7 +27,7 @@ Get-HostedOutboundSpamFilterPolicy [-Identity] ] ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md index fd1ebea9b8..f1c086874f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md @@ -27,7 +27,7 @@ Get-HybridConfiguration [-DomainController ] ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HybridMailflowDatacenterIPs.md b/exchange/exchange-ps/ExchangePowerShell/Get-HybridMailflowDatacenterIPs.md index b9e16d25d2..47d56b16c7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-HybridMailflowDatacenterIPs.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-HybridMailflowDatacenterIPs.md @@ -15,7 +15,7 @@ title: Get-HybridMailflowDatacenterIPs ## SYNOPSIS This cmdlet is available only in the cloud-based service. -This cmdlet has been deprecated and is no longer used. +This cmdlet is deprecated and is no longer used. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -26,7 +26,7 @@ Get-HybridMailflowDatacenterIPs [] ``` ## DESCRIPTION -This cmdlet has been deprecated and is no longer used. +This cmdlet is deprecated and is no longer used. ## EXAMPLES @@ -35,7 +35,7 @@ This cmdlet has been deprecated and is no longer used. Get-HybridMailflowDatacenterIPs ``` -This cmdlet has been deprecated and is no longer used. +This cmdlet is deprecated and is no longer used. ## PARAMETERS diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IPv6StatusForAcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-IPv6StatusForAcceptedDomain.md index 95b42a54fc..341dfde6a7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-IPv6StatusForAcceptedDomain.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-IPv6StatusForAcceptedDomain.md @@ -32,7 +32,7 @@ Use the Get-AcceptedDomain cmdlet to return accepted domains in the Exchange Onl If IPv6 is enabled for an accepted domain in Exchange Online, IPv4 and IPv6 addresses are returned in DNS queries for mail flow records of the domain. If IPv6 is disabled, only IPv4 addresses are returned in DNS queries for mail flow records of the domain. -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'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). > [!NOTE] > diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md index dc6a295bf7..4e66c8198d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md @@ -13,7 +13,7 @@ title: Get-IRMConfiguration # Get-IRMConfiguration ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-IRMConfiguration cmdlet to view the Information Rights Management (IRM) configuration in your organization. @@ -29,7 +29,7 @@ Get-IRMConfiguration [-DomainController ] ## DESCRIPTION The Get-IRMConfiguration cmdlet provides details about the current IRM configuration, including whether individual IRM features are enabled or disabled and provides the URLs used for ServiceLocation, PublishingLocation and LicensingLocation. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md index 09f01eed05..3e3bc98b54 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md @@ -28,7 +28,7 @@ Get-ImapSettings [-DomainController ] ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-InboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-InboundConnector.md index 4b8f165f3a..0dc6a2864e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-InboundConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-InboundConnector.md @@ -30,7 +30,7 @@ Get-InboundConnector [[-Identity] ] ## DESCRIPTION Inbound connectors accept email messages from remote domains that require specific configuration options. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md index 59c768d5f7..13da496b00 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md @@ -13,7 +13,7 @@ title: Get-InboxRule # Get-InboxRule ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-InboxRule cmdlet to view Inbox rule properties. Inbox rules are used to process messages in the Inbox based on conditions specified and take actions such as moving a message to a specified folder or deleting a message. @@ -37,7 +37,7 @@ Get-InboxRule [[-Identity] ] ``` ## DESCRIPTION -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'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). **Note**: This cmdlet doesn't work for members of View-Only Organization Management role group in Exchange Online or the Global Reader role in Microsoft Entra ID. diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md index a0fff4f00b..3c8a1400ef 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md @@ -13,7 +13,7 @@ title: Get-IntraOrganizationConfiguration # Get-IntraOrganizationConfiguration ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-IntraOrganizationConfiguration cmdlet to view the component settings of a hybrid Exchange deployment. @@ -31,7 +31,7 @@ A hybrid Exchange deployment results in one logical organization made up of a nu Hybrid environments are enabled by Intra-Organization connectors. The connectors can be created and managed by cmdlets like New-IntraOrganizationConnector, but we strongly recommend that you use the Hybrid Configuration wizard when configuring a hybrid deployment with an Exchange Online organization. -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'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). ## EXAMPLES @@ -50,7 +50,7 @@ This example returns the settings of the intra-organization configuration. This parameter is available only in the cloud-based service. -The OrganizationGuid parameter specifies the on-premises organization in a hybrid deployment that has multiple on-premises organizations defined. If you don't use the OrganizationGuid parameter for these types of hybrid deployments, the Get-IntraOrganizationConfiguration cmdlet will generate errors. To view the on-premises organization GUID values that are required for this parameter, use the Get-OnPremisesOrganization cmdlet. +The OrganizationGuid parameter specifies the on-premises organization in a hybrid deployment that has multiple on-premises organizations defined. If you don't use the OrganizationGuid parameter for these types of hybrid deployments, the Get-IntraOrganizationConfiguration cmdlet returns errors. To view the on-premises organization GUID values that are required for this parameter, use the Get-OnPremisesOrganization cmdlet. ```yaml Type: OnPremisesOrganizationIdParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md index 9b1bb44334..f8c1970bfe 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md @@ -13,7 +13,7 @@ title: Get-IntraOrganizationConnector # Get-IntraOrganizationConnector ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-IntraOrganizationConnector cmdlet to view the settings of Intra-Organization connectors. @@ -30,7 +30,7 @@ Get-IntraOrganizationConnector [[-Identity] ] ## DESCRIPTION The Get-JournalRule cmdlet displays journal rules configured in your organization. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-LinkedUser.md b/exchange/exchange-ps/ExchangePowerShell/Get-LinkedUser.md index a4e3fe0a73..b75371ad04 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-LinkedUser.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-LinkedUser.md @@ -42,7 +42,7 @@ Get-LinkedUser [[-Identity] ] ``` ## DESCRIPTION -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md index dc9385ddb7..b688ec17cc 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md @@ -15,7 +15,7 @@ title: Get-LogonStatistics ## SYNOPSIS This cmdlet is functional only in Exchange Server 2010. -The Get-LogonStatistics cmdlet has been deprecated and is no longer used. +The Get-LogonStatistics cmdlet is deprecated and is no longer used. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -45,9 +45,9 @@ Get-LogonStatistics -Server ## DESCRIPTION The Get-LogonStatistics cmdlet retrieves logon information about currently active sessions. On Mailbox servers only, you can use the Get-LogonStatistics cmdlet without parameters. In this case, the cmdlet returns the logon statistics for all mailboxes on all databases on the local server. -Users who log on to their mailboxes using Microsoft Office Outlook Web App aren't continually connected to the Mailbox server. An Outlook Web App client connects to the server, performs tasks, and then disconnects from the server. Therefore, you may see few or no logon statistics for Outlook Web App, even if users are logged on with this client. +Users who log on to their mailboxes using Microsoft Office Outlook Web App aren't continually connected to the Mailbox server. An Outlook Web App client connects to the server, performs tasks, and then disconnects from the server. Therefore, you might see few or no logon statistics for Outlook Web App, even if users are logged on with this client. -You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Recipient Provisioning Permissions" section in the Mailbox Permissions topic. +You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you might not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Recipient Provisioning Permissions" section in the Mailbox Permissions topic. ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicy.md index fa455671a6..5fd747c8bd 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicy.md @@ -34,7 +34,7 @@ M365 data-at-rest encryption policy cmdlets are accessible to compliance adminis You can create and assign a Microsoft 365 data-at-rest encryption policy at the tenant level by using the appropriate M365DataAtRestEncryptionPolicy cmdlets in Exchange Online PowerShell. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicyAssignment.md b/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicyAssignment.md index b096ce31ee..a27e3b6d3f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicyAssignment.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicyAssignment.md @@ -28,7 +28,7 @@ Get-M365DataAtRestEncryptionPolicyAssignment [] ## DESCRIPTION This cmdlet lists the Microsoft 365 data-at-rest encryption policy that's currently assigned to the tenant. -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'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). ## EXAMPLES diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md index 1d1068f22f..8025e351a4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md @@ -13,7 +13,7 @@ title: Get-Mailbox # Get-Mailbox ## SYNOPSIS -This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other. +This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Get-Mailbox cmdlet to view mailbox objects and attributes, populate property pages, or supply mailbox information to other tasks. @@ -168,7 +168,7 @@ Get-Mailbox [-MailboxPlan ] ## DESCRIPTION When you use the Get-Mailbox cmdlet in on-premises Exchange environments to view the quota settings for a mailbox, you first need to check the value of the UseDatabaseQuotaDefaults property. The value True means per-mailbox quota settings are ignored, and you need to use the Get-MailboxDatabase cmdlet to see the actual values. If the UseDatabaseQuotaDefaults property is False, the per-mailbox quota settings are used, so what you see with the Get-Mailbox cmdlet are the actual quota values for the mailbox. -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'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). ## EXAMPLES @@ -886,7 +886,7 @@ You can use any value that uniquely identifies the server. For example: You can't use this parameter with the Anr, Database, or Identity parameters. -The ServerName and ServerLegacyDN properties for a mailbox may not be updated immediately after a mailbox move within a database availability group (DAG). To get the most up-to-date values for these mailbox properties, run the command `Get-Mailbox | Get-MailboxStatistics | Format-List Name,ServerName,ServerLegacyDN`. +The ServerName and ServerLegacyDN properties for a mailbox might not be updated immediately after a mailbox move within a database availability group (DAG). To get the most up-to-date values for these mailbox properties, run the command `Get-Mailbox | Get-MailboxStatistics | Format-List Name,ServerName,ServerLegacyDN`. **Note**: The result from this parameter could be a legacy value before migration. For better results, use the Database parameter instead. diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantAppointmentBookingFlow.md b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantAppointmentBookingFlow.md new file mode 100644 index 0000000000..42f0e9d432 --- /dev/null +++ b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantAppointmentBookingFlow.md @@ -0,0 +1,206 @@ +--- +applicable: Microsoft Teams +author: tomkau +external help file: Microsoft.Rtc.Management.dll-Help.xml +Locale: en-US +manager: bulenteg +Module Name: MicrosoftTeams +ms.author: tomkau +online version: https://learn.microsoft.com/powershell/module/microsoftteams/get-csmainlineattendantappointmentbookingflow +schema: 2.0.0 +title: Get-CsMainlineAttendantAppointmentBookingFlow +--- + +# Get-CsMainlineAttendantAppointmentBookingFlow + +## SYNOPSIS +The Get-CsMainlineAttendantAppointmentBookingFlow cmdlet returns the identified Mainline attendant appointment booking flow. + +## SYNTAX + +``` +Get-CsMainlineAttendantAppointmentBookingFlow [-Identity ] [-Tenant ] [-First ] [-Skip ] [-ExcludeContent ] [-Sort ] [-Descending ] [-NameFilter ] [] +``` + +## DESCRIPTION +The Get-CsMainlineAttendantAppointmentBookingFlow cmdlet lets you retrieve information about the Mainline attendant appointment booking flows n your organization. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Get-CsMainlineAttendantAppointmentBookingFlow +``` + +This example gets the first 100 Mainline attendant appointment booking flows in the organization. + +### -------------------------- Example 2 -------------------------- +``` +Get-CsMainlineAttendantAppointmentBookingFlow -Identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01 +``` + +This example gets the Mainline attendant appointment booking flow with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01. If no appointment booking flow exists with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01, then this example generates an error. + +## PARAMETERS + +### -Identity + +> Applicable: Microsoft Teams + +PARAMVALUE: Guid + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant + +> Applicable: Microsoft Teams + +PARAMVALUE: Guid + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -First + +> Applicable: Microsoft Teams + +The First parameter gets the first N appointment flows, up to a maximum of 100 at a time. +When not specified, the default behavior is to return the first 100 appointment flows. It is intended to be used in conjunction with the `-Skip` parameter for pagination purposes. +If a number greater than 100 is supplied, the request will fail. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: 100 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Skip + +> Applicable: Microsoft Teams + +The Skip parameter skips the first N appointment flows. It is intended to be used in conjunction with the `-First` parameter for pagination purposes. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExcludeContent + +> Applicable: Microsoft Teams + +The ExcludeContent parameter only displays the Name and Id of the appointment flow. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Sort + +> Applicable: Microsoft Teams + +The Sort parameter specifies the property used to sort. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: Name +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Descending + +> Applicable: Microsoft Teams + +The Descending parameter sorts appointment booking flows in descending order + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NameFilter + +> Applicable: Microsoft Teams + +The NameFilter parameter returns appointment booking flows where the name contains specified string + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### CommonParameters +This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### Identity +Represents the unique identifier of an appointment booking flow. + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue + +## NOTES + +## RELATED LINKS diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md new file mode 100644 index 0000000000..1360745f2e --- /dev/null +++ b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md @@ -0,0 +1,122 @@ +--- +applicable: Microsoft Teams +author: tomkau +external help file: Microsoft.Rtc.Management.dll-Help.xml +Locale: en-US +manager: bulenteg +Module Name: MicrosoftTeams +ms.author: tomkau +online version: https://learn.microsoft.com/powershell/module/microsoftteams/get-csmainlineattendantflow +schema: 2.0.0 +title: Get-CsMainlineAttendantFlow +--- + +# Get-CsMainlineAttendantFlow + +## SYNOPSIS +The Get-CsMainlineAttendantFlow cmdlet returns information about the Mainline Attendant flows configured in your organization + +## SYNTAX + +``` +Get-CsMainlineAttendantFlow [-MaConfigId ] [-Type ] [-FlowId ] [-Tenant ] [] +``` + +## DESCRIPTION +The Get-CsMainlineAttendantFlow cmdlet returns information about the Mainline Attendant flows configured in your organization. + +> [!CAUTION] +> This cmdlet will only work for customers that are participating in the Voice Applications private preview for these features. General Availability for this functionality has not been determined at this time. + +## EXAMPLES + +### Example 1 +``` +Get-CsMainlineAttendantFlow +``` + +This example will list all the Mainline Attendant flows in the tenant. + +### Example 2 +``` +Get-CsMainlineAttendantFlow -MaConfig 0b31bbe5-e2a0-4117-9b6f-956bca6023f8 +``` + +This example will list all the Mainline Attendant flows associated with the specific configuration id. + +### Example 3 +``` +Get-CsMainlineAttendantFlow -Type Type 1 | Type 2 +``` + +This example will list all the Mainline Attendant flows with the specified type. + +### Example 4 +``` +Get-CsMainlineAttendantFlow -FlowId 956bca6-e2a0-4117-9b6f-023f80b31bbe5 +``` + +This example will list the Mainline Attendant flow with the specified flow id. + +## PARAMETERS + +### -MaConfigId +The Mainline Attendant configuration Id + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Type +The Mainline Attendant flow type + +PARAMVALUE: Appointment | QuestionAndAnswer + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -FlowId +The Mainline Attendant flow id + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### CommonParameters +This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue + +## NOTES + +## RELATED LINKS + diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantQuestionAnswerFlow.md b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantQuestionAnswerFlow.md new file mode 100644 index 0000000000..89ed9d9101 --- /dev/null +++ b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantQuestionAnswerFlow.md @@ -0,0 +1,183 @@ +--- +applicable: Microsoft Teams +author: tomkau +external help file: Microsoft.Rtc.Management.dll-Help.xml +Locale: en-US +manager: bulenteg +Module Name: MicrosoftTeams +ms.author: tomkau +online version: https://learn.microsoft.com/powershell/module/microsoftteams/get-csmainlineattendantquestionanswerflow +schema: 2.0.0 +title: Get-CsMainlineAttendantQuestionAnswerFlow +--- + +# Get-CsMainlineAttendantQuestionAnswerFlow + +## SYNOPSIS +The Get-CsMainlineAttendantQuestionAnswerFlow cmdlet returns the identified Mainline attendant question and answer flow. + +## SYNTAX + +``` +Get-CsMainlineAttendantQuestionAnswerFlow [-Identity ] [-Tenant ] [-First ] [-Skip ] [-ExcludeContent ] [-Sort ] [-Descending ] [-NameFilter ] [] +``` + +## DESCRIPTION +The Get-CsMainlineAttendantQuestionAnswerFlow cmdlet lets you retrieve information about the Mainline attendant question and answer flows n your organization. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Get-CsMainlineAttendantQuestionAnswerFlow +``` + +This example gets the first 100 Mainline attendant question and answer flows in the organization. + +### -------------------------- Example 2 -------------------------- +``` +Get-CsMainlineAttendantQuestionAnswerFlow -Identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01 +``` + +This example gets the Mainline attendant question and answer flow with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01. If no question and answer flow exists with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01, then this example generates an error. + +## PARAMETERS + +### -Identity +PARAMVALUE: Guid + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +PARAMVALUE: Guid + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -First +The First parameter gets the first N appointment flows, up to a maximum of 100 at a time. +When not specified, the default behavior is to return the first 100 question and answer flows. It is intended to be used in conjunction with the `-Skip` parameter for pagination purposes. +If a number greater than 100 is supplied, the request will fail. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: 100 +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Skip +The Skip parameter skips the first N appointment flows. It is intended to be used in conjunction with the `-First` parameter for pagination purposes. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExcludeContent +The ExcludeContent parameter only displays the Name and Id of the question and answer flow. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Sort +The Sort parameter specifies the property used to sort. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: Name +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Descending +The Descending parameter sorts appointment booking flows in descending order + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -NameFilter +The NameFilter parameter returns question and answer booking flows where the name contains specified string + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### CommonParameters +This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### Identity +Represents the unique identifier of a question and answer booking flow. + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue + +## NOTES + +## RELATED LINKS + diff --git a/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md b/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md index 5e7990cbf7..1a498ef064 100644 --- a/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md +++ b/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md @@ -125,6 +125,15 @@ Returns a list of all blocked number patterns added to the tenant list. ### [Get-CsInboundExemptNumberPattern](Get-CsInboundExemptNumberPattern.md) Returns a specific or the full list of all number patterns exempt from call blocking. +### [Get-CsMainlineAttendantAppointmentBookingFlow](Get-CsMainlineAttendantAppointmentBookingFlow.md) +Returns the identified Mainline attendant appointment booking flow. + +### [Get-CsMainlineAttendantFlow](Get-CsMainlineAttendantFlow.md) +Returns information about the Mainline Attendant flows configured in your organization. + +### [Get-CsMainlineAttendantQuestionAnswerFlow](Get-CsMainlineAttendantQuestionAnswerFlow.md) +Returns the identified Mainline attendant question and answer flow. + ### [Get-CsMeetingMigrationStatus](Get-CsMeetingMigrationStatus.md) You use the `Get-CsMeetingMigrationStatus` cmdlet to check the status of meeting migrations. @@ -791,6 +800,12 @@ Adds a blocked number pattern to the tenant list. ### [New-CsInboundExemptNumberPattern](New-CsInboundExemptNumberPattern.md) This cmdlet lets you configure a new number pattern that is exempt from tenant call blocking. +### [New-CsMainlineAttendantAppointmentBookingFlow](New-CsMainlineAttendantAppointmentBookingFlow.md) +Creates new Mainline Attendant appointment booking flows. + +### [New-CsMainlineAttendantQuestionAnswerFlow](New-CsMainlineAttendantQuestionAnswerFlow.md) +Creates new Mainline Attendant question and answer (FAQ) flows. + ### [New-CsOnlineApplicationInstance](New-CsOnlineApplicationInstance.md) Creates an application instance in Microsoft Entra ID. @@ -1064,6 +1079,12 @@ Removes a blocked number pattern from the tenant list. ### [Remove-CsInboundExemptNumberPattern](Remove-CsInboundExemptNumberPattern.md) Removes a number pattern exempt from call blocking. +### [Remove-CsMainlineAttendantAppointmentBookingFlow](Remove-CsMainlineAttendantAppointmentBookingFlow.md) +Removes an existing Mainline attendant appointment booking flow. + +### [Remove-CsMainlineAttendantQuestionAnswerFlow](Remove-CsMainlineAttendantQuestionAnswerFlow.md) +Removes an existing Mainline attendant question and answer flow. + ### [Remove-CsOnlineApplicationInstanceAssociation](Remove-CsOnlineApplicationInstanceAssociation.md) Use the Remove-CsOnlineApplicationInstanceAssociation cmdlet to remove the association between an application instance and the associated application configuration. @@ -1340,6 +1361,12 @@ Modifies one or more parameters of a blocked number pattern in the tenant list. ### [Set-CsInboundExemptNumberPattern](Set-CsInboundExemptNumberPattern.md) Modifies one or more parameters of an exempt number pattern in the tenant list. +### [Set-CsMainlineAttendantAppointmentBookingFlow](Set-CsMainlineAttendantAppointmentBookingFlow.md) +Modifies an existing Mainline Attendant appointment booking flow. + +### [Set-CsMainlineAttendantQuestionAnswerFlow](Set-CsMainlineAttendantQuestionAnswerFlow.md) +Modifies an existing Mainline Attendant question and answer (FAQ) flow. + ### [Set-CsOnlineApplicationInstance](Set-CsOnlineApplicationInstance.md) Updates an application instance in Microsoft Entra ID. diff --git a/teams/teams-ps/MicrosoftTeams/New-CsAutoAttendantCallFlow.md b/teams/teams-ps/MicrosoftTeams/New-CsAutoAttendantCallFlow.md index 7e23f4fdaf..5edb50aea2 100644 --- a/teams/teams-ps/MicrosoftTeams/New-CsAutoAttendantCallFlow.md +++ b/teams/teams-ps/MicrosoftTeams/New-CsAutoAttendantCallFlow.md @@ -195,4 +195,4 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable [New-CsAutoAttendantMenu](https://learn.microsoft.com/powershell/module/microsoftteams/new-csautoattendantmenu) -[New-CsAutoAttendantPrompt](https://learn.microsoft.com/powershell/module/microsoftteams/new-csautoattendantprompt) +[Get-CsMainlineAttendantFlow](https://learn.microsoft.com/powershell/module/microsoftteams/new-csautoattendantprompt) diff --git a/teams/teams-ps/MicrosoftTeams/New-CsComplianceRecordingForCallQueueTemplate.md b/teams/teams-ps/MicrosoftTeams/New-CsComplianceRecordingForCallQueueTemplate.md index 2cc3f34801..676809efba 100644 --- a/teams/teams-ps/MicrosoftTeams/New-CsComplianceRecordingForCallQueueTemplate.md +++ b/teams/teams-ps/MicrosoftTeams/New-CsComplianceRecordingForCallQueueTemplate.md @@ -45,7 +45,7 @@ This example creates a new Compliance Recording for Call Queue template. > Applicable: Microsoft Teams -The Id of the compliance recording for call queue bot to invite. +The Application Instance Id of the compliance recording bot to invite. ```yaml Type: System.String diff --git a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlow.md b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlow.md new file mode 100644 index 0000000000..f07207651e --- /dev/null +++ b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlow.md @@ -0,0 +1,129 @@ +--- +applicable: Microsoft Teams +author: tomkau +external help file: Microsoft.Rtc.Management.dll-Help.xml +Locale: en-US +manager: bulenteg +Module Name: MicrosoftTeams +ms.author: tomkau +online version: https://learn.microsoft.com/powershell/module/microsoftteams/new-csmainlineattendantappointmentbookingflow +schema: 2.0.0 +title: New-CsMainlineAttendantAppointmentBookingFlow +--- + +# New-CsMainlineAttendantAppointmentBookingFlow + +## SYNOPSIS +Creates new Mainline Attendant appointment booking flow + +## SYNTAX + +``` +New-CsMainlineAttendantAppointmentBookingFlow -Name -Description -CallerAuthenticationMethod -ApiAuthenticationType -ApiDefinitions [-Tenant ] [] +``` + +## DESCRIPTION +The New-CsMainlineAttendantAppointmentBookingFlow cmdlet creates a new appointment booking connection that can be used with Mainline Attendant + +> [!CAUTION] +> This cmdlet will only work for customers that are participating in the Voice Applications private preview for these features. General Availability for this functionality has not been determined at this time. + +## EXAMPLES + + +## PARAMETERS + +### -Name +The name of the appointment booking flow + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +The description for the appointment booking flow + +Limit: 500 characters. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallerAuthenticationMethod +The method by which the caller is authenticated + +PARAVALUES: sms | email | verification_link | voiceprint | user_details + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApiAuthenticationType +The method of authentication used by the API + +PARAVALUES: basic | api_key | bearer_token_static | bearer_token_dynamic + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApiDefinitions +The parameters used by the API + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### CommonParameters +This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue + +## NOTES + +## RELATED LINKS + diff --git a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlow.md b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlow.md new file mode 100644 index 0000000000..e8ae2d797b --- /dev/null +++ b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlow.md @@ -0,0 +1,112 @@ +--- +applicable: Microsoft Teams +author: tomkau +external help file: Microsoft.Rtc.Management.dll-Help.xml +Locale: en-US +manager: bulenteg +Module Name: MicrosoftTeams +ms.author: tomkau +online version: https://learn.microsoft.com/powershell/module/microsoftteams/new-csmainlineattendantquestionanswerflow +schema: 2.0.0 +title: New-CsMainlineAttendantQuestionAnswerFlow +--- + +# New-CsMainlineAttendantQuestionAnswerFlow + +## SYNOPSIS +Creates new Mainline Attendant question and answer (FAQ) flow + +## SYNTAX + +``` +New-CsMainlineAttendantQuestionAnswerFlow -Name -Description -ApiAuthenticationType -KnowledgeBase [-Tenant ] [] +``` + +## DESCRIPTION +The New-CsMainlineAttendantQuestionAnswerFlow cmdlet creates a question and answer connection that can be used with Mainline Attendant + +> [!CAUTION] +> This cmdlet will only work for customers that are participating in the Voice Applications private preview for these features. General Availability for this functionality has not been determined at this time. + +## EXAMPLES + + +## PARAMETERS + +### -Name +The name of the question and answer flow + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +The description for the question and answer flow + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApiAuthenticationType +The method of authentication used by the API + +PARAVALUES: basic | api_key | bearer_token_static | bearer_token_dynamic + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -KnowledgeBase +The knowledge base definition + +The parameters used by the API + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### CommonParameters +This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue + +## NOTES + +## RELATED LINKS + diff --git a/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantAppointmentBookingFlow.md b/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantAppointmentBookingFlow.md new file mode 100644 index 0000000000..22c8bc1dbf --- /dev/null +++ b/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantAppointmentBookingFlow.md @@ -0,0 +1,84 @@ +--- +applicable: Microsoft Teams +author: tomkau +external help file: Microsoft.Rtc.Management.dll-Help.xml +Locale: en-US +manager: bulenteg +Module Name: MicrosoftTeams +ms.author: tomkau +online version: https://learn.microsoft.com/powershell/module/microsoftteams/remove-csmainlineattendantappointmentbookingflow +schema: 2.0.0 +title: Remove-CsMainlineAttendantAppointmentBookingFlow +--- + +# Remove-CsMainlineAttendantAppointmentBookingFlow + +## SYNOPSIS +The Remove-CsMainlineAttendantAppointmentBookingFlow cmdlet deletes an existing Mainline attendant appointment booking flow. + +## SYNTAX + +``` +Remove-CsMainlineAttendantAppointmentBookingFlow -Identity [-Tenant ] [] +``` + +## DESCRIPTION +The Remove-CsMainlineAttendantAppointmentBookingFlow cmdlet deletes an existing Mainline attendant appointment booking flow. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Remove-CsMainlineAttendantAppointmentBookingFlow -Identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01 +``` + +This example removes the Mainline attendant appointment booking flow with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01. If no appointment booking flow exists with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01, then this example generates an error. + +## PARAMETERS + +### -Identity +PARAMVALUE: Guid + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +PARAMVALUE: Guid + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### CommonParameters +This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### Identity +Represents the unique identifier of a Mainline attendant appointment booking flow. + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue + +## NOTES + +## RELATED LINKS + diff --git a/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantQuestionAnswerFlow.md b/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantQuestionAnswerFlow.md new file mode 100644 index 0000000000..023b3d2ee9 --- /dev/null +++ b/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantQuestionAnswerFlow.md @@ -0,0 +1,84 @@ +--- +applicable: Microsoft Teams +author: tomkau +external help file: Microsoft.Rtc.Management.dll-Help.xml +Locale: en-US +manager: bulenteg +Module Name: MicrosoftTeams +ms.author: tomkau +online version: https://learn.microsoft.com/powershell/module/microsoftteams/remove-csmainlineattendantquestionanswerflow +schema: 2.0.0 +title: Remove-CsMainlineAttendantQuestionAnswerFlow +--- + +# Remove-CsMainlineAttendantQuestionAnswerFlow + +## SYNOPSIS +The Remove-CsMainlineAttendantQuestionAnswerFlow cmdlet deletes an existing Mainline attendant question and answer flow. + +## SYNTAX + +``` +Remove-CsMainlineAttendantQuestionAnswerFlow -Identity [-Tenant ] [] +``` + +## DESCRIPTION +The Remove-CsMainlineAttendantQuestionAnswerFlow cmdlet deletes an existing Mainline attendant question and answer flow. + +## EXAMPLES + +### -------------------------- Example 1 -------------------------- +``` +Remove-CsMainlineAttendantQuestionAnswerFlow -Identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01 +``` + +This example removes the Mainline attendant question and answer flow with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01. If no question and answer flow exists with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01, then this example generates an error. + +## PARAMETERS + +### -Identity +PARAMVALUE: Guid + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Tenant +PARAMVALUE: Guid + +```yaml +Type: Guid +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### CommonParameters +This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +### Identity +Represents the unique identifier of a Mainline attendant question and answer flow. + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue + +## NOTES + +## RELATED LINKS + diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantAppointmentBookingFlow.md b/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantAppointmentBookingFlow.md new file mode 100644 index 0000000000..61e17500cc --- /dev/null +++ b/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantAppointmentBookingFlow.md @@ -0,0 +1,145 @@ +--- +applicable: Microsoft Teams +author: tomkau +external help file: Microsoft.Rtc.Management.dll-Help.xml +Locale: en-US +manager: bulenteg +Module Name: MicrosoftTeams +ms.author: tomkau +online version: https://learn.microsoft.com/powershell/module/microsoftteams/set-csmainlineattendantappointmentbookingflow +schema: 2.0.0 +title: Set-CsMainlineAttendantAppointmentBookingFlow +--- + +# Set-CsMainlineAttendantAppointmentBookingFlow + +## SYNOPSIS +Changes an existing Mainline Attendant appointment booking flow + +## SYNTAX + +``` +Set-CsMainlineAttendantAppointmentBookingFlow -Identity [-Name ] [-Description ] [-CallerAuthenticationMethod ] [-ApiAuthenticationType ] [-ApiDefinitions ] [-Tenant ] [] +``` + +## DESCRIPTION +The Set-CsMainlineAttendantAppointmentBookingFlow cmdlet changes an existing appointment booking flow that is used with Mainline Attendant + +> [!CAUTION] +> This cmdlet will only work for customers that are participating in the Voice Applications private preview for these features. General Availability for this functionality has not been determined at this time. + +## EXAMPLES + + +## PARAMETERS + +### -Identity +The unique Id of the appointment booking flow to change + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +The name of the appointment booking flow + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +The description for the appointment booking flow + +Limit: 500 characters. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -CallerAuthenticationMethod +The method by which the caller is authenticated + +PARAVALUES: sms | email | verification_link | voiceprint | user_details + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApiAuthenticationType +The method of authentication used by the API + +PARAVALUES: basic | api_key | bearer_token_static | bearer_token_dynamic + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApiDefinitions +The parameters used by the API + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### CommonParameters +This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue + +## NOTES + +## RELATED LINKS + + diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantQuestionAnswerFlow.md b/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantQuestionAnswerFlow.md new file mode 100644 index 0000000000..5335328561 --- /dev/null +++ b/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantQuestionAnswerFlow.md @@ -0,0 +1,128 @@ +--- +applicable: Microsoft Teams +author: tomkau +external help file: Microsoft.Rtc.Management.dll-Help.xml +Locale: en-US +manager: bulenteg +Module Name: MicrosoftTeams +ms.author: tomkau +online version: https://learn.microsoft.com/powershell/module/microsoftteams/set-csmainlineattendantquestionanswerflow +schema: 2.0.0 +title: Set-CsMainlineAttendantQuestionAnswerFlow +--- + +# Set-CsMainlineAttendantQuestionAnswerFlow + +## SYNOPSIS +Changes an existing Mainline Attendant question and answer (FAQ) flow + +## SYNTAX + +``` +Set-CsMainlineAttendantQuestionAnswerFlow -Identity [-Name ] [-Description ] [-ApiAuthenticationType ] [-KnowledgeBase ] [-Tenant ] [] +``` + +## DESCRIPTION +The Set-CsMainlineAttendantQuestionAnswerFlow cmdlet changes an existing question and answer connection that can be used with Mainline Attendant + +> [!CAUTION] +> This cmdlet will only work for customers that are participating in the Voice Applications private preview for these features. General Availability for this functionality has not been determined at this time. + +## EXAMPLES + + +## PARAMETERS + +### -Identity +The unique identifier for the question and answer flow. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Name +The name of the question and answer flow + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Description +The description for the question and answer flow + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ApiAuthenticationType +The method of authentication used by the API + +PARAVALUES: basic | api_key | bearer_token_static | bearer_token_dynamic + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -KnowledgeBase +The knowledge base definition + +The parameters used by the API + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### CommonParameters +This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216). + +## INPUTS + +## OUTPUTS + +### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue + +## NOTES + +## RELATED LINKS + +