OPS705 Lab 1 (2207)

LAB PREPARATION

Purpose / Objectives of Lab 1

In this lab, you will login to Microsoft Azure for the first time, navigate your way to DevTest Labs, and spin up your first VM image. The main purpose of this lab is to ensure you can access your account and familiarize yourself with the Azure user interface.

While you are working through this lab, it is highly recommended that you write notes down in your OPS705 Lab Logbook. These are general notes and commands to help you remember how to do this lab. Each lab has its own page in the logbook. You may use this logbook during all quizzes, so fill it out accordingly!

If you encounter technical issues, please contact your professor via e-mail or in your section's Microsoft Teams group.

Minimum Requirements

Before beginning, you must have:

1. Watched the Week 1 video lecture
2. Read through the Week 1 slides, and have them handy as a reference for concepts
3. Your Seneca Azure login credentials (check your e-mail)
4. Your OPS705 Lab Logbook
5. A mobile device (phone/tablet) to setup 2FA (two-factor authentication)
6. An Internet connection is helpful (If you don't have one... How are you here?)

INVESTIGATION 1: Connecting to Your Azure Account

In this investigation, you'll log in to your Seneca-provided Azure account, and perform some light house-keeping to make future labs easier.

1. Look for an e-mail within your inbox titled Account information for new or modified users from Microsoft. This contains your username and temporary password. Keep this handy in a browser window.
2. In a new browser window, navigate to: https://portal.azure.com
3. Enter the username and password found in your welcome e-mail.
4. On your first login, you'll be asked to change your password. Do so now. It's recommended you use the same password as your normal Seneca account.
5. You'll next be asked to set up two-factor authentication. Do not bypass this step!
6. Once you've set that up, verify it by logging out and logging back in again.
7. Conduct a small celebration (pat on the back, a quick jig, perhaps a fist pump) and move on to Part 2.

INVESTIGATION 2: DevTest Labs

Microsoft Azure's DevTest Labs is where we'll be doing most of our work in this course. In this investigation, you'll get a first look and set it up for easy access.

1. Click on the menu bar icon, and select All Services. (Refer to Figure 1.)
2. In the Search All text box, type DevTest Labs.
3. Click DevTest Labs.
4. Click OPS705-2207-NAA.
5. With this new window (i.e. blade) open, find the push-pin icon next to the title, and click it. This will add it to your Dashboard for easy navigation next time you log in.
6. In the newly-opened Pin to dashboard options window, select Private and My Dashboard, then click Pin.
7. Click on the menu bar icon once again, and select Dashboard.
8. Scroll down to the bottom of your screen, and you should see the new Lab icon. However, at having it way at the bottom isn't very convenient! Let's change that.
9. Towards the top of the screen, look for a option titled Edit. Click that.
10. This now allows you to drag icons around. Move the Lab icon to where you find it most convenient for you.
11. Click Done customizing when finished.
12. At the very top of your screen, find the cog (Settings) icon, and click it.
13. In the new options blade, under Choose your default view, select Dashboard. Now close the options blade by clicking the X icon in the top right.
14. Next time you login, your Dashboard will be the first thing you see. Simply click on the Lab icon and go from there!

INVESTIGATION 3: Testing With a Web App Instance

Now that you're set up with your account in DevTest Labs, it's time to test things out! You'll get a sneak peak at some of the work you'll be doing in this course, as well as ensuring you have full access to the course resources.

1. In the DevTest Labs > OPS705-2207-NAA blade, click on My virtual machines.
2. In this new blade, click the + Add button to create a new item.
3. The Choose a base page comes up. Give it a few moments to fully populate (i.e. load).
4. Select the Web App item.
5. In the configure blade pop-up, in the Environment name text box, enter: yourSenecaUsername-lab1 (substitute yourSenecaUsername with your actual Seneca username)
6. You'll be sent back to the My virtual machines blade, and see a brief notification at the top of your window that your environment is being created. This can take a few minutes. A new notification will appear when creation is complete. It will also be added to your list of virtual machines momentarily.
7. Once creation is complete, you'll see another notification. Otherwise, look for the Status of the new Web App to say Ready.
8. When the app is ready, click on it.
9. In the app's Overview, you'll see a list of resources. Find the one with the type App Service plan and click it.
10. In this new blade, find the App(s) / Slots status in the second column at the top of the Overview tab. Click the '1 / 0 link.
11. Now click on the one instance listed.
12. You should now be in an Overview blade of this instance, with a randomly generated name. Find the URL status and click on the link.
13. A new page will open with the text Hey, App Service Developers!.
14. Test complete! This web page is now accessible anywhere from that URL, and serves as an easy test of your account.

We'll dive into what a Web App is and why you had to click through to many blades to get to the URL in the second half of the course (after Study Week).

Lab Submission

Lab 1's submission is quite simple. Just finish the lab! Your professor will have access to the Web App you created and will verify your work once the due date has passed. Once your lab has been marked, make sure to delete the Web App to not waste funds.