{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/stage-failure-when-you-use-an-existing-computer-account-to-join-a-domain-with-ad-dns-rollback-checks/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/stage-failure-when-you-use-an-existing-computer-account-to-join-a-domain-with-ad-dns-rollback-checks/",
        "slug": "stage-failure-when-you-use-an-existing-computer-account-to-join-a-domain-with-ad-dns-rollback-checks",
        "url": "https://update.dsesecurity.com/updates/stage-failure-when-you-use-an-existing-computer-account-to-join-a-domain-with-ad-dns-rollback-checks/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/stage-failure-when-you-use-an-existing-computer-account-to-join-a-domain-with-ad-dns-rollback-checks.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/stage-failure-when-you-use-an-existing-computer-account-to-join-a-domain-with-ad-dns-rollback-checks/"
        },
        "title": "Stage Failure When You Use an Existing Computer Account to Join a Domain with AD/DNS rollback checks",
        "summary": "Use Failure When You Use an Existing Computer Account to Join a Domain to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "explainer",
            "name": "Explainer"
        },
        "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-27T16:59:18+00:00",
        "modified_at": "2026-08-27T17:41:22+00:00",
        "reviewed_on": "2026-08-27",
        "reading_minutes": 3,
        "word_count": 594,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of Failure When You Use an Existing Computer Account to Join a Domain",
        "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": "Failure When You Use an Existing Computer Account to Join a Domain",
            "url": "https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/failure-when-you-use-an-existing-computer-account-to-join-a-domain",
            "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>Frame this document as a source-led configuration and assurance check: Stage Failure When You Use an Existing Computer Account to Join a Domain with AD/DNS rollback checks. 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/troubleshoot/windows-server/active-directory/failure-when-you-use-an-existing-computer-account-to-join-a-domain\" target=\"_blank\" rel=\"noopener noreferrer\">Failure When You Use an Existing Computer Account to Join a Domain</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>At Introduction below H1, Microsoft states: “This article addresses the issue of failing to join a computer to a domain when an existing computer account with the same name already exists.” The research record locates this support at <strong>Introduction below H1</strong>.</li>\n<li>At Symptoms, Microsoft states: “When you try to use an existing computer account name to join a computer to a domain, the operation fails and you receive the following error messages:” The research record locates this support at <strong>Symptoms</strong>.</li>\n</ul>\n<p>Keep the evidence boundary at these traced claims. They support a review of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services; they do not support conclusions outside the source&#8217;s stated conditions.</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, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, 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>Symptoms</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Which owner can attest to the recorded state of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, including exceptions?</li>\n<li>What baseline for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials must accompany the source-specific observation?</li>\n<li>Which success, stop, and escalation criteria are written before testing begins?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>DSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.</p>\n<p>An implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before and after the test, and store only sanitized operational evidence.</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>Symptoms</strong>. Favor sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state, linked to stable identifiers, time, and operator.</p>\n<p>Label this evidence set <strong>DSE-20260827-488</strong> so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.</p>\n<p>Retain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/failure-when-you-use-an-existing-computer-account-to-join-a-domain\" target=\"_blank\" rel=\"noopener noreferrer\">Failure When You Use an Existing Computer Account to Join a Domain</a> — Microsoft</li>\n</ul>",
        "content_text": "Frame this document as a source-led configuration and assurance check: Stage Failure When You Use an Existing Computer Account to Join a Domain with AD/DNS rollback checks. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Failure When You Use an Existing Computer Account to Join a Domain from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “This article addresses the issue of failing to join a computer to a domain when an existing computer account with the same name already exists.” The research record locates this support at Introduction below H1.\nAt Symptoms, Microsoft states: “When you try to use an existing computer account name to join a computer to a domain, the operation fails and you receive the following error messages:” The research record locates this support at Symptoms.\n\nKeep the evidence boundary at these traced claims. They support a review of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services; they do not support conclusions outside the source’s stated conditions.\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, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, 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 Symptoms, which observable configuration, record, or test can confirm applicability here?\nWhich owner can attest to the recorded state of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, including exceptions?\nWhat baseline for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials must accompany the source-specific observation?\nWhich success, stop, and escalation criteria are written before testing begins?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before and after the test, and store only sanitized operational evidence.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Introduction below H1; Symptoms. Favor sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state, linked to stable identifiers, time, and operator.\nLabel this evidence set DSE-20260827-488 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\nOfficial references\n\nFailure When You Use an Existing Computer Account to Join a Domain — Microsoft",
        "content_markdown": "Frame this document as a source-led configuration and assurance check: Stage Failure When You Use an Existing Computer Account to Join a Domain with AD/DNS rollback checks. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [Failure When You Use an Existing Computer Account to Join a Domain](https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/failure-when-you-use-an-existing-computer-account-to-join-a-domain) from Microsoft supports the following bounded statements:\n\n- At Introduction below H1, Microsoft states: “This article addresses the issue of failing to join a computer to a domain when an existing computer account with the same name already exists.” The research record locates this support at Introduction below H1.\n\n- At Symptoms, Microsoft states: “When you try to use an existing computer account name to join a computer to a domain, the operation fails and you receive the following error messages:” The research record locates this support at Symptoms.\n\nKeep the evidence boundary at these traced claims. They support a review of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services; they do not support conclusions outside the source’s stated conditions.\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, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, 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 Symptoms, which observable configuration, record, or test can confirm applicability here?\n\n- Which owner can attest to the recorded state of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, including exceptions?\n\n- What baseline for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials must accompany the source-specific observation?\n\n- Which success, stop, and escalation criteria are written before testing begins?\n\n## DSE recommendation:\n\nDSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.\n\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before and after the test, and store only sanitized operational evidence.\n\n## Verification and evidence\n\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Introduction below H1; Symptoms. Favor sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state, linked to stable identifiers, time, and operator.\n\nLabel this evidence set DSE-20260827-488 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\n\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\n\n## Official references\n\n- [Failure When You Use an Existing Computer Account to Join a Domain](https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/failure-when-you-use-an-existing-computer-account-to-join-a-domain) — 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/stage-failure-when-you-use-an-existing-computer-account-to-join-a-domain-with-ad-dns-rollback-checks/",
                "url": "https://update.dsesecurity.com/updates/stage-failure-when-you-use-an-existing-computer-account-to-join-a-domain-with-ad-dns-rollback-checks/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-27"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/stage-failure-when-you-use-an-existing-computer-account-to-join-a-domain-with-ad-dns-rollback-checks/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Stage Failure When You Use an Existing Computer Account to Join a Domain with AD/DNS rollback checks",
                        "item": "https://update.dsesecurity.com/updates/stage-failure-when-you-use-an-existing-computer-account-to-join-a-domain-with-ad-dns-rollback-checks/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/stage-failure-when-you-use-an-existing-computer-account-to-join-a-domain-with-ad-dns-rollback-checks/#article",
                "identifier": "https://update.dsesecurity.com/updates/stage-failure-when-you-use-an-existing-computer-account-to-join-a-domain-with-ad-dns-rollback-checks/",
                "url": "https://update.dsesecurity.com/updates/stage-failure-when-you-use-an-existing-computer-account-to-join-a-domain-with-ad-dns-rollback-checks/",
                "headline": "Stage Failure When You Use an Existing Computer Account to Join a Domain with AD/DNS rollback checks",
                "description": "Use Failure When You Use an Existing Computer Account to Join a Domain to review this narrow operational decision without extending the source beyond…",
                "abstract": "Use Failure When You Use an Existing Computer Account to Join a Domain to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Frame this document as a source-led configuration and assurance check: Stage Failure When You Use an Existing Computer Account to Join a Domain with AD/DNS rollback checks. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Failure When You Use an Existing Computer Account to Join a Domain from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “This article addresses the issue of failing to join a computer to a domain when an existing computer account with the same name already exists.” The research record locates this support at Introduction below H1.\nAt Symptoms, Microsoft states: “When you try to use an existing computer account name to join a computer to a domain, the operation fails and you receive the following error messages:” The research record locates this support at Symptoms.\n\nKeep the evidence boundary at these traced claims. They support a review of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services; they do not support conclusions outside the source’s stated conditions.\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, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, 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 Symptoms, which observable configuration, record, or test can confirm applicability here?\nWhich owner can attest to the recorded state of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, including exceptions?\nWhat baseline for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials must accompany the source-specific observation?\nWhich success, stop, and escalation criteria are written before testing begins?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before and after the test, and store only sanitized operational evidence.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Introduction below H1; Symptoms. Favor sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state, linked to stable identifiers, time, and operator.\nLabel this evidence set DSE-20260827-488 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\nOfficial references\n\nFailure When You Use an Existing Computer Account to Join a Domain — Microsoft",
                "datePublished": "2026-08-27T16:59:18+00:00",
                "dateModified": "2026-08-27T17:41:22+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/stage-failure-when-you-use-an-existing-computer-account-to-join-a-domain-with-ad-dns-rollback-checks/"
                },
                "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/stage-failure-when-you-use-an-existing-computer-account-to-join-a-domain-with-ad-dns-rollback-checks/#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": "Stage Failure When You Use an Existing Computer Account to Join a Domain with AD/DNS rollback checks"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure",
                    "Explainer",
                    "Advisory priority"
                ],
                "genre": "Explainer",
                "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": 594,
                "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": "Failure When You Use an Existing Computer Account to Join a Domain",
                    "url": "https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/failure-when-you-use-an-existing-computer-account-to-join-a-domain"
                }
            }
        ]
    }
}