microsoftlearning / dp-420-cosmos-db-dev

DP-420: Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB

DP-420: Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB

• Are you a MCT? - Have a look at our GitHub User Guide for MCTs

What are we doing?

• To support this course, we will need to make frequent updates to the course content to keep it current with the Azure services used in the course. We are publishing the lab instructions and lab files on GitHub to allow for open contributions between the course authors and MCTs to keep the content current with changes in the Azure platform.

• We hope that this brings a sense of collaboration to the labs like we've never had before - when Azure changes and you find it first during a live delivery, go ahead and make an enhancement right in the lab source. Help your fellow MCTs.

How should I use these files relative to the released MOC files?

• The instructor handbook and PowerPoints are still going to be your primary source for teaching the course content.

• These files on GitHub are designed to be used in conjunction with the student handbook, but are in GitHub as a central repository so MCTs and course authors can have a shared source for the latest lab files.

• It will be recommended that for every delivery, trainers check GitHub for any changes that may have been made to support the latest Azure services, and get the latest files for their delivery.

What about changes to the student handbook?

• We will review the student handbook on a quarterly basis and update through the normal MOC release channels as needed.

How do I contribute?

• Any MCT can submit a pull request to the code or content in the GitHub repro, Microsoft and the course author will triage and include content and lab code changes as needed.

• You can submit bugs, changes, improvement and ideas. Find a new Azure feature before we have? Submit a new demo!

dp-420-cosmos-db-dev's Issues

Lab 30 : Error in Create Azure Cosmos DB account using Azure CLI

Lab/Demo: 30

Task: Create Azure Cosmos DB account using Azure CLI

Step: 8. Create a new Azure Cosmos DB account using the predefined variables and the following command:

az cosmosdb create --name $accountName --resource-group $resourceGroup

Description of issue
When running the code an error pointing at credential access scope:

Missing file in 17-denormalize lab folder

Module: 08

Lab/Demo: 17-denormalize

Task: Run the change feed sample

Step: 03

Description of issue
When attempting to execute one of the program's options an error occurs:
The type initializer for 'Progfam' threw an exception ... The configuration file 'appSettings.json' was not found and is not optional.
The file is not in the folder.

Screenshot is attached.

Create a provisioned account same database name twice

Module: 02

Lab/Demo: 01

Task: 00

Step: 00

Create a provisioned account

Description of issue

Repro steps:

1. Back in the Data Explorer pane, expand the nothroughputdb database node and then observe the requiredthroughputcontainer container node within the hierarchy.

2. In the Data Explorer pane, expand New Container and then select New Database.

3. In the New Database popup, enter the following values for each setting, and then select OK:

   Setting	Value
   Database id	manualthroughputdb
   Share throughput across containers	Select this option
   Database throughput	Manual
   RU/s	400

4. Back in the Data Explorer pane, expand the manualthroughputdb database node and then observe the childcontainer container node within the hierarchy.

In the New Database popup, enter the following values for each setting, and then select OK:

we have created database manualthroughputdb on step number 16 then again we have to create db with same name on step 19
manualthroughputdb can not be created again

Lab 14 Observation

At the end of Lab 14, I was never able to observe the output showing up in the Logs pane on the Code + Test screen.

However, I was able to go to the Monitor screen, and all the expected output was very clearly logged as expected there.

Lab 16 Observations

Module: 8 – Implement a data modeling and partitioning strategy for Azure Cosmos DB for NoSQL

Lab/Demo: 16 – Measure performance for customer entities

Task: Prepare your development environment

Using student account resp. student-VM.

Generally (and not just this lab) … consider making the data loads more “free tier” friendly.
Otherwise a test/free/demo account would burn thru the given credit (USD 200.- at the time of writing) in no time.

e.g. setting up each container – slowly – with a small bunch of items (5 to 10) in the first attempt and only after this scaling everything up. This should everybody give enough insight what it is about.

Step: 7

The auto-typer does not send a CRLF after the last line (dotnet run --load-data). So if you indeed – as suggested – take a break, you are in for a surprise (as in … coming back and still most of the work to do).

Also loading the data usually fails.
As far as I remember, I ran this lab two to four times … and every single time there has been an issue with the setup of the database and containers.
I got “unavailable due to demand”, “request timed out” … and those are that I can remember.
That said … it would be helpful for the data loader to be able to continue wherever it ran into an issue.
And I am quite sure that at least once already the initialization script init.sh failed.

Lab 21 Observation

In Lab 21, when you are instructed to add two extra read regions, you might add a note stating that the regions need to be located close together geographically. You will get an error if the regions are more than 5000 miles apart. This happened to me initially when I selected US West, US East, and Central Europe regions, and it prevented me from switching to the strong consistency level until I went back and configured regions that were closer together.

Lab 31 Observations

Module: Create resource template for Azure Cosmos DB for NoSQL

all Bicep related course pages

Seems worth mentioning that Account, Database, Container after resource is just a name, not a command or directive.

Lab/Demo: 31

Task: all tasks with code snippets

Consider adding the Type icon (the green T) to the values in the table as well.
Sometimes typing something yourself makes remembering easier (but having an easy way to get to those class names, date values, … would be great).

Task: Create Azure Cosmos DB for NoSQL resources using Azure Resource Manager templates

Step: 22

Consider using a throughput RU/s value other than the default of 400 (e.g. 450, 500, …).

Task: Create Azure Cosmos DB for NoSQL resources using Bicep templates

Step: 3 & 7

The code snippet in step 3 is not az-cli linter friendly.
Running az-cli issues a warning no-loc-expr-outside-params about using resourceGroup().location instead of a parameter.

Step: 14

Consider using a throughput RU/s value other than the default of 400 (e.g. 450, 500, …).
See also Step 22 when using ARM templates

Product.cs does not contain a "tag" property

Module: 05

Lab/Demo: 02 Paginate cross-product query results with the Azure Cosmos DB SQL API SDK

Step: 15

Description of issue

Repro steps:

Product.cs does not contain a "tag" property. However the sql command and the final c# code are referencing the tag property.

public class Product
{
	public string id { get; set; }
	public string categoryId { get; set; }
	public string categoryName { get; set; }
	public string sku { get; set; }
	public string name { get; set; }
	public string description { get; set; }
	public double price { get; set; }
}

SELECT p.name, t.name AS tag FROM products p JOIN t IN p.tags

Lab 28 Role Assignments Issue

Module: DP-420

Lab/Demo: 28

Task: Create an Azure Key Vault and store the Azure Cosmos DB account credentials as a secret

Step: 4 and 5

Description of issue
The instructions for Lab 28 ask to create a key vault in Azure Portal and then navigate to the Secrets page. On the Key vault -> Secrets page, I received the error "The operation is not allowed by RBAC. If role assignments were recently changed, please wait several minutes for role assignments to become effective." If I click Generate/Import, I am allowed to fill out the fields, but clicking Create shows the same error. I am unable to complete the lab without generating the Secret.

I am using account: [email protected]

Lab 17 Issue

If you try and run Lab 17 - Denormalize right after Lab 16, you will run into the following error when executing the "dotnet run" command:

Unhandled exception. Microsoft.Azure.Cosmos.CosmosException : Response status code does not indicate success: Conflict (409); Substatus: 0; ActivityId: 38f1b7a1-3487-4549-b1a6-1356c2b051d4; Reason: (
Errors : [
"Resource with specified id or name already exists."
]

To fix this, you need to first manually delete the CosmosDB database created in Lab 16, so you can recreate it here.

Suggested fix would be to create a difference resource in Lab 17 than "cosmicworks-q46mjbiavkfgg". Each lab should have uniquely named resources.

Lab28 – Secrets placed differently and not viewable for student account

Module: Implement security in Azure Cosmos DB for NoSQL

Lab/Demo: 28

Task: Create an Azure Key Vault and store the Azure Cosmos DB account credentials as a secret

Step: 4

The Secrets are no longer in the Settings section but moved to Objects

Step: 6

Student accounts are not eligible to see secrets (but still can create them somehow) → cannot get the required Secret Identifier for oncoming steps.

Task: Adding the Secret Identifier to your webapp

Step: 4

No can do as I cannot get the Secret Identifier.

Task: Deploy your application to Azure App Services

Step: 13

The deployment cannot commence because “This region has quota of 0 instances for your subscription. Try selecting different region or SKU.” But without knowing, which region does have quotas (for student accounts), this is a game of guessing (my first try was “West US” though).

Task: all

Step: all

Lab time most likely too short to complete the whole lab.

Lab 17 issue redux

So, in #25 it was reported that unless you delete the Lab16 resource group, the deployment fails.

I understand they are meant to be standalone labs, however, as we all have to use subscriptions provided by an ALH (given Azure Passes are no more), the ALHs group these two Module 8 labs together.

To back up what @ejneuman said, can we not have an instruction stating resources need to be cleaned up after / prior lab 16/17 ? Or can ALHs be notified that they need to seperate the lab instances from one another?

Failed to run `az login`

Module: 31

Lab/Demo: 00

Task: 00

Step: 00

https://github.com/microsoftlearning/dp-420-cosmos-db-dev/blob/main/instructions/31-create-container-arm-template.md#create-azure-cosmos-db-sql-api-resources-using-azure-resource-manager-templates

Description of issue

Failed to run az login.

PS C:\Users\Student\dp-420-cosmos-db-dev\31-create-container-arm-template> az login
The default web browser has been opened at https://login.microsoftonline.com/common/oauth2/authorize. Please continue the login in the web browser. If no web browser is available or if the web browser fails to open, use device code flow with `az login --use-device-code`.                                      lease continue the login in t
Certificate verification failed. This typically happens when using Azure CLI behind a proxy that intercw with `az login --use-deviceepts traffic with a self-signed certificate. Please add this certificate to the trusted CA bundle. More info: https://docs.microsoft.com/cli/azure/use-cli-effectively#work-behind-a-proxy. Error detail: HTTPepts traffic with a self-signSConnectionPool(host='login.microsoftonline.com', port=443): Max retries exceeded with url: /common/oau.com/cli/azure/use-cli-effectth2/token (Caused by SSLError(SSLError(1, '[SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:112): Max retries exceeded with 5)')))

Repro steps:

1. Run az login

Note:

I think it is due to an older version of Azure CLI, because the error is resolved by running az upgrade .

PS C:\Users\Student\dp-420-cosmos-db-dev\31-create-container-arm-template> az --version
azure-cli                         2.28.0 *

core                              2.28.0 *
telemetry                          1.0.6

Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\Student\.azure\cliextensions'

Python (Windows) 3.8.9 (tags/v3.8.9:a743f81, Apr  6 2021, 13:22:56) [MSC v.1928 32 bit (Intel)]        

Legal docs and information: aka.ms/AzureCliLegal


You have 2 updates available. Consider updating your CLI installation with 'az upgrade'

Please let us know how we are doing: https://aka.ms/azureclihats
and let us know if you're interested in trying out our newest features: https://aka.ms/CLIUXstudy

Lab 31 : Deploy the Bicep template using the az deployment group create command:

Lab/Demo: 31

Task: Create Azure Cosmos DB for NoSQL resources using Bicep templates

Step: 07 :Deploy the Bicep template using the az deployment group create command:

az deployment group create --name "bicep-deploy-account" --resource-group $resourceGroup --template-file .\deploy.bicep

Description of issue:
When running the code, there is an issue with the account authorization:

Lab 27 Issue - Continuous Backup Option Has Moved

In the Optional section of Lab 27 to enable continuous backup, this feature has moved. It is no longer on the Features screen under Settings. Instead:

Under the Settings section, select Backup & Restore.
Next to Backup policy mode, select (change).
Select Continuous (7 Days).
Click Save.

M:4 - L:06 - T:Connect to the Azure Cosmos DB SQL API account from the SDK S:8

Module: 04

Lab/Demo: Lab 06

Task: Connect to the Azure Cosmos DB SQL API account from the SDK S

Step: 08

Description of issue
Step 8 references the emulator, but the lab is connected to a real CosmosDB account.

"Asynchronously invoke the CreateDatabaseIfNotExistsAsync method of the client variable passing in the name of the new database (cosmicworks) you would like to create within the emulator and storing the result in a variable of type Database:"

"Create a composite index in the indexing policy" not possible with the default cosmos db indexing policy

Module: dp-420-cosmos-db-dev

Lab/Demo: 24-query-optimization.md

Task: Create a composite index in the indexing policy

Description of issue
If I follow the description in the tutorial for "Create a composite index in the indexing policy" I got an error message from the Cosmos DB engine.

Section:

 In the Data Explorer, expand the cosmicworks database node, select the products container node, and then select New SQL Query.

Delete the contents of the editor area.

Create a new SQL query that will order the results by the categoryName in descending order first, and then by the price in ascending order:

SELECT 
    p.name,
    p.categoryName,
    p.price
FROM
    products p
ORDER BY
    p.categoryName DESC,
    p.price ASC
Select Execute Query.

Observe the results and stats of the query. The request unit charge should be pretty high since we do not have a composite index for the multiple order-by expressions.

Repro steps:

1. Follow all described steps to create an azure cosmos db account => database and container
2. Navigate to "In the Data Explorer, expand the cosmicworks database node, select the products container node, and then select New SQL Query."
3. Execute the following query

SELECT 
   p.name,
   p.categoryName,
   p.price
FROM
   products p
ORDER BY
   p.categoryName DESC,
   p.price ASC

Error: "Failed to query item for container products:
Message: {"Errors":["The order by query does not have a corresponding composite index that it can be served from."]}"

Lab 30 Observations

Module: Manage an Azure Cosmos DB for NoSQL solution using DevOps practices

Lab/Demo: 30

Task: generally

Consider upgrading the lab to Azure-Cli 2.49 or later to have auto complete.
Consider making the instructions less PowerShell-y and maybe also add specifics for e.g. Bash, …
Consider using VSCode only when required. This lab does not require it, so a simple PowerShell/(Git)Bash would be sufficient.
Although senior staff might know, one can use PowerShell w/out VSCode, not necessarily everyone does know.

Not a lab issue, yet still worth noting … seems like az-cli updates on Scales aren’t updateable. Tried multiple times to refresh the database/container, but still the changed scaling only was shown after closing the browser (no new login required though).

Task: Create Azure Cosmos DB account using the Azure CLI

Step: 8

Consider using region besides South Central US … whenever I tried something with this region, it usually failed due to high demand (timezone: CET, time frame: 9am-5pm). In my experience West US works almost every single time I request it.

Task: Adjust the throughput of an existing container using the Azure CLI

Step: 6

As per az cosmosdb sql container throughput migrate output, the default maximum throughput is 1,000.

{
  "id": "/subscriptions/92a5590d-8d7f-44d1-9a46-4e7fab67784e/resourceGroups/Cosmoslod37011099/providers/Microsoft.DocumentDB/databaseAccounts/csms2175/sqlDatabases/cosmicworks/containers/products/throughputSettings/default/migrateToAutoscale",  
  "location": null,  
  "name": "mzZM",  
  "resource": {
    "autoscaleSettings": {
      "autoUpgradePolicy": null,
      "maxThroughput": 1000,
      "targetMaxThroughput": null
    },
    "etag": null,
    "instantMaximumThroughput": "10000",
    "minimumThroughput": "1000",
    "offerReplacePending": null,
    "rid": null,
    "softAllowedMaximumThroughput": "1000000",
    "throughput": 100,
    "ts": null
  },
  "resourceGroup": "Cosmoslod37011099",
  "tags": null,
  "type": "Microsoft.DocumentDB/databaseAccounts/sqlDatabases/containers/throughputSettings/migrateToAutoscale"
}

Lab 24 Observation

In two places in this lab the following is stated:

Observe the results and stats of the query. The request unit charge should be lower now that a composite index is in place.

However, in both cases the first time the query was run it failed because of the lack of a supporting composite index. So it's hard to say the charge is lower when you don't actually have a point of reference for that, since no RUs were generated for the failed queries. It seems to me the messaging to consider would be that the query was now successful because the appropriate composite index has been created.

Lab 25: no json sample files provided

Module: 11

Lab/Demo: 1

Task: Run a script to create the containers and the workload

Step: Build and run the project using the dotnet run command

When you run the code on your own machine, targeting your own cosmos db instance, you get an error because it can't find the json files with the sample data.

Repro steps:

1. Follow the steps described in https://github.com/MicrosoftLearning/dp-420-cosmos-db-dev/blob/main/instructions/25-monitor.md
2. Copy the program.cs code (https://github.com/MicrosoftLearning/dp-420-cosmos-db-dev/blob/main/25-monitor/Program.cs) into your own solution and run it.
3. It crashes, because there are no json files.

Environment Setup Issue

In 00-setup-environment, you should also specify to install the Azure CLI from https://learn.microsoft.com/en-us/cli/azure/install-azure-cli-windows?tabs=azure-cli.

This is necessary, for example, in Lab 16 when you need to run the az commands.

Creating new Container Issues - DP-420-Cosmos-DB-Dev

Description of issue:

If a lab is running multiple sets of instructions concurrently (i.e. 06-sdk-crud.md, 07-sdk-batch.md, 08-sdk-bulk.md) the user will run into an issue if the Azure Cosmos DB and container have already been created in an earlier set of instructions. It will give them an error about the resource already existing as the lab instance is still running, and the instructions do not note deleting the resources if doing multiple exercises one after the next.

We've let the class know they'll need to delete the resource before creating another, but could an addition be added to the steps letting the user know they'll need to delete the Cosmos DB before attempting to create another in the following steps?

Fix for Lab 09

When you first open script.cs in Lab 09, you need to run the following terminal commands to make sure the code compiles correctly with the newer version of the framework.

1. dotnet remove package Microsoft.Azure.Cosmos
2. dotnet add package Azure.Cosmos --version 4.0.0-preview3
3. dotnet build

You can then proceed as directed.

Lab 15 Observations

Module: 7 – Integrate Azure Cosmos DB for NoSQL with Azure services

Lab/Demo: 15 – Search data using Azure Cognitive Search and Azure Cosmos DB for NoSQL

Task: Create Azure Cognitive Search resource

Step: 1

Azure Cognitive Search has been renamed to Azure AI Search.
Looking for cognitive search gives Azure Cognitive Search solution for Sentinel as the first result. This is (obviously) not the intended resource.
Only the second result (Azure AI Search) mentions on the card … “formerly Azure Cognitive Search”.

Task: Validate index with example search queries

Generally: as the search field/method has changed, lots of the steps do no longer work.
When I ran first through the labs, I did some digging into the JSON(?) syntax and could make most or even all of the steps work.

Step: 5

No count field.

Step: 7

top is ignored.

Step: 9

Pagination not working.

Step: 11

Price filter not working.

Step: 13

Buckets not working.

LAB Error: Process Azure Cosmos DB for NoSQL data using Azure Functions

Module:

Lab/Demo: Process Azure Cosmos DB for NoSQL data using Azure Functions

Task: Implement function code in .NET

Step: 10

Description of issue
In the Data+Test section of the Function App, the log window is stuck "Connecting to Application Insights"

Typos in instructions for lab 15

Module: 07

Lab/Demo: 15

Task: 00

Step: 00

Description of issue

There are some small typos in the instructions for lab 15 (instructions/15-cognitive-search.md).
For example:

• Line 154: ... can pick right back up form the same ... should be ... can pick right back up from the same ....
• Line 213: ... giving a higher score to results that contains both terms ... should be ... giving a higher score to results that contain both terms ....

Repro steps:

1. Open the instructions for lab 15 (instructions/15-cognitive-search.md).

"Experiencing authentication issues" (various labs - when accessing Data Explorer in particular)

Module: 00

Lab/Demo: 01

Task: 'Use the Data Explorer to create a new database and container'

Step: 01

Description of issue

I'll use Lab 1 as an example, but this seems to occur in various labs after one has successfully created the Azure Cosmos DB, and is then directed to click the 'Data Explorer'. An error like so is popped:

Repro steps:

1. Take the course as written, create Azure Cosmos DB for NoSQL account, access Data Explorer.
2. Regardless of error, it seems to be more of a warning then a blocker....one can apparently nevertheless ignore it and continue the steps to the end successfully.

Troubleshooting:

I have not seen this error before, in this course, or in others - but it appears as if there is something within Data Explorer that would very much like to connect to the Office Admin center and authenticate for some reason. The Azure subscriptions we use would not normally ever have that allowed except insofar as a series might need to utilize Office admin...and if that was the case, a Student would receive an O365 Tenant, and not an Azure sub.

-I tested in a lab both with and without the ACPs used for security, and the behavior is the same even with no ACP restrictions - does not appear related to ACP blocking.

-I tested with several other subscriptions, both Prod and Dev, and received exactly the same error/warning, so it does not appear related to 'misconfiguration' of our normal sub used in this course. (and this course/same sub/same config did not experience this error until some point recently)

Has anyone else seen this behavior, and perhaps can confirm it is an Azure-specific issue?

Module 3 - Connect to Azure Cosmos DB for NoSQL with the SDK' - Stop the Azure Cosmos DB Emulator

Code is not rendering properly at the end of the lab

> 📝 It may take a minute for all instances of the emulator to exit.

Unable to Execute Query

Module: 05

Lab/Demo: 09

Task: 04

Step: 14

Description of issue
Every time I try to run the query the following error appears:

handled exception. System.MissingMethodException: Method not found: 'System.String Microsoft.Azure.Documents.IAuthorizationTokenProvider.GetUserAuthorizationToken(System.String, System.String, System.String, Microsoft.Azure.Documents.Collections.INameValueCollection, Microsoft.Azure.Documents.AuthorizationTokenType, System.String ByRef)'.

Repro steps:

Included the following code with the correct endpoints and keys:

using System;
using Azure.Cosmos;

string endpoint = "";

string key = "";

CosmosClient client = new CosmosClient(endpoint, key);

CosmosDatabase database = await client.CreateDatabaseIfNotExistsAsync("cosmicworks");

CosmosContainer container = await database.CreateContainerIfNotExistsAsync("products", "/categoryId");

string sql = "SELECT * FROM products p";
QueryDefinition query = new (sql);

await foreach (Product product in container.GetItemQueryIterator(query))
{
Console.WriteLine($"[{product.id}]\t{product.name,35}\t{product.price,15:C}");
}

and received an error when I tried to run the application with donet run

Lab 01 Recommended Click Step Change

In Lab 01, I believe the following click step should be changed:

4. In the Select API option pane, select the Create option within the Core (SQL) - Recommended section.

Think this should be:

4. In the Select API option pane, select the Create option within the Azure Cosmos DB for NoSQL section.

Lab 26 Observation

There are three places in this lab where you instruct the user to run the "dotnet run" command from the terminal. However, I would recommend you add a reminder before each of these that they need to save the Program.cs file first.

(There might be other labs where this is also an issue, but it stood out here. Might want to scrub all labs and make sure the user is instructed to save the file before switching to the terminal to run the program.)

Lab 23 Observation

At the very end of this lab, the following statement is made:

Observe the new RU charge in the console output, which should be slightly less than the original charge:

This actually isn't quite accurate. The new RU charge is slightly less than the modified index, and not the original charge. For comparison:

Original: 48.38 RU
Modified Index: 8.38 RU
No Index: 7.05 RU

Lab 14 Observations

Module: 07 – Integrate Azure Cosmos DB for NoSQL with Azure services

Lab/Demo: 14 – Process Azure Cosmos DB for NoSQL data using Azure Functions

Task: Implement function code in .NET

Step: 10

As every other step, mentioning log section ...

• the default log panel is Azure Insight Logs
• with the student account, the Azure Insight Logs panel isn’t available (it keeps connecting and connecting and …)
• with an Azure Demo Account, the Azure Insight Logs is not very helpful, as it does not provide any log output at all

Suggestion: add an info to switch to Filesystem Logs, which are – despite the mentioned restrictions – more helpful.

Step: 11

Compilation fails …

2024-01-30T13:36:06.174 [Information] Script for function 'ItemsListener' changed. Reloading.
2024-01-30T13:36:06.208 [Error] run.csx(1,1): error CS0006: Metadata file 'Microsoft.Azure.DocumentDB.Core' could not be found
2024-01-30T13:36:06.208 [Error] run.csx(5,23): error CS0234: The type or namespace name 'Documents' does not exist in the namespace 'Microsoft.Azure' (are you missing an assembly reference?)
2024-01-30T13:36:06.208 [Error] run.csx(7,38): error CS0246: The type or namespace name 'Document' could not be found (are you missing a using directive or an assembly reference?)
2024-01-30T13:36:06.208 [Error] run.csx(11,13): error CS0246: The type or namespace name 'Document' could not be found (are you missing a using directive or an assembly reference?)
2024-01-30T13:36:06.208 [Information] Compilation failed.

There are resources (Google, Reddit, …) explaining why that happens and how to solve it.
Admittedly, I am not verse enought to understand that all (also it seems to require a local VSCode as well).

Lab 28 Issue

Lab/Demo: 28

Task: Import the multiple missing libraries into the .NET script

Step: 4. Add the [Microsoft.Azure.Services.AppAuthentication][nuget.org/packages/Microsoft.Azure.Services.AppAuthentication] package from NuGet using the following command:

dotnet add package Microsoft.Azure.Services.AppAuthentication

Description of issue
Error : There are no versions available for the package ´Microsoft.Azure.Services.AppAuthentication´.

After that, in the Deploy your application to Azure App Services, on step 17,selecting the folder to deploy, this happens:

Selecting Deploy anyway will result in an error :

Lab 32 Observations

Through some weird quirk of the New Stored Procedure UI, I was unable to save the document if I first typed in the title, and then added the code to the stored procedure. What DID work was to add the code first, and THEN type in the title.

In the final block of code you paste into the stored procedure, you might think about including the comma that needs to be added so it doesn't get missed, like this:

,
(error, newDoc) => {
if (error) throw new Error(error.message);
context.getResponse().setBody(newDoc);
}

Lab 28 Observation

The click steps around "granting our web application an access policy" have changed very slightly.

The Access Polices link isn't in the Settings section any more, but is further up the left nav, in the "Overview" section.

Instead of + Add Access Policy, you click + Create.

Instead of Save, you click Create.

Lab 27 - Issue when trying to restore

Lab/Demo: 27

Task: Restore the database to the point before you deleted the salesOrder document

Step: 1

Description of issue

When opening the Point In Time Restore page, there is an error which stops the student from continuing with the exercise.

Seems to be an account authorization issue.