Bulk update of links to archived azurerm content

Author: mikefrobbins

.openpublishing.redirection.json

@@ -2882,7 +2882,7 @@
     },
     {
       "source_path_from_root": "/articles/media-services/media-services-manage-with-powershell.md",
-      "redirect_url": "/powershell/module/azurerm.media/?view=azurermps-4.2.0",
+      "redirect_url": "/powershell/module/az.media/",
       "redirect_document_id": false
     },
     {

articles/automation/TOC.yml

@@ -400,8 +400,6 @@
     href: /cli/azure/automation
   - name: Azure PowerShell Az
     href: /powershell/module/az.automation/
-  - name: Azure PowerShell AzureRM
-    href: /powershell/module/azurerm.automation/
   - name: .NET
     href: /dotnet/api/microsoft.azure.management.automation
   - name: REST

articles/automation/shared-resources/modules.md

@@ -17,7 +17,6 @@ ms.service: azure-automation
 Azure Automation uses a number of PowerShell modules to enable cmdlets in runbooks and DSC resources in DSC configurations. Supported modules include:
 
 * [Azure PowerShell Az.Automation](/powershell/azure/new-azureps-module-az).
-* [Azure PowerShell AzureRM.Automation](/powershell/module/azurerm.automation/).
 * Other PowerShell modules.
 * Internal `Orchestrator.AssetManagement.Cmdlets` module.
 * Python 2 modules.
@@ -137,7 +136,7 @@ Be sure to test all runbooks and DSC configurations carefully, in a separate Aut
 
 To ensure that you don't run any existing runbooks or DSC configurations that use AzureRM modules, you must stop and unschedule all affected runbooks and configurations. First, make sure that you review each runbook or DSC configuration and its schedules separately, to ensure that you can reschedule the item in the future if necessary.
 
-When you're ready to remove your schedules, you can either use the Azure portal or the [Remove-AzureRmAutomationSchedule](/powershell/module/azurerm.automation/remove-azurermautomationschedule) cmdlet. See [Remove a schedule](schedules.md#remove-a-schedule).
+When you're ready to remove your schedules, you can either use the Azure portal or the [Remove-AzAutomationSchedule](/powershell/module/az.automation/remove-azautomationschedule) cmdlet. See [Remove a schedule](schedules.md#remove-a-schedule).
 
 ### Remove AzureRM modules
 

articles/automation/state-configuration/remove-node-and-configuration-package.md

@@ -50,10 +50,6 @@ with Azure PowerShell using the following steps.
 
 You can also unregister a node using the PowerShell cmdlet [Unregister-AzAutomationDscNode][04].
 
->[!NOTE]
-> If your organization still uses the deprecated AzureRM modules, you can use
-> [Unregister-AzureRmAutomationDscNode][05].
-
 ---
 
 
@@ -136,7 +132,6 @@ dpkg -P <package name>
 [02]: ../automation-dsc-onboarding.md
 [03]: ../tutorial-configure-servers-desired-state.md#register-a-vm-to-be-managed-by-state-configuration
 [04]: /powershell/module/az.automation/unregister-azautomationdscnode
-[05]: /powershell/module/azurerm.automation/unregister-azurermautomationdscnode
 [06]: /powershell/module/psdesiredstateconfiguration/remove-dscconfigurationdocument
 [07]: #delete-a-configuration-from-the-node
 [08]: #remove-the-dsc-package-from-a-linux-node

articles/automation/troubleshoot/desired-state-configuration.md

@@ -308,8 +308,8 @@ configuration name. This enables the node but doesn't assign a node configuratio
 
 ### Issue
 
-When you register a node by using [Register-AzAutomationDSCNode][14] or
-[Register-AzureRMAutomationDSCNode][18], you receive the following error:
+When you register a node by using [Register-AzAutomationDSCNode][14], you receive the following
+error:
 
 ```error
 One or more errors occurred.
@@ -450,7 +450,6 @@ channels:
 [15]: /powershell/module/Az.Automation/Remove-AzAutomationDscConfiguration
 [16]: /powershell/module/Az.Automation/Set-AzAutomationDscNode
 [17]: /powershell/module/az.compute/invoke-azvmruncommand
-[18]: /powershell/module/azurerm.automation/register-azurermautomationdscnode
 [19]: /powershell/module/psdesiredstateconfiguration/set-dsclocalconfigurationmanager
 [20]: /powershell/scripting/overview
 [21]: /powershell/scripting/wmf/known-issues/known-issues-dsc

articles/automation/tutorial-configure-servers-desired-state.md

@@ -233,7 +233,7 @@ $reports[0]
 <!-- link references -->
 [01]: ./automation-security-overview.md
 [02]: /azure/virtual-machines/windows/quick-create-portal
-[03]: /powershell/azure/azurerm/install-azurerm-ps
+[03]: /powershell/azure/install-azure-powershell
 [04]: /powershell/dsc/configurations/configurations
 [05]: /powershell/dsc/managing-nodes/metaConfig
 [06]: /powershell/dsc/overview
@@ -246,7 +246,7 @@ $reports[0]
 [13]: /powershell/module/Az.Automation/Import-AzAutomationDscConfiguration
 [14]: /powershell/module/Az.Automation/Register-AzAutomationDscNode
 [15]: /powershell/module/Az.Automation/Start-AzAutomationDscCompilationJob
-[16]: /powershell/module/azurerm.automation/register-azurermautomationdscnode
+[16]: /powershell/module/az.automation/register-azautomationdscnode
 [17]: automation-dsc-cd-chocolatey.md
 [18]: automation-dsc-compile.md
 [19]: automation-dsc-getting-started.md

articles/automation/update-management/enable-from-runbook.md

@@ -52,7 +52,7 @@ Sign in to the [Azure portal](https://portal.azure.com).
 
 ## Install and update modules
 
-It's required to update to the latest Azure modules and import the [AzureRM.OperationalInsights](/powershell/module/azurerm.operationalinsights) module to successfully enable Update Management for your VMs with the runbook.
+It's required to update to the latest Azure modules and import the [Az.OperationalInsights](/powershell/module/az.operationalinsights) module to successfully enable Update Management for your VMs with the runbook.
 
 1. In your Automation account, select **Modules** under **Shared Resources**.
 
@@ -66,7 +66,7 @@ It's required to update to the latest Azure modules and import the [AzureRM.Oper
 
 5. Select **Browse gallery** to open the module gallery.
 
-6. Search for `AzureRM.OperationalInsights` and import this module into your Automation account.
+6. Search for `Az.OperationalInsights` and import this module into your Automation account.
 
     ![Import OperationalInsights module](media/enable-from-runbook/import-operational-insights-module-azurerm.png)
 

articles/azure-cache-for-redis/cache-migration-guide.md

@@ -65,12 +65,12 @@ General steps to implement this option are:
 2. Save a snapshot of the existing Redis cache. You can [configure Redis to save snapshots](https://redis.io/topics/persistence) periodically, or run the process manually using the [SAVE](https://redis.io/commands/save) or [BGSAVE](https://redis.io/commands/bgsave) commands. The RDB file is named “dump.rdb” by default and will be located at the path specified in the *redis.conf* configuration file.
 
     > [!NOTE]
-    > If you’re migrating data within Azure Cache for Redis, see [these instructions on how to export an RDB file](cache-how-to-import-export-data.md) or use the [PowerShell Export cmdlet](/powershell/module/azurerm.rediscache/export-azurermrediscache) instead.
+    > If you’re migrating data within Azure Cache for Redis, see [these instructions on how to export an RDB file](cache-how-to-import-export-data.md) or use the [PowerShell Export cmdlet](/powershell/module/az.rediscache/export-azrediscache) instead.
     >
 
 3. Copy the RDB file to an Azure storage account in the region where your new cache is located. You can use AzCopy for this task.
 
-4. Import the RDB file into the new cache using these [import instructions](cache-how-to-import-export-data.md) or the [PowerShell Import cmdlet](/powershell/module/azurerm.rediscache/import-azurermrediscache).
+4. Import the RDB file into the new cache using these [import instructions](cache-how-to-import-export-data.md) or the [PowerShell Import cmdlet](/powershell/module/az.rediscache/import-azrediscache).
 
 5. Update your application to use the new cache instance.
 

articles/azure-cache-for-redis/cache-vnet-migration.md

@@ -76,12 +76,12 @@ General steps to implement this option are:
 2. Save a snapshot of the existing Redis cache. You can [configure Redis to save snapshots](https://redis.io/topics/persistence) periodically, or run the process manually using the [SAVE](https://redis.io/commands/save) or [BGSAVE](https://redis.io/commands/bgsave) commands. The RDB file is named “dump.rdb” by default and will be located at the path specified in the *redis.conf* configuration file.
 
     > [!NOTE]
-    > If you’re migrating data within Azure Cache for Redis, see [these instructions on how to export an RDB file](cache-how-to-import-export-data.md) or use the [PowerShell Export cmdlet](/powershell/module/azurerm.rediscache/export-azurermrediscache) instead.
+    > If you’re migrating data within Azure Cache for Redis, see [these instructions on how to export an RDB file](cache-how-to-import-export-data.md) or use the [PowerShell Export cmdlet](/powershell/module/az.rediscache/export-azrediscache) instead.
     >
 
 3. Copy the RDB file to an Azure storage account in the region where your new cache is located. You can use AzCopy for this task.
 
-4. Import the RDB file into the new cache using these [import instructions](cache-how-to-import-export-data.md) or the [PowerShell Import cmdlet](/powershell/module/azurerm.rediscache/import-azurermrediscache).
+4. Import the RDB file into the new cache using these [import instructions](cache-how-to-import-export-data.md) or the [PowerShell Import cmdlet](/powershell/module/az.rediscache/import-azrediscache).
 
 5. Update your application to use the new cache instance.
 

articles/azure-cache-for-redis/managed-redis/managed-redis-migration-guide.md

@@ -64,12 +64,12 @@ General steps to implement this option are:
 2. Save a snapshot of the existing Redis cache. You can [configure Redis to save snapshots](https://redis.io/topics/persistence) periodically, or run the process manually using the [SAVE](https://redis.io/commands/save) or [BGSAVE](https://redis.io/commands/bgsave) commands. The RDB file is named “dump.rdb” by default and will be located at the path specified in the *redis.conf* configuration file.
 
     > [!NOTE]
-    > If you’re migrating data within Azure Managed Redis, see [these instructions on how to export an RDB file](managed-redis-how-to-import-export-data.md) or use the [PowerShell Export cmdlet](/powershell/module/azurerm.rediscache/export-azurermrediscache) instead.
+    > If you’re migrating data within Azure Managed Redis, see [these instructions on how to export an RDB file](managed-redis-how-to-import-export-data.md) or use the [PowerShell Export cmdlet](/powershell/module/az.rediscache/export-azrediscache) instead.
     >
 
 3. Copy the RDB file to an Azure storage account in the region where your new cache is located. You can use AzCopy for this task.
 
-4. Import the RDB file into the new cache using these [import instructions](managed-redis-how-to-import-export-data.md) or the [PowerShell Import cmdlet](/powershell/module/azurerm.rediscache/import-azurermrediscache).
+4. Import the RDB file into the new cache using these [import instructions](managed-redis-how-to-import-export-data.md) or the [PowerShell Import cmdlet](/powershell/module/az.rediscache/import-azrediscache).
 
 5. Update your application to use the new cache instance.