Developer Environment (Java)
In this lab, you will set up an Office365 trial subscription, an Azure trial subscription, configure your Azure subscription for the DevCamp, and provision a virtual machine in the subscription to use for development of further labs.
In this hands-on lab, you will set up an Office365 developer subscription, and Azure trial subscription, and an Azure-based virtual machine for the development environment for subsequent labs in the DevCamp. To expedite the process, we've prepared a Windows image that you will copy into your own environment, start the virtual machine and connect to it. You will then configure the components for Azure development.
- Set up an Office365 trial subscription.
- Set up an Azure trial subscription.
- Configure your Azure subscription for DevCamp.
- Create an Azure Virtual Machine for remote development.
- Connect to the Azure Virtual Machine and configure it for development.
- Review the features of the Azure Portal.
You will need a cell phone and credit card for identity verification.
The credit card will not be charged unless you remove the spending limit on the subscription you will create.
This hands-on-lab has the following exercises:
- Exercise 1: Set up Office 365 trial subscription
- Exercise 2: Set up Azure trial subscription
- Exercise 3: Start your VSTS trial subscription
- Exercise 4: Configure your Azure subscription for DevCamp
- Exercise 5: Use an Azure Virtual Machine for remote development
- Exercise 6: Deploy Shared API application
- Exercise 7: Azure Portal walk-through
- Exercise 8: View the resources you created
Before you start
🔺If you already have an Office 365 subscription, please use an alternate browser or use private mode! This will help avoid any issues with conflicting accounts.
Clear your browsers cache and restart your browser.
Do not skip exercise 1! Even if you already have an Office 365 subscription and address, follow exercise 1 and create a new account.
Use the account created in exercise 1 for all the following exercises and hands-on labs!
To register for a free trial use an e-mail address and a phone number that has not been used for a free trial yet!
In your browser, go to products.office.com/en-us/business/office-365-enterprise-e3-business-software and click the link that says
This will navigate you to this page:
Enter the information requested, and click Next which will take you to the following page:
user idand a
tenant namefor your trial. In this case I chose
devcampross, but you can choose anything you'd like, as long as it is unique. You'll also have to choose a password, and click
Create my account.
Next you will see this page, which asks for phone verification:
After this process is complete, your O365 trial will be set up, and you'll see this page:
Make note of your user id, which will be used to sign onto the Azure portal later.
You're ready to go, which will take you to the following screen:
Click on the
Adminapp icon, which will open the Office365 admin center page in your browser. It will look like this:
If you'd like to see the welcome tour click
Next, or simply close the dialog box.
Stay on this page until the next exercise.
Next, we want to set up an Azure subscription. Go to azure.microsoft.com/en-us/free and click
If the free trial option is not available login to portal.office.com and click
Cost Management + Billing in the menu on the left. This will open the
Cost Management + Billing blade. From the blade's menu select
Subscriptions and click on
New subscription at the top of the blade:
From the list select the
Developer support option to create a Azure trial:
BEGIN Steps for Azure Pass redemption - Follow this step if you are using an Azure Pass. If you are not using an Azure Pass, please skip ahead to END Steps for Azure Pass redemption
Navigate to www.microsoftazurepass.com and sign in. Make sure to clean your browser cache and use a private window! The sign in screen must display the company icon shown on the left side:
Enter the code that is provided by your facilitator into the text box, then click
Claim Promo Code.
END Steps for Azure Pass redemption
After clicking on the
Azure Subscriptionlink you will be taken to the page for creating a new trial subscription:
Enter the requested information and click
Enter the information about you, and verify your identity by phone.
Next, you will need to verify via credit card. Your credit card will not be charged unless you remove the spending cap from your subscription. Supported cards must be either a Credit or Debit card, from vendors Visa, Mastercard, American Express, or Discover.
Finally after the verification process, you'll have to agree to the terms of the trial subscription and click the
It will take a few moments to set up your Azure subscription.
When the subscription set up process is complete, click on
Get started with your Azure subscriptionbutton:
You should now be taken to the Azure Portal where you can explore your new Azure Trial Subscription.
In a future lab we will use Visual Studio Team Services, or "VSTS" for short. In this exercise we will enable a free trial subscription.
In your browser, go to www.visualstudio.com/team-services and click on
Sign inin the upper right corner.
Complete the sign in process if needed, and you should be taken to a screen that looks like this:
Add your name and email address (if not already populated) and click
On the My Benefits screen, click
Use your benefitsunder the heading Visual Studio Dev Essentials.
Acceptbutton to access your Visual Studio Dev Essentials benefits.
Confirmin the modal dialogue.
You have now activated a Visual Studio Team Services Trial Subscription, which will be used in a future lab.
We have created an Azure Resource Group template that will configure the resources you need in Azure for the DevCamp. To deploy these resources in your Azure subscription,
control + clickon the blue Deploy to Azure button below (on a MAC, use
Apple Key + click):
You should see a new tab open in your browser and open the Azure portal, with a blade that looks like this:
Name your resource group
DevCamp, and choose a location for your deployment.
Please do not choose the region West India for your deployment. It is missing a resource that is needed for the labs!
Check the box that indicates you agree to the terms and conditions, and click the
The Resource Group template will start deploying, and the portal may pin a tile to the dashboard showing the status:
It will also be visible in the Notifications dropdown:
This will take approximately 20-30 minutes to complete. Please do not continue on until the template has completed.
In a later session, we will take a look at Azure Resource Group templates, and how to manage your infrastructure the same way you manage your code. As a short introduction, a template is a JSON file that contains definitions for the resources you want in your resource group. When you apply the resource group template, Azure will apply the template to your Azure resource group, and create the resources you have specified in the template. This makes it easy to maintain the infrastructure definition in the JSON text file.
In the resource group template we have created for DevCamp, there are several types of resources including Web Apps and a Virtual Machine. Resource Group Templates are usually fairly quick to apply - the reason this one takes so long is that we are creating a Windows Virtual machine and installing all the tools you will need for the DevCamp including Visual Studio, the Java development kit, and other software resources.
You will know when the Resource Group finishes provisioning either by the Notification drop-down, or by navigation on the left-hand bar to
DevCampand check the
Once the Resource Group creation is done, you can visit the resource group by clicking
Resource Groupson the left navigation pane:
Then click on your Resource group to open it:
The Azure resource group template will have created a virtual machine that can be used for remote development on Windows. Exercise 5 describes the configuration for the Windows virtual machine, which would be appropriate for any of the languages.
In the DevCamp resource group, select the DevCamp DevTest Lab.
Find the Windows virtual machine in your DevTest lab. The name will start with the prefix
Select the machine name and open the virtual machine blade then click
Connectto connect to the machine using Remote Desktop:
This will download a remote desktop connection file, and when you open it, remote desktop on your local machine will attempt to attach to your virtual machine.
When the windows security dialog pops up, the user name
l-adminshould be pre-selected. If not click on the
More choiceslink, then choose
Use a different account.
Use the following credentials to log on to the machine:
User Name =
It would be wise to change the password in the virtual machine.
When remote desktop is connected, you will see server manager initially. We will want to turn of IE enhanced security, to make accessing the web within the virtual machine easier. First click
Then click the
Onnext to IE Enhanced Security Configuration.
A dialog box pops up - choose to turn enhanced security off for administrators.
We are going to use git to clone the DevCamp github repository to this development machine. Click on the Start menu, and type
NOTE: On some high resolution monitors (HIGH DPI), you will notice that the icons and command line windows appear small. If this is an issue, you can download Remote Desktop Connection Manager 2.7.
Change directory to the root using
git clone https://github.com/AzureCAT-GSI/DevCamp.git:
All of the content for this DevCamp will now be located in
Inside your development Virtual Machine, open a NEW command prompt window and execute this command to verify that the node version is v6 or greater:
If the Node version on your machine does not equal v6, we will need to update the version. Open a browser window and go to nodejs.org, and click on the
Other Downloadslink under the current version LTS, you may have to scroll down and click on
Previous Releasesto find v6 or download it directly from here. If a newer version is already installed you have to uninstall it first:
In the next page, click on
Windows Installer (.msi), download the MSI and run the installation.
Please do not skip this step, because we will need node.js to install the Azure cross platform command line interface in the next step.
We will use the Microsoft Azure Cross Platform Command Line to interact with our subscription.
There is a new python-based command line interface in preview - we are not going to use that one. Please follow these instructions to install the node-based command line interface.
If necessary finish the Node installation, then install the Microsoft Azure Cross Platform Command Line by executing in a NEW command prompt window:
npm install azure-cli -g
If you are not developing in Java for the DevCamp, you can skip this step. We have already installed the Java JDK, but we will install gradle and Eclipse. We will be using the gradle build manager - to install that using the chocolatey package manager, open a NEW command window as administrator and type:
choco install -y gradle
Close the command window, open a NEW command window as administrator and also install maven with:
choco install -y maven
Close the command window, open a NEW command window as administrator and go to the root directory using
cd \, and perform these commands in sequence:
refreshenv git clone https://github.com/swagger-api/swagger-codegen.git cd swagger-codegen mvn clean package
Be careful to not upgrade to versions newer than Neon since they no longer support gradle.
Spring Tool Suite is available here:
For example, after downloading the Eclipse installer, run it and you'll get this screen:
Eclipse IDE for Java EE developers. In the next screen, leave the defaults and choose
When that is done, click
LAUNCHto start the IDE and choose a directory for your workspace. You will end up with the initial Eclipse screen:
Helpin the menu bar, and choose
Install New Software...:
In the window that pops up, choose
All Available Sitesfor the
Work withdropdown, type
gradlein the search box, and when the search is complete (which sometimes takes a minute or two - there is a progress bar in the lower left corner of the Eclipse main window), choose
Buildshop: Eclipse Plug-ins for Gradle:
Click through the dialog, install the package and let Eclipse restart.
Install New Software..., and click the
Add..button next to the
Work withdropdown. In the
Add Repositorydialog box, give the repository a name, and type
http://dl.microsoft.com/eclipsefor the Location, and click
This will load a list of available packages. Choose the
Azure Toolkit for Javapackage and the
Team Explorer Everywherepackage in the list, and complete the package installation as before:
If you encounter an error you might have to manually download a previous version of the Scala IDE matching your Eclipse version from http://scala-ide.org/download/prev-stable.html (select the highest available version for matching your Eclipse version). Install it by extracting the zip file. Again select
Install New Software..., and click the
Add..button next to the
Work withdropdown. Select the extracted folder. Now the Scala IDE components will be listed. Select them all and continue the installation.
Also, install the
Spring Tool Suite (STS) for Eclipsepackage by using the menu item
Eclipse Marketplace..., type
Find:box and choose
Go. In the list of packages, scroll down to
Spring Tools (aka Spring IDE and Spring Tool Suite) X.X.X.RELEASEand click
The API application has been prepared for you to be available as a communication partner during different exercises and just needs to be deployed once. It will be first used in the second hands on lab.
Open a browser and navigate to https://portal.azure.com. Locate the app service named
incidentapi...in the resource group blade:
Click on the app service, which will bring up the app service blade. Click on
Browseat the top:
A new browser tab will open.
If the page looks like the image displayed below, this means the API was automatically deployed from GitHub, and you can skip the rest of this exercise.
If the page looks like the image below, continue with this exercise
On the details blade select
If the app deployment is connected, click
Disconnecton the menu bar.
Setupon the menu bar.
Paste the following in the Repository URL field
On your local machine or the virtual machine in Azure, open a browser window and go to the main Azure portal page, http://portal.azure.com. Log in with the credentials you supplied in the subscription sign-up exercise. You should see the Azure portal, similar to this:
There is a lot to notice on this screen. At the upper left corner, the icon under the
Microsoft Azurebanner allows you to shrink and expand the left bar:
Under that, clicking on the
+ Newitem will allow you to create new deployments, virtual machines, databases, etc:
On the left you will see a list of the Azure services that you can use on the left hand side. Notice that this list will scroll up and down to reveal more services, and finally an item that says
More Services >:
You can click on any of these and see what items are deployed, and easily create new deployments.
At the top of the window you have a search box where you can search for any resources:
The bell icon is for notifications, and in this screenshot, it indicates that there are two notifications pending:
Clicking on the bell will show you the notifications:
If you click on one of the notifications, you can go to the details blade that matches the content of the notification, e.g. the details blade of the starting virtual machine.
>_icon opens the Azure Cloud Shell which gives you authenticated shell access to Azure within the browser. It opens at the bottom of the window.
The gear at the top of the screen lets you set the color palate for the portal, whether or not there will be animations, and other options for the portal itself:
The "smiley face" button allows you to send feedback to Microsoft:
Clicking on the icon will give you a form to let us know about your experience:
The Question icon will give you the ability to enter a support case, manage support requests, or get further information on Azure.
Your login name and company name on the upper left hand corner has two functions:
If you hover the mouse over your name, you'll get information about your login, the directory and subscription:
If you click on your name, you can sign out, change your password, view your permissions, and view your bill:
Next we will look at the resource group we set up with the template. Click on
Resource Groupson the left hand side:
Click on the resource group that you created:
A new blade will open with the overview of all of the contents of the resource group listed:
You can click on any of the items on the left hand side which will view or manipulate settings for the resource group as a whole. If you click on any of the individual resources in the center, you will get more information on that resource.
Azure automatically logs changes to resource group and who made those changes. Clicking
Activity logon the left of the blade will allow you to query the log, and clicking on any logged items will give you additional information on that entry:
Automation scriptwill allow you to view, edit or download the resource group template that would create this resource group.
The Windows VM is managed by an Azure DevTest lab named
DevCampwhich handles the startup and shutdown of the machine. To change the start up schedule, click on the DevTest Lab icon and select
Configuration and policiesunder the
Modify the Auto-shutdown schedule based on your time zone.
The Azure portal is currently in a re-designing phase during which the
Auto-Startoption may not be available at all times. Skip the next to steps if it does not show up on the VM's menu.
The machine does not automatically turn on. To enable this, in the Policy Settings blade, select
Change the schedule based on your time zone.
It is particularly useful to create resources in the Azure portal, then save or edit the resource group template. Resource group templates will be explained further in a later lab.
Going back to the list of resources in the resource group
DevCamp, we'll go through the list of each resource, with a description. Feel free to click on the resource and view its detail blade.
Also, our resource group template has added a random string to the end of many of the resources. In this description, we have replaced that string with
adevcamp...- Storage account for storing artifacts for the DevTest labs.
DevCamp- This is the DevTest lab that is used to manage the VM images and artifacts.
DevCamp...- This is the Azure Key Vault that is used to manage secure credentials.
DevCampVnet- This is an Azure Virtual Network, which will allow components of the resource group to communicate as if they were on the same physical network.
dotnetapp...- App service for running the .NET application when deployed to the cloud. If you are not using .NET in the labs, you can safely delete this.
incidentapi...- App service for running the API service that provides a REST API to the web applications.
incidentappplan...- App Service Plan, which defines how the app services in the resource group will be configured.
incidentblobstg...- Storage account for storing the uploaded images and the Azure Queue, from the modern-cloud-apps hands on lab.
incidentcache...- This is the Redis cache that we use from the application to make data access faster. The modern-cloud-apps hands on lab adds support to the application to be able to leverage the cache.
incidentdb...- This is the CosmosDB database that will hold the JSON incident documents stored by the application.
incidentdiagstg...- Storage account for storing diagnostics from the services in the resource group.
javaapp...- App service for running the Java application when deployed to the cloud. If you are not using Java in the labs, you can safely delete this.
nodejsapp...- App service for running the Node.js application when deployed to the cloud. If you are not using Node.js in the labs, you can safely delete this.
In the second resource group
DevCamp-WinDev-..., additional resources were created.
They are all called
WinDev-... but are of different types:
Public IP address- This is a public IP that will allow the Windows development virtual machine to communicate with the Internet (e.g. via Remote Desktop). If you delete the Windows virtual machine, you can safely delete this.
Virtual machine- This is the Windows server virtual machine that we are using as a development machine for these hands-on-labs. You can delete this machine after the developer-environment lab if you are using an on-premises/local machine for development.
Network interface- This is a public network interface that will allow the Windows development virtual machine to communicate on the network. If you delete the Windows virtual machine, you can safely delete this.
Disk- Storage account for storing for VHDs for the machines DevTest labs.
To clean up a Resource Group, we typically simply delete the Resource Group. However, since we are using an Azure DevTest Lab to manage our Virtual Machine, we have an additional step.
Azure DevTest Labs create a series of Resource Locks that prevent accidental deletion of resources. Locks allow us to safeguard against accidental deletion of critical resources, and to delete the Resource Group we first need to delete the locks.
Open your DevCamp Resource Group, and in the navigation pane select Locks. You should see the 3 locks created by the DevTest Lab. To delete, select the three dots to the right of the Notes column, and select Delete.
After all 3 locks have been deleted you are able to delete the resource group. Navigate to the Overview tab and select Delete. The Resource Group will take several minutes to remove, but when finished all resources will no longer accrue charges in your subscription.
In this hands-on lab, you learned how to:
- Set up an Office365 developer subscription.
- Set up an Azure trial subscription allowing you to complete this course free of charge.
- Configure your Azure subscription for DevCamp.
- Create an Azure Virtual Machine for development where you can carry out the following hands on labs.
- Connect to the Azure Virtual Machine and configure it for development.
- Use the Azure portal to view the resources that you created giving you a first overview of the management of Azure resources.
After completing this module, you can continue on to Module 2: Building modern cloud apps.
Java.View Module 2 instructions for
Copyright 2016 Microsoft Corporation. All rights reserved. Except where otherwise noted, these materials are licensed under the terms of the MIT License. You may use them according to the license as is most appropriate for your project. The terms of this license can be found at https://opensource.org/licenses/MIT.