--- title: "Availability replica is not joined | Microsoft Docs" ms.custom: "" ms.date: "01/09/2019" ms.prod: "sql-server-2014" ms.reviewer: "" ms.technology: high-availability ms.topic: conceptual f1_keywords: - "sql12.swb.agdashboard.arp4joined.issues.f1" helpviewer_keywords: - "Availability Groups [SQL Server], policies" ms.assetid: 9c0d10b1-9e12-430c-83b9-ca2bd0a3afc4 author: MashaMSFT ms.author: mathoma manager: craigg --- # Availability replica is not joined ## Introduction ||| |-|-| |**Policy Name**|Availability Replica Join State| |**Issue**|Availability Replica is not joined.| |**Category**|**Warning**| |**Facet**|Availability replica| ## Description This policy checks the join state of the availability replica. The policy is in an unhealthy state when the availability replica is added to the availability group, but is not joined properly. The policy is otherwise in a healthy state. > [!NOTE] > For this release of [!INCLUDE[ssCurrent](../../../includes/sscurrent-md.md)], information about possible causes and solutions is located at [Availability replica is not joined](https://go.microsoft.com/fwlink/p/?LinkId=220859) on the TechNet Wiki. ## Possible Causes The secondary replica is not joined to the availability group. For an availability replica to be successfully joined to the availability group, the join state must be Joined Standalone Instance (1) or Joined Failover Cluster (2). ## Possible Solution Use Transact-SQL, PowerShell, or SQL Server Management Studio to join the secondary replica to the availability group. For more information about joining secondary replicas to availability groups, see [Joining a Secondary Replica to an Availability Group (SQL Server)](https://msdn.microsoft.com/library/ff878473\(en-us,SQL.110\).aspx). ## See Also [Overview of AlwaysOn Availability Groups (SQL Server)](overview-of-always-on-availability-groups-sql-server.md) [Use the AlwaysOn Dashboard (SQL Server Management Studio)](use-the-always-on-dashboard-sql-server-management-studio.md)