azure:virtual_machines

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
azure:virtual_machines [2021/02/11 14:51] – mmuzeazure:virtual_machines [2022/11/09 22:58] (current) – [VM Agents] mmuze
Line 4: Line 4:
   * For multi-tier applications with interdependent VMs be sure to put each tier in its own availability set to ensure that all tiers do not end up in the same fault or update domain.   * For multi-tier applications with interdependent VMs be sure to put each tier in its own availability set to ensure that all tiers do not end up in the same fault or update domain.
   * //Availability zones// are separate data centers with their own power, cooling and networking.   * //Availability zones// are separate data centers with their own power, cooling and networking.
 +
 +====== Bastion ======
 +  * [[https://docs.microsoft.com/en-us/azure/bastion/vnet-peering]]
 +
 +
  
  
 ====== Notes ====== ====== Notes ======
   * What options are there for making a VM accessible from the Internet (e.g. public IP, load-balancer, NAT, etc)?   * What options are there for making a VM accessible from the Internet (e.g. public IP, load-balancer, NAT, etc)?
 +
 +====== VM Agents ======
 +  * Log Analytics agent has been superseded by the Azure Monitor agent. Log Analytics agent was previously known as Microsoft Monitoring Agent and OMS.
  
  
  • azure/virtual_machines.1613055077.txt.gz
  • Last modified: 2021/02/11 14:51
  • by mmuze