• Virtual Networks & Subnets
• User Defined Routes & Network Security Groups
• VPN Gateways
• Azure Firewall

Virtual Networks & Subnets

User Defined Routes & Network Security Groups

• Name
• Priority
• Source IP Range
• Source Port
• Target IP Range
• Target Port
• Traffic Direction (Inbound/Outbound)
• Allow/Deny Action

Virtual Private Gateways

• Point to Site - This VPN connection will run through an IPSEC tunnel over the internet. The endpoints will be a software defined VPN connection such as you would install on your laptop and then still connecting to a VPN gateway within Azure. This allows for a dedicated connection to Azure from your external network and is great for allowing your developers or contractors access to Azure when necessary.
• Site to Site - This VPN connection will also run through an IPSEC tunnel over the internet with endpoints being your external network's VPN device and the VPN Gateway within Azure.
• Express Route - This connection runs over a dedicated pair of physical circuits that will connect your external network to Azure. THis can be done through a number of different approaches depending on how your external network is setup and can be implemented using a large list of supported network vendors. See the document list below for more information.

Azure Firewall

• Stateful Service
• Not applied to a single NIC or Subnet
• Highly Available and Scalable based on demand
• All network filtering rules can be applied across multiple subscriptions and virtual networks
• White Listing capabilities for outbound HTTP/S traffic based on FQDN

Conclusion

Additional Resoures

• Azure Virtual Network
• Network Security Groups
• User Defined Routing
• Virtual Private Gateway
• Azure Firewall

• Azure Monitor
  • Activity Log
  • Diagnostics
  • Metrics
  • Network Watcher
  • Alerting
• Application Insights
• Log Analytics
• Azure Advisor
• Azure Security Center

Azure Monitor

Activity Log

Diagnostics & Metrics

Network Watcher

• Network Topology
• Network Performance Monitor
• Connection Monitor
• IP Flow Verify
• Next Hop
• Security Group View
• VPN Diagnostics
• Packet Capture
• Connection Troubleshoot

Alerting

Conclusion

Additional Resources

• Monitoring in Azure
• Activity Log
• Diagnostic Logs
• Metrics
• Network Watcher
• Azure Alerts
• Create and Manage Alerts using Azure Monitor

Serverless computing is a cloud-computing execution model in which the cloud provider acts as the server, dynamically managing the allocation of machine resources. Pricing is based on the actual amount of resources consumed by an application, rather than on pre-purchased units of capacity.

• Resource Organization
• Resource Security
• Auditing
• Cost Controls

Resource Organization

Resource Security

Auditing

Cost Controls

Conclusion

Additional Resources

• Azure Enterprise Scaffolding for Governance
• Resource Management Basics
• Resource Manager Overview

• Azure Activity Log
• Role Based Access Control
• Resource Locks
• Azure Policy
• Azure Cost Management

The Collaborative Approach

• interviews with business owners and key stakeholders to gather requirements
• write everything up into a requirements document
• create the necessary diagrams and mockups
• submit them for approval and review

Getting Started - Conversation Flows

• User Profile Updates
• Predictive Analytics Response
• Knowledge Base Search
• Claim Management System Status Check

Conversation Flow Design

1. I created the first ChatDown file to correspond to the updating of a User's Phone number
2. I converted the first file to a transcript
3. I then taught the tech lead at Genex about the anatomy of the Chatdown file and how the Chatdown tool works
4. I then showed the transcript within the Bot Emulator so that he could see what the conversation would look like
5. I then gave the Tech Lead homework to create the remaining Chatdown files and convert them to transcripts
6. Lastly, the Tech Lead sat down with the business owners and showed them how to use the Bot Emulator to view the transcripts themselves so that they could provide feedback so that changes could be made prior to development

Remaining Conversation Patterns

Conclusion

Additional Tools

• Azure Bot Service Documentation v4 Preview
• Azure Bot Builder Tools
• Azure LuDown
• Azure ChatDown
• Azure QnA Maker
• Azure Bot Emulator

 {
  "name": "MyVnet",
  "type": "Microsoft.Network/networkInterfaces",
  "apiVersion": "2016-09-01",
  ... 
}

resource "azurerm_virtual_network" "vnet1" {
  name                = "MyVnet"
  ... 
}

New-AzureRmResourceGroupDeployment -ResourceGroupName $resourceGroupName -TemplateFile $templateFilePath -TemplateParameterFile $parametersFilePath

• terraform init will prepare the directory, download any listed providers, etc. You run it once in a new Terraform project and then again if anything changes
• terraform plan will show all the changes that potentially will be made if the Terraform is run. It is like doing a test run
• terraform apply does the actual creation or change of the resources
• terraform destroy will delete the resources described in the template files

"parameters": {
    "location": {
      "type": "string",
      "defaultValue": " westeurope",
      "metadata": {
        "description": "Which region to use."
      }
    }
}

variable "location" {
  description = "Which region to use."
  default = "westeurope"
}

"parameters": {
        "location": {
            "value": "centralus"
        }
}

location = "centralus"

"variables": {
    "virtualNetworkName": "[concat(parameters('resourceGroupName'), '-vnet')]"
}

locals {
  virtualNetworkName = "${var.resourceGroupName}-vnet"
}

{
      "name": "[variables('publicIpAddressName')]",
      "type": "Microsoft.Network/publicIpAddresses",
      "apiVersion": "2016-09-01",
      "location": "[parameters('location')]",
      "properties": {
        "publicIpAllocationMethod": "[variables('publicIpAddressType')]"
      }
}

resource "azurerm_public_ip" "basicvm" {
  name                         = "${local.publicIpAddressName}"
  location                     = "${var.resource_group_location}"
  ... 
  public_ip_address_allocation = "${local.publicIpAddressType}"
}

{
      "name": "[variables('networkInterfaceName')]",
      "type": "Microsoft.Network/networkInterfaces",
      "apiVersion": "2016-09-01",
      "location": "[parameters('location')]",
      "dependsOn": [
        "[concat('Microsoft.Network/virtualNetworks/', variables('virtualNetworkName'))]",
        "[concat('Microsoft.Network/publicIpAddresses/', variables('publicIpAddressName'))]",
        "[concat('Microsoft.Network/networkSecurityGroups/', variables('networkSecurityGroupName'))]"
      ],
     "properties": {
        "ipConfigurations": [
          {
            "name": "ipconfig1",
            "properties": {
              "subnet": {
                "id": "[variables('subnetRef')]"
              },
              "privateIPAllocationMethod": "Dynamic",
              "publicIpAddress": {
                "id": "[resourceId(resourceGroup().name,'Microsoft.Network/publicIpAddresses', variables('publicIpAddressName'))]"
              }
            }
          }
        ],
        "networkSecurityGroup": {
          "id": "[resourceId(resourceGroup().name, 'Microsoft.Network/networkSecurityGroups', variables('networkSecurityGroupName'))]"
        }
}

resource "azurerm_network_interface" "basicvm" {
  name                = "${local.networkInterfaceName}"
  location            = "${var.resource_group_location}"
  resource_group_name = "${azurerm_resource_group.basicvm.name}"

  ip_configuration {
    name                          = "ipConfig"
    subnet_id                     = "${azurerm_subnet.basicvm.id}"
    private_ip_address_allocation = "dynamic"
    public_ip_address_id          = "${azurerm_public_ip.basicvm.id}"
  }
}

"variables": {
          "nsg_id": "[resourceId('MyResourceGroup', 'Microsoft.Network/networkSecurityGroups', 'MyNsg')]"
}

data "azurerm_network_security_group" "test" {
  name                = "MyNsg"
  resource_group_name = "MyResourceGroup"
}

output "nsg_id" {
  value = "${data.azurerm_network_security_group.test.id}"
}

terraform init
terraform apply

terraform destroy

Here is the PowerShell to make the change:

$rg = "TestVMSS-RG" #change for your resource group

$VMScaleSetName = "PeteVMSS02" #change for your virtual machine scale set name
$vmss = Get-AzureRMVMss -ResourceGroupName $rg -VMScaleSetName $VMScaleSetName

$vmss.VirtualMachineProfile.LicenseType = "Windows_Server"

Update-AzureRmVmss -ResourceGroupName $rg -VMScaleSetName $VMScaleSetName -VirtualMachineScaleSet $vmss

Update-AzureRmVmssInstance -ResourceGroupName $rg -VMScaleSetName $VMScaleSetName -InstanceId "*"   

Azure Hybrid Benefit

Enterprise Dev/Test or PAYG Dev/Test Subscription

SQL Server Developer Edition

BYOL SQL Server Licenses

Azure Cost Management (Cloudyn)

Azure Advisor

Right-Size/Shut Down/Deallocate VMs

Use Visual Studio Subscrption (MSDN) Keys

Migrate to PaaS Services

Wrap Up