1. Resources
  2. Detection rules
  3. Storage Account Object Replication Policy Created

Storage Account Object Replication Policy Created detection rules

Someone creates an object replication policy on a storage account. From then on Azure Storage copies the block blobs of the chosen containers to another storage account, which can be in another subscription or another tenant.

Platform
Azure
Severity
Medium
Log source
Azure Activity log
Last updated
Rule formats
Sigmaand queries for: SplunkMicrosoft SentinelIBM QRadar
What an attacker needs
The Contributor role on the storage account or above, blob versioning and change feed on the account, and a destination account the attacker controls.
Impact
A continuing copy of the replicated containers in another storage account, made by Azure Storage with no read by the attacker's identity.
Response
Delete the replication policy on the source account, contain the caller and treat the replicated blobs as disclosed if the destination is not yours.
Mitigation
Set AllowCrossTenantReplication to false on every storage account and limit the roles that can write replication policies.
Operation
MICROSOFT.STORAGE/STORAGEACCOUNTS/OBJECTREPLICATIONPOLICIES/WRITE

How the attack works

Object replication asynchronously copies block blobs from containers in a source storage account to containers in a destination account. A replication policy names the two accounts and holds rules that pair a source container with a destination container. The policy is created on the destination account first, Azure Storage gives it a policy ID, and the same policy is then created on the source account. After that the service checks the change feed of the source account and copies every write and delete to the destination, including the versions, metadata and properties of each blob. Microsoft documents that the two accounts can be in different subscriptions and, optionally, in different Microsoft Entra tenants.

For an attacker with control-plane rights on a storage account, a replication policy is a copy job that Azure runs for them. No blob is ever read with the attacker's identity, so resource logs of the source account show no client downloading the data, and new data keeps flowing for as long as the policy exists. Microsoft states the consequence in its own documentation: granting the permission to configure object replication should be understood as also granting permission to copy data between the source and destination accounts. The Azure Activity log records the policy write (Microsoft.Storage/storageAccounts/objectReplicationPolicies/write) with its caller on each account in a subscription you collect from. Cross-tenant replication is disabled by default only for storage accounts created after 15 December 2023. No public incident report was found that describes this at the level of the audit event.

What an attacker needs

  • Microsoft documents that configuring an object replication policy needs the Contributor role at the level of the storage account or higher. Owner and Storage Account Contributor include the policy write as well.
  • Blob versioning on both accounts and change feed on the source account. Enabling them needs Microsoft.Storage/storageAccounts/blobServices/write, which the same roles have.
  • A destination account that the attacker controls. For a destination in another tenant, the source account must allow cross-tenant replication (AllowCrossTenantReplication).

Impact

A continuing copy of the block blobs in the replicated containers, with their versions, in an account the attacker reads at leisure. The copy does not depend on the attacker's access to the source account after the policy exists, and it carries on for new and changed blobs until the policy is deleted.

Detection rules

Storage Account Object Replication Policy Created or Changed

Detects a successful create or update of an object replication policy on a storage account (Microsoft.Storage/storageAccounts/objectReplicationPolicies/write). Once the policy exists on the source account, Azure Storage copies the block blobs of the paired containers to the destination account, which can be in another subscription or, where the account allows it, in another Microsoft Entra tenant. Microsoft states that the permission to configure object replication also grants the ability to copy data between the two accounts. The event does not name the other account, so read the policy after the rule fires. A setup inside your own subscriptions produces two events, one for each account.

LevelMediumStatusExperimentalLog sourceAzure Activity log
title: Storage Account Object Replication Policy Created or Changed
id: 041fc969-feb4-4978-89e5-3500446bf1a5
status: experimental
description: >-
  Detects a successful create or update of an object replication policy on a
  storage account
  (Microsoft.Storage/storageAccounts/objectReplicationPolicies/write). Once
  the policy exists on the source account, Azure Storage copies the block
  blobs of the paired containers to the destination account, which can be in
  another subscription or, where the account allows it, in another Microsoft
  Entra tenant. Microsoft states that the permission to configure object
  replication also grants the ability to copy data between the two accounts.
  The event does not name the other account, so read the policy after the
  rule fires. A setup inside your own subscriptions produces two events, one
  for each account.
references:
  - https://attack.mitre.org/techniques/T1537/
  - https://learn.microsoft.com/en-us/azure/storage/blobs/object-replication-overview
  - https://learn.microsoft.com/en-us/azure/storage/blobs/object-replication-configure
  - https://learn.microsoft.com/en-us/azure/role-based-access-control/permissions/storage
author: Forestall
date: 2026-11-18
tags:
  - attack.exfiltration
  - attack.t1537
logsource:
  product: azure
  service: activitylogs
detection:
  selection:
    OperationNameValue: MICROSOFT.STORAGE/STORAGEACCOUNTS/OBJECTREPLICATIONPOLICIES/WRITE
    ActivityStatusValue:
      - Success
      - Succeeded
  condition: selection
falsepositives:
  - Planned replication for disaster recovery, latency or data distribution, usually set up once by a platform team or an infrastructure-as-code pipeline. Match the event to a change record and exclude the deployment identities in a filter_ selection by Caller once confirmed.
level: medium

False positives

  • Planned replication for disaster recovery, latency or data distribution, usually set up once by a platform team or an infrastructure-as-code pipeline. Match the event to a change record and exclude the deployment identities in a filter_ selection by Caller once confirmed.

Detection logic

Patterns that need more than one event, a baseline or knowledge of your own environment. Each is a hypothesis to build and tune in your SIEM, not a ready rule.

Replication policy whose destination is outside your own accounts

Detection hypothesisCompares with an earlier valueNeeds your own lists

Replication between two accounts of the same team is disaster recovery. Replication to an account in another subscription group or another tenant is a data flow out of the organization. The write event is the same for both, and only the policy resource names the two accounts.

  1. In the Azure Activity log, find MICROSOFT.STORAGE/STORAGEACCOUNTS/OBJECTREPLICATIONPOLICIES/WRITE with status Success. Keep the Caller and the resource ID of the storage account.
  2. Read the policy resource and take sourceAccount and destinationAccount from its properties.
  3. Compare both with your own list of subscriptions and storage accounts. Flag a policy whose destination is not on the list.
  4. Read the AllowCrossTenantReplication property of the storage account and check whether an earlier MICROSOFT.STORAGE/STORAGEACCOUNTS/WRITE by the same Caller could have changed it.

EventsMICROSOFT.STORAGE/STORAGEACCOUNTS/OBJECTREPLICATIONPOLICIES/WRITEMICROSOFT.STORAGE/STORAGEACCOUNTS/WRITE

LimitsIt needs a job that reads the policy after the event and your own inventory of accounts. Microsoft documents that the account fields hold a full resource ID when cross-tenant replication is disallowed and may hold only an account name otherwise, and a bare name does not show the tenant. The storage account write event does not say which property changed.

Triage

  • Identify the Caller, the caller's IP address and the storage account, and whether the account is the source or the destination of the policy.
  • Read the policy on the account. Its properties name the source account, the destination account and the container rules.
  • Find out who owns the other account. A destination outside your subscriptions or your tenant is the case that matters most.
  • Check what the source containers hold, and when the policy was enabled on the source account.
  • Look at what the caller changed on the account before the policy, such as blob versioning, the change feed or the cross-tenant replication setting.

Response

Once the attack is confirmed:

  1. Delete the replication policy on the source account, which stops the copying.
  2. Contain the caller. Revoke its sessions, rotate its credentials and remove its role on the storage account.
  3. If the destination account is in your tenant, secure it and review who read from it. If it is outside your tenant, treat every blob in the replicated containers since the policy was enabled as disclosed.
  4. Set AllowCrossTenantReplication to false on the account once no approved cross-tenant policy needs it.
  5. Rotate secrets that were stored in the replicated blobs, and assess what data was copied for notification duties.

Mitigation

  • Set AllowCrossTenantReplication to false on every storage account, and enforce it with Azure Policy. Accounts created before 15 December 2023 allow cross-tenant replication unless the property is set.
  • Limit Contributor, Storage Account Contributor and Owner on storage accounts that hold sensitive data, and assign them through Privileged Identity Management.
  • Keep an inventory of the replication policies each account should have, and compare it with the policies that exist.
  • Send the Azure Activity log to your SIEM, so a new policy is seen when it is created.

Frequently asked questions

Does the storage account's resource log show the attacker reading the blobs?

No. Object replication is carried out by Azure Storage itself, which reads the change feed of the source account and copies the blobs. There is no download by the attacker's identity to find. The control-plane write of the policy in the Azure Activity log is the event that shows the setup.

Can data be replicated to a storage account in another tenant?

Yes, if the source account allows it. Microsoft documents that cross-tenant object replication is disabled by default for storage accounts created after 15 December 2023. An account created before that date can take part in cross-tenant policies while its AllowCrossTenantReplication property is not set or is true. Setting the property to false prevents new cross-tenant policies.

Why does the rule fire twice for one replication setup?

A replication policy is created on the destination account first and then, with the same policy ID, on the source account. Each of the two writes is its own Activity log event in the subscription of that account. If both accounts are in subscriptions you collect from, you see both. If the destination is outside, you only see the write on your source account.

Is there a public incident that used object replication to take data?

No public incident report was found that describes it at the level of the audit event. The page is based on what Microsoft documents about the feature, including its statement that the permission to configure object replication also grants the ability to copy data between the two accounts.

References

We respect your privacy

We use cookies to keep this site secure and working properly. With your permission, we also use optional cookies to understand usage and improve the experience. Cookie Policy

You can change your choice at any time.