Validate the database connection before adding a highly available RDS broker

Source facts

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.

Applicability

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.

DSE recommendation

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.

Verification

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.

Official references

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