MicrosoftDocs · jaydestro · May 29, 2025 · May 30, 2025 · May 30, 2025 · May 30, 2025
diff --git a/articles/cosmos-db/continuous-backup-restore-introduction.md b/articles/cosmos-db/continuous-backup-restore-introduction.md
@@ -19,7 +19,7 @@ Azure Cosmos DB's point-in-time restore feature helps in multiple scenarios incl
 * Restoring a deleted account, database, or a container.
 * Restoring into any region (where backups existed) at the restore point in time.
 
-> [!VIDEO https://aka.ms/docs.continuous-backup-restore]
+> [!VIDEO https://www.youtube.com/embed/m3lKJf47bQA?si=yVT3iGBLa40eQXdb]
 
 Azure Cosmos DB performs data backup in the background without consuming any extra provisioned throughput (RUs) or affecting the performance and availability of your database. Continuous backups are taken in every region where the account exists. For example, an account can have a write region in West US and read regions in East US and East US 2. These replica regions can then be backed up to a remote Azure Storage account in each respective region. By default, each region stores the backup in Locally Redundant storage accounts. If the region has [Availability zones](/azure/architecture/reliability/architect) enabled  then the backup is stored in Zone-Redundant storage accounts.
 

diff --git a/articles/cosmos-db/nosql/change-feed-design-patterns.md b/articles/cosmos-db/nosql/change-feed-design-patterns.md
@@ -17,7 +17,7 @@ ms.custom: cosmos-db-video, build-2023
 The Azure Cosmos DB change feed enables efficient processing of large datasets that have a high volume of writes. Change feed also offers an alternative to querying an entire dataset to identify what has changed. This article focuses on common change feed design patterns, design tradeoffs, and change feed limitations.
 
 >
-> [!VIDEO https://aka.ms/docs.change-feed-azure-functions]
+> [!VIDEO 9fa5b80e-43be-4aaf-ac16-c928be26e1ab]
 
 Azure Cosmos DB is well-suited for IoT, gaming, retail, and operational logging applications. A common design pattern in these applications is to use changes to the data to trigger other actions. Examples of these actions include:
 

diff --git a/articles/cosmos-db/nosql/changefeed-ecommerce-solution.md b/articles/cosmos-db/nosql/changefeed-ecommerce-solution.md
@@ -19,7 +19,7 @@ The Azure Cosmos DB change feed is a mechanism to get a continuous and increment
 This article describes how change feed can be used by an e-commerce company to understand user patterns, perform real-time data analysis and visualization. You will analyze events such as a user viewing an item, adding an item to their cart, or purchasing an item. When one of these events occurs, a new record is created, and the change feed logs that record. Change feed then triggers a series of steps resulting in visualization of metrics that analyze the company performance and activity. Sample metrics that you can visualize include revenue, unique site visitors, most popular items, and average price of the items that are viewed versus added to a cart versus purchased. These sample metrics can help an e-commerce company evaluate its site popularity, develop its advertising and pricing strategies, and make decisions regarding what inventory to invest in.
 
 >
-> [!VIDEO https://aka.ms/docs.ecomm-change-feed]
+> [!VIDEO 1b16a06b-2d7d-440d-8a47-6097aeb4654f]
 >
 
 ## Solution components
@@ -391,4 +391,4 @@ To delete the resources that you created during this lab, navigate to the resour
 
 ## Next steps 
 
-* To learn more about change feed, see [working with change feed support in Azure Cosmos DB](../change-feed.md)
+* To learn more about change feed, see [working with change feed support in Azure Cosmos DB](../change-feed.md)
diff --git a/articles/cosmos-db/nosql/modeling-data.md b/articles/cosmos-db/nosql/modeling-data.md
@@ -20,7 +20,7 @@ While schema-free databases, like Azure Cosmos DB, make it super easy to store a
 How is data going to be stored? How is your application going to retrieve and query data? Is your application read-heavy, or write-heavy?
 
 >
-> [!VIDEO https://aka.ms/docs.modeling-data]
+> [!VIDEO 01973aa6-4cdf-402d-8721-d33477ec0dde]
 
 After reading this article, you'll be able to answer the following questions:
 

diff --git a/articles/cosmos-db/nosql/serverless-computing-database.md b/articles/cosmos-db/nosql/serverless-computing-database.md
@@ -115,7 +115,7 @@ Native integration between Azure Cosmos DB and Azure Functions is available in t
 * In Visual Studio, you can create the trigger using the [Azure Functions Tools](/azure/azure-functions/functions-develop-vs):
 
   >
-  >[!VIDEO https://aka.ms/docs.change-feed-azure-functions]
+  >[!VIDEO 751f6542-10e8-4784-a094-2a03ae23b281]
 
 ## Why choose Azure Functions integration for serverless computing?
 

diff --git a/articles/cosmos-db/nosql/tutorial-dotnet-bulk-import.md b/articles/cosmos-db/nosql/tutorial-dotnet-bulk-import.md
@@ -16,7 +16,7 @@ ms.custom: devx-track-csharp, cosmos-db-video, devx-track-dotnet
 This tutorial shows how to build a .NET console application that optimizes provisioned throughput (RU/s) required to import data to Azure Cosmos DB. 
 
 >
-> [!VIDEO https://aka.ms/docs.learn-live-dotnet-bulk]
+> [!VIDEO 1a4e6f33-985f-4b3c-b307-341e5b30309a]
 
 In this article, you'll read data from a sample data source and import it into an Azure Cosmos DB container.
 This tutorial uses [Version 3.0+](https://www.nuget.org/packages/Microsoft.Azure.Cosmos) of the Azure Cosmos DB .NET SDK, which can be targeted to .NET Framework or .NET Core.