Merge pull request #123798 from madhurinms/patch-22

Update agent-deploy.md

Author: Court72

articles/storage-mover/agent-deploy.md

@@ -127,12 +127,9 @@ The agent is delivered with a default user account and password. Connect to the
 
 ## Bandwidth throttling
 
-Take time to consider the amount of bandwidth a new machine uses before you deploy it to your network. An Azure Storage Mover agent communicates with a source share using the local network, and the Azure Storage service on the wide area network (WAN) link. In both cases, the agent uses all available network bandwidth.
+Take time to consider the amount of bandwidth a new machine uses before you deploy it to your network. An Azure Storage Mover agent communicates with a source share using the local network, and the Azure Storage service on the wide area network (WAN) link. In both cases, the agent is designed to make full use of the network's bandwidth by default. However, you can now [set bandwidth management schedules](./bandwidth-management.md) for your Storage Mover agents.
 
-> [!IMPORTANT]
-> The current Azure Storage Mover agent does not support bandwidth throttling schedules.
-
-If bandwidth throttling is important to you, create a local virtual network with an internet connection and configure quality of service (QoS) settings. This approach allows you to expose the agent through the virtual network and to locally configure an unauthenticated network proxy server on the agent if needed.
+Alternatively, you can create a local virtual network with an internet connection and configure quality of service (QoS) settings. This approach allows you to expose the agent through the virtual network and to locally configure an unauthenticated network proxy server on the agent if needed.
 
 ## Decommissioning an agent