Fixed Warnings

Author: SnehaSudhirG

.openpublishing.redirection.json

@@ -7558,6 +7558,11 @@
             "redirect_url": "source-control-integration",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/automation/manage-runas-account.md",
+            "redirect_url": "/azure/automation/migrate-run-as-accounts-managed-identity",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/automation/manage-run-as-account.md",
             "redirect_url": "/azure/automation/migrate-run-as-accounts-managed-identity",

articles/automation/automation-graphical-authoring-intro.md

@@ -416,5 +416,4 @@ You have the option to revert to the Published version of a runbook. This operat
 
 * To get started with graphical runbooks, see [Tutorial: Create a graphical runbook](./learn/powershell-runbook-managed-identity.md).
 * To know more about runbook types and their advantages and limitations, see [Azure Automation runbook types](automation-runbook-types.md).
-* To understand how to authenticate using the Automation Run As account, see [Run As account](automation-security-overview.md#run-as-account).
 * For a PowerShell cmdlet reference, see [Az.Automation](/powershell/module/az.automation/#automation).

articles/automation/delete-run-as-account.md

@@ -27,9 +27,6 @@ To configure or update or delete a Run As account and a Classic Run As accounts,
     - Cloud Application Administrator
     - Global Administrator
 
-To learn more about permissions, see [Run As account permissions](automation-security-overview.md#permissions).
-
-
 ## Delete a Run As or Classic Run As account
 
 1. In the Azure portal, open the Automation account.

articles/automation/troubleshoot/extension-based-hybrid-runbook-worker.md

@@ -240,7 +240,7 @@ A runbook running on a Hybrid Runbook Worker fails with the following error mess
 
 #### Cause
 
-This error occurs when you attempt to use a [Run As account](../automation-security-overview.md#run-as-accounts) in a runbook that runs on a Hybrid Runbook Worker where the Run As account certificate isn't present. Hybrid Runbook Workers don't have the certificate asset locally by default. The Run As account requires this asset to operate properly.
+This error occurs when you attempt to use a Run As account in a runbook that runs on a Hybrid Runbook Worker where the Run As account certificate isn't present. Hybrid Runbook Workers don't have the certificate asset locally by default. The Run As account requires this asset to operate properly.
 
 #### Resolution
 

articles/automation/troubleshoot/hybrid-runbook-worker.md

@@ -151,7 +151,7 @@ A runbook running on a Hybrid Runbook Worker fails with the following error mess
 
 #### Cause
 
-This error occurs when you attempt to use a [Run As account](../automation-security-overview.md#run-as-accounts) in a runbook that runs on a Hybrid Runbook Worker where the Run As account certificate isn't present. Hybrid Runbook Workers don't have the certificate asset locally by default. The Run As account requires this asset to operate properly.
+This error occurs when you attempt to use a Run As account in a runbook that runs on a Hybrid Runbook Worker where the Run As account certificate isn't present. Hybrid Runbook Workers don't have the certificate asset locally by default. The Run As account requires this asset to operate properly.
 
 #### Resolution
 

articles/automation/troubleshoot/runbooks.md

@@ -58,7 +58,6 @@ When you receive errors during runbook execution in Azure Automation, you can us
 
 1. If your runbook is suspended or unexpectedly fails:
 
-    * [Renew the certificate](../manage-runas-account.md#cert-renewal) if the Run As account has expired.
     * [Renew the webhook](../automation-webhooks.md#update-a-webhook) if you're trying to use an expired webhook to start the runbook.
     * [Check job statuses](../automation-runbook-execution.md#job-statuses) to determine current runbook statuses and some possible causes of the issue.
     * [Add additional output](../automation-runbook-output-and-messages.md#working-with-message-streams) to the runbook to identify what happens before the runbook is suspended.
@@ -195,7 +194,7 @@ Run Login-AzureRMAccount to login.
 
 ### Cause
 
-This error can occur when you're not using a Run As account or the Run As account has expired. For more information, see [Azure Automation Run As accounts overview](../automation-security-overview.md#run-as-accounts).
+This error can occur when you're not using a Run As account or the Run As account has expired.
 
 This error has two primary causes:
 
@@ -720,7 +719,7 @@ Follow [Step 5 - Add authentication to manage Azure resources](../learn/powershe
 
 #### Insufficient permissions
 
-[Add permissions to Key Vault](../manage-runas-account.md#add-permissions-to-key-vault) to ensure that your Run As account has sufficient permissions to access Key Vault.
+Add permissions to Key Vault to ensure that your Run As account has sufficient permissions to access Key Vault.
 
 ## Scenario: Runbook fails with "Parameter length exceeded" error
 

articles/automation/troubleshoot/shared-resources.md

@@ -109,30 +109,12 @@ $Body = @"
 "@
 ```
 
-## Run As accounts
-
-### <a name="unable-create-update"></a>Scenario: You're unable to create or update a Run As account
-
-#### Issue
-
-When you try to create or update a Run As account, you receive an error similar to the following:
-
-```error
-You do not have permissions to create…
-```
 
-#### Cause
-
-You don't have the permissions that you need to create or update the Run As account, or the resource is locked at a resource group level.
-
-#### Resolution
-
-To create or update a Run As account, you must have appropriate [permissions](../automation-security-overview.md#permissions) to the various resources used by the Run As account.
-
-If the problem is because of a lock, verify that the lock can be removed. Then go to the resource that is locked in Azure portal, right-click the lock, and select **Delete**.
+## Run As accounts
 
 > [!NOTE]
-> Azure Automation Run as accounts, including  Classic Run as accounts have retired on **30 September 2023** and replaced with [Managed Identities](automation-security-overview.md#managed-identities). You would no longer be able to create or renew Run as accounts through the Azure portal. For more information, see [migrating from an existing Run As accounts to managed identity](migrate-run-as-accounts-managed-identity.md?tabs=run-as-account#sample-scripts).
+> Azure Automation Run as accounts, including  Classic Run as accounts have retired on **30 September 2023** and replaced with [Managed Identities](../automation-security-overview.md#managed-identities)
+You would no longer be able to create or renew Run as accounts through the Azure portal. For more information, see [migrating from an existing Run As accounts to managed identity](../migrate-run-as-accounts-managed-identity.md#sample-scripts).
 
 
 ### <a name="iphelper"></a>Scenario: You receive the error "Unable to find an entry point named 'GetPerAdapterInfo' in DLL 'iplpapi.dll'" when executing a runbook

articles/automation/troubleshoot/start-stop-vm.md

@@ -107,7 +107,7 @@ Review the following list for potential resolutions:
   * **ScheduledStartStop_Parent**
   * **SequencedStartStop_Parent**
 
-* Verify that your [Run As account](../automation-security-overview.md#run-as-accounts) has proper permissions to the VMs you're trying to start or stop. To learn how to check the permissions on a resource, see [Quickstart: View roles assigned to a user using the Azure portal](../../role-based-access-control/check-access.md). You'll need to provide the application ID for the service principal used by the Run As account. You can retrieve this value by going to your Automation account in the Azure portal. Select **Run as accounts** under **Account Settings**, and select the appropriate Run As account.
+* To learn how to check the permissions on a resource, see [Quickstart: View roles assigned to a user using the Azure portal](../../role-based-access-control/check-access.md). You'll need to provide the application ID for the service principal used by the Run As account. You can retrieve this value by going to your Automation account in the Azure portal. Select **Run as accounts** under **Account Settings**, and select the appropriate Run As account.
 
 * VMs might not be started or stopped if they're being explicitly excluded. Excluded VMs are set in the `External_ExcludeVMNames` variable in the Automation account to which the feature is deployed. The following example shows how you can query that value with PowerShell.
 
@@ -199,9 +199,7 @@ This issue can be caused by an improperly configured or expired Run As account.
 
 To verify that your Run As account is properly configured, go to your Automation account in the Azure portal and select **Run as accounts** under **Account Settings**. If a Run As account is improperly configured or expired, the status shows the condition.
 
-If your Run As account is misconfigured, delete and re-create your Run As account. For more information, see [Azure Automation Run As accounts](../automation-security-overview.md#run-as-accounts).
-
-If the certificate is expired for your Run As account, follow the steps in [Self-signed certificate renewal](../manage-runas-account.md#cert-renewal) to renew the certificate.
+If your Run As account is misconfigured, delete and re-create your Run As account.
 
 If there are missing permissions, see [Quickstart: View roles assigned to a user using the Azure portal](../../role-based-access-control/check-access.md). You must provide the application ID for the service principal used by the Run As account. You can retrieve this value by going to your Automation account in the Azure portal. Select **Run as accounts** under **Account Settings**, and select the appropriate Run As account.
 

articles/expressroute/how-to-custom-route-alert.md

@@ -12,7 +12,7 @@ ms.author: duau
 ---
 # Configure custom alerts to monitor advertised routes
 
-This article helps you use Azure Automation and Logic Apps to constantly monitor the number of routes advertised from the ExpressRoute gateway to on-premises networks. Monitoring can help prevent hitting the 1000 routes limit](expressroute-faqs.md#how-many-prefixes-can-be-advertised-from-a-vnet-to-on-premises-on-expressroute-private-peering).
+This article helps you use Azure Automation and Logic Apps to constantly monitor the number of routes advertised from the ExpressRoute gateway to on-premises networks. Monitoring can help prevent hitting the 1000 [routes limit](expressroute-faqs.md#how-many-prefixes-can-be-advertised-from-a-vnet-to-on-premises-on-expressroute-private-peering).
 
 **Azure Automation** allows you to automate execution of custom PowerShell script stored in a *runbook*. When using the configuration in this article, the runbook contains a PowerShell script that queries one or more ExpressRoute gateways. It collects a dataset containing the resource group, ExpressRoute gateway name, and number of network prefixes advertised on-premises.
 
@@ -34,8 +34,6 @@ Verify that you have met the following criteria before beginning your configurat
 
 * You have at least one ExpressRoute gateway in your deployment.
 
-* You have a basic understanding of [Run As accounts](../automation/manage-runas-account.md) in Azure Automation.
-
 * You are familiar with [Azure Logic Apps](../logic-apps/logic-apps-overview.md).
 
 * You are familiar with using Azure PowerShell. Azure PowerShell is required to collect the network prefixes in ExpressRoute gateway. For more information about Azure PowerShell in general, see the [Azure PowerShell documentation](/powershell/azure/).
@@ -48,7 +46,7 @@ Verify that you have met the following criteria before beginning your configurat
 
 ## <a name="accounts"></a>Create and configure accounts
 
-When you create an Automation account in the Azure portal, a [Run As](../automation/automation-security-overview.md#run-as-accounts) account is automatically created. This account takes following actions:
+When you create an Automation account in the Azure portal, a Run As account is automatically created. This account takes following actions:
 
 * Creates an Azure Active Directory (Azure AD) application with a self-signed certificate. The Run As account itself has a certificate that needs to be renewed by default every year.
 

articles/network-watcher/network-watcher-monitor-with-azure-automation.md

@@ -44,7 +44,7 @@ Before you start this scenario, you must have the following pre-requisites:
 
 ### Create the runbook
 
-The first step to configuring the example is to create the runbook. This example uses a run-as account. To learn about run-as accounts, visit [Authenticate Runbooks with Azure Run As account](../automation/manage-runas-account.md)
+The first step to configuring the example is to create the runbook.
 
 ### Step 1