Skip to content

Commit fda66c8

Browse files
authored
Merge branch 'MicrosoftDocs:main' into Concepts-Network-Fabric-OptionA-OptionB
2 parents 15d20e9 + ecc3621 commit fda66c8

File tree

238 files changed

+878
-1063
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

238 files changed

+878
-1063
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5244,6 +5244,11 @@
52445244
"redirect_url": "/azure/virtual-wan/virtual-wan-about",
52455245
"redirect_document_id": false
52465246
},
5247+
{
5248+
"source_path_from_root": "/articles/virtual-wan/openvpn-azure-ad-client.md",
5249+
"redirect_url": "/azure/virtual-wan/point-to-site-entra-vpn-client-windows",
5250+
"redirect_document_id": false
5251+
},
52475252
{
52485253
"source_path_from_root": "/articles/virtual-wan/high-availability-vpn-client.md",
52495254
"redirect_url": "/azure/virtual-wan/global-hub-profile",
4.69 KB
Loading
-1.99 KB
Loading
-3.33 KB
Loading
-10.3 KB
Loading
23.9 KB
Loading
-36.1 KB
Loading

articles/automanage/arm-deploy.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,10 @@ ms.date: 12/10/2021
1010
# Onboard a machine to Automanage with an Azure Resource Manager (ARM) template
1111

1212
> [!CAUTION]
13-
> On 31 August 2024, both Automation Update Management and the Log Analytics agent it uses will be retired. Migrate to Azure Update Manager before that. Refer to guidance on migrating to Azure Update Manager [here](/azure/update-manager/guidance-migration-automation-update-management-azure-update-manager?WT.mc_id=Portal-Microsoft_Azure_Automation). [Migrate Now](https://portal.azure.com/).
13+
> On September 30, 2027, the Azure Automanage Best Practices service will be retired. As a result, attempting to create a new configuration profile or onboarding a new subscription to the service will result in an error. Learn more [here](https://aka.ms/automanagemigration/) about how to migrate to Azure Policy before that date.
14+
15+
> [!CAUTION]
16+
> Starting February 1st 2025, Azure Automanage will begin rolling out changes to halt support and enforcement for all services dependent on the deprecated Microsoft Monitoring Agent (MMA). To continue using Change Tracking and Management, VM Insights, Update Management, and Azure Automation, [migrate to the new Azure Monitor Agent (AMA)][01].
1417
1518
## Overview
1619
Follow the steps to onboard a machine to Automanage Best Practices using an ARM template.
@@ -65,3 +68,7 @@ As with any ARM template, it's possible to factor out the parameters into a sepa
6568

6669
## Next steps
6770
Learn more about Automanage for [Linux](./automanage-linux.md) and [Windows](./automanage-windows-server.md)
71+
72+
<!-- Link reference definitions -->
73+
[01]: https://aka.ms/mma-to-ama
74+

articles/automanage/automanage-account.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,10 @@ ms.date: 12/10/2021
99
# Automanage Accounts
1010

1111
> [!CAUTION]
12-
> On 31 August 2024, both Automation Update Management and the Log Analytics agent it uses will be retired. Migrate to Azure Update Manager before that. Refer to guidance on migrating to Azure Update Manager [here](/azure/update-manager/guidance-migration-automation-update-management-azure-update-manager?WT.mc_id=Portal-Microsoft_Azure_Automation). [Migrate Now](https://portal.azure.com/).
12+
> On September 30, 2027, the Azure Automanage Best Practices service will be retired. As a result, attempting to create a new configuration profile or onboarding a new subscription to the service will result in an error. Learn more [here](https://aka.ms/automanagemigration/) about how to migrate to Azure Policy before that date.
13+
14+
> [!CAUTION]
15+
> Starting February 1st 2025, Azure Automanage will begin rolling out changes to halt support and enforcement for all services dependent on the deprecated Microsoft Monitoring Agent (MMA). To continue using Change Tracking and Management, VM Insights, Update Management, and Azure Automation, [migrate to the new Azure Monitor Agent (AMA)](https://aka.ms/mma-to-ama/).
1316
1417
The Automanage account is the identity that is used by the Automanage service to perform its automated operations.
1518

articles/automanage/automanage-arc.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,10 @@ ms.date: 05/12/2022
1010
# Azure Automanage for Machines Best Practices - Azure Arc-enabled servers
1111

1212
> [!CAUTION]
13-
> On 31 August 2024, both Automation Update Management and the Log Analytics agent it uses will be retired. Migrate to Azure Update Manager before that. Refer to guidance on migrating to Azure Update Manager [here](/azure/update-manager/guidance-migration-automation-update-management-azure-update-manager?WT.mc_id=Portal-Microsoft_Azure_Automation). [Migrate Now](https://portal.azure.com/).
13+
> On September 30, 2027, the Azure Automanage Best Practices service will be retired. As a result, attempting to create a new configuration profile or onboarding a new subscription to the service will result in an error. Learn more [here](https://aka.ms/automanagemigration/) about how to migrate to Azure Policy before that date.
14+
15+
> [!CAUTION]
16+
> Starting February 1st 2025, Azure Automanage will begin rolling out changes to halt support and enforcement for all services dependent on the deprecated Microsoft Monitoring Agent (MMA). To continue using Change Tracking and Management, VM Insights, Update Management, and Azure Automation, [migrate to the new Azure Monitor Agent (AMA)](https://aka.ms/mma-to-ama/).
1417
1518
> [!CAUTION]
1619
> This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and planning accordingly. For more information, see the [CentOS End Of Life guidance](/azure/virtual-machines/workloads/centos/centos-end-of-life).
@@ -35,7 +38,7 @@ Automanage supports the following operating systems for Azure Arc-enabled server
3538
| --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------- |
3639
| [Machines Insights Monitoring](/azure/azure-monitor/vm/vminsights-overview) | Azure Monitor for machines monitors the performance and health of your virtual machines, including their running processes and dependencies on other resources. | Production |
3740
| [Update Management](../automation/update-management/overview.md) | You can use Update Management in Azure Automation to manage operating system updates for your machines. You can quickly assess the status of available updates on all agent machines and manage the process of installing required updates for servers. | Production, Dev/Test |
38-
| [Microsoft Antimalware](../security/fundamentals/antimalware.md) | Microsoft Antimalware for Azure is a free real-time protection that helps identify and remove viruses, spyware, and other malicious software. It generates alerts when known malicious or unwanted software tries to install itself or run on your Azure systems. **Note:** Microsoft Antimalware requires that there be no other antimalware software installed, or it may fail to work. This is also only supported for Windows Server 2016 and above. | Production, Dev/Test |
41+
| [Microsoft Antimalware](../security/fundamentals/antimalware.md) | Microsoft Antimalware for Azure is a free real-time protection that helps identify and remove viruses, spyware, and other malicious software. It generates alerts when known malicious or unwanted software tries to install itself or run on your Azure systems. **Note:** Microsoft Antimalware requires that there be no other anti-malware software installed, or it may fail to work. This is also only supported for Windows Server 2016 and above. | Production, Dev/Test |
3942
| [Change Tracking & Inventory](../automation/change-tracking/overview.md) | Change Tracking and Inventory combines change tracking and inventory functions to allow you to track virtual machine and server infrastructure changes. The service supports change tracking across services, daemons software, registry, and files in your environment to help you diagnose unwanted changes and raise alerts. Inventory support allows you to query in-guest resources for visibility into installed applications and other configuration items. | Production, Dev/Test |
4043
| [Machine Configuration](../governance/machine-configuration/overview.md) | Machine Configuration policy is used to monitor the configuration and report on the compliance of the machine. The Automanage service will install the Azure security baseline using the Guest Configuration extension. For Arc machines, the machine configuration service will install the baseline in audit-only mode. You will be able to see where your VM is out of compliance with the baseline, but noncompliance won't be automatically remediated. | Production, Dev/Test |
4144
| [Azure Automation Account](../automation/automation-create-standalone-account.md) | Azure Automation supports management throughout the lifecycle of your infrastructure and applications. | Production, Dev/Test |

0 commit comments

Comments
 (0)