{"id":81,"date":"2018-10-29T19:10:14","date_gmt":"2018-10-29T18:10:14","guid":{"rendered":"http:\/\/pro.timphaus.de\/?p=81"},"modified":"2019-12-17T17:56:50","modified_gmt":"2019-12-17T16:56:50","slug":"scheduled-start-start-azure-machine","status":"publish","type":"post","link":"https:\/\/dynamiacs.com\/?p=81","title":{"rendered":"Scheduled Start\/Start Azure Machine"},"content":{"rendered":"\n

I think\neveryone has the same problem: the Azure Virtual machines runs overnight where\nnobody is working on it and the costs are growing. <\/p>\n\n\n\n

To reduce\nthe cost for virtual machines in Azure Microsoft Flow can be used to schedule\nthe start\/stop processes of each Virtual Machine or complete resource groups in\nAzure.<\/p>\n\n\n\n

For this\nthere are two setups needed to be setup: Azure Automation Account and the\nFlows.<\/p>\n\n\n\n

Azure Automation Accounts<\/strong><\/p>\n\n\n\n

First\nsteps are done in Azure. In Azure the service “Automation Accounts”\ncan be used for start\/stop processes. <\/p>\n\n\n\n

The\nservice can easily be found by the search function in the top pane.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

In the\nAutomation Accounts a new Account will be created by choosing “+\nADD”. It is necessary to choose the Subscription in which the virtual\nmachines are located. If there are virtual machines in different subscriptions\nfor each subscription an Automation Account is needed.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

In the\nnext window the name of the Account and the used Subscription and resource\ngroup is defined. The Location should be in the location as the subscription is\nand for “create azure run as account” should be Yes.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

After the\naccount is created there the runbooks for start\/stop processes has to be\ndefined. In the Account the runbooks can be find in the details.:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

For this\nprocess the needed templates can be found in the gallery:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

In the\ngallery there are the needed runbooks available: The “Stop Azure V2\nVMs” and the “Start Azure V2 VMs”. Both of them are needed as a\nrunbook in the Automation Account.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The\nFollowing steps are similar to the Stop and the Start Runbook.<\/p>\n\n\n\n

After\nselecting the runbook template this template need to be imported into the\nAutomation Account.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

In the\nnext window the name of the runbook and a description is defined.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The\nimported runbook need to be published to be available. For this the imported\nrunbook has to be edit:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

In the\nedit screen the button “publish” will publish the runbook to be\nactivated.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

These\nsteps are the setup which has to be done before setup the flows. This setup has\nto be done only one time because all of the future VMs in the subscription can\nbe used with this setup.<\/p>\n\n\n\n

Microsoft Flow<\/strong><\/p>\n\n\n\n

After\nthis is finished the setup in Microsoft Flow can be done. For this business\ncase you have to setup only 2 steps for stop and 2 steps for start. These steps\nare 95% similar. Only the runbook name and the recurrence hour are different.<\/p>\n\n\n\n

Here an\noverview of the created flow which is now described how to setup.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Now the\nsteps for stop a machine are described.<\/p>\n\n\n\n

The first\nstep is the trigger for the recurrence so that Flow knows when to run.<\/p>\n\n\n\n

To setup\nthis step there is a connector called “Schedule” and within this\nconnector there is a trigger called “recurrence”.<\/p>\n\n\n\n

In the\ntrigger there is the setup for the time and when the flow has to run. Here in\nthis example the trigger runs once a day at 08:36 in the time zone UTC+01:00.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

There are\nalso options available to use another frequency. If you choose weekly at the\nfrequency you can choose on which weekdays the flow should run.<\/p>\n\n\n\n

At the\nbottom there is a short preview of your setup is shown. <\/p>\n\n\n\n

The next\nstep in this flow is the action to do something. Here the action is an action\nfrom the connector called “Azure Automation”. The action to do is the\n“create Job” action. This action allows flow to create automated job\nin azure. This job is defined through the selected runbook. To setup this the\nnew Action called Azure Automation is created within the flow.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

In this\nsetup the used credentials to allow flow to connect to azure are  selected. The mentioned azure subscription is\nselected. Then the resource group and the account of the needed Automation\nAction can be selected. The needed runbook for the stop process is selected and\nin the fields “VM Name” and “ResourceGroupName” the\ninformation from the virtual machine which is to processed by this flow has to\nentered.<\/p>\n\n\n\n

The same\nsetup but with another runbook has to be done for the start process.<\/p>\n","protected":false},"excerpt":{"rendered":"

I think everyone has the same problem: the Azure Virtual machines runs overnight where nobody is working on it and the costs are growing. To reduce the cost for virtual machines in Azure Microsoft Flow can be used to schedule the start\/stop processes of each Virtual Machine or complete resource groups in Azure. For this…<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_kad_blocks_custom_css":"","_kad_blocks_head_custom_js":"","_kad_blocks_body_custom_js":"","_kad_blocks_footer_custom_js":"","_kadence_starter_templates_imported_post":false,"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","footnotes":""},"categories":[8],"tags":[31,30,32],"class_list":["post-81","post","type-post","status-publish","format-standard","hentry","category-blog","tag-azure-automation","tag-scheduled","tag-virtual-machine"],"taxonomy_info":{"category":[{"value":8,"label":"Blog"}],"post_tag":[{"value":31,"label":"Azure Automation"},{"value":30,"label":"Scheduled"},{"value":32,"label":"Virtual Machine"}]},"featured_image_src_large":false,"author_info":{"display_name":"Jan","author_link":"https:\/\/dynamiacs.com\/?author=2"},"comment_info":0,"category_info":[{"term_id":8,"name":"Blog","slug":"blog","term_group":0,"term_taxonomy_id":8,"taxonomy":"category","description":"","parent":0,"count":38,"filter":"raw","cat_ID":8,"category_count":38,"category_description":"","cat_name":"Blog","category_nicename":"blog","category_parent":0}],"tag_info":[{"term_id":31,"name":"Azure Automation","slug":"azure-automation","term_group":0,"term_taxonomy_id":31,"taxonomy":"post_tag","description":"","parent":0,"count":1,"filter":"raw"},{"term_id":30,"name":"Scheduled","slug":"scheduled","term_group":0,"term_taxonomy_id":30,"taxonomy":"post_tag","description":"","parent":0,"count":1,"filter":"raw"},{"term_id":32,"name":"Virtual Machine","slug":"virtual-machine","term_group":0,"term_taxonomy_id":32,"taxonomy":"post_tag","description":"","parent":0,"count":1,"filter":"raw"}],"_links":{"self":[{"href":"https:\/\/dynamiacs.com\/index.php?rest_route=\/wp\/v2\/posts\/81","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dynamiacs.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dynamiacs.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dynamiacs.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/dynamiacs.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=81"}],"version-history":[{"count":2,"href":"https:\/\/dynamiacs.com\/index.php?rest_route=\/wp\/v2\/posts\/81\/revisions"}],"predecessor-version":[{"id":273,"href":"https:\/\/dynamiacs.com\/index.php?rest_route=\/wp\/v2\/posts\/81\/revisions\/273"}],"wp:attachment":[{"href":"https:\/\/dynamiacs.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=81"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dynamiacs.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=81"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dynamiacs.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=81"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}