{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/validate-dns-responses-based-on-time-of-day-with-an-azure-cloud-app-server-with-ad-dns-evidence/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/validate-dns-responses-based-on-time-of-day-with-an-azure-cloud-app-server-with-ad-dns-evidence/",
        "slug": "validate-dns-responses-based-on-time-of-day-with-an-azure-cloud-app-server-with-ad-dns-evidence",
        "url": "https://update.dsesecurity.com/updates/validate-dns-responses-based-on-time-of-day-with-an-azure-cloud-app-server-with-ad-dns-evidence/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/validate-dns-responses-based-on-time-of-day-with-an-azure-cloud-app-server-with-ad-dns-evidence.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/validate-dns-responses-based-on-time-of-day-with-an-azure-cloud-app-server-with-ad-dns-evidence/"
        },
        "title": "Validate DNS Responses Based on Time of Day with an Azure Cloud App Server with AD/DNS evidence",
        "summary": "Use DNS Responses Based on Time of Day with an Azure Cloud App Server to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "checklist",
            "name": "Checklist"
        },
        "priority": {
            "slug": "advisory",
            "name": "Advisory"
        },
        "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": "microsoft-365-identity",
                "name": "Microsoft 365 & Identity",
                "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/"
            },
            {
                "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-08-27T17:05:44+00:00",
        "modified_at": "2026-08-27T17:14:53+00:00",
        "reviewed_on": "2026-08-27",
        "reading_minutes": 3,
        "word_count": 595,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of DNS Responses Based on Time of Day with an Azure Cloud App Server",
        "dse_recommendation": "Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards.",
        "primary_source": {
            "name": "DNS Responses Based on Time of Day with an Azure Cloud App Server",
            "url": "https://learn.microsoft.com/en-us/windows-server/networking/dns/deploy/dns-tod-azure-cloud-app-server",
            "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": "<p>Treat this document as a focused evidence review: Validate DNS Responses Based on Time of Day with an Azure Cloud App Server with AD/DNS evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.</p>\n<h2>Source fact:</h2>\n<p>The official <a href=\"https://learn.microsoft.com/en-us/windows-server/networking/dns/deploy/dns-tod-azure-cloud-app-server\" target=\"_blank\" rel=\"noopener noreferrer\">DNS Responses Based on Time of Day with an Azure Cloud App Server</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>At Introduction below H1, Microsoft states: “You can use this topic to learn how to distribute application traffic across different geographically distributed instances of an application by using DNS policies that are based on the time of day.” The research record locates this support at <strong>Introduction below H1</strong>.</li>\n<li>At Introduction below H1, Microsoft states: “This allows you to load balance traffic across application instances during peak time periods when your primary servers are overloaded with traffic.” The research record locates this support at <strong>Introduction below H1</strong>.</li>\n</ul>\n<p>These statements are the factual basis for this document. Do not extend them into a broader assurance. Review Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles only where the source and recorded environment align.</p>\n<h2>What the source does not establish</h2>\n<p>The cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution, ownership, and change authority instead of treating documented behavior as a deployment guarantee.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>Introduction below H1</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>Introduction below H1</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Within Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles, which versions, roles, and configuration states define the review population?</li>\n<li>Could Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution invalidate the test, hide a failure, or change applicability?</li>\n<li>Who owns the decision, and which observation requires stopping, escalation, or rollback?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>DSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles, observed and expected states, owner, and reason for deviation.</p>\n<p>If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution and sanitize protected material before retention.</p>\n<h2>Verification and evidence</h2>\n<p>Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations <strong>Introduction below H1</strong>; <strong>Introduction below H1</strong>. Favor PowerShell exports, zone and policy inventories, sanitized query tests, event-channel data, replication state, and rollback commands, linked to stable identifiers, time, and operator.</p>\n<p>Label this evidence set <strong>DSE-20260827-102</strong> so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.</p>\n<p>Keep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://learn.microsoft.com/en-us/windows-server/networking/dns/deploy/dns-tod-azure-cloud-app-server\" target=\"_blank\" rel=\"noopener noreferrer\">DNS Responses Based on Time of Day with an Azure Cloud App Server</a> — Microsoft</li>\n</ul>",
        "content_text": "Treat this document as a focused evidence review: Validate DNS Responses Based on Time of Day with an Azure Cloud App Server with AD/DNS evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official DNS Responses Based on Time of Day with an Azure Cloud App Server from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “You can use this topic to learn how to distribute application traffic across different geographically distributed instances of an application by using DNS policies that are based on the time of day.” The research record locates this support at Introduction below H1.\nAt Introduction below H1, Microsoft states: “This allows you to load balance traffic across application instances during peak time periods when your primary servers are overloaded with traffic.” The research record locates this support at Introduction below H1.\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles only where the source and recorded environment align.\nWhat the source does not establish\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution, ownership, and change authority instead of treating documented behavior as a deployment guarantee.\nApplicability questions\n\nFor source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nWithin Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles, which versions, roles, and configuration states define the review population?\nCould Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution invalidate the test, hide a failure, or change applicability?\nWho owns the decision, and which observation requires stopping, escalation, or rollback?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles, observed and expected states, owner, and reason for deviation.\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution and sanitize protected material before retention.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Introduction below H1; Introduction below H1. Favor PowerShell exports, zone and policy inventories, sanitized query tests, event-channel data, replication state, and rollback commands, linked to stable identifiers, time, and operator.\nLabel this evidence set DSE-20260827-102 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nKeep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.\nOfficial references\n\nDNS Responses Based on Time of Day with an Azure Cloud App Server — Microsoft",
        "content_markdown": "Treat this document as a focused evidence review: Validate DNS Responses Based on Time of Day with an Azure Cloud App Server with AD/DNS evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [DNS Responses Based on Time of Day with an Azure Cloud App Server](https://learn.microsoft.com/en-us/windows-server/networking/dns/deploy/dns-tod-azure-cloud-app-server) from Microsoft supports the following bounded statements:\n\n- At Introduction below H1, Microsoft states: “You can use this topic to learn how to distribute application traffic across different geographically distributed instances of an application by using DNS policies that are based on the time of day.” The research record locates this support at Introduction below H1.\n\n- At Introduction below H1, Microsoft states: “This allows you to load balance traffic across application instances during peak time periods when your primary servers are overloaded with traffic.” The research record locates this support at Introduction below H1.\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles only where the source and recorded environment align.\n\n## What the source does not establish\n\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution, ownership, and change authority instead of treating documented behavior as a deployment guarantee.\n\n## Applicability questions\n\n- For source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\n\n- Within Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles, which versions, roles, and configuration states define the review population?\n\n- Could Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution invalidate the test, hide a failure, or change applicability?\n\n- Who owns the decision, and which observation requires stopping, escalation, or rollback?\n\n## DSE recommendation:\n\nDSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles, observed and expected states, owner, and reason for deviation.\n\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution and sanitize protected material before retention.\n\n## Verification and evidence\n\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Introduction below H1; Introduction below H1. Favor PowerShell exports, zone and policy inventories, sanitized query tests, event-channel data, replication state, and rollback commands, linked to stable identifiers, time, and operator.\n\nLabel this evidence set DSE-20260827-102 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\n\nKeep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.\n\n## Official references\n\n- [DNS Responses Based on Time of Day with an Azure Cloud App Server](https://learn.microsoft.com/en-us/windows-server/networking/dns/deploy/dns-tod-azure-cloud-app-server) — Microsoft"
    },
    "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/validate-dns-responses-based-on-time-of-day-with-an-azure-cloud-app-server-with-ad-dns-evidence/",
                "url": "https://update.dsesecurity.com/updates/validate-dns-responses-based-on-time-of-day-with-an-azure-cloud-app-server-with-ad-dns-evidence/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-27"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/validate-dns-responses-based-on-time-of-day-with-an-azure-cloud-app-server-with-ad-dns-evidence/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Validate DNS Responses Based on Time of Day with an Azure Cloud App Server with AD/DNS evidence",
                        "item": "https://update.dsesecurity.com/updates/validate-dns-responses-based-on-time-of-day-with-an-azure-cloud-app-server-with-ad-dns-evidence/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/validate-dns-responses-based-on-time-of-day-with-an-azure-cloud-app-server-with-ad-dns-evidence/#article",
                "identifier": "https://update.dsesecurity.com/updates/validate-dns-responses-based-on-time-of-day-with-an-azure-cloud-app-server-with-ad-dns-evidence/",
                "url": "https://update.dsesecurity.com/updates/validate-dns-responses-based-on-time-of-day-with-an-azure-cloud-app-server-with-ad-dns-evidence/",
                "headline": "Validate DNS Responses Based on Time of Day with an Azure Cloud App Server with AD/DNS evidence",
                "description": "Use DNS Responses Based on Time of Day with an Azure Cloud App Server to review this narrow operational decision without extending the source beyond…",
                "abstract": "Use DNS Responses Based on Time of Day with an Azure Cloud App Server to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Treat this document as a focused evidence review: Validate DNS Responses Based on Time of Day with an Azure Cloud App Server with AD/DNS evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official DNS Responses Based on Time of Day with an Azure Cloud App Server from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “You can use this topic to learn how to distribute application traffic across different geographically distributed instances of an application by using DNS policies that are based on the time of day.” The research record locates this support at Introduction below H1.\nAt Introduction below H1, Microsoft states: “This allows you to load balance traffic across application instances during peak time periods when your primary servers are overloaded with traffic.” The research record locates this support at Introduction below H1.\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles only where the source and recorded environment align.\nWhat the source does not establish\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution, ownership, and change authority instead of treating documented behavior as a deployment guarantee.\nApplicability questions\n\nFor source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nWithin Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles, which versions, roles, and configuration states define the review population?\nCould Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution invalidate the test, hide a failure, or change applicability?\nWho owns the decision, and which observation requires stopping, escalation, or rollback?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of Windows DNS servers, AD-integrated zones, policies, forwarders, logging channels, clients, and administrative roles, observed and expected states, owner, and reason for deviation.\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory replication, domain-controller health, service accounts, routing, time, certificates, and upstream resolution and sanitize protected material before retention.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Introduction below H1; Introduction below H1. Favor PowerShell exports, zone and policy inventories, sanitized query tests, event-channel data, replication state, and rollback commands, linked to stable identifiers, time, and operator.\nLabel this evidence set DSE-20260827-102 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nKeep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.\nOfficial references\n\nDNS Responses Based on Time of Day with an Azure Cloud App Server — Microsoft",
                "datePublished": "2026-08-27T17:05:44+00:00",
                "dateModified": "2026-08-27T17:14:53+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/validate-dns-responses-based-on-time-of-day-with-an-azure-cloud-app-server-with-ad-dns-evidence/"
                },
                "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/validate-dns-responses-based-on-time-of-day-with-an-azure-cloud-app-server-with-ad-dns-evidence/#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": "Validate DNS Responses Based on Time of Day with an Azure Cloud App Server with AD/DNS evidence"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure",
                    "Checklist",
                    "Advisory priority"
                ],
                "genre": "Checklist",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Microsoft 365 & Identity",
                        "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 595,
                "timeRequired": "PT3M",
                "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": "DNS Responses Based on Time of Day with an Azure Cloud App Server",
                    "url": "https://learn.microsoft.com/en-us/windows-server/networking/dns/deploy/dns-tod-azure-cloud-app-server"
                }
            }
        ]
    }
}