diff --git a/Instructions/00-powershell-script.md b/Instructions/00-powershell-script.md index b930080..9e4c572 100644 --- a/Instructions/00-powershell-script.md +++ b/Instructions/00-powershell-script.md @@ -108,7 +108,7 @@ When a parameter is added to the script execution, the parameter performs severa 1. **Read and Parse the .env File**: If using an **.env** file, reads it and parses its content. By default, the script uses the **.env** file for configuration values, but this setting can be overridden by setting the *-useEnvFile* parameter to *False*. 1. **Conditional Resource Creation and Configuration**: Conditionally creates Azure resources and configures network rules. 1. **Resource Group Creation**: Creates a new resource group. By default, a Resource Group is created, but this setting can be skipped by setting the *-skipCreatingResourceGroup* parameter to *True*. - 1. **Deployment and Configuration of Azure Cosmos DB resources**: Deploys v-Core-based Azure Cosmos DB for MongoDB resources. By default, a Cosmos DB cluster is created, but this setting can be skipped by setting the *-skipCreatingCosmosDBCluster* parameter to *True*. + 1. **Deployment and Configuration of Azure Cosmos DB resources**: Deploys vCore-based Azure Cosmos DB for MongoDB resources. By default, a Cosmos DB cluster is created, but this setting can be skipped by setting the *-skipCreatingCosmosDBCluster* parameter to *True*. 1. **Deployment and Configuration of Azure OpenAI Resources**: Deploys Azure OpenAI models and setups. By default, an Azure OpenAI account, deployment, and completion deployment are created, but these settings can be skipped by setting the respective parameters to *True*. 1. **Update the .env File**: Updates the **.env** file with the latest configurations. Updating the **.env** file is done by default unless the parameter *-updateEnvFile* is set to *False*. 1. **Output Resource Information**: Outputs detailed information about the created or configured resources. diff --git a/Instructions/01-create-account.md b/Instructions/01-create-account.md index 7510063..fe0e370 100644 --- a/Instructions/01-create-account.md +++ b/Instructions/01-create-account.md @@ -1,22 +1,22 @@ --- lab: - title: 'Create a v-Core-based Azure Cosmos DB for MongoDB account using the Azure portal' - module: 'Module 1 - Get Started with v-Core-based Azure Cosmos DB for MongoDB' + title: 'Create a vCore-based Azure Cosmos DB for MongoDB account using the Azure portal' + module: 'Module 1 - Get Started with vCore-based Azure Cosmos DB for MongoDB' --- -In this lab, we guide you through the process of creating a v-Core-based Azure Cosmos DB for MongoDB account using the Azure portal. We walk you through the steps of setting up the Cosmos DB account, configuring the necessary settings, and preparing it for use. The focus is on understanding the different configuration options and how they affect the behavior and performance of the Cosmos DB. By the end of this lab, you have a fully configured Cosmos DB for MongoDB ready for data storage and retrieval. +In this lab, we guide you through the process of creating a vCore-based Azure Cosmos DB for MongoDB account using the Azure portal. We walk you through the steps of setting up the Cosmos DB account, configuring the necessary settings, and preparing it for use. The focus is on understanding the different configuration options and how they affect the behavior and performance of the Cosmos DB. By the end of this lab, you have a fully configured Cosmos DB for MongoDB ready for data storage and retrieval. ### Objectives - Understand the process of creating a new resource in Azure portal. -- Learn how to set up a v-Core-based Azure Cosmos DB for MongoDB account. +- Learn how to set up a vCore-based Azure Cosmos DB for MongoDB account. - Familiarize with the different configuration options available during the setup. - Understand the process of reviewing and finalizing the setup of the Cosmos DB account. - Learn how to connect to the newly created Cosmos DB account using the Azure portal's Mongo Shell. -## Create your v-Core-based Azure Cosmos DB for MongoDB account +## Create your vCore-based Azure Cosmos DB for MongoDB account -Let's go ahead and learn how easy is to create your v-Core-based Azure Cosmos DB for MongoDB account using the Azure portal. To create this account, follow these steps: +Let's go ahead and learn how easy is to create your vCore-based Azure Cosmos DB for MongoDB account using the Azure portal. To create this account, follow these steps: 1. Sign in to the [Azure portal](https://portal.azure.com/). @@ -64,7 +64,7 @@ Let's go ahead and learn how easy is to create your v-Core-based Azure Cosmos DB | Firewall rules | Manually add all the IP ranges that you would like to grant access to your Cosmos DB account by selecting a *Rule Name*, a *Start IP address* and an *End IP address.* | > [!NOTE] - > On a production environment, you would likely select **Private Access** for your *conectivity method* and use a *virtual network* and a *subnet* provided by your Azure network administrator. You will also most likely set private endpoints for access to the v-Core-based Azure Cosmos DB for MongoDB account. + > On a production environment, you would likely select **Private Access** for your *conectivity method* and use a *virtual network* and a *subnet* provided by your Azure network administrator. You will also most likely set private endpoints for access to the vCore-based Azure Cosmos DB for MongoDB account. > > Under the **Firewall rules** section is where you can add specific IP addresses that are allowed to access the Cosmos DB account. This is useful for restricting access to only specific IP addresses, such as your organization's IP addresses. You will notice there are two options: **+ Add current client IP address (your current public IP address)** and **+ Add 0.0.0.0 - 255.255.255.255**. The first option will add your current IP address to the list of allowed IP addresses, which could be benign if your public IP from your client never changes. The second option will allow you to add the range of ***ALL*** IP addresses in the internet. Be very careful of ever selecting that second option, since it opens your cluster to the whole internet. @@ -72,21 +72,21 @@ Let's go ahead and learn how easy is to create your v-Core-based Azure Cosmos DB 1. In the **Review + create** tab, review your account settings, and then select the **Create** button. -It takes 5+ minutes for the v-Core-based Azure Cosmos DB for MongoDB account to be created. Once the account is created, you can use the Azure portal to access your account. +It takes 5+ minutes for the vCore-based Azure Cosmos DB for MongoDB account to be created. Once the account is created, you can use the Azure portal to access your account. -## Connect to your v-Core-based Azure Cosmos DB for MongoDB account using the Azure portal +## Connect to your vCore-based Azure Cosmos DB for MongoDB account using the Azure portal -Time to connect to your v-Core-based Azure Cosmos DB for MongoDB account using the Azure portal. To do connect to the account, follow these steps: +Time to connect to your vCore-based Azure Cosmos DB for MongoDB account using the Azure portal. To do connect to the account, follow these steps: 1. If you aren't signed in, sign in to the [Azure portal](https://portal.azure.com). 1. In the search bar at the top of the portal, type **Azure Cosmos DB** and select it from the search results. -1. In the **Azure Cosmos DB** window, select your newly created v-Core-based Azure Cosmos DB for MongoDB account. +1. In the **Azure Cosmos DB** window, select your newly created vCore-based Azure Cosmos DB for MongoDB account. Let's get familiar with a couple of options available to you in the *Azure Cosmos DB for MongoDB (vCore)* window. You notice that there are several options available to you in the menu, including **Overview**, **Quit start**, **Networking**, **Connection string**, among others. For this lab, you focus on those four options you listed. -1. **Overview**: the Overview option provides you with a quick overview of your v-Core-based Azure Cosmos DB for MongoDB account. The overview includes the account's name, status, subscription, resource group, and location. This overview also includes the MongoDB version, admin username, cluster tier, shard count, disk size, connectivity method, and high availability. One interesting option available is to **Reset password**. +1. **Overview**: the Overview option provides you with a quick overview of your vCore-based Azure Cosmos DB for MongoDB account. The overview includes the account's name, status, subscription, resource group, and location. This overview also includes the MongoDB version, admin username, cluster tier, shard count, disk size, connectivity method, and high availability. One interesting option available is to **Reset password**. 1. **Reset password**: On the top of the overview page, select **Reset password**. You're prompted to enter a new password and to confirm it. This option is useful if you ever need to change the password for the admin user. @@ -94,17 +94,17 @@ Let's get familiar with a couple of options available to you in the *Azure Cosmo 1. **Quick start**: You'll skip this one for now and revisit it in the next section of the lab. -1. **Networking**: This tab provides you with the options to configure the network settings for your v-Core-based Azure Cosmos DB for MongoDB account. This option includes the ability to add IP addresses to the firewall rules, private endpoint connections and allow public access from Azure services and resources within Azure to this cluster. +1. **Networking**: This tab provides you with the options to configure the network settings for your vCore-based Azure Cosmos DB for MongoDB account. This option includes the ability to add IP addresses to the firewall rules, private endpoint connections and allow public access from Azure services and resources within Azure to this cluster. 1. **Connection string**: This option should list the connection string your application needs to connect to this cluster. Remember that just knowing the connection string isn't enough to connect to the cluster. Remember that you also need to ensure that the IP address from where you're connecting is allowed in the firewall rules. - 1. **Connection String**: Select on the **Copy** button to copy the connection string to your clipboard. You use this connection string to connect to your v-Core-based Azure Cosmos DB for MongoDB account. + 1. **Connection String**: Select on the **Copy** button to copy the connection string to your clipboard. You use this connection string to connect to your vCore-based Azure Cosmos DB for MongoDB account. 1. Copy the connection string to your application's configuration file or to a secure location for later use in your application. -### Connect to your v-Core-based Azure Cosmos DB for MongoDB account using the Azure portal's Mongo Shell +### Connect to your vCore-based Azure Cosmos DB for MongoDB account using the Azure portal's Mongo Shell -Now that you have your v-Core-based Azure Cosmos DB for MongoDB account created, let's connect to it using the Azure portal's Mongo Shell. To connect, follow these steps: +Now that you have your vCore-based Azure Cosmos DB for MongoDB account created, let's connect to it using the Azure portal's Mongo Shell. To connect, follow these steps: 1. In the **Azure Cosmos DB for MongoDB (vCore)** window, select **Quick start**. @@ -113,7 +113,7 @@ Now that you have your v-Core-based Azure Cosmos DB for MongoDB account created, 1. In the **Quick start** window, select **Launch quick start**. This option creates a sample database for you to test on. In a production environment, you would most likely not use the **Launch quick start** option, since you would be creating your own databases and collections. - 1. Enter the password for the admin user you created when you created the v-Core-based Azure Cosmos DB for MongoDB account in the Mongo Shell window. Select **Next**. + 1. Enter the password for the admin user you created when you created the vCore-based Azure Cosmos DB for MongoDB account in the Mongo Shell window. Select **Next**. 1. Select the **Create new database and collection** button. On the Mongo Shell screen, you notice that the MongoDB commands to create the new database and collection were run. Select **Next**. @@ -125,7 +125,7 @@ Now that you have your v-Core-based Azure Cosmos DB for MongoDB account created, 1. In the **Quick start** window, select **Mongo Shell**. - 1. Enter the password for the admin user you created when you created the v-Core-based Azure Cosmos DB for MongoDB account in the Mongo Shell window. + 1. Enter the password for the admin user you created when you created the vCore-based Azure Cosmos DB for MongoDB account in the Mongo Shell window. 1. To test the connection, let's run some MongoDB commands. Run the following commands: @@ -154,7 +154,7 @@ Now that you have your v-Core-based Azure Cosmos DB for MongoDB account created, exit ``` -You now have a fully configured v-Core-based Azure Cosmos DB for MongoDB account and you connected to it using the Azure portal's Mongo Shell. You're ready to start using it to store and retrieve data. +You now have a fully configured vCore-based Azure Cosmos DB for MongoDB account and you connected to it using the Azure portal's Mongo Shell. You're ready to start using it to store and retrieve data. ## Clean Up @@ -164,9 +164,9 @@ After completing the lab exercises, it's important to clean up any resources you 1. **Delete Resource Group**: If you created a new resource group for this lab, navigate to *Resource groups*, find your group, and delete it. This action removes all the resources contained within it, including your Azure Cosmos DB instance. -1. **Manually Delete Individual Resources**: If you added resources to an existing resource group, you need to delete each resource individually. Navigate to the v-Core-based Azure Cosmos DB for MongoDB account and delete it. +1. **Manually Delete Individual Resources**: If you added resources to an existing resource group, you need to delete each resource individually. Navigate to the vCore-based Azure Cosmos DB for MongoDB account and delete it. -1. **Verify Deletion**: Confirm that the v-Core-based Azure Cosmos DB for MongoDB account resource you no longer need was successfully removed and is no longer listed in your Azure portal. +1. **Verify Deletion**: Confirm that the vCore-based Azure Cosmos DB for MongoDB account resource you no longer need was successfully removed and is no longer listed in your Azure portal. 1. **Review Billing**: Check your Azure billing section to ensure no unexpected charges are incurred, verifying that all unwanted resources were successfully deleted. @@ -174,4 +174,4 @@ This cleanup process helps maintain your Azure account organized and free from u ## Conclusion -This lab guided you through how to set up a v-Core-based Azure Cosmos DB for MongoDB account using the Azure portal. The lab showed you how to connect to the newly created v-Core-based Azure Cosmos DB for MongoDB account using the Azure portal's Mongo Shell. You learned how to configure the network settings for your v-Core-based Azure Cosmos DB for MongoDB account and how to retrieve the connection string for your application. You also learned how to reset the password for the admin user. You should now have a good understanding of the different configuration options available when setting up a v-Core-based Azure Cosmos DB for MongoDB account and how to connect to it using the Azure portal's Mongo Shell. In the next module, you'll learn how to migrate existing MongoDB databases to your v-Core-based Azure Cosmos DB for MongoDB account. +This lab guided you through how to set up a vCore-based Azure Cosmos DB for MongoDB account using the Azure portal. The lab showed you how to connect to the newly created vCore-based Azure Cosmos DB for MongoDB account using the Azure portal's Mongo Shell. You learned how to configure the network settings for your vCore-based Azure Cosmos DB for MongoDB account and how to retrieve the connection string for your application. You also learned how to reset the password for the admin user. You should now have a good understanding of the different configuration options available when setting up a vCore-based Azure Cosmos DB for MongoDB account and how to connect to it using the Azure portal's Mongo Shell. In the next module, you'll learn how to migrate existing MongoDB databases to your vCore-based Azure Cosmos DB for MongoDB account. diff --git a/Instructions/02-migrate.md b/Instructions/02-migrate.md index fc3a0d9..f0d0bac 100644 --- a/Instructions/02-migrate.md +++ b/Instructions/02-migrate.md @@ -1,20 +1,20 @@ --- lab: - title: 'Migrate a MongoDB database to a v-Core-based Azure Cosmos DB for MongoDB account' - module: 'Module 2 - Migrate to v-Core-based Azure Cosmos DB for MongoDB' + title: 'Migrate a MongoDB database to a vCore-based Azure Cosmos DB for MongoDB account' + module: 'Module 2 - Migrate to vCore-based Azure Cosmos DB for MongoDB' --- -Data migration is a critical step in the process of moving from an existing MongoDB database to a v-Core-based Azure Cosmos DB for MongoDB account. While there are several ways to migrate a MongoDB database to a v-Core-based Azure Cosmos DB for MongoDB account, this lab focuses on using the MongoDB native tools to migrate the database. The MongoDB native tools are the most common way to migrate a MongoDB database to another. Most MongoDB administrators and developers are familiar with these tools. +Data migration is a critical step in the process of moving from an existing MongoDB database to a vCore-based Azure Cosmos DB for MongoDB account. While there are several ways to migrate a MongoDB database to a vCore-based Azure Cosmos DB for MongoDB account, this lab focuses on using the MongoDB native tools to migrate the database. The MongoDB native tools are the most common way to migrate a MongoDB database to another. Most MongoDB administrators and developers are familiar with these tools. > [!NOTE] > While this lab uses the MongoDB community edition, similar migration steps can be used for other MongoDB editions. ### Objectives -In this lab, you learn how to use the MongoDB native tools to migrate a MongoDB database to a v-Core-based Azure Cosmos DB for MongoDB account. You use the following tools: +In this lab, you learn how to use the MongoDB native tools to migrate a MongoDB database to a vCore-based Azure Cosmos DB for MongoDB account. You use the following tools: - **mongodump**: This tool is used to dump the data from the local MongoDB server into a BSON (Binary JSON) file. -- **mongorestore**: This tool is used to restore the dumped data into the v-Core-based Azure Cosmos DB for MongoDB server. +- **mongorestore**: This tool is used to restore the dumped data into the vCore-based Azure Cosmos DB for MongoDB server. ### Build your own lab environment @@ -35,7 +35,7 @@ If you need to build your own lab environment, you need the following components You need access to the following Azure resources for this lab: -- v-Core-based Azure Cosmos DB for MongoDB account +- vCore-based Azure Cosmos DB for MongoDB account You can create these resources via the *Azure portal* or use the ***create-azure-resources.ps1*** PowerShell script with the ***.env** file. Don't use existing production resources for this lab or any lab. @@ -45,7 +45,7 @@ You can create these resources via the *Azure portal* or use the ***create-azure This file is both used to retrieve and store the necessary environment variables for both the PowerShell script and the vector search application APIs. It's the easiest way to prepopulate your resource information. The file is used to store the environment variables for your Azure Cosmos DB and Azure OpenAI account. -If you already have an existing Resource Group, a v-Core-based Azure Cosmos DB for MongoDB account, an Azure Storage Account or an Azure Log Analytics workspace that you would like to use, just fill in those values in the **.env** file and set the skip create option for that resource to **true**. By default, the *create-azure-resources.ps1* script uses this file to retrieve the necessary environment variables. Note that the *create-azure-resources.ps1* script will populate the environment variables with default values if not specified in the .env file. +If you already have an existing Resource Group, a vCore-based Azure Cosmos DB for MongoDB account, an Azure Storage Account or an Azure Log Analytics workspace that you would like to use, just fill in those values in the **.env** file and set the skip create option for that resource to **true**. By default, the *create-azure-resources.ps1* script uses this file to retrieve the necessary environment variables. Note that the *create-azure-resources.ps1* script will populate the environment variables with default values if not specified in the .env file. To learn more about the ***.env*** file and its parameters, review the [***.env*** file documentation](./00-env-file.md). @@ -57,7 +57,7 @@ To learn more about the ***.env*** file and its parameters, review the [***.env* If you aren't using existing resources, or you aren't creating them through the Azure portal, this script creates the necessary Azure resources for this lab. It gives you the flexibility to create some or all of the resources required for this lab. You can either run the script as is or modify it to suit your needs. The resources created by the script include: - Resource Group -- v-Core-based Azure Cosmos DB for MongoDB account +- vCore-based Azure Cosmos DB for MongoDB account The script has a rich set of parameters to help you customize the resources to be created. It also uses an ***.env*** file to retrieve and store the necessary environment variables for both the PowerShell script and the vector search application APIs. @@ -85,7 +85,7 @@ To create the necessary Azure resources for this lab: 1. Make sure that the **.env** file is populated with the resource information. > [!NOTE] -> The v-Core-based Azure Cosmos DB for MongoDB account will need a firewall rule to allow access from your current public IP address. If your Azure Cosmos DB account was generated by the *create-azure-resources.ps1* script, it should have created the firewall rule for you. Check the existing firewall rules under the ***Networking*** *Setting* section of the *Azure Cosmos DB Account*. If you are not sure what your current public IP address is, you can use the following command to find out: +> The vCore-based Azure Cosmos DB for MongoDB account will need a firewall rule to allow access from your current public IP address. If your Azure Cosmos DB account was generated by the *create-azure-resources.ps1* script, it should have created the firewall rule for you. Check the existing firewall rules under the ***Networking*** *Setting* section of the *Azure Cosmos DB Account*. If you are not sure what your current public IP address is, you can use the following command to find out: > ```powershell > Invoke-RestMethod -Uri 'http://ipinfo.io/ip' -Method Get > ``` @@ -172,11 +172,11 @@ We should now have a running MongoDB server on your local machine. Let's load so This command loads the sample data into the MongoDB server running on your local machine. -We should now have a running MongoDB server with some data into it, it's time to migrate it to v-Core-based Azure Cosmos DB for MongoDB. +We should now have a running MongoDB server with some data into it, it's time to migrate it to vCore-based Azure Cosmos DB for MongoDB. -## Migrate to a v-Core-based Azure Cosmos DB for MongoDB account using MongoDB native tools (offline) +## Migrate to a vCore-based Azure Cosmos DB for MongoDB account using MongoDB native tools (offline) -To export the data from the local MongoDB server and import it into the v-Core-based Azure Cosmos DB for MongoDB account, you use the MongoDB **mongodump** and **mongorestore** native tools. In a production environment, if your database is large, you might need to search for other ways to migrate the database like through *Azure Data Migration Service*. +To export the data from the local MongoDB server and import it into the vCore-based Azure Cosmos DB for MongoDB account, you use the MongoDB **mongodump** and **mongorestore** native tools. In a production environment, if your database is large, you might need to search for other ways to migrate the database like through *Azure Data Migration Service*. 1. Dump the data from your local MongoDB server into a BSON file. Run the following command in the terminal: @@ -186,16 +186,16 @@ To export the data from the local MongoDB server and import it into the v-Core-b This command creates a BSON file in the `../data/cosmicworks` folder. The **mongodump** command outputs the progress of the dump operation. -1. Restore the dumped data into your v-Core-based Azure Cosmos DB for MongoDB server. Replace ****, ****, **yourMongoDBClusterName**, and **yourDatabaseName** with your actual username, password, Azure MongoDB cluster name, and database name: +1. Restore the dumped data into your vCore-based Azure Cosmos DB for MongoDB server. Replace ****, ****, **yourMongoDBClusterName**, and **yourDatabaseName** with your actual username, password, Azure MongoDB cluster name, and database name: ```bash & mongorestore --uri "mongodb+srv://:@yourMongoDBClusterName.mongocluster.cosmos.azure.com/?tls=true&authMechanism=SCRAM-SHA-256&retrywrites=false&maxIdleTimeMS=120000" --db cosmicworks1 ../data/cosmicworks/cosmicworks ``` - This command restores the BSON file into your v-Core-based Azure Cosmos DB for MongoDB server. The **mongorestore** command outputs the progress of the restore operation. + This command restores the BSON file into your vCore-based Azure Cosmos DB for MongoDB server. The **mongorestore** command outputs the progress of the restore operation. > [!NOTE] -> Don't forget to make sure the firewall rules for your v-Core-based Azure Cosmos DB for MongoDB account are set to allow access from your current public IP address. If your Azure Cosmos DB account was generated by the *create-azure-resources.ps1* script, it should have created the firewall rule for you. Check the existing firewall rules under the ***Networking*** *Setting* section of the *v-Core-based Azure Cosmos DB for MongoDB* account. If you are not sure what your current public IP address is, you can use the following command to find out: +> Don't forget to make sure the firewall rules for your vCore-based Azure Cosmos DB for MongoDB account are set to allow access from your current public IP address. If your Azure Cosmos DB account was generated by the *create-azure-resources.ps1* script, it should have created the firewall rule for you. Check the existing firewall rules under the ***Networking*** *Setting* section of the *vCore-based Azure Cosmos DB for MongoDB* account. If you are not sure what your current public IP address is, you can use the following command to find out: > ```powershell > Invoke-RestMethod -Uri 'http://ipinfo.io/ip' -Method Get > ``` @@ -204,7 +204,7 @@ Let's verify the migration completed successfully. 1. Open the MongoDB Compass application. -1. Connect to your v-Core-based Azure Cosmos DB for MongoDB connection string. +1. Connect to your vCore-based Azure Cosmos DB for MongoDB connection string. 1. Select **Continue** on the warning screen. @@ -213,9 +213,9 @@ Let's verify the migration completed successfully. 1. Close the MongoDB Compass application. > [!NOTE] -> Note that while you used the **mongodump** and **mongorestore** tools to migrate the data from your local MongoDB server to the v-Core-based Azure Cosmos DB for MongoDB account, we could have also use **mongoexport** and **mongoimport** tools to do the same. +> Note that while you used the **mongodump** and **mongorestore** tools to migrate the data from your local MongoDB server to the vCore-based Azure Cosmos DB for MongoDB account, we could have also use **mongoexport** and **mongoimport** tools to do the same. -You should now have a running v-Core-based Azure Cosmos DB for MongoDB server with the data from your local MongoDB server. You successfully migrated the data from your local MongoDB server to the v-Core-based Azure Cosmos DB for MongoDB account using the MongoDB native tools. +You should now have a running vCore-based Azure Cosmos DB for MongoDB server with the data from your local MongoDB server. You successfully migrated the data from your local MongoDB server to the vCore-based Azure Cosmos DB for MongoDB account using the MongoDB native tools. ## Clean Up @@ -235,4 +235,4 @@ This cleanup process helps maintain your Azure account organized and free from u ## Conclusion -You successfully migrated a MongoDB database to a v-Core-based Azure Cosmos DB for MongoDB account using the MongoDB native tools. There are several other ways to migrate a MongoDB database to a v-Core-based Azure Cosmos DB for MongoDB account, including using Azure Data Studio for offline migrations and Azure Databricks for online/offline migrations. The method you choose depends on your specific requirements and constraints. +You successfully migrated a MongoDB database to a vCore-based Azure Cosmos DB for MongoDB account using the MongoDB native tools. There are several other ways to migrate a MongoDB database to a vCore-based Azure Cosmos DB for MongoDB account, including using Azure Data Studio for offline migrations and Azure Databricks for online/offline migrations. The method you choose depends on your specific requirements and constraints. diff --git a/Instructions/03-manage.md b/Instructions/03-manage.md index 2057bf0..4e39dbb 100644 --- a/Instructions/03-manage.md +++ b/Instructions/03-manage.md @@ -1,10 +1,10 @@ --- lab: - title: 'Manage a v-Core-based Azure Cosmos DB for MongoDB account' - module: 'Module 3 - Manage v-Core-based Azure Cosmos DB for MongoDB' + title: 'Manage a vCore-based Azure Cosmos DB for MongoDB account' + module: 'Module 3 - Manage vCore-based Azure Cosmos DB for MongoDB' --- -In this lab, you learn how to manage, scale, monitor, and generate alerts on a v-Core-based Azure Cosmos DB for MongoDB account. You use monitoring tools to track operations and scale your account to handle increased or decreased traffic. You learn how to enable diagnostic settings to collect logs and metrics from your Cosmos DB account. You learn how to create alerts to notify you when certain conditions are met. You run a simulated workload to generate some data for your logs and metrics. Finally, you review the logs and metrics that are being generated. +In this lab, you learn how to manage, scale, monitor, and generate alerts on a vCore-based Azure Cosmos DB for MongoDB account. You use monitoring tools to track operations and scale your account to handle increased or decreased traffic. You learn how to enable diagnostic settings to collect logs and metrics from your Cosmos DB account. You learn how to create alerts to notify you when certain conditions are met. You run a simulated workload to generate some data for your logs and metrics. Finally, you review the logs and metrics that are being generated. ### Objectives @@ -31,7 +31,7 @@ If you need to build your own lab environment, you need the following components You need access to the following Azure resources for this lab: -- v-Core-based Azure Cosmos DB for MongoDB account +- vCore-based Azure Cosmos DB for MongoDB account - Azure storage account - Log Analytics workspace @@ -43,7 +43,7 @@ You can create these resources via the *Azure portal* or use the ***create-azure This file is both used to retrieve and store the necessary environment variables for both the PowerShell script and the vector search application APIs. It's the easiest way to prepopulate your resource information. The file is used to store the environment variables for your Azure Cosmos DB and Azure OpenAI account. -If you already have an existing Resource Group or a v-Core-based Azure Cosmos DB for MongoDB account that you would like to use, just fill in those values in the **.env** file and set the skip create option for that resource to **true**. By default, the *create-azure-resources.ps1* script uses this file to retrieve the necessary environment variables. The *create-azure-resources.ps1* script populates the environment variables with default values if not specified in the **.env** file. +If you already have an existing Resource Group or a vCore-based Azure Cosmos DB for MongoDB account that you would like to use, just fill in those values in the **.env** file and set the skip create option for that resource to **true**. By default, the *create-azure-resources.ps1* script uses this file to retrieve the necessary environment variables. The *create-azure-resources.ps1* script populates the environment variables with default values if not specified in the **.env** file. To learn more about the ***.env*** file and its parameters, review the [***.env*** file documentation](./00-env-file.md). @@ -55,7 +55,7 @@ To learn more about the ***.env*** file and its parameters, review the [***.env* If you aren't using existing resources, or you aren't creating them through the Azure portal, this script creates the necessary Azure resources for this lab. It gives you the flexibility to create some or all of the resources required for this lab. You can either run the script as is or modify it to suit your needs. The resources created by the script include: - Resource Group -- v-Core-based Azure Cosmos DB for MongoDB account +- vCore-based Azure Cosmos DB for MongoDB account - Azure storage account - Log Analytics workspace @@ -85,20 +85,20 @@ To create the necessary Azure resources for this lab: 1. Make sure that the **.env** file is populated with the resource information. > [!NOTE] -> The v-Core-based Azure Cosmos DB for MongoDB account will need a firewall rule to allow access from your current public IP address. If your Azure Cosmos DB account was generated by the *create-azure-resources.ps1* script, it should have created the firewall rule for you. Check the existing firewall rules under the ***Networking*** *Setting* section of the *Azure Cosmos DB Account*. If you are not sure what your current public IP address is, you can use the following command to find out: +> The vCore-based Azure Cosmos DB for MongoDB account will need a firewall rule to allow access from your current public IP address. If your Azure Cosmos DB account was generated by the *create-azure-resources.ps1* script, it should have created the firewall rule for you. Check the existing firewall rules under the ***Networking*** *Setting* section of the *Azure Cosmos DB Account*. If you are not sure what your current public IP address is, you can use the following command to find out: > ```powershell > Invoke-RestMethod -Uri 'http://ipinfo.io/ip' -Method Get > ``` Once the resources are created and your **.env** file is populated with the resource information, you can proceed to the next step. -## Scale a v-Core-based Azure Cosmos DB for MongoDB account +## Scale a vCore-based Azure Cosmos DB for MongoDB account -As your application performance needs changes, you might need to scale your v-Core-based Azure Cosmos DB for MongoDB account to handle increased or decreased traffic. You can scale your account by changing the cluster tier (number of vCores and RAM), the storage capacity, and enabling high availability. To do scale your account, let's follow these steps: +As your application performance needs changes, you might need to scale your vCore-based Azure Cosmos DB for MongoDB account to handle increased or decreased traffic. You can scale your account by changing the cluster tier (number of vCores and RAM), the storage capacity, and enabling high availability. To do scale your account, let's follow these steps: 1. Sign in to the [Azure portal](https://portal.azure.com). -1. Navigate to your v-Core-based Azure Cosmos DB for MongoDB account. +1. Navigate to your vCore-based Azure Cosmos DB for MongoDB account. 1. In the left-hand menu, select **Scale** under the *Settings* section. @@ -112,24 +112,24 @@ As your application performance needs changes, you might need to scale your v-Co 1. Once you made your changes, select **Save** to apply the changes. -Scaling your account will take a few minutes to complete, but go ahead and continue to the next section of the lab while these changes are performed in the background. Once the changes are applied, your v-Core-based Azure Cosmos DB for MongoDB account is scaled to the new settings. The good news is that your application won't go down during this process. +Scaling your account will take a few minutes to complete, but go ahead and continue to the next section of the lab while these changes are performed in the background. Once the changes are applied, your vCore-based Azure Cosmos DB for MongoDB account is scaled to the new settings. The good news is that your application won't go down during this process. It's important to note that you can only scale up or down the cluster tier and storage capacity. You can't change the number of vCores and RAM independently. Additionally, keeping track on the cost of these changes is important when scaling up or down. -## Monitor a v-Core-based Azure Cosmos DB for MongoDB account +## Monitor a vCore-based Azure Cosmos DB for MongoDB account -Monitoring your v-Core-based Azure Cosmos DB for MongoDB account is important to ensure that your application is running smoothly and to identify any potential issues. Azure provides various tools to help you monitor your Azure Cosmos DB account, including Azure Monitor, metrics, and logs. In this section, you focus on using the v-Core-based Azure Cosmos DB for MongoDB account logs to monitor the account. +Monitoring your vCore-based Azure Cosmos DB for MongoDB account is important to ensure that your application is running smoothly and to identify any potential issues. Azure provides various tools to help you monitor your Azure Cosmos DB account, including Azure Monitor, metrics, and logs. In this section, you focus on using the vCore-based Azure Cosmos DB for MongoDB account logs to monitor the account. > [!NOTE] -> The *create-azure-resources.ps1* script should have created a Log Analytics workspace and Azure storage account for you, otherwise work with your Azure Administrator to create these resources. You will use these resources to monitor your v-Core-based Azure Cosmos DB for MongoDB account. +> The *create-azure-resources.ps1* script should have created a Log Analytics workspace and Azure storage account for you, otherwise work with your Azure Administrator to create these resources. You will use these resources to monitor your vCore-based Azure Cosmos DB for MongoDB account. ### Enable diagnostic settings -One you have your Log Analytics workspace and Azure storage account, it's time to enable diagnostic settings for your v-Core-based Azure Cosmos DB for MongoDB account. When you enable diagnostics, allows you to collect logs and metrics from your Cosmos DB account and store them in the Log Analytics workspace. To do enable diagnostics, let's follow these steps: +One you have your Log Analytics workspace and Azure storage account, it's time to enable diagnostic settings for your vCore-based Azure Cosmos DB for MongoDB account. When you enable diagnostics, allows you to collect logs and metrics from your Cosmos DB account and store them in the Log Analytics workspace. To do enable diagnostics, let's follow these steps: 1. Sign in to the [Azure portal](https://portal.azure.com). -1. Navigate to your v-Core-based Azure Cosmos DB for MongoDB account. +1. Navigate to your vCore-based Azure Cosmos DB for MongoDB account. 1. In the left-hand menu, select **Diagnostic settings** under the *Monitoring* section. @@ -148,17 +148,17 @@ One you have your Log Analytics workspace and Azure storage account, it's time t 1. Select **Save** to apply the changes. -Your v-Core-based Azure Cosmos DB for MongoDB account is now configured to send logs and metrics to the Log Analytics workspace and the Azure storage account. To see it in action, let's run some queries against your Cosmos DB account. +Your vCore-based Azure Cosmos DB for MongoDB account is now configured to send logs and metrics to the Log Analytics workspace and the Azure storage account. To see it in action, let's run some queries against your Cosmos DB account. ### Run a simulated workload -To generate some data for your logs and metrics, let's run some queries against your v-Core-based Azure Cosmos DB for MongoDB account. +To generate some data for your logs and metrics, let's run some queries against your vCore-based Azure Cosmos DB for MongoDB account. > [!NOTE] > Make sure you have the necessary Cosmos DB environment variables in your **.env** file before running the workload application. > [!NOTE] -> Make sure you have the v-Core-based Azure Cosmos DB for MongoDB account firewall rules set to allow access from your current public IP address. +> Make sure you have the vCore-based Azure Cosmos DB for MongoDB account firewall rules set to allow access from your current public IP address. 1. Right-click on the **03-manage** folder and select **Open in integrated Terminal**. @@ -198,19 +198,19 @@ You come back a little later to stop the workload. In the meantime, let's review 1. Sign in to the [Azure portal](https://portal.azure.com). -1. Navigate to your v-Core-based Azure Cosmos DB for MongoDB account. +1. Navigate to your vCore-based Azure Cosmos DB for MongoDB account. 1. In the left-hand menu, Under *Monitoring*, select the **Logs** section. -1. In the *Logs* pane, by default, a set of queries already prepared for you're displayed. You can run these queries to view the logs generated by your v-Core-based Azure Cosmos DB for MongoDB account or ***X*** out of the queries and run your own. for now, *let's ***X*** out of the **Queries** dialog*. +1. In the *Logs* pane, by default, a set of queries already prepared for you're displayed. You can run these queries to view the logs generated by your vCore-based Azure Cosmos DB for MongoDB account or ***X*** out of the queries and run your own. for now, *let's ***X*** out of the **Queries** dialog*. 1. Let's get familiar with the **Query** pane. - 1. If you select the Table tab, you can see the different tables that are available to query. In this case, you should see a table called **VCoreMongoRequests** under the *Azure Cosmos DB for MongoDB (vCore)* section. This table contains the logs generated by your v-Core-based Azure Cosmos DB for MongoDB account. + 1. If you select the Table tab, you can see the different tables that are available to query. In this case, you should see a table called **VCoreMongoRequests** under the *Azure Cosmos DB for MongoDB (vCore)* section. This table contains the logs generated by your vCore-based Azure Cosmos DB for MongoDB account. 1. Under the **Queries** tab, you see some sample queries that you can run to view the logs. You can also write your own queries here. 1. On the right-hand side, you're able to write and edit your queries. You can select to **Run**, **Save, and define a **Time range** for your queries. Let's go ahead and write and run some queries. -1. In the *Logs* pane, you can run a query to view the logs generated by your v-Core-based Azure Cosmos DB for MongoDB account. These queries are written in KQL (Kusto Query Language). You can use the **Run** button to run the query and view the results. +1. In the *Logs* pane, you can run a query to view the logs generated by your vCore-based Azure Cosmos DB for MongoDB account. These queries are written in KQL (Kusto Query Language). You can use the **Run** button to run the query and view the results. 1. Let's try the following query to view the number of requests made per minute to your Cosmos DB account over the last 24 hours. Change the local time zone formula to match your local time zone if necessary: @@ -232,7 +232,7 @@ You come back a little later to stop the workload. In the meantime, let's review KQL is a powerful query language allows you to create complex queries to get better insight on your logs. To learn more about running KQL queries, review the [Kusto Query Language (KQL) documentation](https://docs.microsoft.com/en-us/azure/data-explorer/kusto/query/). -There are several ways to monitor your v-Core-based Azure Cosmos DB for MongoDB account, we scratched the surface. You can also use Azure Monitor to create alerts, view metrics, and more. Learn more about [Azure Monitor](https://docs.microsoft.com/en-us/azure/azure-monitor/). +There are several ways to monitor your vCore-based Azure Cosmos DB for MongoDB account, we scratched the surface. You can also use Azure Monitor to create alerts, view metrics, and more. Learn more about [Azure Monitor](https://docs.microsoft.com/en-us/azure/azure-monitor/). ### Create an alert rule @@ -244,7 +244,7 @@ You can also create alerts to notify you when certain conditions are met. For ex 1. On the *Created rule* pane, use the following settings: - 1. **Scope** tab: Select your v-Core-based Azure Cosmos DB for MongoDB account. + 1. **Scope** tab: Select your vCore-based Azure Cosmos DB for MongoDB account. 1. **Condition** tab: 1. Enter the following settings: @@ -304,7 +304,7 @@ Now that you reviewed the logs and created an alert, let's stop the simulated wo 1. Return to the workload application and choose **option 0** to exit the application. -Monitoring and creating alerts for your v-Core-based Azure Cosmos DB for MongoDB account is important to ensure that your application is running smoothly and to identify any potential issues. Monitoring and alerting are integral parts of managing your v-Core-based Azure Cosmos DB for MongoDB account. +Monitoring and creating alerts for your vCore-based Azure Cosmos DB for MongoDB account is important to ensure that your application is running smoothly and to identify any potential issues. Monitoring and alerting are integral parts of managing your vCore-based Azure Cosmos DB for MongoDB account. ## Clean Up @@ -324,4 +324,4 @@ This cleanup process helps maintain your Azure account organized and free from u # Conclusion -In this lab, you learned to manage, scale, monitor, and generate alerts on a v-Core-based Azure Cosmos DB for MongoDB account. You used monitoring tools to track operations and generate alerts. You also learned how to scale your account to handle increased or decreased traffic. You can now apply these skills to your own applications and databases. +In this lab, you learned to manage, scale, monitor, and generate alerts on a vCore-based Azure Cosmos DB for MongoDB account. You used monitoring tools to track operations and generate alerts. You also learned how to scale your account to handle increased or decreased traffic. You can now apply these skills to your own applications and databases. diff --git a/Instructions/04-vector-search.md b/Instructions/04-vector-search.md index 3382cb7..c330749 100644 --- a/Instructions/04-vector-search.md +++ b/Instructions/04-vector-search.md @@ -1,15 +1,15 @@ --- lab: - title: 'Building an AI copilot using v-Core-based Azure Cosmos DB for MongoDB vector search and Azure OpenAI' - module: 'Module 4 - Use Azure AI OpenAI and vector search to create AI copilots with v-Core-based Azure Cosmos DB for MongoDB' + title: 'Building an AI copilot using vCore-based Azure Cosmos DB for MongoDB vector search and Azure OpenAI' + module: 'Module 4 - Use Azure AI OpenAI and vector search to create AI copilots with vCore-based Azure Cosmos DB for MongoDB' --- -In this lab, you use Azure OpenAI to create embeddings for v-Core-based Azure Cosmos DB for MongoDB documents, establishing your AI copilot for advanced data exploration. You build a vector index from these embeddings, allowing you to create vector searches. The vector searches involves generating an embedding for user prompts, using those user prompt embeddings to find similar documents in the database through a vector search, and enhancing the search results deploying an Azure OpenAI GPT-3.5 chat. This process illustrates a Retrieval-Augmented Generation (RAG) approach, mixing AI with database technologies to refine search results and responses. +In this lab, you use Azure OpenAI to create embeddings for vCore-based Azure Cosmos DB for MongoDB documents, establishing your AI copilot for advanced data exploration. You build a vector index from these embeddings, allowing you to create vector searches. The vector searches involves generating an embedding for user prompts, using those user prompt embeddings to find similar documents in the database through a vector search, and enhancing the search results deploying an Azure OpenAI GPT-3.5 chat. This process illustrates a Retrieval-Augmented Generation (RAG) approach, mixing AI with database technologies to refine search results and responses. ### Objectives - Load data from Azure Blob Storage to a local directory. -- Import data into v-Core-based Azure Cosmos DB for MongoDB, generating embeddings for *category* and *name* fields of each product during the process. +- Import data into vCore-based Azure Cosmos DB for MongoDB, generating embeddings for *category* and *name* fields of each product during the process. - Create a Vector index on the generated vector column. - Perform vector searches using prompts and display the closest matching products. - Use GPT-3.5 to enhance vector search results, enabling your AI copilot to provide more detailed insights. @@ -22,7 +22,7 @@ If you need to build your own lab environment, you need the following components - **Visual Studio Code**: Ensure Visual Studio Code is installed on your machine. - **Azure Subscription**: Have access to an Azure Subscription for creating and using the necessary resources: - - **v-Core-based Azure Cosmos DB for MongoDB**: Access to create or use an existing a v-Core-based Azure Cosmos DB for MongoDB account. + - **vCore-based Azure Cosmos DB for MongoDB**: Access to create or use an existing a vCore-based Azure Cosmos DB for MongoDB account. - **Azure OpenAI Account**: Access to create or use an existing Azure OpenAI account. - **Azure OpenAI Deployments**: Access to create deployments for embeddings and completions in your Azure OpenAI account. @@ -38,7 +38,7 @@ If you need to build your own lab environment, you need the following components To support your AI copilot, you need access to the following Azure resources for this lab: -- v-Core-based Azure Cosmos DB for MongoDB account +- vCore-based Azure Cosmos DB for MongoDB account - Azure OpenAI account, including deployments for embeddings and completions You can create these resources via the *Azure portal* or use the ***create-azure-resources.ps1*** PowerShell script with the ***.env** file. Don't use existing production resources for this lab or any lab. @@ -47,9 +47,9 @@ You can create these resources via the *Azure portal* or use the ***create-azure *This file must either be populated manually, or by the create-azure-resources.ps1 script before you can run your application, since it contains the connection information to your Azure resources.* -This file is both used to retrieve and store the necessary environment variables for both the PowerShell script and the vector search application APIs. It's the easiest way to prepopulate your resource information. The file is used to store the environment variables for your v-Core-based Azure Cosmos DB for MongoDB and Azure OpenAI account. +This file is both used to retrieve and store the necessary environment variables for both the PowerShell script and the vector search application APIs. It's the easiest way to prepopulate your resource information. The file is used to store the environment variables for your vCore-based Azure Cosmos DB for MongoDB and Azure OpenAI account. -If you already have an existing Resource Group, a v-Core-based Azure Cosmos DB for MongoDB account, or an Azure OpenAI account that you would like to use, just fill in those values in the .env file and set the skip create option for that resource to **true**. By default, the *create-azure-resources.ps1* script uses this file to retrieve the necessary environment variables. The *create-azure-resources.ps1* script populates the environment variables with default values if not specified in the .env file. +If you already have an existing Resource Group, a vCore-based Azure Cosmos DB for MongoDB account, or an Azure OpenAI account that you would like to use, just fill in those values in the .env file and set the skip create option for that resource to **true**. By default, the *create-azure-resources.ps1* script uses this file to retrieve the necessary environment variables. The *create-azure-resources.ps1* script populates the environment variables with default values if not specified in the .env file. To learn more about the ***.env*** file and its parameters, review the [***.env*** file documentation](./00-env-file.md). @@ -61,7 +61,7 @@ To learn more about the ***.env*** file and its parameters, review the [***.env* If you aren't using existing resources, or you aren't creating them through the Azure portal, this script creates the necessary Azure resources for this lab. It gives you the flexibility to create some or all of the resources required for this lab. You can either run the script as is or modify it to suit your needs. The resources created by the script include: - Resource Group -- v-Core-based Azure Cosmos DB for MongoDB account +- vCore-based Azure Cosmos DB for MongoDB account - Azure OpenAI account - Azure OpenAI deployments for embeddings - Azure OpenAI deployments for completions @@ -92,7 +92,7 @@ To create the necessary Azure resources for this lab: 1. Make sure that the **.env** file is populated with the resource information. > [!NOTE] -> The v-Core-based Azure Cosmos DB for MongoDB account will need a firewall rule to allow access from your current public IP address. If your v-Core-based Azure Cosmos DB for MongoDB account was generated by the *create-azure-resources.ps1* script, it should have created the firewall rule for you. Check the existing firewall rules under the ***Networking*** *Setting* section of the *v-Core-based Azure Cosmos DB for MongoDB Account*. If you are not sure what your current public IP address is, you can use the following command to find out: +> The vCore-based Azure Cosmos DB for MongoDB account will need a firewall rule to allow access from your current public IP address. If your vCore-based Azure Cosmos DB for MongoDB account was generated by the *create-azure-resources.ps1* script, it should have created the firewall rule for you. Check the existing firewall rules under the ***Networking*** *Setting* section of the *vCore-based Azure Cosmos DB for MongoDB Account*. If you are not sure what your current public IP address is, you can use the following command to find out: > ```powershell > Invoke-RestMethod -Uri 'http://ipinfo.io/ip' -Method Get > ``` @@ -722,7 +722,7 @@ After completing the setup and configuration steps, you're now ready to explore > Make sure you have the necessary environment variables in your **.env** file before running the application. > [!NOTE] -> Make sure you have the v-Core-based Azure Cosmos DB for MongoDB account firewall rules set to allow access from your current public IP address. +> Make sure you have the vCore-based Azure Cosmos DB for MongoDB account firewall rules set to allow access from your current public IP address. 1. **Launch the Application**: Navigate to the root directory of your project in the integrated terminal within Visual Studio Code. To start the application, enter the following commands. @@ -785,9 +785,9 @@ After completing the lab exercises, it's important to clean up any resources you 1. **Azure Portal**: Sign in to the [Azure portal](https://portal.azure.com). -1. **Delete Resource Group**: If you created a new resource group for this lab, navigate to *Resource groups*, find your group, and delete it. This action removes all the resources contained within it, including your Azure Cosmos DBv-Core-based Azure Cosmos DB for MongoDB account and any Azure OpenAI resources. +1. **Delete Resource Group**: If you created a new resource group for this lab, navigate to *Resource groups*, find your group, and delete it. This action removes all the resources contained within it, including your Azure Cosmos DBvCore-based Azure Cosmos DB for MongoDB account and any Azure OpenAI resources. -1. **Manually Delete Individual Resources**: If you added resources to an existing group, you need to delete each resource individually. Navigate to each resource created for this lab (for example, v-Core-based Azure Cosmos DB for MongoDB account, Azure OpenAI account) and delete them. +1. **Manually Delete Individual Resources**: If you added resources to an existing group, you need to delete each resource individually. Navigate to each resource created for this lab (for example, vCore-based Azure Cosmos DB for MongoDB account, Azure OpenAI account) and delete them. 1. **Verify Deletion**: Confirm all resources you no longer need were successfully removed and are no longer listed in your Azure portal. @@ -797,6 +797,6 @@ This cleanup process helps maintain your Azure account organized and free from u # Conclusion -In this lab, you employed Azure OpenAI to generate embeddings for v-Core-based Azure Cosmos DB for MongoDB documents and built a vector index for in-depth searches, effectively integrating these tools as your AI copilot. By transforming user prompts into embeddings to search for similar documents in the database, and then enhancing these search outcomes using GPT-3.5 chat from Azure OpenAI, you effectively demonstrated a Retrieval-Augmented Generation (RAG) approach. This step shows how integrating AI with database searches can refine the relevance and depth of query results. +In this lab, you employed Azure OpenAI to generate embeddings for vCore-based Azure Cosmos DB for MongoDB documents and built a vector index for in-depth searches, effectively integrating these tools as your AI copilot. By transforming user prompts into embeddings to search for similar documents in the database, and then enhancing these search outcomes using GPT-3.5 chat from Azure OpenAI, you effectively demonstrated a Retrieval-Augmented Generation (RAG) approach. This step shows how integrating AI with database searches can refine the relevance and depth of query results. This lab not only guided you through the technical steps of implementing vector search and AI enhancements. The lab also illustrated the powerful capabilities of the Retrieval-Augmented Generation (RAG) approach in creating more dynamic, intelligent, and user-friendly data retrieval systems. diff --git a/_config.yml b/_config.yml index d608b1c..edfcad0 100644 --- a/_config.yml +++ b/_config.yml @@ -1,4 +1,4 @@ -title: 'Build an AI copilot with v-Core-based Azure Cosmos DB for MongoDB and Azure OpenAI' +title: 'Build an AI copilot with vCore-based Azure Cosmos DB for MongoDB and Azure OpenAI' remote_theme: MicrosoftLearning/Jekyll-Theme exclude: - readme.md diff --git a/index.md b/index.md index 47bcdd9..58c98fc 100644 --- a/index.md +++ b/index.md @@ -4,7 +4,7 @@ permalink: index.html layout: home --- -This repository contains the hands-on lab exercises for Microsoft course **Build an AI App with v-Core-based Azure Cosmos DB for MongoDB**. The exercises are designed to accompany the learning materials and enable you to practice using the technologies they describe. +This repository contains the hands-on lab exercises for Microsoft course **Build an AI App with vCore-based Azure Cosmos DB for MongoDB**. The exercises are designed to accompany the learning materials and enable you to practice using the technologies they describe. > 📝 To complete these exercises, you’ll require a Microsoft Azure subscription. You can sign up for a free trial at [https://azure.microsoft.com][azure].