> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-admin-guide/parallels-ras-21-administrators-guide/ras-multi-tenant-architecture/deploying-tenant-broker-and-tenants/deploying-a-tenant/verify-join-status.md).

# Verify join status

After you join a Tenant to the Tenant Broker, you should verify that the procedure was successful.

First, verify the Tenant Broker status in the Tenant console:

1. Log in to the Tenant Farm.
2. In the RAS Console, navigate to **Farm** > **Site** and select the **Site** tab in the right pane.
3. You should see the **Tenant Broker** section with the **Status** column, which should say **OK**. If the status is **Not verified**, make sure that the Tenant Broker is operational (or contact the Tenant Broker admin if you are not him or her).

You can also see additional Tenant Broker information by right-clicking it and choosing **Properties**. The information includes the following:

* **Name:** The Tenant Broker name.
* **Primary address:** The primary RAS Connection Broker address.
* **Secondary address:** The secondary RAS Connection Broker address (if available).

You should then verify the Tenant status in the Tenant Broker console:

1. Log in to the Tenant Broker.
2. In the RAS Console, navigate to **Farm** > **Tenants**.
3. In the **Tenants** tab, find the Tenant of interest and examine the **Status** column, which should say **OK** if the Tenant is joined properly. For other possible **Status** column values, see [**Tenant configuration**](/landing/ras-admin-guide/parallels-ras-21-administrators-guide/ras-multi-tenant-architecture/managing-tenants/tenant-configuration.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.parallels.com/landing/ras-admin-guide/parallels-ras-21-administrators-guide/ras-multi-tenant-architecture/deploying-tenant-broker-and-tenants/deploying-a-tenant/verify-join-status.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.