I store weekly Macrium backup files in Azure Blob Storage and want to ensure the setup is cost efficient and automatically removes old data.

Question

I store weekly Macrium backup files in Azure Blob Storage and want to ensure the setup is cost efficient and automatically removes old data.

David Leslie 0

I am using an Azure Storage Account to store Macrium backup files that are uploaded weekly. I provided my developer with instructions to optimise costs and ensure old backup data is automatically removed, but his responses indicate that some settings may not be correctly applied , particularly around the Storage Account Access Tier (Cool).

I would like Azure Support to verify and, if possible, adjust my storage account configuration to ensure cost‑optimized settings are applied correctly.

Current Situation / Issue

We store Macrium backup files in Azure Blob Storage.
Backups older than ~7 days should be automatically deleted to avoid unnecessary storage costs.
I requested the following changes:
1. PowerShell cleanup logic to delete blobs older than 7+ days and to ensure no blob versions or snapshots exist.
  1. Azure Blob Lifecycle Management rules to delete blobs older than 7+ days (including versions and snapshots).
    1. Storage Account configuration:
      - Access tier: Cool
        - Redundancy: __LRS__ - Do _not_ use Archive tier (because restores need to be fast). - My developer responded with:
  - The PowerShell script already deletes older backups and keeps only the latest ones.
    - Lifecycle Management can be configured as requested.
      - However, he stated: “Access tier isn’t relevant for the storage you use. You don’t upload to an archive tier anyway.”

Requested Help From Azure Support

I need Azure Support to:

Verify whether the Storage Account Access Tier can (and should) be changed to Cool to reduce storage costs for our use case (Macrium backup files retained for 7 days).
Check whether any blob snapshots or versions exist that may be silently increasing storage cost.
Confirm that Lifecycle Management rules can safely handle deletion of older backups without interfering with Macrium's restore processes.
If possible, apply or assist with applying the correct configuration, or advise whether other settings (e.g., account-tier-level settings vs. per-blob-tier settings) need to be adjusted. I am using an Azure Storage Account to store Macrium backup files that are uploaded weekly. I provided my developer with instructions to optimise costs and ensure old backup data is automatically removed, but his responses indicate that some settings may not be correctly applied , particularly around the Storage Account Access Tier (Cool). I would like Azure Support to verify and, if possible, adjust my storage account configuration to ensure cost‑optimized settings are applied correctly. Current Situation / Issue
- We store Macrium backup files in Azure Blob Storage.
- Backups older than ~7 days should be automatically deleted to avoid unnecessary storage costs.
- I requested the following changes:
1. PowerShell cleanup logic to delete blobs older than 7+ days and to ensure no blob versions or snapshots exist.
2. Azure Blob Lifecycle Management rules to delete blobs older than 7+ days (including versions and snapshots).
3. Storage Account configuration:
  - Access tier: Cool
  - Redundancy: LRS
  - Do not use Archive tier (because restores need to be fast).
- My developer responded with:
- - The PowerShell script already deletes older backups and keeps only the latest ones.
- Lifecycle Management can be configured as requested.
- However, he stated:
  “Access tier isn’t relevant for the storage you use. You don’t upload to an archive tier anyway.”
Requested Help From Azure Support I need Azure Support to:
1. Verify whether the Storage Account Access Tier can (and should) be changed to Cool to reduce storage costs for our use case (Macrium backup files retained for 7 days).
2. Check whether any blob snapshots or versions exist that may be silently increasing storage cost.
3. Confirm that Lifecycle Management rules can safely handle deletion of older backups without interfering with Macrium's restore processes.
4. If possible, apply or assist with applying the correct configuration, or advise whether other settings (e.g., account-tier-level settings vs. per-blob-tier settings) need to be adjusted.

David Leslie 0 Reputation points

2025-12-11T13:00:15.92+00:00
Hi Vallepu,

Please firstly understand that I am not technical and find Azure to be extremely complicated.

Are you able to change my storage and and existing blobs to the Cool access tier for me and place my backup files there?

If you can do that, will future files go there or is there something I need to ask my developer to change on their script etc?

You've said I need to manage my snapshots carefully to avoid extra charges and to delete and re-create snapshots associated with a blob whenever I update the blob. I don't understand what this means. Is it something you can do for me or is there something I need to tell my developer to do?

You've said "Ensure only one automated cleanup mechanism is active (either PowerShell or Lifecycle) otherwise you risk conflict or race conditions." Again, is this something you can do for me or is there something I need to tell my developer to do?

You've said:

Should other settings be adjusted (account-level vs. blob-level)?

The account access tier is set correctly (Cool)

All backups are uploaded at the correct blob tier (inherit from account unless explicitly overridden)

Lifecycle rules are applied at the correct container

No settings like soft-delete, versioning, or snapshots conflict with cleanup rules

Again, is this something you can do for me or is there something I need to tell my developer to do?

Can you please place your answers alongside my questions?

I would just like you and/or my developer to get all files stored from now on, on the Cool Access Tier, to minimise my monthly Azure costs (but not in Archive which takes a long time to retrieve).

I will look forward to hearing from you.

Many thanks.

David
Vallepu Venkateswarlu 1,400 Reputation points Microsoft External Staff Moderator

2025-12-11T13:20:20.8833333+00:00

Hi @ David Leslie •,

Are you able to change my storage and and existing blobs to the Cool access tier for me and place my backup files there? Sorry, we don’t have access to your environment to change all blobs to the Cool tier. Please reach out to your developer to perform this change

If you can do that, will future files go there or is there something I need to ask my developer to change on their script etc?

You can create a PowerShell or CLI script to automate this process. If any blobs are not using the Cool tier, the script can automatically change them to Cool by running through an Automation Runbook.

You've said I need to manage my snapshots carefully to avoid extra charges and to delete and re-create snapshots associated with a blob whenever I update the blob. I don't understand what this means. Is it something you can do for me or is there something I need to tell my developer to do?

You need to manage from your side, Inform your developer manage those to avoid extra cost.

You've said "Ensure only one automated cleanup mechanism is active (either PowerShell or Lifecycle) otherwise you risk conflict or race conditions."

You will need to manage this from your side. Please inform your developer to handle these changes to avoid additional costs.

Finally, We can only help troubleshoot issues when a service is not working as per your configuration. Customizations, such as changing tiers to Cool, managing snapshot costs, or setting up automations—must be done from your side.

Please feel free to ask if the provided solution does not help or if you have any additional questions.,

I hope this information helps to address all your queries. Please "upvote", This will help us and others in the community as well.
David Leslie 0 Reputation points

2025-12-11T14:28:59.06+00:00

I have forwarded all of the above conversations to my developer who has responded as follows:

"This isn't relevant because you aren't using blobs and you can't reduce size any further ad you need the overlap. The only settings tweakable are IOPS and throughput."

I don't understand what any of that means and am just trying to get to where I need to get to and costs of c£20/month rather than c£200/month.

How exactly and simply can you help me to resolve this?
Vallepu Venkateswarlu 1,400 Reputation points Microsoft External Staff Moderator

2025-12-11T15:33:38.0866667+00:00

Hi @ David Leslie •,

I don't understand what any of that means and am just trying to get to where I need to get to and costs of c£20/month rather than c£200/month. How exactly and simply can you help me to resolve this?

Make sure your Storage Account access tier is set to Cool, The Cool tier is designed for backup files that you keep only a few days. Hot tier is much more expensive.

Delete old backup files (and any hidden snapshots/versions). Enable a Lifecycle Management rule to automatically delete backups older than 7 days. Once the rule is in place, Azure will automatically remove old backups and any associated versions or snapshots, so you only pay for one week’s worth of data.

No changes to IOPS or throughput are required—Azure Blob Storage does not have IOPS or throughput charges. Billing is based only on storage capacity, transactions, data transfer, and optional features.

Ref: How you're charged for Azure Blob Storage

There are no IOPS or throughput costs for Blob Storage. Those apply only to Azure Files Premium or Azure Managed Disks, not block blobs.

Ref: Azure Blob Storage pricing

Please "upvote" if the information helped you. This will help us and others in the community as well.
David Leslie 0 Reputation points

2025-12-11T17:15:27.77+00:00

I've been back to my developer on your points.

On your point " Delete old backup files (and any hidden snapshots/versions). Enable a Lifecycle Management rule to automatically delete backups older than 7 days." he says:

"The script already does this - if we turn it on, it will delete your backups if you ever need them. We have deleted the Azure backups - they will remove themselves in 12 days time."

On your point "There are no IOPS or throughput costs for Blob Storage", he says:

"Yes this is correct, you don't use blob storage."

I asked him if he could make sure my Storage Account access tier is set to Cool and he has said:

"You aren't using blobs - that option isn't available."

So, I'm stuck and don't know what to do.
David Leslie 0 Reputation points

2025-12-11T17:54:52.1466667+00:00

I've been back to my developer on your points.

On your point " Delete old backup files (and any hidden snapshots/versions). Enable a Lifecycle Management rule to automatically delete backups older than 7 days." he says:

"The script already does this - if we turn it on, it will delete your backups if you ever need them. We have deleted the Azure backups - they will remove themselves in 12 days time."

On your point "There are no IOPS or throughput costs for Blob Storage", he says:

"Yes this is correct, you don't use blob storage."

I asked him if he could make sure my Storage Account access tier is set to Cool and he has said:

"You aren't using blobs - that option isn't available."

So, I'm stuck and don't know what to do.
Vallepu Venkateswarlu 1,400 Reputation points Microsoft External Staff Moderator

2025-12-11T17:59:05.3566667+00:00

Hi @ David Leslie •,,

If you are not using Blob storage, please let us know which storage account type you are using.

Kindly share a screenshot so we can confirm whether it is a Blob storage account or another type.
David Leslie 0 Reputation points

2025-12-11T18:01:11.2666667+00:00

I've been back to my developer on your points.

On your point " Delete old backup files (and any hidden snapshots/versions). Enable a Lifecycle Management rule to automatically delete backups older than 7 days." he says:

"The script already does this - if we turn it on, it will delete your backups if you ever need them. We have deleted the Azure backups - they will remove themselves in 12 days time."

On your point "There are no IOPS or throughput costs for Blob Storage", he says:

"Yes this is correct, you don't use blob storage."

I asked him if he could make sure my Storage Account access tier is set to Cool and he has said:

"You aren't using blobs - that option isn't available."

So, I'm stuck and don't know what to do.
David Leslie 0 Reputation points

2025-12-11T18:03:59.5866667+00:00

Please send me the link to get to the page where I can see my storage account type
Vallepu Venkateswarlu 1,400 Reputation points Microsoft External Staff Moderator

2025-12-12T06:11:17.1266667+00:00

To check whether you are using Blob Storage or File Storage:

Go to Azure Portal → Storage accounts → select the storage account.

In the left menu:

If “Containers” is present and your files/backups are inside Containers → you are using Blob Storage.

If “File shares” is present and data is stored there → you are using Azure File Storage.

If both appear, the storage account supports both types, and usage depends on where the data is stored.
David Leslie 0 Reputation points

2025-12-12T09:07:51.7533333+00:00

'Containers isn't present in the left menu.
Vallepu Venkateswarlu 1,400 Reputation points Microsoft External Staff Moderator

2025-12-12T11:35:29.5033333+00:00
Hi @ David Leslie •,

From the screenshot you shared earlier the storage account Kind is FileStorage (Premium File Shares). If that is the account you are talking about, Blob features like account-level Cool access tier and Blob lifecycle management do NOT apply to File Storage accounts.

Options if you really need blob features (cool tier & lifecycle):

Move/upload Macrium backup files to a StorageV2 (General purpose v2) or BlobStorage account (recommended). StorageV2 supports default access tier (Hot/Cool) and lifecycle rules.

Or create a new StorageV2 account and change your backup target to the new account.

Converting a FileStorage account to StorageV2 is not possible; you must create a new account and copy data.

If you already have a StorageV2 account and the backups are in a blob container there, ignore the FileStorage note, proceed with lifecycle & tier settings below

Ref: Blob Storage

Blob Storage is ideal for:- Serving images or documents directly to a browser.

Storing files for distributed access.

Streaming video and audio.

Storing data for backup and restore, disaster recovery, and archiving.

Storing data for analysis by an on-premises or Azure-hosted service.

File shares can be used for many common scenarios:

Many on-premises applications use file shares.

Configuration files can be stored on a file share and accessed from multiple VMs.

Resource logs, metrics, and crash dumps are just three examples of data that can be written to a file share and processed or analyzed later.

1 answer

Your answer

David Leslie 0 Reputation points

2025-12-11T13:00:15.92+00:00

Hi Vallepu,

Please firstly understand that I am not technical and find Azure to be extremely complicated.

Are you able to change my storage and and existing blobs to the Cool access tier for me and place my backup files there?

If you can do that, will future files go there or is there something I need to ask my developer to change on their script etc?

You've said I need to manage my snapshots carefully to avoid extra charges and to delete and re-create snapshots associated with a blob whenever I update the blob. I don't understand what this means. Is it something you can do for me or is there something I need to tell my developer to do?

You've said "Ensure only one automated cleanup mechanism is active (either PowerShell or Lifecycle) otherwise you risk conflict or race conditions." Again, is this something you can do for me or is there something I need to tell my developer to do?

You've said:

Should other settings be adjusted (account-level vs. blob-level)?

The account access tier is set correctly (Cool)

All backups are uploaded at the correct blob tier (inherit from account unless explicitly overridden)

Lifecycle rules are applied at the correct container

No settings like soft-delete, versioning, or snapshots conflict with cleanup rules

Again, is this something you can do for me or is there something I need to tell my developer to do?

Can you please place your answers alongside my questions?

I would just like you and/or my developer to get all files stored from now on, on the Cool Access Tier, to minimise my monthly Azure costs (but not in Archive which takes a long time to retrieve).

I will look forward to hearing from you.

Many thanks.

David
Vallepu Venkateswarlu 1,400 Reputation points Microsoft External Staff Moderator

2025-12-11T13:20:20.8833333+00:00

Hi @ David Leslie •,

Are you able to change my storage and and existing blobs to the Cool access tier for me and place my backup files there? Sorry, we don’t have access to your environment to change all blobs to the Cool tier. Please reach out to your developer to perform this change

If you can do that, will future files go there or is there something I need to ask my developer to change on their script etc?

You can create a PowerShell or CLI script to automate this process. If any blobs are not using the Cool tier, the script can automatically change them to Cool by running through an Automation Runbook.

You've said I need to manage my snapshots carefully to avoid extra charges and to delete and re-create snapshots associated with a blob whenever I update the blob. I don't understand what this means. Is it something you can do for me or is there something I need to tell my developer to do?

You need to manage from your side, Inform your developer manage those to avoid extra cost.

You've said "Ensure only one automated cleanup mechanism is active (either PowerShell or Lifecycle) otherwise you risk conflict or race conditions."

You will need to manage this from your side. Please inform your developer to handle these changes to avoid additional costs.

Finally, We can only help troubleshoot issues when a service is not working as per your configuration. Customizations, such as changing tiers to Cool, managing snapshot costs, or setting up automations—must be done from your side.

Please feel free to ask if the provided solution does not help or if you have any additional questions.,

I hope this information helps to address all your queries. Please "upvote", This will help us and others in the community as well.
David Leslie 0 Reputation points

2025-12-11T14:28:59.06+00:00

I have forwarded all of the above conversations to my developer who has responded as follows:

"This isn't relevant because you aren't using blobs and you can't reduce size any further ad you need the overlap. The only settings tweakable are IOPS and throughput."

I don't understand what any of that means and am just trying to get to where I need to get to and costs of c£20/month rather than c£200/month.

How exactly and simply can you help me to resolve this?
Vallepu Venkateswarlu 1,400 Reputation points Microsoft External Staff Moderator

2025-12-11T15:33:38.0866667+00:00

Hi @ David Leslie •,

I don't understand what any of that means and am just trying to get to where I need to get to and costs of c£20/month rather than c£200/month. How exactly and simply can you help me to resolve this?

Make sure your Storage Account access tier is set to Cool, The Cool tier is designed for backup files that you keep only a few days. Hot tier is much more expensive.

Delete old backup files (and any hidden snapshots/versions). Enable a Lifecycle Management rule to automatically delete backups older than 7 days. Once the rule is in place, Azure will automatically remove old backups and any associated versions or snapshots, so you only pay for one week’s worth of data.

No changes to IOPS or throughput are required—Azure Blob Storage does not have IOPS or throughput charges. Billing is based only on storage capacity, transactions, data transfer, and optional features.

Ref: How you're charged for Azure Blob Storage

There are no IOPS or throughput costs for Blob Storage. Those apply only to Azure Files Premium or Azure Managed Disks, not block blobs.

Ref: Azure Blob Storage pricing

Please "upvote" if the information helped you. This will help us and others in the community as well.
David Leslie 0 Reputation points

2025-12-11T17:15:27.77+00:00

I've been back to my developer on your points.

On your point " Delete old backup files (and any hidden snapshots/versions). Enable a Lifecycle Management rule to automatically delete backups older than 7 days." he says:

"The script already does this - if we turn it on, it will delete your backups if you ever need them. We have deleted the Azure backups - they will remove themselves in 12 days time."

On your point "There are no IOPS or throughput costs for Blob Storage", he says:

"Yes this is correct, you don't use blob storage."

I asked him if he could make sure my Storage Account access tier is set to Cool and he has said:

"You aren't using blobs - that option isn't available."

So, I'm stuck and don't know what to do.
David Leslie 0 Reputation points

2025-12-11T17:54:52.1466667+00:00

I've been back to my developer on your points.

On your point " Delete old backup files (and any hidden snapshots/versions). Enable a Lifecycle Management rule to automatically delete backups older than 7 days." he says:

"The script already does this - if we turn it on, it will delete your backups if you ever need them. We have deleted the Azure backups - they will remove themselves in 12 days time."

On your point "There are no IOPS or throughput costs for Blob Storage", he says:

"Yes this is correct, you don't use blob storage."

I asked him if he could make sure my Storage Account access tier is set to Cool and he has said:

"You aren't using blobs - that option isn't available."

So, I'm stuck and don't know what to do.
Vallepu Venkateswarlu 1,400 Reputation points Microsoft External Staff Moderator

2025-12-11T17:59:05.3566667+00:00

Hi @ David Leslie •,,

If you are not using Blob storage, please let us know which storage account type you are using.

Kindly share a screenshot so we can confirm whether it is a Blob storage account or another type.
David Leslie 0 Reputation points

2025-12-11T18:01:11.2666667+00:00

I've been back to my developer on your points.

On your point " Delete old backup files (and any hidden snapshots/versions). Enable a Lifecycle Management rule to automatically delete backups older than 7 days." he says:

"The script already does this - if we turn it on, it will delete your backups if you ever need them. We have deleted the Azure backups - they will remove themselves in 12 days time."

On your point "There are no IOPS or throughput costs for Blob Storage", he says:

"Yes this is correct, you don't use blob storage."

I asked him if he could make sure my Storage Account access tier is set to Cool and he has said:

"You aren't using blobs - that option isn't available."

So, I'm stuck and don't know what to do.
David Leslie 0 Reputation points

2025-12-11T18:03:59.5866667+00:00

Please send me the link to get to the page where I can see my storage account type
Vallepu Venkateswarlu 1,400 Reputation points Microsoft External Staff Moderator

2025-12-12T06:11:17.1266667+00:00

To check whether you are using Blob Storage or File Storage:

Go to Azure Portal → Storage accounts → select the storage account.

In the left menu:

If “Containers” is present and your files/backups are inside Containers → you are using Blob Storage.

If “File shares” is present and data is stored there → you are using Azure File Storage.

If both appear, the storage account supports both types, and usage depends on where the data is stored.
David Leslie 0 Reputation points

2025-12-12T09:07:51.7533333+00:00

'Containers isn't present in the left menu.
Vallepu Venkateswarlu 1,400 Reputation points Microsoft External Staff Moderator

2025-12-12T11:35:29.5033333+00:00

Hi @ David Leslie •,

From the screenshot you shared earlier the storage account Kind is FileStorage (Premium File Shares). If that is the account you are talking about, Blob features like account-level Cool access tier and Blob lifecycle management do NOT apply to File Storage accounts.

Options if you really need blob features (cool tier & lifecycle):

Move/upload Macrium backup files to a StorageV2 (General purpose v2) or BlobStorage account (recommended). StorageV2 supports default access tier (Hot/Cool) and lifecycle rules.

Or create a new StorageV2 account and change your backup target to the new account.

Converting a FileStorage account to StorageV2 is not possible; you must create a new account and copy data.

If you already have a StorageV2 account and the backups are in a blob container there, ignore the FileStorage note, proceed with lifecycle & tier settings below

Ref: Blob Storage

Blob Storage is ideal for:- Serving images or documents directly to a browser.

Storing files for distributed access.

Streaming video and audio.

Storing data for backup and restore, disaster recovery, and archiving.

Storing data for analysis by an on-premises or Azure-hosted service.

File shares can be used for many common scenarios:

Many on-premises applications use file shares.

Configuration files can be stored on a file share and accessed from multiple VMs.

Resource logs, metrics, and crash dumps are just three examples of data that can be written to a file share and processed or analyzed later.

Answer 1

Hi @ David Leslie •,

Welcome to Microsoft Q&A Platform.

Should the Storage Account Access Tier be changed to Cool?

Yes — for backup files that are kept only 7 days and accessed rarely, the Cool access tier is the cost-optimal choice. Cool reduces storage cost without impacting restore speed (unlike Archive). and move existing blobs can also be moved to Cool if needed.

Can we check whether blob snapshots or versions exist and are adding hidden cost?

Yes, as states in Pricing and billing, Blob snapshots, like blob versions, are billed at the same rate as active data, Microsoft recommends managing your snapshots carefully to avoid extra charges.
Delete and re-create snapshots associated with a blob whenever you update the blob.

Can Lifecycle Management rules safely delete backup files older than 7 days?

Yes, The Lifecycle will delete the current versions of a blob, previous versions of a blob, or blob snapshots at the end of their lifecycles. Ref: Azure Blob Storage lifecycle management

Note: Ensure only one automated cleanup mechanism is active (either PowerShell or Lifecycle) otherwise you risk conflict or race conditions.

Should other settings be adjusted (account-level vs. blob-level)?

The account access tier is set correctly (Cool)
All backups are uploaded at the correct blob tier (inherit from account unless explicitly overridden)
Lifecycle rules are applied at the correct container
No settings like soft-delete, versioning, or snapshots conflict with cleanup rules

I hope this information helps to address all your question's.

Please Accept the answer if the information helped you. This will help us and others in the community as well.

Share via

I store weekly Macrium backup files in Azure Blob Storage and want to ensure the setup is cost efficient and automatically removes old data.

1 answer

Your answer