One of the most customer requested features in SQL, from as far back as SQL 2012, has been Always On Availability Groups. This takes disaster recovery and high availability to a new level by enabling multiple copies of the database to be highly available, enabling the possibility of Read-Only workloads and enabling the ability of offloading management tasks such as backups.  Unlike database mirroring, Always On Availability Groups allow for failover of a group of databases in a single SQL Server instance.    This step-by-step details the creation of a SQL Server 2016 / 2017 Always On Availability Group to ensure high availability of mission-critical databases.   Step 1: Windows Failover Cluster Feature Installation   The Windows Failover Cluster feature needs to be added to all machines running SQL Server instances that will be configured as replicas.  The following steps will add the feature to machines running Windows Server 2016:   Run the Server Manager console and select Add roles and features.  Once the Add Roles Features Wizard has launched, click Next until the Select Features dialog box has been reached.  Select the Failover Clustering checkbox.  Add Roles and Features Wizard  Select Add Features within the Add features that are required for Failover Clustering dialog box and click Next. Add Roles and Features Wizard   Click Next until the Confirm installation selections dialog box is reached and select Install.   Step 2: Enabling Windows Failover Clustering Configuration for SQL Server    At this point, proper Active Directory rights are required to configure the Windows Server Failover Cluster. Microsoft provides a complete listing of different Active Directory permissions able to create a Windows Server Failover Cluster. Take a moment to review the Step-By-Step Guide to Configuring Accounts in Active Directory for more details.   The following steps will configure Windows Failover Clustering:   Run Failover Cluster Manager found under Tools (top right) within the Server Manager Console.   Click Validate Configuration inside the Actions box. Failover Cluster Manager  Click Next in the Validate a Configuration Wizard: Before You Begin dialog box.  Add the server hostnames of the SQL Server instances that you want to configure as replicas in the Availability Group and click Next. Validate a Configuration Wizard   Ensure the Run all tests option is selected in the Testing Options dialog box and click Next.  Click Next in the Confirmation dialog box.  Select Finish in the Summary dialog box to create the Windows Failover Cluster. NOTE: It is expected that the Failover Cluster Validation Wizard will report several warnings especially if shared storage is not utilized. Be aware that these warning messages will configure a file share witness for said cluster quorum configuration. An error messages reported will need to be addresses prior to the creation of the Windows Server Failover Cluster.  Enter the server name and IP address of said Windows Server Failover Cluster in the Access Point for Administering the Cluster dialog box. Create Cluster Wizard: Access Point for Adminstrating the Cluster  Click Next in the Confirmation dialog box to create the Windows Failover Cluster using the servers as nodes of the cluster. Be sure to include the required DNS and Active Directory entries for the cluster hostname.  Verify that the configuration is successful within the Summery dialog box.  Select More Actions > Configure Cluster Quorum Settings... to configure the cluster quorum configuration to use a file share.  The wizard will configure the cluster to use Node Majority by default.  Click Next.  Select Add or change the quorum witness option in the Select Quorum Configuration page and click Next.  Select Configure a file share witness option in the Select Quorum Witness page and Next.  Type the path of the file share needed to use in the File Share Path: text box within the Configure File Share Witness page and click Next.  Click Next in the Confirmation page.  Click Finish in the Summary page.   Step 3: Enabling the SQL Server 2016 Always On Availability Groups Feature   Work can now start in enabling the Always On Availability Groups feature in SQL Server 2016 now that the Windows Server Failover Cluster has been created. All SQL Server instances need to be configured as replicas in said Availability Group.   The following steps will enable the Always On Availability Group feature:   Run the SQL Server Configuration Manager and double-click the SQLServer (MSSQLSERVER) service to open the Properties dialog box. SQL Server Configuration Manager  Select the Always On High Availability tab in the Properties dialog box and check off the Enable Always On Availability Groups checkbox.  Click OK when prompted to restart the Server service.     Step 4: Creating and Configuring SQL Server Always On Availability Groups   Availability Groups can be created on temporary databases or on existing ones. Some solutions, like SharePoint, require the creation of a temporary database so that the solution can harness the AlwaysOn Availability Group when creating the admin content databases and farm configuration.  The temporary database is then removed from the Availability Group configuration once the SharePoint farm is created.    The following steps will create and configure a SQL Server Always On Availability Group:   Open SQL Server Management Studio and connect to the SQL Server instance.  Expand the Always On High Availability folder in the Object Explorer.  Right-click on the Availability Groups folder and select the New Availability Group Wizard... option launching the New Availability Group Wizard. SQL Server Management Studio  Click Next on the Introduction page.  Enter the name of the Availability Group in the Availability group name: field and click Next.  Select the checkbox beside the database to be included in the Availability Group within the Select Databases page. NOTE: The selected databases need to be in a Full Recovery model prior to joining them in the Availability Group.  Click Next.  Under the Replicas tab within the Specify Replicas page, click Add Replicas and connect to the other SQL Server instances previously joined as nodes with the Windows Server Failover Cluster and configure the following options: - Automatic Failover (Up to 2):  Checked- Synchronous Commit (Up to 3): Checked- Readable Secondary: No  Verify that the port number value is 5022 in the Endpoints tab.  Select the Create an availability group listener option within the Listener tab and enter the following details:  - Listener DNS name: Name that will be used in the application connection string- Port: 1433  Click Add... once completed and provide the required IP Address.  Enter the preferred virtual IP address in the IPv4 Address field within the Add IP Address dialog box and click OK > Next.  Select the Full option within the Select Initial Data Synchronization page.   New Availability Group: Select Initial Data Synchronization NOTE: This enables a temporary file share to store database backups used to initialize the databases in an Availability group.  The file share folder is accessible to both the SQL service account and the replicas. It is recommended that manual initialization of the databases prior to configuration should be initialized in the case of larger databases as the network may not be able to accommodate the size of the database backups.  Click Next.  Verify all validation checks are successful in the Validation page and click Next.  Verify all configuration settings and click Finish in the Summary page.  Verify all task have been completed successfully in the Results page.   The creation of the SQL Server Always On Availability Group is now complete.  Do note that any additional new databases will need to be manually added.