Auto Shutdown and Auto Start an Azure VM ||azure tutorial for beginners

||#microsoftazuretraining
#exam #azureservices #microsoft #ms
#azure ||#microsoftazure ||#azuretutorials
How to Automate Azure VM Shutdown & Start during off hours to reduce costs |VM Auto Start OFF| 2023?
Auto Start/Stop of Azure VM || Step-by-step with troubleshooting the issue
Automate VMs with Azure Logic Apps | Auto-Start & Auto-Shutdown Made Easy!
Azure automation tasks-
In this video, we are going to have a look at how you can automatically start and stop an Azure VM using automation tasks. With automation tasks, Azure offers a simple way to manage a specific resource or resource group using automation task templates. This can be especially helpful if you are trying to reduce the cost of your Azure VMs.
You can automate the process of starting and stopping Azure Virtual Machines (VMs) using several Azure services and tools, including Azure Automation, Azure Logic Apps, and Azure Functions. Here's a high-level overview of how you can achieve this automation:
Here We follow Azure Logic App
Azure Logic Apps:
Azure Logic Apps enable you to create workflows that integrate with various Azure services, including VMs.
Create a Logic App: Create a new Logic App in the Azure portal.
Add Triggers: Set up triggers to start and stop VMs. You can use the "Recurrence" trigger to schedule these actions.
Add Actions: Add actions to start and stop VMs. You can use the Azure Resource Manager connectors to interact with VMs.
Authentication: Ensure that the Logic App has the necessary permissions to manage VMs.
by
Jojo Paul

[@Joyroute-jojo]

Azure provides a way to schedule the automatic shutdown and startup of VMs which can help manage costs effectively. For automatic shutdown, you can use the built-in feature in the Azure portal that allows you to set a specific time for the VM to shut down daily.
For automatic startup, while there isn’t a built-in feature like auto-shutdown, you can achieve this by using Azure Automation or Logic Apps. Azure Automation can be used to create runbooks that start and stop VMs on a schedule. However, please note that while Azure Automation itself is free, you may incur charges for the resources it consumes.
The auto start of an Azure VM does attract some cost, but it’s generally minimal. Here are the areas where you might incur costs:
Storage: The Start/Stop VM function should need less than 1GiB, so the monthly storage costs with Azure Files Pricing will be less than $1.
Networking: The transferred data size is low for this function, so the monthly networking costs with Azure Bandwidth Pricing will also be less than $11.
Application Insights: This is part of Azure Monitor, and there might be some costs associated with it.
However, these costs are typically much lower than the cost of running a VM 24/7. By starting and stopping VMs based on your usage patterns, you can significantly reduce your overall Azure costs.

[@bullyellis1]

Thank you so much for posting this video! Well explained, right to the point. This was a real gem.

[@Joyroute-jojo]

You're very welcome!

[@manojpdq]

Thanks for this well explained video. Just have a doubt. Can we do the same activity using Azure autonomation account and runbooks? What is the difference?

[@Joyroute-jojo]

The main difference . It is easy . No much confusion. All settings given directly.

[@manojpdq]

@@Joyroute-jojo Thanks for your reply. I tried your steps. But it didn't fire. After many search in google, it looks like the issue with API connections of office365. The error shown as Test connection failed. Error 'REST API is not yet supported for this mailbox. This error can occur for sandbox (test) accounts or for accounts that are on a dedicated (on-premise) mail server.' Unable to fix this one.

[@Tim4976_]

Hi thank you for this video. Just wondering why powering off VM will not help reduce the cost - at 2:14 ? Can you please explain? I am only doing powering off task but not Deallocate VM task. So is this not enough to reduce cost?

[@Joyroute-jojo]

you have to deallocate to reduce the cost

[@Joyroute-jojo]

Difference between powering off and deallocating a virtual machine (VM) in the context of Microsoft Azure:
Power Off:
When you power off a VM, it means that the operating system within the VM is shut down. This typically occurs when an administrator initiates a shutdown.
In this state, the VM’s processes are halted, but the allocated hardware (including IP addresses) remains reserved.
You are still billed for the VM while it is in the “Stopped” state.
Essentially, the VM is like a computer that is turned off but still plugged into the wall.
If you find the VM in the Azure console, its state will be listed as “Stopped.”
Deallocated:
When you deallocate a VM through Azure (using the Azure portal, PowerShell, or Azure CLI), it enters a state called “Stopped (deallocated).”
In this state:
Any non-static public IPs associated with the VM are released.
You stop paying for the VM’s compute costs.
It’s a great way to save money on your Azure costs when you don’t need the VMs running.
The VM’s underlying hardware lease is released, making it available for other customers.
The VM resource is not billed while in the “Deallocated” state.
In summary, powering off keeps the hardware reserved (and you continue to be billed), while deallocating releases the hardware and stops the billing for compute costs.

[@acarmichael2000]

I wish this was available in azure gov. Nice vid though for commercial, thnanks.

[@Joyroute-jojo]

You're welcome! . kindly subscribe and support ..

[@rajashekherc131]

As it is linked to logic apps and has billing affected, can we anyhow have any free scheduler from platform level

[@Joyroute-jojo]

For automatic shutdown, you can use the built-in feature in the Azure portal that allows you to set a specific time for the VM to shut down daily
As per my understanding .
For automatic startup, while there isn’t a built-in feature like auto-shutdown, you can achieve this by using Azure Automation or Logic Apps
Yes, the auto start of an Azure VM does attract some cost, but it’s generally minimal. Here are the areas where you might incur costs:
Storage:
The Start/Stop VM function should need less than 1GiB, so the monthly storage costs with Azure Files Pricing will be less than $1.
Networking:
The transferred data size is low for this function, so the monthly networking costs with Azure Bandwidth Pricing will also be less than $1.
Application Insights:
This is part of Azure Monitor, and there might be some costs associated with it.
However, these costs are typically much lower than the cost of running a VM 24/7. By starting and stopping VMs based on your usage patterns, you can significantly reduce your overall Azure costs.

[@rosamarialagunes3214]

this configuration has an additional cost as runbooks in automation account?

[@Joyroute-jojo]

OK .

[@sivabalasankar]

is we can stop and start right?, i didn't get the mail while start and stop

[@Joyroute-jojo]

It works . please recheck the configuration

[@SivabalasankarA]

@@Joyroute-jojo yeah right, thanks a lot one doubt i want to add rule to stop and start daily for everyday what is the interval and frequency i need to give and also vm need to run mon to friday what i need to give in ffrequency
pleae help me bro

[@dtrannet]

pls explain the Interval in details

[@Joyroute-jojo]

I will do a video On this topic soon .

[@rokos3701]

Promo`SM ☝️

[@Joyroute-jojo]

yes

[@eyecatcheramit]

You made it look too simple

[@Joyroute-jojo]

thank you