Folder and document names have been updated. Please check your HOL documents for links that use folder names in their path and make sure they are still valid and working.

If you commit and push the git project to github, then you get a storage key in your github public repo

In Exercise 1- Task 2.4 need to change screenshot for Create Function App blade. Now, we have to select Runtime Stack(Language) during create Function App. For TollBoothEvents function need to select Java Script for Runtime Stack.
snag_1dd9e9c5
For the second function TollBoothFunctionApp choose .NET for Runtime Stack option.
In Exercise 3- Task 1: UI for adding Event Grid Trigger is changed. Please add new screenshots.
Also please re-validate the lab and update necessary changes.
Please update the lab guide and let me know when it will be ready.

Files are uploaded to the blob storage but function Process Image is not triggered, I tried to update Microsoft.Azure.Webjobs to version 3.0.0 as documentation indicates, I get this error

Thank you in advance for all your help.

By default when creating a cosmosdb it is required to enable partition. The provided db URI gives the following error. How do I correct this ?
2018-12-31T12:30:53.872 [Error] Critical error: One or more errors occurred.
2018-12-31T12:30:53.872 [Error] Cross partition query is required but disabled. Please set x-ms-documentdb-query-enablecrosspartition to true, specify x-ms-documentdb-partitionkey, or revise your query to avoid this exception.

ActivityId: 5d1538fe-4235-40c0-9700-e7cd4a9f00bf, Microsoft.Azure.Documents.Common/2.1.0.0, Windows/10.0.14393 documentdb-netcore-sdk/1.7.1

Exercise 4:- Task 3 :- step 5
Showing an error , i.e file name "Uploadimage.exe" is missing.
I have attached screenshot for reference

Exercise 2: Task 5: Step 11: The Integration flow is not similar for me as it is in the lab guide. Also there's a warning highlighted in the image below. Not sure why the warning message is there.

Step 12: Not able to add Event Grid Subscription. I tried the way shown in the image below but this also didn't work.

Can you please look into this?

Thanks,
Seerat

Followed exact same steps mentioned on HOL: https://cloudworkshop.blob.core.windows.net/serverless-architecture/Hands-on%20lab/HOL%20step-by-step%20-%20Serverless%20architecture.html#serverless-architecture-hands-on-lab-step-by-**step

Application Map

Cosmos DB

Please create updated HTML documents

This workshop is scheduled for a January 2020 content update. Please review open issue #56 and provide additional recommended changes for SME review.

Needs the updated lab guide. There is lots of update in Azure.
Azure Function integration service is not showing Cosmos DB as an option of +New Output.
See the attached screenshot. Cosmos DB option is not there in the new output section.

https://github.com/Microsoft/MCW-Serverless-architecture/blob/master/Hands-on%20lab/HOL%20step-by-step%20-%20Serverless%20architecture.md#task-3-add-an-azure-cosmos-db-output-to-the-saveplatedata-function

In the Help references section of HOL step-by-step - Serverless architecture.md, the following links are broken:

• Creating a function app (https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-first-azure-function%23create-a-function-app)
• Creating an Azure Cosmos DB account (https://docs.microsoft.com/en-us/azure/cosmos-db/tutorial-develop-sql-api-dotnet%23create-an-azure-cosmos-db-account)

at Task 1: Provision the storage account in section Exercise 1: Azure data, storage, and serverless environment setup the screen caputre of step 4.g. doesn't reassemble the current UI in the Azure Portal anymore. The end user has to select the Hot or Cold tier at a different place than shown in the screen capture.

Student guide dates need updating. Will create and submit pull request.

Hi

The first step is to create a Storage account which require a resource group. But that is not part of the steps.

Thanks to the authors for this intro to Azure serverless architecture.

From a "cloud engineering" perspective, it would be nice to see this setup automated so it could live in a "gitops-spirit" environment.

I will work on this a bit and hope to have a first version by the end of the year.
Never really worked with ARM, so this will take some time.
And it's a sparetime project to me.

Thanks again

Let's add a link to Microsoft/MCW in the related reference like other workshops

Exercise 1 Task 2 while creating the second Function App Lab guide says select java script for Runtime Stack but Currently we see that javascript is not available in Azure Portal, avaiable is only java but if we're selecting java then we're facing issues In Exercise 3 Task 1 Create function to save license plate data to Azure Cosmos DB
Step3 : In the blade menu, select Functions, the click + New Function.

Here we need to create new Function but due to wrong Runtime stack selection while create of second Function App i.e. app whose name ends with Events, we're not able to view the option which is mentioned in Step 4: Enter event grid into the template search form, then select the Azure Event Grid trigger template.

When we're creating the function app with node.js Runtime stack then we're able to create new function as per the instructions mentioned in Step 4: Enter event grid into the template search form, then select the Azure Event Grid trigger template.

@DawnmarieDesJardins Could you please assign this ASAP, as we have a workshop schedued on Aug 15th.

Following needs to be changed:

• Exercise 1 Task 2 while creating the second Function App users should select node.js Runtime stack instead of java/ as javascript is not available in Azure portal.

• Instructions for Create function to save license plate data to Azure Cosmos DB needs additional steps:

• Before Step 4 need instructions as mentioned below:
  4 (a). After clicking on + New Function, select In-Portal then click continue as shown in below image:
  

4 (b). Select More templates

4 (c). Click on Finish and view template

Then users can continue from Step 4 mentioned in lab guide.

Thanks in Advance
Abhishek Pathania

Hi, I am planning to deliver this workshop to one of my customers next week but it seems that some of the instructions and the screenshots are outdated - they no longer reflect what the portal looks like or the steps that need to be followed to accomplish certain tasks. So far I have been able to figure out most tasks but I got stuck on Exercise 2 - Task 5 (Adding EventGrid Subscription to the Function App). Are there any plans to update this workshop soon? Can I get in touch with someone internally (I am MSFT FTE) to get this running in my environment so I can deliver it to my customer next week?

Thank you!

Does anybody know why the ocr is not reading the plate number from the same pics attached to the project files?
all the pictures are moving to NeedsManualReview.

PPT abstract is incorrect

Exercise 1: Task 2: Step 10: Here Version needs to be added as shown below:

Exercise 1: Task 3: Step 4: Now Event Schema is on the separate page from Basics:

Exercise 1: Task 4: Step 3: There are new options available while creating Azure Cosmos DB Account, they are - Apply Free Tier Discount, Account Type and Availability Zones.

Exercise 1: Task 4: Step 7: Indexing is added as shown below:

Exercise 1: Task 4: Step 10 (d): To add throughput firstly you need to check ** Provision dedicated throughput for this container** box and then only you can add throughput.

Exercise 1: Task 6: Step 4: Screenshot needs to be updated.

HOL Unguided - Solution architecture - line 165 in .md is missing alt-text

Exercise 3: Task 4: Step 7: On saving the code it shows the following log.

Exercise 3: Task 5: Step 1: There's no button to Add Event Grid subscription as now we need to do it separately.

Step 2: When tried to separately add Event Grid Subscription, new point is that for:
a. Endpoint Type: Azure Function
b. Endpoint: Click on select endpoint. Now Select Azure Function window will appear, add following configurations there:

• Select your subscription from the drop-down.
• Select you Resource Group serverless-architecture from the drop-down.
• Function App: Select TollBoothFunctionApp from the drop-down.
• Slot: Production
• Function: Select ProcessImage from the drop-down.
• Then select Confirm Selection and Create.

Exercise 4: Task 3: Step 10: Not getting the same output as shown in lab guide for Live Metrics in Application Insights.

Exercise 5: Task 1: No documents fetched under Proccessed and NeedsManualReview collections.

Can you please check?

Thanks,
Seerat

Bullets "Task 2: Finish the ProcessImage function" are out of order.
In addition it sould be added a note clarifying that TODO 5,6,7 will be addressed later in the guide.
Many thanks

1. In Exercise 1- Task 2.4 need to change screenshot for Create Function App blade. Now, we have to select Runtime Stack(Language) during create Function App. For TollBoothEvents function need to select Java Script for Runtime Stack.
   
2. For the second function TollBoothFunctionApp choose .NET for Runtime Stack option.
3. In Exercise 3- Task 1: UI for adding Event Grid Trigger is changed. Please add new screenshots.
4. Also please re-validate the lab and update necessary changes.
5. Please update the lab guide and let me know when it will be ready.

In HOL step-by-step, Task 1: Provision the storage account, step 8:

Select Containers under Blob Service in the menu.

Should be:

Select Browse blobs under Blob Service in the menu.

Currently, the function app project seems a bit old at https://github.com/Microsoft/MCW-Serverless-architecture/tree/master/Hands-on%20lab/starter

If you directly deploy from VS, you will get deployment failure with below detail:
Web deployment task failed. (Web Deploy experienced a connection problem with the server and had to terminate the connection. Contact your server administrator if the problem persists. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_CONNECTION_TERMINATED

How to deploy the function app directly from VS

the project’s with runtime v1, so you’d need to create/deploy to v1 Azure function app. And add the function runtime version in the csproj file:

1. Right click the project and edit the csproj file.
2. Add <AzureFunctionsVersion>v1</AzureFunctionsVersion> under <PropertyGroup>

To enable “Run from package file” option in Publish blade,

1. Right click the project and manage Nuget packages
2. Update Microsoft.NET.Sdk.Functions to latest version (1.0.24).
3. Then you will see “Run from package file” in Publish blade.

Then you'll be able to deploy the project to Azure with “Run from package file” enabled.

On VS Code (Mac) publish didn't work.

1. dotnet restore and dotnet build worked, as well as build from VS Code
2. But deploy didn't work:

3. I also tried from Visual Studio on Mac (not code) but have the same error.

I tried to publish 3 other apps and working ok.

Possible something with path.

When i do as in lab and subscribe savePlateData and queuePlateForManualCheckup, savePlateData documents are not written to cosmos. When i subscribe to all Events it is working. queuePlateForManualCheckup has no problem. But savePlateData event not working.

Followed exact same steps mentioned on HOL: https://cloudworkshop.blob.core.windows.net/serverless-architecture/Hands-on%20lab/HOL%20step-by-step%20-%20Serverless%20architecture.html#serverless-architecture-hands-on-lab-step-by-step

Hands-On Lab Exercise 4: Task 3: Step 13: Not able to run UploadImages project, getting errors+warnings.

Exercise 2->Task 4->Step 7.
uriBase = Environment.GetEnvironmentVariable("computerVisionApiUrl"); is wrong (response is StatusCode: 404: 'Resource Not Found'.)

var uriBase = Environment.GetEnvironmentVariable("computerVisionApiUrl") + "vision/v2.1/ocr";

It should contain also "vision/v2.1/ocr".

This package is scheduled for a November update. Please fork this repo, make your updates, then reference this issue when you submit your pull request.

1. In Exercise 1-Task 1 Issue with Storage name, Storage name have to be in small letters in document you give name as (tollboothstorageINIT).

2. In Exercise 2-Task 4 Issue with File Path, file path sould be clear like this("C:\TollBooth_Clean.zip\MCW-Serverless-architecture-master\Hands-on lab\starter\TollBooth").

Need new MCW headers on all docs please.
Need to rename folders HOL & WDS

Not all images are in the same style, per the Microsoft style guide. Some are "live" and some are clip art.

Having the following error message upon click save instructed by the lab.

There seems to be an issue with the lab. I have tried executing it multiple times and I always end up with an empty "Processed" table - no items at all. Can someone review the steps to make sure nothing is missing and/or ping me internally to discuss this? Thank you.

This MCW is scheduled for content update.
Solliance - please review current content and recommended updates for SME review.

@ZoinerTejada @joelhulen @kylebunting
Solliance team -
This workshop is scheduled for an update in March. Please update this issue with suggested content changes. Once done, we'll assign to our SME team for review and additional feedback.

In the very first step in the pre-requisites it says to build a Storage account with the Blog Type and Hot Tier specified. However, further down it says after copying down the access keys, it says to go to the Containers setting under General Settings, however there is no such place within any of the available Storage Account types. This needs to be resolved before the Ready event coming up.

This should actually be using the "Browse Blobs" settings under the Blobs heading.

Brian

Please add:
Introduction
Update abstracts to reflect new style
Add services/products
Related links (if any)

Hi,
Once I open theTollBooth project within VS , I do not have all the necessary Code to Enter within TODO. For example: What do I enter for databaseMethod.cs? The Code does not seem to work. Can someone Assist?

Regards,
Archana

… which can be fixed by using "https://westeurope.api.cognitive.microsoft.com/vision**/v2.0/ocr**" instead of "https://westeurope.api.cognitive.microsoft.com/vision**/v1.0**" as "computerVisionApiUrl" in Application settings. Seems like Azure Portal shows the wrong endpoint URL... :-)

I recommend the following updates. Please provide feedback on the following:

• Update all images used in the lab to correspond with the latest portal UI changes
• Update NuGet packages and SDKs to latest versions
• Update to Azure Functions 3.x runtime and .NET Core 3.1
• Add GitHub Actions to the WDS and architecture diagram
• Add Durable Functions to WDS and use case scenario

UI needs to be updated for function app publishing from visual studio, UI experience got changed when publishing function app from visual studio.

Ex 3 task 5 step 3 :