agent 1.27 relnotes

Author: Ryan Willis

articles/azure-arc/servers/agent-overview.md

@@ -160,6 +160,7 @@ The Azure Connected Machine agent is designed to manage agent and system resourc
   * The Azure Monitor Agent can use up to 30% of the CPU during normal operations.
   * The Linux OS Update Extension (used by Azure Update Management Center) can use up to 30% of the CPU to patch the server.
   * The Microsoft Defender for Endpoint extension can use up to 30% of the CPU during installation, upgrades, and removal operations.
+  * The Microsoft Sentinel DNS extension can use up to 30% of the CPU to collect logs from DNS servers
 
 ## Instance metadata
 

articles/azure-arc/servers/agent-release-notes-archive.md

@@ -16,6 +16,26 @@ The Azure Connected Machine agent receives improvements on an ongoing basis. Thi
 - Known issues
 - Bug fixes
 
+## Version 1.22 - September 2022
+
+### Known issues
+
+- When connecting a server and specifying multiple tags, the value of the last tag is used for all tags. You will need to fix the tags after onboarding to use the correct values.
+
+### New features
+
+- The default login flow for Windows computers now loads the local web browser to authenticate with Azure Active Directory instead of providing a device code. You can use the `--use-device-code` flag to return to the old behavior or [provide service principal credentials](onboard-service-principal.md) for a non-interactive authentication experience.
+- If the resource group provided to `azcmagent connect` does not exist, the agent will try to create it and continue connecting the server to Azure.
+- Added support for Ubuntu 22.04
+- Added `--no-color` flag for all azcmagent commands to suppress the use of colors in terminals that do not support ANSI codes.
+
+### Fixed
+
+- The agent can now be installed on Red Hat Enterprise Linux 8 servers that have FIPS mode enabled.
+- Agent telemetry is now sent through the proxy server if one is configured.
+- Improved accuracy of network connectivity checks
+- When switching the agent from monitoring mode to full mode, existing restrictions are now retained. Use [azcmagent clear](manage-agent.md#config) to reset individual configuration settings to the default state.
+
 ## Version 1.21 - August 2022
 
 ### New features

articles/azure-arc/servers/agent-release-notes.md

@@ -16,6 +16,17 @@ The Azure Connected Machine agent receives improvements on an ongoing basis. To
 
 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 Arc-enabled servers agent](agent-release-notes-archive.md).
 
+## Version 1.27 - February 2023
+
+### Fixed
+
+- The extension service now correctly restarts when the Azure Connected Machine agent is being upgraded by Update Management Center
+- Resolved issues with the hybrid connectivity component that could result in the "himds" service crashing, the server showing as "disconnected" in Azure, and connectivity issues with Windows Admin Center and SSH
+- Improved handling of resource move scenarios that could impact Windows Admin Center and SSH connectivity
+- Improved reliability when changing the [agent configuration mode](security-overview.md#local-agent-security-controls) from "monitor" mode to "full" mode.
+- Increased the [resource limits](agent-overview.md#agent-resource-governance) for the Microsoft Sentinel DNS extension to improve log collection reliability
+- Tenant IDs are now validated during onboarding for correctness
+
 ## Version 1.26 - January 2023
 
 > [!NOTE]
@@ -75,26 +86,6 @@ This page is updated monthly, so revisit it regularly. If you're looking for ite
 - Improved logging during the installation process.
 - The install script for Windows now saves the MSI to the TEMP directory instead of the current directory.
 
-## Version 1.22 - September 2022
-
-### Known issues
-
-- When connecting a server and specifying multiple tags, the value of the last tag is used for all tags. You will need to fix the tags after onboarding to use the correct values.
-
-### New features
-
-- The default login flow for Windows computers now loads the local web browser to authenticate with Azure Active Directory instead of providing a device code. You can use the `--use-device-code` flag to return to the old behavior or [provide service principal credentials](onboard-service-principal.md) for a non-interactive authentication experience.
-- If the resource group provided to `azcmagent connect` does not exist, the agent will try to create it and continue connecting the server to Azure.
-- Added support for Ubuntu 22.04
-- Added `--no-color` flag for all azcmagent commands to suppress the use of colors in terminals that do not support ANSI codes.
-
-### Fixed
-
-- The agent can now be installed on Red Hat Enterprise Linux 8 servers that have FIPS mode enabled.
-- Agent telemetry is now sent through the proxy server if one is configured.
-- Improved accuracy of network connectivity checks
-- When switching the agent from monitoring mode to full mode, existing restrictions are now retained. Use [azcmagent clear](manage-agent.md#config) to reset individual configuration settings to the default state.
-
 ## Next steps
 
 - Before evaluating or enabling Azure Arc-enabled servers across multiple hybrid machines, review [Connected Machine agent overview](agent-overview.md) to understand requirements, technical details about the agent, and deployment methods.