azure / onboarding-guidance

onboarding-guidance

This GitHub has been replaced by a new landing page for all of the Fast Track for Azure content. The content can be found here FastTrack For Azure GitHub

Consider content on this GitHub repository as old content

Meet the team!

We are a team of dedicated engineers providing customers structured guidance to get started with Azure. We help setup and configure Azure infrastructure as well as provide architecture concepts, best practices and design principles for deploying applications on Azure. Let's get started!!

Set up & configuration of Azure infrastructure

The below onboarding guidance will be applicable across multiple scenarios that leverage Azure infrastructure services. It helps you to provision compute, storage and set up hybrid connectivity.

Table of Contents

Azure 101

• Onboarding Team Introduction ( [ Introduction ] )
• Azure 101 ( Azure Overview )
• Azure Portal 101 ( Azure Portal Walkthrough )

📝 Supporting Resources

Tools Setup

• Tools Introduction ( Introduction )
• Azure Tools Setup ( PowerShell | XplatCLI | CLIv2 )
• Connecting To Azure ( PowerShell | XplatCLI | CLIv2 )
• Setup for Azure Government ( Setup)

📝 Supporting Resources

Storage

• Storage Introduction ( Introduction )
• Azure Resource Group Management ( Portal | PowerShell | XplatCLI | CLIv2 )
• Create a Storage Account ( Portal | PowerShell | XplatCLI | CLIv2 )

📝 Exercises ( PowerShell | XplatCLI | CLIv2 )    📝 Supporting Resources

Compute

• Compute Introduction ( Introduction )
• Find desired image on Azure Marketplace ( Portal | PowerShell | XplatCLI | CLIv2 )
• Create a new VM from Azure Marketplace image ( Portal | PowerShell | XplatCLI | CLIv2 )
• Data disk management ( Portal | PowerShell | XplatCLI | CLIv2 )
• Capture a VM as an Image on Azure ( Portal | PowerShell | XplatCLI | CLIv2 )
• Create a new VM from a captured Image on Azure ( PowerShell | XplatCLI | CLIv2 )
• Upload a supporting OS Image (Syspreped) / OS VHD(Non Syspreped) ( PowerShell | XplatCLI | CLIv2 )

📝 Exercises ( PowerShell | XplatCLI | CLIv2 )    📝 Supporting Resources

Networking

• Azure Networking Introduction ( Portal )
• Create a Virtual Network and Subnet ( Portal | PowerShell | XplatCLI | CLIv2 )
• Create and configure a load balancer ( Portal | PowerShell | XplatCLI | CLIv2 )
• Create and configure Network Security Groups(NSG) ( Portal | PowerShell | XplatCLI | CLIv2 )

  Connectivity

• Create Point to site Connection (On-premises to Azure) ( PowerShell | XplatCLI | CLIv2 )
• Create Site to site Connection (On-premises to Azure) ( PowerShell | XplatCLI | CLIv2 ) *Connect two Virtual Network (Azure to Azure) ( PowerShell | XplatCLI | CLIv2 )

Reference Proof of Concept

• Data Migration to Storage Account (StorageExplorer | PowerShell )
• Deploying Website on Azure IaaS VMs (HTTP | HTTPS)
• Deploying SQL Server on Azure IaaS VMs (Tutorial)

onboarding-guidance's Issues

Does Azure recommend not using standard storage for VMs?

According to - https://github.com/Azure/onboarding-guidance/blob/master/windows/Module%20I/L2-CreateStorageAccount.md

Based on IOPs requirement and stability of the Virtual Machine its recommended to use Premium_LRS.(Standard IOPs)(Premium IOPs).

Which suggests that it is not recommended using standard storage for VMs? I am reasonably sure this isn't the official line from Azure.

It would surely be better to explain the different and let the customer decide what is better, instead of trying to default them to the most costly solution. (the cost of which could easily make them flee to AWS instead!)

Test 1

Test 1

This repo is missing important files

There are important files that Microsoft projects should all have that are not present in this repository. A pull request has been opened to add the missing file(s). When the pr is merged this issue will be closed automatically.

Microsoft teams can learn more about this effort and share feedback within the open source guidance available internally.

Merge this pull request

Badly worded factor in Resource group guidance

A resource can interact with a resource in another resource groups when the two resources are related but they do not share the same lifecycle (for example, a web apps connecting to a database).

If resources are not related can they interact?
If resources do share the same lifecycle can they interact?

As I'm aware there is no restriction on any resource interacting with any other resource that hasn't been specifically configured to do so via security groups