diff --git a/articles/service-fabric/how-to-managed-cluster-modify-node-type.md b/articles/service-fabric/how-to-managed-cluster-modify-node-type.md
index cfbe29c024..8486bd2766 100644
--- a/articles/service-fabric/how-to-managed-cluster-modify-node-type.md
+++ b/articles/service-fabric/how-to-managed-cluster-modify-node-type.md
@@ -163,7 +163,7 @@ In this walkthrough, you learn how to modify the node count for a node type usin
 
 ![Sample showing a node count increase][adjust-node-count]
 
-6) Select `Manage node type scaling` to configure the scaling settings and choose between custom autoscale and manual scale options. Autoscale is a built-in feature that helps applications perform their best when demand changes. You can choose to scale your resource manually to a specific instance count or via a custom autoscale policy that scales based on metric thresholds. You can also schedule instance counts to scale during designated time windows. [Learn more about Azure Autoscale](/azure/azure-monitor/platform/autoscale-get-started?WT.mc_id=Portal-Microsoft_Azure_Monitoring) or [view the how-to video](https://www.microsoft.com/videoplayer/embed/RE4u7ts).
+6) Select `Manage node type scaling` to configure the scaling settings and choose between custom autoscale and manual scale options. Autoscale is a built-in feature that helps applications perform their best when demand changes. You can choose to scale your resource manually to a specific instance count or via a custom autoscale policy that scales based on metric thresholds. You can also schedule instance counts to scale during designated time windows. [Learn more about Azure Autoscale](/azure/azure-monitor/platform/autoscale-get-started?WT.mc_id=Portal-Microsoft_Azure_Monitoring) or [view the how-to video](https://learn-video.azurefd.net/vod/player?id=125ecef8-c287-4a81-9001-69c01558398c).
 
    * **Custom autoscale**: Select the appropriate `scale mode` to define the custom Autoscale policy - `Scale to a specific instance count`or `Scale based on a metric`. The latter is based on metric trigger rules, for example, increase instance count by 1 when CPU Percentage is above 70%. Once you define the policy, select `Save` at the top.
 
diff --git a/articles/virtual-machines/prepay-reserved-vm-instances.md b/articles/virtual-machines/prepay-reserved-vm-instances.md
index 3485eba01b..400d3de02f 100644
--- a/articles/virtual-machines/prepay-reserved-vm-instances.md
+++ b/articles/virtual-machines/prepay-reserved-vm-instances.md
@@ -107,7 +107,7 @@ If you have an EA agreement, you can use the **Add more option** to quickly add
 |Term        |One year or three years. There's also a 5-year term available only for HBv2 VMs.|
 |Quantity    |The number of instances being purchased within the reservation. The quantity is the number of running VM instances that can get the billing discount. For example, if you are running 10 Standard_D2 VMs in the East US, then you would specify quantity as 10 to maximize the benefit for all running VMs. |
 
-> [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE2PjmT]
+> [!VIDEO https://learn-video.azurefd.net/vod/player?id=4e688b15-2bc8-47b5-b67e-16ea39397709]
 
 ## Usage data and reservation utilization