What's new with Azure Connected Machine agent
The Azure Connected Machine agent receives improvements on an ongoing basis. To stay up to date with the most recent developments, this article provides you with information about:
- The latest releases
- Known issues
- Bug fixes
This page is updated monthly, so revisit it regularly. If you're looking for items older than six months, you can find them in archive for What's new with Azure Connected Machine agent.
Warning
Only Connected Machine agent versions within the last 1 year are officially supported by the product group. Customers should update to an agent version within this window.
Version 1.45 - August 2024
Fixed
- Fixed an issue where EnableEnd telemetry would sometimes be sent too soon.
- Added sending a failed timed-out EnableEnd telemetry log if extension takes longer than the allowed time to complete.
New features
- Azure Arc proxy now supports HTTP traffic.
- New proxy.bypass value 'AMA' added to support AMA VM extension proxy bypass.
Version 1.44 - July 2024
Fixed
- Fixed a bug where the service would sometimes reject reports from an upgraded extension if the previous extension was in a failed state.
- Setting OPENSSL_CNF environment at process level to override build openssl.cnf path on Windows.
- Fixed access denied errors in writing configuration files.
- Fixed SYMBIOS GUID related bug with Windows Server 2012 and Windows Server 2012 R2 Extended Security Updates enabled by Azure Arc.
New features
- Extension service enhancements: Added download/validation error details to extension report. Increased unzipped extension package size limit to 1 GB.
- Update of hardwareprofile information to support upcoming Windows Server licensing capabilities.
- Update of the error json output to include more detailed recommended actions for troubleshooting scenarios.
- Block on installation of unsupported operating systems and distribution versions. See Supported operating systems for details.
Note
Azure Connected Machine agent version 1.44 is the last version to officially support Debian 10, Ubuntu 16.04, and Azure Linux (CBL-Mariner) 1.0.
Version 1.43 - June 2024
Fixed
- Fix for OpenSSL Vulnerability for Linux (Upgrading OpenSSL version from 3.0.13 to 3.014)
- Added Server Name Indicator (SNI) to our service calls, fixing Proxy and Firewall scenarios
- Skipped lockdown policy on the downloads directory under Guest Configuration
Version 1.42 - May 2024 (Second Release)
Fixed
- Extensions and machine configuration policies can be used with private endpoints again
Version 1.41 - May 2024
Known issues
Customers using private endpoints with Azure Arc may encounter issues with extension management and machine configuration policies with agent version 1.41. Agent version 1.42 resolves this issue.
New features
- Certificate-based authentication is now supported when using a service principal to connect or disconnect the agent. For more information, see authentication options for the azcmagent CLI.
- azcmagent check now allows you to also check for the endpoints used by the SQL Server enabled by Azure Arc extension using the new
--extensions
flag. This can help you troubleshoot networking issues for both the OS and SQL management components. You can try this out by runningazcmagent check --extensions sql --location eastus
on a server, either before or after it is connected to Azure Arc.
Fixed
- Fixed a memory leak in the Hybrid Instance Metadata service
- Better handling when IPv6 local loopback is disabled
- Improved reliability when upgrading extensions
- Improved reliability when enforcing CPU limits on Linux extensions
- PowerShell telemetry is now disabled by default for the extension manager and policy services
- The extension manager and policy services now support OpenSSL 3
- Colors are now disabled in the onboarding progress bar when the
--no-color
flag is used - Improved detection and reporting for Windows machines that have custom logon as a service rights configured.
- Improved accuracy when obtaining system metadata on Windows:
- VMUUID is now obtained from the Win32 API
- Physical memory is now checked using WMI
- Fixed an issue that could prevent the region selector in the Windows GUI installer from loading
- Fixed permissions issues that could prevent the "himds" service from accessing necessary directories on Windows
Version 1.40 - April 2024
Known issues
The first release of the 1.40 agent may impact SQL Server enabled by Azure Arc when configured with least privileges on Windows servers. The 1.40 agent was re-released to address this problem. To check if your server is affected, run azcmagent show
and locate the agent version number. Agent version 1.40.02664.1629
has the known issue and agent 1.40.02669.1635
fixes it. Download and install the latest version of the agent to restore functionality for SQL Server enabled by Azure Arc.
New features
- Oracle Linux 9 is now a supported operating system
- Customers no longer need to download an intermediate CA certificate for delivery of WS2012/R2 ESUs (Requires April 2024 SSU update)
Fixed
- Improved error handling when a machine configuration policy has an invalid SAS token
- The installation script for Windows now includes a flag to suppress reboots in case any agent executables are in use during an upgrade
- Fixed an issue that could block agent installation or upgrades on Windows when the installer can't change the access control list on the agent's log directories.
- Extension package maximum download size increased to fix access to the latest versions of the Azure Monitor Agent on Azure Arc-enabled servers.
Version 1.39 - March 2024
New features
- Check which extensions are installed and manually remove them with the new azcmagent extension command group. These commands run locally on the machine and work even if a machine has lost its connection to Azure.
- You can now customize the CPU limit applied to the extension manager and machine configuration policy evaluation engine. This might be helpful on small or under-powered VMs where the default resource governance limits can cause extension operations to time out.
Fixed
- Improved reliability of the run command feature with long-running commands
- Removed an unnecessary endpoint from the network connectivity check when onboarding machines via an Azure Arc resource bridge
- Improved heartbeat reliability
- Removed unnecessary dependencies
Version 1.38 - February 2024
Known issues
Windows machines that try and fail to upgrade to version 1.38 manually or via Microsoft Update might not roll back to the previously installed version. As a result, the machine will appear "Disconnected" and won't be manageable from Azure. A new version of 1.38 was released to Microsoft Update and the Microsoft Download Center on March 5, 2024 that resolves this issue.
If your machine was affected by this issue, you can repair the agent by downloading and installing the agent again. The agent will automatically discover the existing configuration and restore connectivity with Azure. You don't need to run azcmagent connect
.
New features
- AlmaLinux 9 is now a supported operating system
Fixed
- The hybrid instance metadata service (HIMDS) now listens on the IPv6 local loopback address (::1)
- Improved logging in the extension manager and policy engine
- Improved reliability when fetching the latest operating system metadata
- Reduced extension manager CPU usage
Next steps
- Before evaluating or enabling Azure Arc-enabled servers across multiple hybrid machines, review Connected Machine agent overview to understand requirements, technical details about the agent, and deployment methods.
- Review the Planning and deployment guide to plan for deploying Azure Arc-enabled servers at any scale and implement centralized management and monitoring.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for