updates

Author: fauhse

articles/storage-mover/bandwidth-management.md

@@ -10,13 +10,13 @@ ms.date: 06/01/2022
 
 # Manage network bandwidth of a Storage Mover agent
 
-In this article, you'll learn how to set bandwidth management schedules for your Storage Mover agents.
+In this article, you learn how to set bandwidth management schedules for your Storage Mover agents.
 
 When migrating your files and folders to Azure, you need to carefully consider the upload bandwidth you want to make available to each of your Storage Mover agents. Other workloads may also depend on having sufficient bandwidth available. To make your Storage Mover agents a good neighbor to other workloads in your network, you can schedule limits for each agent.
 
 ## Prerequisites
 
-Before you can set a bandwidth schedule, you first need to have [deployed a Storage Mover resource](storage-mover-create.md) in one of your resource groups, and [have an agent registered](agent-register.md). Bandwidth limit schedules are set and stored per registered agent.
+Before you can set a bandwidth schedule, you first need to [deploy a Storage Mover resource](storage-mover-create.md) in one of your resource groups, and then [register an agent](agent-register.md). Bandwidth limit schedules are set and stored per registered agent.
 
 ## Understanding the basic concept of bandwidth management
 
@@ -34,10 +34,10 @@ IMAGE of week-long b/w schedule window
 
 This schedule looks a lot like a calendar in outlook, but there are a few important differences:
 
-- The schedule is repeating itself. It has the 7 weekdays and at the end of the week, the schedule repeats.
+- The schedule is repeating itself. It has the seven weekdays and at the end of the week, the schedule repeats.
 - An entry in the schedule is a designated limit the agent shall not exceed. Clear time stretches on a day designate no limitation, allowing the agent to use as much bandwidth as needed.
 - You cannot schedule a limit for a specific date, but for repeating weekdays. As an example, you can say: *"Limit the agent's bandwidth to no more than x during my cloud backup window on Sundays"*
-- The schedule does not store a timezone. When you set a limit that starts for instance at 9am, then that means agent-local time. You can see what timezone is configured for the agent. Pay close attention to this as it may be different to the timezone of your site where the agent is deployed at.
+- The schedule does not store a timezone. When you set a limit that starts for instance at 9am, then that means agent-local time. You can see what timezone is configured for the agent. Pay close attention, the agent's timezone may be different from the timezone of your site where the agent is deployed.
 
 ## Enabling or changing a bandwidth management schedule
 <!-- ########################################################
@@ -57,16 +57,16 @@ Using the Azure portal, you can enable a bandwidth schedule on a registered agen
 <!-- ########################################################
 Tabs: portal / PowerShell
 ########################################################-->
-1. Open the bandwidth scheduling window. ([see previous section](#enabling-or-changing-a-bandwidth-management-schedule-for-an-agent))
+1. Open the bandwidth scheduling window. ([see previous section](#enabling-or-changing-a-bandwidth-management-schedule))
 1. You can create a custom schedule for this selected agent, or you can [reuse a schedule](#reusing-a-schedule-from-another-agent) that was previously created for another agent.
-1. To create a custom schedule, select the "Add limit" command. A dialog will open, allowing you to define a time slice during which you want to set the maximum bandwidth on your WAN link, that the agent is allowed to use.
+1. To create a custom schedule, select the "Add limit" command. A dialog opens, allowing you to define a time slice during which you want to set the maximum bandwidth on your WAN link, that the agent is allowed to use.
    <!-- 
    !########################################################
    IMAGE of Add limit window
    !########################################################
    -->
-1. The dialog requires you to set a start and an end-time during which you want to apply a uplink limit for the agent. You can then pick on which days of the week you like to apply your new limit. Select all weekdays during which you like to apply the same limit. You then need to specify the limit in Mbps (Megabits per second). Overlapping times are not allowed. Any limit you set, will apply at this time in the agent's timezone displayed at the top of the bandwidth management window. You may need to offset your schedule or adjust the agent's timezone. Find more details in the paragraph: "*[Reusing a schedule from another agent](#reusing-a-schedule-from-another-agent)*".
-1. Select the "*Save*" button at the bottom of the "*Bandwidth management*" window to apply your changes to this agent.
+1. The dialog requires you to set a start and an end-time during which you want to apply a uplink limit for the agent. You can then pick on which days of the week you like to apply your new limit. Select all weekdays during which you like to apply the same limit. You then need to specify the limit in Mbps (Megabits per second). Overlapping times are not allowed. Any limit you set, will apply at the displayed time in the agent's timezone. You can find the agent's timezone displayed at the top of the bandwidth management window. You may need to offset your schedule or adjust the agent's timezone. Find more details in the paragraph: "*[Reusing a schedule from another agent](#reusing-a-schedule-from-another-agent)*".
+1. To apply your changes to this agent, select the "*Save*" button at the bottom of the "*Bandwidth management*" window.
 
 > [!NOTE]
 > The bandwidth limit you set limits the *migration data stream* the agent will establish to your target storage in Azure. However, in addition to this data stream, there is control plane traffic from the agent to Azure. Control messages, progress telemetry, and copy logs generally require only a small amount of bandwidth. To ensure proper functionality of the agent throughout your migration, the control plane of the agent is not governed by the limit schedule you set. In an extreme case the agent may exceed the limits you defined by a small amount.
@@ -90,15 +90,24 @@ You can reuse the bandwidth limit schedule from another agent for your currently
 > [!IMPORTANT]
 > Schedules are stored free of a timezone. That enables them to be reused on other agents. A scheduled limit will be in effect during this time in whatever the agent's timezone is. You need to ensure that you offset your bandwidth management schedule if the agent's timezone is different to the one used in the location you've deployed the agent in. For example, if the agent's timezone is UTC but your agent is actually deployed in the Pacific timezone (PST), you need to offset your schedule by -7 hours or adjust your agent's timezone to the correct one for the location. Alternatively, you can adjust the agent's timezone to the correct one for the location. Doing this removes the need to offset your schedule and also enables your schedule to automatically adjust to Daylight Savings, should your timezone observe that.
 
-### [Azure portal](#tab/portal)
+1. Open the bandwidth management schedule for your selected agent. ([See the previous paragraph.](#enabling-or-changing-a-bandwidth-management-schedule))
+1. Select the command "*Import limits from other agents*" and select the agent you like to copy the schedule from. If there are no agents in the list, then there is no other agent that has a schedule set.
+   > [!WARNING]
+   > Using this option will overwrite the currently configured schedule for this agent.
+1. Optionally, you can now modify this copied schedule.
+1. To apply your changes to this agent, select the "*Save*" button at the bottom of the "*Bandwidth management*" window.
 
-   1. Open the bandwidth management schedule for your selected agent. ([See the previous paragraph.](#enabling-or-changing-a-bandwidth-management-schedule))
-   1. Select the command "*Import limits from other agents*" and select the agent you like to copy the schedule from. If there are no agents in the list, then there is no other agent that has a schedule set.
-       > [!WARNING]
-       > Using this option will overwrite the currently configured schedule for this agent.
-   1. Optionally, you can now modify this copied schedule. The other agent's schedule won't be affected by that.
-   1. Select the "*Save*" button at the bottom of the "*Bandwidth management*" window to apply your changes to this agent.
+## Use PowerShell to configure a bandwidth limit schedule.
+<!-- ########################################################
+Add all cmdlets - better to have them in one place.
+########################################################-->
+
+
+## Next steps
 
-### [Azure PowerShell](#tab/CLI)
+Advance to one of the next articles to learn how to deploy a Storage Mover agent or create a migration project.
+> [!div class="nextstepaction"]
+> [Create a migration project](project-manage.md)
 
----
+> [!div class="nextstepaction"]
+> [Create a migration job](job-definition-create.md)