{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-383-complete-both-sides-of-a-json-based-blob-object-replication-policy/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-383-complete-both-sides-of-a-json-based-blob-object-replication-policy/", "slug": "dse-20260909-383-complete-both-sides-of-a-json-based-blob-object-replication-policy", "url": "https://update.dsesecurity.com/updates/dse-20260909-383-complete-both-sides-of-a-json-based-blob-object-replication-policy/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-383-complete-both-sides-of-a-json-based-blob-object-replication-policy.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-383-complete-both-sides-of-a-json-based-blob-object-replication-policy/" }, "title": "Complete both sides of a JSON-based Blob object-replication policy", "summary": "Creating a destination policy does not automatically configure the source; both sides must use the destination-generated policy ID.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "cybersecurity", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-10T00:25:33+00:00", "modified_at": "2026-09-10T02:01:56+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 228, "potentially_affected": "Azure block-blob object replication configured through separate source and destination account owners.", "dse_recommendation": "Track the destination policy and matching source configuration as one coordinated handoff.", "primary_source": { "name": "Configure object replication - Azure Storage | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/storage/blobs/object-replication-configure", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

In the JSON workflow, Azure generates the destination policy ID and includes it in the downloaded definition. The source account must use that same ID. Uploading the destination definition through the portal does not create its source counterpart; the source policy must exist before replication starts.

\n

Object replication requires versioning on both accounts and change feed on the source. A source blob’s object-replication properties are populated only after replication completes or fails, so an empty status is not proof of completed copying. Microsoft Learn.

\n

Applicability

\n

Identify both account owners, approved containers, policy rules and applicable account support. This brief excludes the separate preview for replicating blob index tags.

\n

DSE recommendation

\n

DSE recommends a handoff record containing the reviewed destination policy and the corresponding source import. Confirm the actual account and container identities before applying it, especially across administrative boundaries. Keep permission to configure replication tied to approval for the resulting data copy. Do not close the task when only one owner’s portal operation succeeds.

\n

Verification

\n

Use an approved harmless blob that meets the configured rules. Compare both policy IDs, then verify the source’s eventual replication result and the intended destination object. Preserve failure or incomplete status explicitly and investigate missing policy or container dependencies. Avoid broadening the selected containers merely to make a test object appear.

\n

Official references

\n

Microsoft Learn: Configure object replication. Source retrieved September 9, 2026.

", "content_text": "Source facts\nIn the JSON workflow, Azure generates the destination policy ID and includes it in the downloaded definition. The source account must use that same ID. Uploading the destination definition through the portal does not create its source counterpart; the source policy must exist before replication starts.\nObject replication requires versioning on both accounts and change feed on the source. A source blob’s object-replication properties are populated only after replication completes or fails, so an empty status is not proof of completed copying. Microsoft Learn.\nApplicability\nIdentify both account owners, approved containers, policy rules and applicable account support. This brief excludes the separate preview for replicating blob index tags.\nDSE recommendation\nDSE recommends a handoff record containing the reviewed destination policy and the corresponding source import. Confirm the actual account and container identities before applying it, especially across administrative boundaries. Keep permission to configure replication tied to approval for the resulting data copy. Do not close the task when only one owner’s portal operation succeeds.\nVerification\nUse an approved harmless blob that meets the configured rules. Compare both policy IDs, then verify the source’s eventual replication result and the intended destination object. Preserve failure or incomplete status explicitly and investigate missing policy or container dependencies. Avoid broadening the selected containers merely to make a test object appear.\nOfficial references\nMicrosoft Learn: Configure object replication. Source retrieved September 9, 2026.", "content_markdown": "## Source facts\n\nIn the JSON workflow, Azure generates the destination policy ID and includes it in the downloaded definition. The source account must use that same ID. Uploading the destination definition through the portal does not create its source counterpart; the source policy must exist before replication starts.\n\nObject replication requires versioning on both accounts and change feed on the source. A source blob’s object-replication properties are populated only after replication completes or fails, so an empty status is not proof of completed copying. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/storage/blobs/object-replication-configure).\n\n## Applicability\n\nIdentify both account owners, approved containers, policy rules and applicable account support. This brief excludes the separate preview for replicating blob index tags.\n\n## DSE recommendation\n\nDSE recommends a handoff record containing the reviewed destination policy and the corresponding source import. Confirm the actual account and container identities before applying it, especially across administrative boundaries. Keep permission to configure replication tied to approval for the resulting data copy. Do not close the task when only one owner’s portal operation succeeds.\n\n## Verification\n\nUse an approved harmless blob that meets the configured rules. Compare both policy IDs, then verify the source’s eventual replication result and the intended destination object. Preserve failure or incomplete status explicitly and investigate missing policy or container dependencies. Avoid broadening the selected containers merely to make a test object appear.\n\n## Official references\n\n[Microsoft Learn: Configure object replication](https://learn.microsoft.com/en-us/azure/storage/blobs/object-replication-configure). Source retrieved September 9, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260909-383-complete-both-sides-of-a-json-based-blob-object-replication-policy/", "url": "https://update.dsesecurity.com/updates/dse-20260909-383-complete-both-sides-of-a-json-based-blob-object-replication-policy/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-383-complete-both-sides-of-a-json-based-blob-object-replication-policy/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Complete both sides of a JSON-based Blob object-replication policy", "item": "https://update.dsesecurity.com/updates/dse-20260909-383-complete-both-sides-of-a-json-based-blob-object-replication-policy/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-383-complete-both-sides-of-a-json-based-blob-object-replication-policy/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-383-complete-both-sides-of-a-json-based-blob-object-replication-policy/", "url": "https://update.dsesecurity.com/updates/dse-20260909-383-complete-both-sides-of-a-json-based-blob-object-replication-policy/", "headline": "Complete both sides of a JSON-based Blob object-replication policy", "description": "Creating a destination policy does not automatically configure the source; both sides must use the destination-generated policy ID.", "abstract": "Creating a destination policy does not automatically configure the source; both sides must use the destination-generated policy ID.", "articleBody": "Source facts\nIn the JSON workflow, Azure generates the destination policy ID and includes it in the downloaded definition. The source account must use that same ID. Uploading the destination definition through the portal does not create its source counterpart; the source policy must exist before replication starts.\nObject replication requires versioning on both accounts and change feed on the source. A source blob’s object-replication properties are populated only after replication completes or fails, so an empty status is not proof of completed copying. Microsoft Learn.\nApplicability\nIdentify both account owners, approved containers, policy rules and applicable account support. This brief excludes the separate preview for replicating blob index tags.\nDSE recommendation\nDSE recommends a handoff record containing the reviewed destination policy and the corresponding source import. Confirm the actual account and container identities before applying it, especially across administrative boundaries. Keep permission to configure replication tied to approval for the resulting data copy. Do not close the task when only one owner’s portal operation succeeds.\nVerification\nUse an approved harmless blob that meets the configured rules. Compare both policy IDs, then verify the source’s eventual replication result and the intended destination object. Preserve failure or incomplete status explicitly and investigate missing policy or container dependencies. Avoid broadening the selected containers merely to make a test object appear.\nOfficial references\nMicrosoft Learn: Configure object replication. Source retrieved September 9, 2026.", "datePublished": "2026-09-10T00:25:33+00:00", "dateModified": "2026-09-10T02:01:56+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-383-complete-both-sides-of-a-json-based-blob-object-replication-policy/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260909-383-complete-both-sides-of-a-json-based-blob-object-replication-policy/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Complete both sides of a JSON-based Blob object-replication policy" }, "articleSection": [ "Cybersecurity", "Networks & Infrastructure" ], "keywords": [ "Cybersecurity", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 228, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Configure object replication - Azure Storage | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/storage/blobs/object-replication-configure" } } ] } }