{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-120-validate-the-database-connection-before-adding-a-highly-available-rds-broker/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-120-validate-the-database-connection-before-adding-a-highly-available-rds-broker/", "slug": "dse-20260908-120-validate-the-database-connection-before-adding-a-highly-available-rds-broker", "url": "https://update.dsesecurity.com/updates/dse-20260908-120-validate-the-database-connection-before-adding-a-highly-available-rds-broker/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-120-validate-the-database-connection-before-adding-a-highly-available-rds-broker.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-120-validate-the-database-connection-before-adding-a-highly-available-rds-broker/" }, "title": "Validate the database connection before adding a highly available RDS broker", "summary": "Which database and driver details must be established for RD Connection Broker high availability?", "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": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "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-08T18:15:11+00:00", "modified_at": "2026-09-08T18:23:27+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 202, "potentially_affected": "Administrators preparing RD Connection Broker high availability.", "dse_recommendation": "Create a database-connection record containing the approved server and database identities and the required driver version.", "primary_source": { "name": "Configure RD Connection Broker for High Availability", "url": "https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-connection-broker-cluster", "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

Microsoft’s broker availability procedure requires a database and permits either Azure SQL Database or SQL Server in the local environment. The administrator must obtain the connection string and identify the appropriate ODBC driver. Microsoft uses the string both to determine the driver requirement and later to configure the broker. The procedure then adds the new RD Connection Broker server to the managed server inventory. Microsoft documentation.

\n

Applicability

\n

Identify the current broker deployment, intended database, database owner, driver, and management hosts. Review the full prerequisite list and the correct configuration path for the selected database service.

\n

DSE recommendation

\n

Create a database-connection record containing the approved server and database identities and the required driver version. Handle credentials and connection details through the organization’s protected configuration process. Have the RDS and database owners jointly approve connectivity before adding another broker.

\n

Verification

\n

Check the installed driver and test the approved connection from the intended broker hosts. Complete a controlled broker availability exercise and verify new-session placement and reconnection. Preserve database and broker observations from the same test window, and resolve connectivity exceptions before relying on the second broker.

\n

Official references

\n

Microsoft Learn: Configure RD Connection Broker for High Availability. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft’s broker availability procedure requires a database and permits either Azure SQL Database or SQL Server in the local environment. The administrator must obtain the connection string and identify the appropriate ODBC driver. Microsoft uses the string both to determine the driver requirement and later to configure the broker. The procedure then adds the new RD Connection Broker server to the managed server inventory. Microsoft documentation.\nApplicability\nIdentify the current broker deployment, intended database, database owner, driver, and management hosts. Review the full prerequisite list and the correct configuration path for the selected database service.\nDSE recommendation\nCreate a database-connection record containing the approved server and database identities and the required driver version. Handle credentials and connection details through the organization’s protected configuration process. Have the RDS and database owners jointly approve connectivity before adding another broker.\nVerification\nCheck the installed driver and test the approved connection from the intended broker hosts. Complete a controlled broker availability exercise and verify new-session placement and reconnection. Preserve database and broker observations from the same test window, and resolve connectivity exceptions before relying on the second broker.\nOfficial references\nMicrosoft Learn: Configure RD Connection Broker for High Availability. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft’s broker availability procedure requires a database and permits either Azure SQL Database or SQL Server in the local environment. The administrator must obtain the connection string and identify the appropriate ODBC driver. Microsoft uses the string both to determine the driver requirement and later to configure the broker. The procedure then adds the new RD Connection Broker server to the managed server inventory. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-connection-broker-cluster).\n\n## Applicability\n\nIdentify the current broker deployment, intended database, database owner, driver, and management hosts. Review the full prerequisite list and the correct configuration path for the selected database service.\n\n## DSE recommendation\n\nCreate a database-connection record containing the approved server and database identities and the required driver version. Handle credentials and connection details through the organization’s protected configuration process. Have the RDS and database owners jointly approve connectivity before adding another broker.\n\n## Verification\n\nCheck the installed driver and test the approved connection from the intended broker hosts. Complete a controlled broker availability exercise and verify new-session placement and reconnection. Preserve database and broker observations from the same test window, and resolve connectivity exceptions before relying on the second broker.\n\n## Official references\n\n[Microsoft Learn: Configure RD Connection Broker for High Availability](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-connection-broker-cluster). Source reviewed September 8, 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-20260908-120-validate-the-database-connection-before-adding-a-highly-available-rds-broker/", "url": "https://update.dsesecurity.com/updates/dse-20260908-120-validate-the-database-connection-before-adding-a-highly-available-rds-broker/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-120-validate-the-database-connection-before-adding-a-highly-available-rds-broker/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Validate the database connection before adding a highly available RDS broker", "item": "https://update.dsesecurity.com/updates/dse-20260908-120-validate-the-database-connection-before-adding-a-highly-available-rds-broker/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-120-validate-the-database-connection-before-adding-a-highly-available-rds-broker/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-120-validate-the-database-connection-before-adding-a-highly-available-rds-broker/", "url": "https://update.dsesecurity.com/updates/dse-20260908-120-validate-the-database-connection-before-adding-a-highly-available-rds-broker/", "headline": "Validate the database connection before adding a highly available RDS broker", "description": "Which database and driver details must be established for RD Connection Broker high availability?", "abstract": "Which database and driver details must be established for RD Connection Broker high availability?", "articleBody": "Source facts\nMicrosoft’s broker availability procedure requires a database and permits either Azure SQL Database or SQL Server in the local environment. The administrator must obtain the connection string and identify the appropriate ODBC driver. Microsoft uses the string both to determine the driver requirement and later to configure the broker. The procedure then adds the new RD Connection Broker server to the managed server inventory. Microsoft documentation.\nApplicability\nIdentify the current broker deployment, intended database, database owner, driver, and management hosts. Review the full prerequisite list and the correct configuration path for the selected database service.\nDSE recommendation\nCreate a database-connection record containing the approved server and database identities and the required driver version. Handle credentials and connection details through the organization’s protected configuration process. Have the RDS and database owners jointly approve connectivity before adding another broker.\nVerification\nCheck the installed driver and test the approved connection from the intended broker hosts. Complete a controlled broker availability exercise and verify new-session placement and reconnection. Preserve database and broker observations from the same test window, and resolve connectivity exceptions before relying on the second broker.\nOfficial references\nMicrosoft Learn: Configure RD Connection Broker for High Availability. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:15:11+00:00", "dateModified": "2026-09-08T18:23:27+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-120-validate-the-database-connection-before-adding-a-highly-available-rds-broker/" }, "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-20260908-120-validate-the-database-connection-before-adding-a-highly-available-rds-broker/#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 the database connection before adding a highly available RDS broker" }, "articleSection": [ "IT", "Networks & Infrastructure" ], "keywords": [ "IT", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 202, "timeRequired": "PT1M", "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 RD Connection Broker for High Availability", "url": "https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-connection-broker-cluster" } } ] } }