Skip to content

Commit 575b6d5

Browse files
authored
Merge pull request #10822 from v-smandalika/v-smandalika-7875677
Update Set-ThrottlingPolicyAssociation.md
2 parents c4e7bde + 3fa6886 commit 575b6d5

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

exchange/exchange-ps/exchange/Set-ThrottlingPolicyAssociation.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,11 @@ ms.reviewer:
1414
## SYNOPSIS
1515
This cmdlet is available only in on-premises Exchange.
1616

17-
Use the Set-ThrottlingPolicyAssociation cmdlet to associate a throttling policy with a specific object. The object can be a user with a mailbox, a user without a mailbox, a contact or a computer account.
17+
Use the Set-ThrottlingPolicyAssociation cmdlet to associate a throttling policy with a specific object. The object can be a user with a mailbox, a user without a mailbox, a contact, or a computer account.
1818

19-
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
19+
**Note**: Some parameters in the throttling policy (for example, MessageRateLimit) apply only to objects that have mailbox GUIDs (mailboxes or remote mailboxes) and don't apply to mail users. And, if you want to apply throttling policy to a remote mailbox, first populate the remote mailbox with an ExchangeGUID by using Set-RemoteMailbox -ExchangeGUID.
20+
21+
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
2022

2123
## SYNTAX
2224

@@ -36,7 +38,7 @@ In data center deployments, the object referred to by the Identity and Throttlin
3638

3739
For more information about how to control the resources consumed by individual users, see [User workload management in Exchange Server](https://learn.microsoft.com/Exchange/server-health/workload-management).
3840

39-
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).
41+
You need to be assigned permissions before you can run the Set-ThrottlingPolicyAssociation 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).
4042

4143
## EXAMPLES
4244

@@ -53,7 +55,7 @@ $b = Get-ThrottlingPolicy ITStaffPolicy
5355
Set-Mailbox -Identity tonysmith -ThrottlingPolicy $b
5456
```
5557

56-
You don't need to use the Set-ThrottlingPolicyAssociation cmdlet to associate a user with a policy. The following commands show another way to associate tonysmith to the throttling policy ITStaffPolicy.
58+
You don't need to use the Set-ThrottlingPolicyAssociation cmdlet to associate a user with a policy. The following commands show another way to associate tonysmith with the throttling policy ITStaffPolicy.
5759

5860
## PARAMETERS
5961

@@ -111,7 +113,7 @@ Accept wildcard characters: False
111113
```
112114

113115
### -ThrottlingPolicy
114-
The ThrottlingPolicy parameter specifies the throttling policy that you want to be associated with the object specified by the Identity parameter.
116+
The ThrottlingPolicy parameter specifies the throttling policy that you want the object specified by the Identity parameter to be associated with.
115117

116118
```yaml
117119
Type: ThrottlingPolicyIdParameter

0 commit comments

Comments
 (0)