Coming soon: guest configuration renames to machine configuration

In this post we will give you additional insight into the name change and a status update on key initiatives.

Since the launch of guest configuration in 2018, the product has been a key piece of many Azure security and Azure governance scenarios. The service enables customers to audit and report on configuration settings inside machines, at cloud scale. This past year, we have been working to support customers more holistically, shipping the public preview of  “Apply and Monitor” and “Apply and Autocorrect” assignment types, and are working hard on the upcoming GA of these capabilities.

We have been listening to our customers as well as the community and are excited to announce a name that highlights the current and future capabilities of our service. Guest configuration will become machine configuration. In addition to the name change, we are moving under the Automanage brand umbrella to reinforce the message that the goal of machine configuration is to reduce op-ex and customer burden in managing their Windows and Linux machines both in Azure and on-premises. It is important to note that the current experience within policy will not change. Customers will still be able to apply machine configurations at scale through policy assignments as they have thus far. 

This rebranding will go live soon in the Azure portal as well as our documentation. More information to come soon about the GA of our enforcement capabilities.