Training
Module
Protect your APIs on Azure API Management - Training
Protect your backend APIs from information exposure and implement throttling (rate limiting) to prevent resource exhaustion with policies in Azure API Management.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Applies to: Exchange Server 2013
You can control how resources are consumed by individual users in your Exchange organization by changing the default throttling settings.
Controlling how resources are consumed by individual users was possible in Exchange Server 2010, and this capability has been expanded for Exchange Server 2013. The policy named GlobalThrottlingPolicy defines the default throttling settings for every new and existing user in your organization unless you've customized the throttling policies. In many typical Exchange deployment scenarios, the policy named GlobalThrottlingPolicy is adequate to manage users.
To customize throttling settings to apply only to specific users in your organization, create a new throttling policy with the scope assignment Regular. You can only change the default throttling settings by using the Shell.
Estimated time to complete: 10 minutes.
You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the "User throttling" entry in the Server health and performance permissions topic.
In new Regular-scope policies, you should set only the throttling settings that are different from those in the policy named GlobalThrottlingPolicy and any other organization policies. This way, the rest of the policy settings from the policy named GlobalThrottlingPolicy will be inherited, as will any updates to throttling policies that are added in future Exchange updates. We recommend that you review the section "Manage throttling policies using scopes" in the topic Exchange workload management before following this procedure.
For information about keyboard shortcuts that may apply to the procedures in this topic, see Keyboard shortcuts in the Exchange admin center.
Tip
Having problems? Ask for help in the Exchange forums. Visit the forums at Exchange Server.
This example creates a non-default user throttling policy named ITStaffPolicy that can be associated with specific users. Any parameters that you omit inherit the values from the default throttling policy GlobalThrottlingPolicy. After you create this policy, you must associate it with specific users.
New-ThrottlingPolicy -Name ITStaffPolicy -EwsMaxConcurrency 4 -ThrottlingPolicyScope Regular
This example associates a user with the username tonysmith with the throttling policy ITStaffPolicy (which has higher limits).
Set-ThrottlingPolicyAssociation -Identity tonysmith -ThrottlingPolicy ITStaffPolicy
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.
$b = Get-ThrottlingPolicy ITStaffPolicy
Set-Mailbox -Identity tonysmith -ThrottlingPolicy $b
For more information about syntax and parameters, see New-ThrottlingPolicy and Set-ThrottlingPolicyAssociation.
To verify that you've successfully created the Regular throttling policy, do the following:
Run the following command.
Get-ThrottlingPolicy | Format-List
Verify that the Regular throttling policy you just created is listed in the column that shows the GlobalThrottlingPolicy object.
Run the following command.
Get-ThrottlingPolicy | select *
Verify that the properties for the new Regular policy match the value or values you configured.
Run the following command.
Get-ThrottlingPolicyAssociation
Verify that the new Regular policy is associated with the user or users you associated it with.
Training
Module
Protect your APIs on Azure API Management - Training
Protect your backend APIs from information exposure and implement throttling (rate limiting) to prevent resource exhaustion with policies in Azure API Management.