Azure DSC node configuration (MOF files) are currently limited to 1 MB in size. This limitation does not allow for significantly detailed or complex configurations.
In my specific scenario, we have several IIS websites in a our web farm and we've hit the limit of how many unique websites we can configure per server because the MOF file is larger than 1 MB. The resulting error is that the MOF cannot be encrypted by Azure DSC Automation.100 votes
Great feedback. We will consider this a bug to be addressed in the future.
I would like to use to Linux configuration by Ansible.22 votes
Thanks for the suggestion. We are exploring options to make the Automation platform extensible.
Say you have a configuration that applies to two servers behind a load balancer and it includes the installation of some software.
You now want to upgrade that software so you update the product ID and link to MSI.
Once the servers pick up the change and attempt to apply it, they could both do it simultaneously causing a system outage.
Having DSC respect Availability Groups and Zones would prevent this happening and allow the use of DSC for automatic upgrades.3 votes
This scenario is already addressed by Azure DevOps environments, however we have not done our part to make sure it is easy to understand how to integrate the two services. We will address this in our documentation.
- Don't see your idea?