D365 FO Environments Auto start stop

(0) Share

Report

Posted on by vicky1234

Hi,

I have noticed that the D365 FO VMs in LCS if they are configured to auto shutdown then next morning or so a user does not see the start button but a stop button enabled , because of this the user will have to first stop the environment and then start it .

Am I missing any setups here because i should see the start button only when the machine was shut down automatically last night.

Also in case I want to auto start the machine I need to configure a task in azure portal which is very expensive . So is there a way to auto start it without incurring heavy charges.

Thanks,

I have the same question (0)

All responses (9)

Answers (1)

Martin Dráb 237,965 Most Valuable Professional on at

Like (1)

Report

What very expensive charges do you mean regarding automatic start?

Personally I start my VM through command line. I don't always start at the same time, sometimes I'm travelling or so, therefore automatic start at a certain time doesn't work well for me. Starting the VM when it's not needed is when extra costs would occur.

Was this reply helpful? Yes No
nunomaia 25 Moderator on at

Like (1)

Report

When you schedule to automatically shut down a LCS managed virtual Machine in Azure. LCS sometimes don’t recognises that VM’s was shutdown by Azure.

You must press stop and then start to overcome this small glitch. It not a main issue, just press 2 times the button.

Was this reply helpful? Yes No
André Arnaud de Cal... 301,079 Super User 2025 Season 2 on at

Like (1)

Report

Hi Vicky,

The auto-shutdown can be scheduled in the Azure portal. You can also use the Azure portal for automatic or manual startup. You don't necessarily have to go to the LCS environment page and click stop and start.

Was this reply helpful? Yes No
vicky1234 66 on at

Like (0)

Report

Thanks Martin , Nuno and Andre.

I know that I can start and stop from LCS and same from azure portal.

From portal i can even schedule to stop and start.

The point I want to raise is that if I schedule the auto start option in azure portal then does it incur extra cost /charges as it will be using some logic app at the backend.

One of my friend says that it will incur costs and there is no doc to justify it.

Thanks,

VK

Was this reply helpful? Yes No
Suggested answer

Sam N 15 on at

Like (1)

Report

Hi VK,

This automation task that you mention will technically incur costs. Check out this demo Auto Shutdown and Auto Start an Azure VM | Microsoft Docs In the demo video, it shows that the task is billable.

From my reading, the documentation about Automation Tasks states that it costs per Consumption pricing model of Logic Apps

However, this pricing model provides first 4,000 actions are free as a monthly bonus.

Was this reply helpful? Yes No
vicky1234 66 on at

Like (0)

Report

Thanks Sam,

the image is shared is actually from the same video which you have shared.

Is there an alternative to avoid charges and create the startup of the VM ?

Was this reply helpful? Yes No
vicky1234 66 on at

Like (0)

Report

Hi,

So just to understand the pricing section in more detail.
Wrt to the below image from the msdn docs

The CPU and memory value i took from the virtual machine if this is the correct ones.

And based on this criterias the VM will incur me

=730*((8*0.1982)+(56*0.0142))= 1700 $ I am 100% sure this calculation is wrong but i would like to understand what will be the right value.

Will wait for the reply

Was this reply helpful? Yes No
Verified answer

Martin Dráb 237,965 Most Valuable Professional on at

Like (1)

Report

The calculation indeed makes no sense.

The logic apps won't run all the time when your VM is running and they won't consume the same resources that you have dedicated for your VM.

For example, let's say a logic app should start a VM at 7 AM, so it'll run on this schedule, start the VMs and ends. It'll take maybe a few minutes and consume almost no resources. Then the logic app will wait for another day, without doing anything (and you not paying anything).

Start/Stop VMs v2 need a few more resources (such as a storage account), but it's all very cheap.

By the way, you can easily create your own solution, if you wish, such as having an Azure Function running on schedule and start or stop a list of VMs defined in a table.

Was this reply helpful? Yes No
vicky1234 66 on at

Like (0)

Report

Thanks Martin,

The example explains pretty much that very less amount will be required.

I will schedule the task however is there a way that I can calculate the amount to be spent as the I need to share the amount with the client .

Was this reply helpful? Yes No