Data lifecycle management – Cloud Adoption Framework

Table of Contents0.1 In this article1 Lifecycle of data2 Managing data lifecycles3 Next steps Article 04/19/2022 2 minutes to read 2 contributors In this article Data lifecycle management is the practice of using certain policies to effectively manage […]

Data lifecycle management is the practice of using certain policies to effectively manage data for the entire time it exists within your system. These policies should consist of overarching storage and data policies that drive your data management processes. Since business goals and drivers dictate data lifecycle management policies, they generally tie into a framework of overall IT governance and management and service level agreements (SLAs).

Once you know what type of data you have and how it will be used, you already know its most likely evolution and destiny. Your need to understand how your data evolves, determine how it grows, monitor changes in its usage over time, decide how long it should exist, and adhere to all rules and regulations that apply to that data.

Data lifecycle management addresses these needs using a combination of processes, policies, and software so that your teams can use appropriate technology for each phase of your data’s lifecycle.

Lifecycle of data

Data products can have different lifecycles. In a typical lifecycle pattern, newly ingested data gets used and accessed often. As its age increases, its rate of access often decreases, and older data sees a drastic drop in usage.

Data lifecycles can differ from this typical pattern, though. Some data remains unused after its initial ingestion, or is rarely accessed once it’s been stored. Some data products might expire days or months after their creation, while other data products are actively used and modified across their entire lifetimes.

Most countries have regulations that dictate how long you’re required to store data, such as personal data and accounting data. A particular country might require you to retain primary documentation five years for data such as incoming and outgoing invoices, cash book balances, bank vouchers, and salary slips. It also might require secondary documentation be retained for three to five years, which includes things like letters, agreements, and notes.

Managing data lifecycles

There are two ways to approach data lifecycle management in cloud-scale analytics.

  • You can use the inbuilt data lifecycle features of each Azure service containing persisted data such as Azure data lake. This method is good for moving data to cold and archive tiers, but fails to ensure data is deleted after a specified amount of time.


The archive tier is not currently supported for zone-redundant storage accounts. For more information, see data redundancy.

  • You can integrate data lifecycle in an onboarding process, which gives application business owners an opportunity to define their data lifecycle policy. This process involves a custom application to capture key metrics into metadata standards for each data product. Part of this method involves moving data from hot to cold to archive, and ensures the deletion of data after a specified amount of time.

Next steps

Source Article

Next Post

Identity and access management considerations for AKS - Cloud Adoption Framework

Thu Jun 23 , 2022
Table of Contents0.1 In this article1 Design considerations2 Design recommendations Article 04/29/2022 2 minutes to read 2 contributors In this article Your organization or enterprise needs to design suitable security settings to meet their requirements. Identity and access […]