ained in the previous step: ```sh { "CosmosDb": { "Endpoint": "https:/.documents.azure.com:443/", "TenantId": "", "DatabaseName": "eshop", "ProductsContainerName": "products", "CartsContainerName": "carts", "OrdersContainerName": "orders" }, "AzureBlobStorage": { "AccountName": "" } } ``` 14. Create an app registration in the Azure Portal 15. Create an app secret in the Azure Portal 16. You will need to allow your app to get access to Azure Cosmos DB. Retrieve the 4 ids mentioned below and modify the file "populate/set_rbac.ps1". | Variable | Reference | | ---------------------------- | ------------------------------------------------- | | Subscription Id | Cosmos DB > Overview > Subscription Id | | Azure Cosmos DB account name | cosmos-eastus2-nosql-2 | | Resource group name | Cosmos DB > Overview > Resource group name | | Principal Id | App registration Object Id | ```sh $SubscriptionId = "" # Azure subscription id $AccountName = "" # cosmos db account name $ResourceGroupName = "" # resource group name of the Cosmos DB account $PrincipalId = "" # object id of the app registered in Entra ID ``` 17. Open a Powershell prompt, run Connect-AzAccount and execute ./set_rbac.ps1 ![Cosmos DB - RBAC](assets/cosmos-rbac.png) 18. Allow your app (or virtual machine) to access the storage account - In the Azure portal, goto your storage account - Select Access Control (IAM) in the menu ![Storage - Access Control](assets/storage-access-control.png) - Click on "Add role assignment" - In the filter textbox, type "Storage Blob Data Contributor" ![Storage - Blob Data contributor](assets/storage-blob-data-contributor.png) - Click on "Members" - Select the name of your application ![Storage - Role assignment](assets/storage-role-assignment.png) - Click on the "Select" button - Click on "Review and assign" ![Storage - Role assignment](assets/storage-review.png) 19. Create a container and copy the content of the "azure-storage" folder to your storage account ![Storage - Create container](assets/storage-create-container.png) ![Storage - Upload files](assets/storage-upload-files.png) ![Storage - Files uploaded](assets/storage-files-uploaded.png) 20. Build webapi backend project with dotnet build ```sh cd webapi dotnet build ``` ![Dotnet build](assets/dotnet_build.png) 18. On your secondary region VM (Australia East), modify the .env file with the IP address of the socket server in your primary region (East US 2) ![socket_server_ip](assets/socket_server_ip.png) 19. There is no authentication built into this project. The user email is hard-coded in /nextjs/models/constants.ts. Change it to suit your demo needs ![npm run build](assets/constants_email.png) 19. In mcp-server and nextjs folders, copy .env.template to .env and modify the values to suit your demo needs ```json AZURE_COSMOSDB_NOSQL_ENDPOINT=https://.documents.azure.com:443/ AZURE_COSMOSDB_NOSQL_DATABASE=eshop AZURE_COSMOSDB_NOSQL_PRODUCTS_CONTAINER=products AZURE_COSMOSDB_NOSQL_CARTS_CONTAINER=carts AZURE_COSMOSDB_NOSQL_ORDERS_CONTAINER=orders NEXT_PUBLIC_AZURE_TENANT_ID= NEXT_PUBLIC_AZURE_CLIENT_ID= NEXT_PUBLIC_AZURE_CLIENT_SECRET= NEXT_PUBLIC_AZURE_STORAGE_ACCOUNT_NAME= NEXT_PUBLIC_AZURE_STORAGE_CONTAINER_NAME=img AZURE_OPENAI_ENDPOINT=https://.openai.azure.com/ AZURE_OPENAI_API_KEY= AZURE_OPENAI_EMBEDDING_MODEL=text-embedding-3-small AZURE_OPENAI_API_VERSION=2024-05-01-preview ``` 20. Build nextjs frontend project ```sh cd nextjs npm run build ``` ![npm run build](assets/npm_run_build.png) ## Populate the products catalog In this section, we'll read the products catalog from the populate/catalog.json file and populate the Azure Cosm

#cosmosdb

CosmosDB MCP Server

Azure Cosmos DB MCP CLient & Server

Snippy