High availability SharePoint Server 2016 farm in Azure deployment content updated


The content for deploying a high-availability SharePoint Server 2016 farm in Azure steps you through creating and configuring the following:

This content has been updated for the use of:

  • Azure managed disks instead of storage accounts  Managed disks are an easier and more scalable way to add operating system and data disks to Azure virtual machines. All you have to do is specify the type of storage (Premium or Standard) and the disk size, and Azure storage creates and manages the disks on your behalf. You no longer need to create and manage storage accounts.
  • Windows Server 2016 cloud witness as an alternative to the majority node server in the SQL cluster  Windows Server 2016 now supports the use of a cloud witness for a failover Windows Server cluster, rather than deploying an additional virtual machine to act as the cluster quorum witness (the MN1 virtual machine in the figure above). This was suggested as a deployment alternative by a CAAB member at the August 2017 CAAB Webinar. Thanks for that suggestion!

The SharePoint Server 2016 High Availability Farm in Azure Deployment Kit, a ZIP file in the TechNet Gallery that contains additional resources to accelerate deployment (including all the new PowerShell code), has also been updated.

 

To join the CAAB, become a member of the CAAB space in the Microsoft Tech Community and send a quick email to CAAB@microsoft.com to introduce yourself. Please feel free to include any information about your experience in creating cloud-based solutions with Microsoft products or areas of interest. Join now and add your voice to the cloud adoption discussion that is happening across Microsoft and the industry.

Comments (2)

  1. Dean Gross says:

    The reference above to the Office 365 Yammer network is obsolete, that network has been moved the Microsoft Tech Community

  2. Joe Davies says:

    Hi Dean, You are right. I copied the standard blurb from a much earlier post. It is now corrected. Thanks for letting me know. Joe

Skip to main content