Morning session
Introduction


Azure structure

MS Account > Mgmt group (optional) > subscription > resource group > resources



Policy - what can be done. Applied at subscription level

RBAC - who can do it. Can be applied at resource group level or resource level.



Multiple subscriptions for one account e.g. different subscription for diff department, training etc. Use management groups to manage this (optional).



Policies can be applied to subscriptions to control what resources can be purchased. This is a new feature. Policies can also be applied to management groups for better scaling.



Create VM will create multiple resources. Use resource groups to manage this. Use this from the get go so over time its easier to manage. E.g. Windows VMs, Linux VMs. Use resource groups for Role based access control. Only win admins can access win environment etc



Essential learning

Resource group

Virtual networks

Storage

Apps

Azure Active directory



Lab preparation (perform for each module)

Add 20533E Environment script

Remove 20533E Environment

East US datacenter (always. Don’t use aus)

VM size - Standard_D1_V2



Module 1
May not be the most cost effective. Initial vs ongoing. Too early to know which is better.



Public cloud - aws etc

Private cloud - your own managed cloud



Cloud services

Software (exchange, sharepoint, office365). Use of app.

Platform - Services (sql, azure AD, ). Management of app.

Infrastructure - VMs, networks. Control of infra/app etc. More control. Cost effective?



IDaaS

DRaaS



Using MS platform to host application.

Platform managed by MS. You manage application. They handle all the patching, OS level. May not be suitable. Alternative is IaaS for app. You get full control over VM.



Platform you only get access to the application itself. Not the OS itself.



Backup every 5 minutes.



Physically compliant with defence standard. Aus government compliant for data.



4 datacenters in aus. Melb, syd and 2 in canberra.



https://azure.microsoft.com/en-au/pricing/calculator/



Answer key is useful if youre struggling with labs. Full details on how to perform the labs.



Tags used for categorizing resources with billing



MS Azure Classic - Outdated information. We use Azure Resource Manager.



New portal is backwards compatible with resources created in old portal. New powershell commands usually have rm in them.



Difference between VPN and ExpressRoute

Does not go over the public internet
Extra cost through service provider


Planning design sequence - Resource groups > VNET > Storage > VM



Afternoon session
Virtual networks
Max 8 nics per VM.



Virtual networks (VNET)- Provides DHCP service. No need for DHCP server.



Azure will reserve first three addresses and the last address. Total of four addresses per subnet.



You can configure the DHCP service but if you have any issues you're on your own.



Resource group does not affect connectivity. More for administration of resources. Must be the same datacentre.



Once you establish a connection. It is very difficult to change the connection config. Workaround is to delete VM (keep hard drive) and assign different network.



The VNET connection for the VM is done during the build process. Used to be optional but any VM must use a



250ish VNET per datacentre



PaaS resources accessed via internet. Publicly accessible.



Service Endpoint is used to connect a PaaS resource to a VNET (e.g. SQL). Reason to use Service Endpoint is to use the Azure backbone. Otherwise goes over the public internet via FQDN. Feature was implemented approx 1 year ago. Similar function to a firewall.



Sql managed instance - https://docs.microsoft.com/en-us/azure/sql-database/sql-database-managed-instance



VM with public address is assigned at the VM NIC level. Still need a VNET. Address is assigned from Microsoft's public address.



The VNETs communicate once you configure Peering. Peering is used to connect resources on different datacenters (Microsoft one in melb and one in syd etc). Connect VNETs using different datacenters.



VMNet connected devices will show NICs not VMs. Deleting the VM will not delete the VM's NIC.  The hard drive is also left intact. IP is linked to the NIC. Unable to release IP until NIC is deleted (Infinite lease).



Configure static IP using Azure portal as opposed to within the OS.



Access control can be done at the VNET level not just at resource group level.



The VM will use the DNS configured on the VNET. You can configure the VM to point at a DC within that VNET. You can configure multiple DHCP addresses.



DC location best practice. Have one as close to VMs as possible. Can be over link but link must be at least T3 (45mbit).



Lookup global vnet peering



Create RG then VNET. VNET goes in a RG.



Sent from Outlook