This topic contains 6 replies, has 4 voices, and was last updated by
September 2, 2016 at 1:18 pm #53168ParticipantPoints: 0Rank: Member
Hi is anyone using the "DSC (Pull server) as a service" available in Azure Automation?
I am trying to decide whether we need to setup a DSC pull server in a VM or just use Azure automation.
It seems like azure automation solves a few issues like not having to manage certificates to encrypt credentials etc so I am keen on using it but I am not sure if it can be used across different subscriptions though;for example if I have say 5 azure subscriptions, would I be able to manage VM's spread out in these 5 subscriptions using DSC configured on just 1 Azure automation account?
If I have to create a different automation account for each subscription and upload the same DSC config files into each then that would be an inefficient process.
If anyone has any info I would really appreciate it.
September 6, 2016 at 5:16 pm #53561
Yes you can have one AA account managing VMs across different subscriptions. In fact, you can use that account to manage VMs that are on-premise or in any other cloud such as AWS. You will only need to create one AA account to upload, compile and create your assets. Then you can register all the VMs to this account.
There is one minor difference which is how the VMs are registered/on-boarded. If the VMs are in the same subscription we provide a one click on-boarding experience. If the VMs are on-premises or in any other cloud, you can use a script or manually register the VMs but that should be just a once time thing.
here are some more information: Onboarding machines for management by Azure Automation DSC
September 7, 2016 at 10:31 am #53695ParticipantPoints: 0Rank: Member
great, thanks for the reply WeiJie.
I will then use the DSC saas service rather than building out a pull server on a vm and yes on-boarding on-premise servers is pretty cool so looking forward to doing that as well.
May have more questions as I continue to look around 🙂
September 7, 2016 at 4:03 pm #53753
September 7, 2016 at 4:11 pm #53755
I noticed that you've posted to the above mentioned forum already. Thanks!
October 7, 2016 at 6:13 pm #55088ParticipantPoints: 1Rank: Member
I've been using it for a month now, in combination with scalesets, across different resource groups in different regions, and it works fine. One thing that is not working is communication back from AA to VMSS, so when scaleset scales up and register new VMs in DSC Nodes, and then scale down, VMs stay registered in AA and accrue $6 per month. They are never reused, so number of orphaned DSC nodes will just keep growing....
October 8, 2016 at 11:05 am #55106ParticipantPoints: 0Rank: Member
If you are using VMSS then create Shut Down script to remove this computer from Azure . I did something similar to remove Computer from Octopus Server .
The topic ‘Azure Automation DSC’ is closed to new replies.