Prerequisites for the Global Integration Bootcamp Labs

This page highlights the pre-requisites for the Global Integration Bootcamp. In this document (Labs Setup Guide) you can find comprehensive instructions on how to be totally prepared for all the labs.


The Hands-On Labs for this event have been carefully designed and prepared by the organisers to provide you with an opportunity for first-hand experience with the Microsoft integration toolset, using realistic scenarios.

However, it is impossible for us to provide all participants with an environment in which to do these activities. It is therefore your responsibility to ensure that you have the necessary pre-requisites prepared before you arrive at the event. This includes the steps in all sections of this document excluding the Optional Setups section (which are recommended but not mandatory). If you do not complete these steps in advance of the event, it will be impossible for you to complete the hands-on activities as there simply won’t be enough time or bandwidth.

Minimum Requirements

The minimum requirements to setup and run the labs for this Global Integration Bootcamp event are:

  • An Azure Subscription (MSDN or Trial)

    • Instruction to create Trial Subscription below
  • A developer machine with:

    • Visual Studio 2015 (recommended to have latest updates)
    • Azure .Net SDK (at least 2.9)
  • (For Lab 1) A provisioned instance of API Management Service
  • (For Lab 3) A developer machine with BizTalk Server 2016 installed and configured

    • A Hyper-V virtual machine has been pre-prepared and can be downloaded as described in the Labs Setup Guide; this will save you heaps of time
    • Alternatively, you may choose to setup your own VM, either running in a local virtual machine environment (i.e VMWare) or within Azure.


You may use the BizTalk Server machine for all of the development activity required for all labs. However be aware that installing the Azure Logic Apps Enterprise Integration Tools will prevent any BizTalk applications from being developed on this machine (incompatible project types). In this case, the labs do not require BizTalk application development but be aware for future use.

Table of Requirements

The following table shows the requirements that are necessary to complete each of the labs. In case there are any labs that you prefer to skip, you can ignore the indicated requirements for that lab.

Requirement LAB 1 LAB 2 LAB 3 LAB 4 LAB 5
Azure Subscription
Visual Studio 2015

(Community Edition is fine)

Azure SDK for .NET*  
SQL Server 2016      
BizTalk Server 2016        
Microsoft Azure Logic Apps Enterprise Integration Tools for Visual Studio 2015 2.0*        
Service Bus Explorer*      
Google Chrome Postman      
On-Premises Gateway* (installed and configured as part of Lab 2)        
Legacy Order System database* (imported as part of Lab 2)        
Azure Storage Explorer*        
PowerBI Account        
Device Explorer*        

* These installers may also be retrieved from within the archive that can be downloaded from here.

Naming Conventions

Because so many participants around the globe will be creating the same resources whilst completed the labs, the following naming conventions are suggested to prevent errors due to name clashes:

Resource Suggested Name* Sample
Resource Group gib<loc>17-rgrp-<ini><##> gibmel17-rgrp-pc01
Service Bus gib<loc>17-sbus-<ini><##> gibmel17-sbus-pc01
Storage Account gib<loc>17st<ini><##> gibmel17stpc01
API Management gib<loc>17<ini><##> gibmel17pc01
API App gib<loc>17<ini><##>ordersapi gibmel17pc01ordersapi
Function App gib<loc>17-func-<ini><##> gibmel17-func-pc01
Logic Apps Lab 1 gib<loc>17-logic-<ini><##>-validatemaporder gibmel17-logic-pc01-validatemaporder
Logic Apps Lab 2 gib<loc>17-logic-<ini><##>- storeorderonprem gibmel17-logic-pc01-storeorderonprem
Logic Apps Lab 3 gib<loc>17-logic-<ini><##>-procbusinesscustorder gibmel17-logic-pc01-procbusinesscustorder
IoT Hub gib<loc>17-ioth-<ini><##> gibmel17-ioth-pc01
Document DB gib<loc>17-docdb-<ini><##> gibmel17-docdb-pc01

* Replace <loc> for a 3 char acronym of your location
* Replace <ini> for your 2 initials
* Replace <##> for 2 random numbers for uniqueness

It is also suggested that everything be created under a single resource group (or perhaps on resource group for each lab). The reasoning behind this is that it will be far easier to “clean up” artifacts after the event to save unnecessary charges, as you can delete the entire resource group which deletes everything in it as well.

For instructions on installations and configuration to be prepared for the entire day, please download this document.