Graphical Runbook and Graphical PowerShell Workflow runbooks must be created in Azure Portal. After it is created, it can be exported and imported to another Azure automation account. however, it cannot be edited in any 3rd party tool. This is one of the limitation of graphical runbooks.
Azure Automation is available for Azure Classic portal and now Azure Resource Manager. There are many article you can find on the Internet for Classic portal.
Today I will try to show you how to create an Azure standalone account without linking it to any other management solutions or Azure OMS Log Analytics.
When we create an Azure automation account in ARM (Azure Resource Manager), it automatically will create below:
I think, primarily, I need to explain what is Azure automation and then why we need to use it. Azure automation is an application (SaaS) that we can automate manual tasks, long-running process, or repeated tasks in it. It was designed for Cloud purposes only but right now it can be used in on premise environment too. if it is used properly, it really saves time, money and increase reliability of regular admin tasks.
You may know that there are two type command you can use, Azcopy and Azurecopy. Both can do similar things.
First of all, I would like to start minor example in this article to show you what to do with azcopy.
Microsoft considered the feedback from customers and partners for VMs sizes on Azure that are optimized for larger low latent storage computing power, better price performance for workloads that are storage intensive and require 8 GiB of memory per vCPU. L Series has been designed with this in mind.
There are two level of load balancing available for Azure.
DNS Level; load balancing for traffic to different cloud services located in different datacenters or to different Azure web sites in different data centers or external end points.
Network Level: incoming traffic to a different virtual machines in a cloud services or traffic between VMs in a cloud services or virtual network.
DNS Level is done with Traffic Manager whereas Network level is done with Azure load balancer. Today’s subject is only traffic manager.
Basically, Traffic Manager in Azure allows to control user traffic to different endpoints. That could be cloud services, websites etc… Intelligence policy needs to be applied onto DNS queries in order to operating Traffic Manager.
There are three load balancing methods available to distribute the traffic for Azure Traffic Manager.
Round Robin; it is used for distributing the traffic across a set of VM in same datacenter or across cloud services or websites in different datacenters. The best recommendation for Round Robin is to use it if the VMs are in same datacenter.
Performance; it is recommended for websites in different geographic locations. Traffic Manager considers the location that the request is coming from and it chooses closest endpoint in terms of low latency. The best case scenario for Performance load-balancing is that a website located more than one datacenter in
Failover; That method can be use when a primary site answers all requests and secondary site takes over the control if the primary site is offline.
The basic process is the following:
An Internet client queries a domain name corresponding to a web service.
DNS forwards the name query request to Traffic Manager.
Traffic Manager chooses the next cloud service in the round robin list and sends back the DNS name. The Internet client’s DNS server resolves the name to an IP address and sends it to the Internet client.
The Internet client connects with the cloud service chosen by Traffic Manager.
Primarily, you need to aware that information I will provide below presents current Azure Storage structure. Before Feb 2015, there was only standard storage structure that supports IaaS and PaaS. This standard structure comprises of four different storage types, Blob, Table, Queue, and File. Secondary, since February, Premium Azure storage is also available. This storage much faster than any other standard storage. However, Premium storage is only available in some regions and few type of IaaS servers.