Merge pull request #208102 from SwathiDhanwada-MSFT/patch-39

 (AzureCXP) fixes MicrosoftDocs/azure-docs#97151

Author: prmerger-automator[bot]

articles/automation/automation-security-overview.md

@@ -58,6 +58,8 @@ For details on using managed identities, see [Enable managed identity for Azure
 ## Run As accounts
 
 Run As accounts in Azure Automation provide authentication for managing Azure Resource Manager resources or resources deployed on the classic deployment model. There are two types of Run As accounts in Azure Automation:
+- Azure Run As Account
+- Azure Classic Run As Account
 
 To create or renew a Run As account, permissions are needed at three levels:
 
@@ -183,4 +185,4 @@ For runbooks that use Hybrid Runbook Workers on Azure VMs, you can use [runbook
 * To create an Automation account from the Azure portal, see [Create a standalone Azure Automation account](automation-create-standalone-account.md).
 * If you prefer to create your account using a template, see [Create an Automation account using an Azure Resource Manager template](quickstart-create-automation-account-template.md).
 * For authentication using Amazon Web Services, see [Authenticate runbooks with Amazon Web Services](automation-config-aws-account.md).
-* For a list of Azure services that support the managed identities for Azure resources feature, see [Services that support managed identities for Azure resources](../active-directory/managed-identities-azure-resources/services-support-managed-identities.md).
+* For a list of Azure services that support the managed identities for Azure resources feature, see [Services that support managed identities for Azure resources](../active-directory/managed-identities-azure-resources/services-support-managed-identities.md).