Optimizing Azure Table Storage: Automated Data Cleanup using a PowerShell script with Azure Automate

Scenario

This blog’s aim is to manage Table Storage data efficiently. Imagine you have a large Azure Table Storage that accumulates logs from various applications or any unused older data. Over time, this data grows significantly, making it necessary to periodically clean up old entries to maintain performance and manage costs. You decide to automate this process using Azure Automation. However, lifecycle management policies are limited to the Blob service only.

By scheduling a PowerShell script, you can efficiently delete outdated data from your Azure Table Storage without manual intervention. This approach ensures that your storage remains optimized, and your applications continue to run smoothly.

Below is the PowerShell script which delete Table Entities based on Timestamp: -

Connect-AzAccount -Identity

$SubscriptionID = "xxxxxxxxxxxxxxxxxx"
$AzureContext = Set-AzContext –SubscriptionId $SubscriptionID
Update-AzConfig -DisplaySecretsWarning $false

$StorageAccount = "xxxxxxxxxxxxxxxxxxx"
$StorageAccountKey = "xxxxxxxxxxxxxxxxxxx"

$ctx = New-AzStorageContext -StorageAccountName $StorageAccount -StorageAccountKey $StorageAccountKey

$alltablename = (Get-AzStorageTable –Context $ctx).CloudTable

foreach ($table in $alltablename)

{
$tabledata = Get-AzTableRow -Table $table -CustomFilter "Timestamp gt datetime 'YYYY-MM-DDThh:mm:ssZ' " |
Remove-AzTableRow -Table $table
}

#DISCLAIMER
#The sample scripts are not supported under any Microsoft standard support program or service. The sample scripts are provided AS IS without warranty of any kind. Microsoft further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample scripts and documentation remains with you. In no event shall Microsoft, its authors, owners of this repository or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including,
#without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample scripts or documentation, even if Microsoft has been advised of the possibility of such damages.

Here are the steps to schedule a PowerShell script in Azure Automation :-

Create an Azure Automation Account by following the link:
- Quickstart - Create an Azure Automation account using the portal | Microsoft Learn
Add Modules to Azure Automation Account:
- Navigate to the created automation account page.
- Go to the "Modules" tab under the "Shared Resources" section and choose the "Add a module" option.
- You can either manually import modules from your local machine or import inbuilt modules from the gallery.
- In this article, we will proceed with the gallery option.
- Search for the Storage Modules.
- Add the module with recommended Runtime version.
Create a PowerShell Runbook:
- In the Azure Portal, navigate to your Automation Account.
- Under "Process Automation", select "Runbooks".
- Click on "Create a runbook".
- Enter a name for the runbook, select "PowerShell" as the Runbook type, and click "Create".
- Once Runbook is created, in the "Edit PowerShell Runbook" page.
- Enter your PowerShell script and click "Publish".
Schedule the Runbook:
- Go to the respective Runbook and choose the "Link to schedule" option.
- Select the "Link a schedule to your Runbook" option and choose the appropriate schedule.
- If you go ahead wit Schedule option, you can create a new schedule by specifying the name, description, start date, time, time zone, and repeating information.
Monitor the Runbook:
- You can monitor the runbook's execution by going to the Jobs section under Process Automation in your Automation account.
- Here, you can see the status of the runbook jobs, view job details, and troubleshoot any issues.

Note:

Using a managed identity from Microsoft Entra ID allows your runbook to securely access other Microsoft Entra-protected resources without needing to manage credentials. This identity is automatically managed by Azure, eliminating the need for you to provision or rotate secrets manually. Managed identities are the preferred authentication method for runbooks and are set as the default for your Automation account, ensuring secure and streamlined access to necessary resources. Refer :- Using a system-assigned managed identity for an Azure Automation account | Microsoft Learn

These steps should help you schedule your PowerShell script in Azure Automation. If you have any more questions or need further assistance, feel free to ask!

References :-

Perform Azure Table storage operations with PowerShell | Microsoft Learn

Quickstart - Create an Azure Automation account using the portal | Microsoft Learn

Using a system-assigned managed identity for an Azure Automation account | Microsoft Learn

Published on: September 16, 2024

Learn more

Azure PaaS Blog articles

Blog image

Azure PaaS Blog articles

Learn more

Optimizing Azure Table Storage: Automated Data Cleanup using a PowerShell script with Azure Automate

Related posts

Introducing the Azure MCP Server

Microsoft Azure Quantum Development Kit overview

How to Trigger or Schedule the Pipeline in Azure Data Factory (15)

Azure OpenAI Service now authorized for all U.S. Government data classification levels

GPT-4.1 is now available at Azure AI Foundry

Introducing Region Selection in Azure Cosmos DB Data Explorer for NoSQL Accounts

Microsoft Attempts to Fix Microsoft Graph PowerShell SDK Problem with Azure Automation

Introducing Spring Cloud Azure Starter Key Vault JCA: Streamlined TLS and mTLS for Spring Boot

Resolving Microsoft Graph PowerShell 2.26+ compatibility issues with Azure Runbooks

Getting insights from changes to items in Azure Cosmos DB just got easier!