Skip to content

Commit b065aa0

Browse files
authored
Update towards minor changes
1 parent 9ca0037 commit b065aa0

File tree

1 file changed

+3
-6
lines changed

1 file changed

+3
-6
lines changed

articles/storage-mover/agent-deploy.md

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: stevenmatthew
55
ms.author: shaas
66
ms.service: azure-storage-mover
77
ms.topic: how-to
8-
ms.date: 10/30/2023
8+
ms.date: 07/19/2024
99
---
1010

1111
<!--
@@ -127,12 +127,9 @@ The agent is delivered with a default user account and password. Connect to the
127127

128128
## Bandwidth throttling
129129

130-
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.
130+
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.
131131

132-
> [!IMPORTANT]
133-
> The current Azure Storage Mover agent does not support bandwidth throttling schedules.
134-
135-
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.
132+
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.
136133

137134
## Decommissioning an agent
138135

0 commit comments

Comments
 (0)