{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-057-account-for-cache-misses-against-both-azure-vm-storage-limits/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260909-057-account-for-cache-misses-against-both-azure-vm-storage-limits/",
        "slug": "dse-20260909-057-account-for-cache-misses-against-both-azure-vm-storage-limits",
        "url": "https://update.dsesecurity.com/updates/dse-20260909-057-account-for-cache-misses-against-both-azure-vm-storage-limits/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260909-057-account-for-cache-misses-against-both-azure-vm-storage-limits.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-057-account-for-cache-misses-against-both-azure-vm-storage-limits/"
        },
        "title": "Account for cache misses against both Azure VM storage limits",
        "summary": "Why can a host-cached disk's read workload still consume a VM's uncached storage allowance?",
        "format": {
            "slug": "explainer",
            "name": "Explainer"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "featured": false,
        "image": {
            "theme": "managed-it",
            "label": "Managed IT operations",
            "alt": "A controlled technology lifecycle progressing from assessment to approved production.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/managed-it-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/managed-it-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "it",
                "name": "IT",
                "url": "https://update.dsesecurity.com/topic/it/"
            }
        ],
        "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:30:59+00:00",
        "modified_at": "2026-09-10T00:35:07+00:00",
        "reviewed_on": "2026-09-09",
        "reading_minutes": 2,
        "word_count": 249,
        "potentially_affected": "Azure VMs and managed disks supporting premium-storage host caching, with the actual cache mode identified.",
        "dse_recommendation": "Map the measured read path before deciding which storage limit needs attention.",
        "primary_source": {
            "name": "Virtual machine and disk performance - Azure Virtual Machines | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/disks-performance",
            "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": "<h2>Source facts</h2>\n<p>Azure VMs with premium storage and host caching have separate cached and uncached storage limits. A read satisfied by host cache counts against the cached limit. A cache miss must reach the disk and counts against both cached and uncached VM limits. Attached disks also have their own IOPS and throughput limits. Enabling caching therefore does not make every read independent of the remote disk path. <a href=\"https://learn.microsoft.com/en-us/azure/virtual-machines/disks-performance\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>Use this distinction when a read-heavy workload has host caching enabled but still appears constrained by uncached storage. Identify the VM size, disk configuration, actual cache mode, and whether the observed workload is reading data already present in cache.</p>\n<h2>DSE recommendation</h2>\n<p>Map the measured read path before deciding which storage limit needs attention. Ask the performance owner to distinguish cache-hit and cache-miss behavior and compare VM-level evidence with the affected disks. Keep observations from an already warmed workload separate from first-read behavior. Do not assume a higher disk tier or a cache setting alone resolves an unexplained limit.</p>\n<h2>Verification</h2>\n<p>Use a representative nonproduction workload to compare the relevant VM and disk metrics under controlled read conditions. Record the workload shape, cache configuration, measured latency, and which limit approaches saturation. Change one relevant condition at a time and compare results with the proposed explanation. If the observed bottleneck moves between cached and uncached paths, preserve that finding rather than combining the results into one unexplained throughput number.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/azure/virtual-machines/disks-performance\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Virtual machine and disk performance</a>. Source reviewed September 9, 2026.</p>",
        "content_text": "Source facts\nAzure VMs with premium storage and host caching have separate cached and uncached storage limits. A read satisfied by host cache counts against the cached limit. A cache miss must reach the disk and counts against both cached and uncached VM limits. Attached disks also have their own IOPS and throughput limits. Enabling caching therefore does not make every read independent of the remote disk path. Microsoft Learn.\nApplicability\nUse this distinction when a read-heavy workload has host caching enabled but still appears constrained by uncached storage. Identify the VM size, disk configuration, actual cache mode, and whether the observed workload is reading data already present in cache.\nDSE recommendation\nMap the measured read path before deciding which storage limit needs attention. Ask the performance owner to distinguish cache-hit and cache-miss behavior and compare VM-level evidence with the affected disks. Keep observations from an already warmed workload separate from first-read behavior. Do not assume a higher disk tier or a cache setting alone resolves an unexplained limit.\nVerification\nUse a representative nonproduction workload to compare the relevant VM and disk metrics under controlled read conditions. Record the workload shape, cache configuration, measured latency, and which limit approaches saturation. Change one relevant condition at a time and compare results with the proposed explanation. If the observed bottleneck moves between cached and uncached paths, preserve that finding rather than combining the results into one unexplained throughput number.\nOfficial references\nMicrosoft Learn: Virtual machine and disk performance. Source reviewed September 9, 2026.",
        "content_markdown": "## Source facts\n\nAzure VMs with premium storage and host caching have separate cached and uncached storage limits. A read satisfied by host cache counts against the cached limit. A cache miss must reach the disk and counts against both cached and uncached VM limits. Attached disks also have their own IOPS and throughput limits. Enabling caching therefore does not make every read independent of the remote disk path. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-performance).\n\n## Applicability\n\nUse this distinction when a read-heavy workload has host caching enabled but still appears constrained by uncached storage. Identify the VM size, disk configuration, actual cache mode, and whether the observed workload is reading data already present in cache.\n\n## DSE recommendation\n\nMap the measured read path before deciding which storage limit needs attention. Ask the performance owner to distinguish cache-hit and cache-miss behavior and compare VM-level evidence with the affected disks. Keep observations from an already warmed workload separate from first-read behavior. Do not assume a higher disk tier or a cache setting alone resolves an unexplained limit.\n\n## Verification\n\nUse a representative nonproduction workload to compare the relevant VM and disk metrics under controlled read conditions. Record the workload shape, cache configuration, measured latency, and which limit approaches saturation. Change one relevant condition at a time and compare results with the proposed explanation. If the observed bottleneck moves between cached and uncached paths, preserve that finding rather than combining the results into one unexplained throughput number.\n\n## Official references\n\n[Microsoft Learn: Virtual machine and disk performance](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-performance). Source reviewed 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-057-account-for-cache-misses-against-both-azure-vm-storage-limits/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-057-account-for-cache-misses-against-both-azure-vm-storage-limits/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-09"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-057-account-for-cache-misses-against-both-azure-vm-storage-limits/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Account for cache misses against both Azure VM storage limits",
                        "item": "https://update.dsesecurity.com/updates/dse-20260909-057-account-for-cache-misses-against-both-azure-vm-storage-limits/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-057-account-for-cache-misses-against-both-azure-vm-storage-limits/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260909-057-account-for-cache-misses-against-both-azure-vm-storage-limits/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-057-account-for-cache-misses-against-both-azure-vm-storage-limits/",
                "headline": "Account for cache misses against both Azure VM storage limits",
                "description": "Why can a host-cached disk's read workload still consume a VM's uncached storage allowance?",
                "abstract": "Why can a host-cached disk's read workload still consume a VM's uncached storage allowance?",
                "articleBody": "Source facts\nAzure VMs with premium storage and host caching have separate cached and uncached storage limits. A read satisfied by host cache counts against the cached limit. A cache miss must reach the disk and counts against both cached and uncached VM limits. Attached disks also have their own IOPS and throughput limits. Enabling caching therefore does not make every read independent of the remote disk path. Microsoft Learn.\nApplicability\nUse this distinction when a read-heavy workload has host caching enabled but still appears constrained by uncached storage. Identify the VM size, disk configuration, actual cache mode, and whether the observed workload is reading data already present in cache.\nDSE recommendation\nMap the measured read path before deciding which storage limit needs attention. Ask the performance owner to distinguish cache-hit and cache-miss behavior and compare VM-level evidence with the affected disks. Keep observations from an already warmed workload separate from first-read behavior. Do not assume a higher disk tier or a cache setting alone resolves an unexplained limit.\nVerification\nUse a representative nonproduction workload to compare the relevant VM and disk metrics under controlled read conditions. Record the workload shape, cache configuration, measured latency, and which limit approaches saturation. Change one relevant condition at a time and compare results with the proposed explanation. If the observed bottleneck moves between cached and uncached paths, preserve that finding rather than combining the results into one unexplained throughput number.\nOfficial references\nMicrosoft Learn: Virtual machine and disk performance. Source reviewed September 9, 2026.",
                "datePublished": "2026-09-10T00:30:59+00:00",
                "dateModified": "2026-09-10T00:35:07+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260909-057-account-for-cache-misses-against-both-azure-vm-storage-limits/"
                },
                "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-057-account-for-cache-misses-against-both-azure-vm-storage-limits/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Account for cache misses against both Azure VM storage limits"
                },
                "articleSection": [
                    "IT"
                ],
                "keywords": [
                    "IT",
                    "Explainer",
                    "Information priority"
                ],
                "genre": "Explainer",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "IT",
                        "url": "https://update.dsesecurity.com/topic/it/"
                    }
                ],
                "wordCount": 249,
                "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": "Virtual machine and disk performance - Azure Virtual Machines | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/disks-performance"
                }
            }
        ]
    }
}