Codemash: Architecting and Building Serverless Solutions in Azure Pre-Compliler

Please read-through and complete this document before our event starts on Tuesday.

Prepare your Environment

Use the information provided on the codemash site to prepare your personal development machine. Note that there may be some issues with using a free Azure account.

There are two other things you will likely need if you are setting up your environment for the first time.

Please make sure you have the .Net Core 3.1 SDK installed on your machine.

Please make sure you have a GitHub account that you can push code to and connect to your Azure account.

If you run into any issues, please reach out directly to Brian via twitter/linked in DM or by email brian at majorguidancesolutions dot com.

Additional Set up and preparation for the event

For this event, we will be working through an official Microsoft Cloud Workshop - the Serverless Architecture MCW.

Complete the Before the hands-on lab setup guide

To get set up for the event, complete the following before the hands-on lab setup guide

For the most part, you will be able to work through this exactly as stated. However, there are a couple of things to be aware of.

Note: Although it is not required and could make life more difficult, I do recommend using your own password for the VM. You can update the VM Password during the Custom Deployment by setting any new value in the Vm Password field. You can also reset this later if you forget the password or have already deployed with the default password. Also, you will likely delete or not use the Lab VM during Codemash as we likely will not have the bandwidth, and should not bog down the network for others.

Deployment Template

The deployment template should take less than 10 minutes to complete, with the majority of that deployment being the lab VM.

Manual Setup

If you want to work through the entire pre-requisite set up manually, instead of deploying the template to get things in your azure subscription, you can walk through each provisioning manually. If you want to take the manual approach, use this document.

If you take this approach, consider not setting up the LabVM and just using your local machine. All of the files for the lab are available in the MCW-Serverless-Architecture GitHub Repo

M365 is not required

The use of M365 is not required. The official documentation will ask that you do that, and you are welcome to do so if you wish (it may have issues if you are on a corporate account).

My personal preference is to use SendGrid and just get a free account there. When we build the logic app you can just use the SendGrid connector, rather than the M365.

Note: Using SendGrid will require you to set up a free account and you should go through the process of validating your sender before the precompiler to ensure you can send emails from a logic app. You will also need to create an API key with SendMail permission (I will demonstrate the logic app and the API Key during our session).

Resource Group Name

The suggested name is hands-on-lab-<suffix>

Instead of using that name, I would recommend something more useful, such as codemash-serverless-precompiler for your resource group. As we will be working in Ohio, I would recommend the East US region, however, any primary region should work for the lab.

Do not plan on using the Lab VM from CodeMash

The deployment for this MCW does give you a developer lab vm that works very well for the MCW. However, we all know that using the conference wi-fi - even in a covid limited attendance - should NOT be counted as possible (even if it will be).

  1. Get the files on your local machine

    Please make sure you set up your machine as above with development tools. Wait for the deployment to complete. When the deployment has completed, Connect to your lab vm and get the files from the lab vm to your local machine.

    Lab files will be located in the directory C:\ServerlessMCW\MCW-Serverless-architecture-main\Hands-on lab.

    You do not need to get any of the other files. In addition to being on the lab vm, all of these files will be located in the MCW-Serverless-architecture GitHub repository hands-on lab -> lab files directory.

  2. Stop/de-allocate or delete the VM

    Having a VM running costs
    $$$. Having it de-allocated costs less $$
    $ but still costs money.

    Once you are confident your deployment has completed and you have the files on your local machine, it is my recommendation that you would de-allocate or delete the Lab VM to avoid paying additional fees for it and/or using up any free credits you might have on your subscription.

Final Note

If you have any questions or problems, or if you cannot get your Azure subscription to work, email me or contact me on twitter and I can help you out so that you will be able to complete the event.

You are ready

You should now be ready for our event.