Creating a SharePoint farm in windows azure just got a whole lot easier. During WPC 2014 Microsoft released an update to the preview portal (http://portal.azure.com) that makes it possible to configure a SharePoint farm entirely from the portal. Needless to say I had to try it out.
- The first step in creating your SharePoint farm is to jump into the new portal http://portal.azure.com
- The click new, and find the SharePoint Server Farm option
- When clicked a new blade will load, that will enable a lot of customization
- The first four boxes are for naming a resource group, and assigning a user name and password for the domain admin (remember this one).
- Then you can configure whether you want high availability (fail-over of all the servers, beware of the bill if you select this). If you are configuring a real production farm with fail-over you are probably better of doing it with powershell, but maybe this feature will fulfill some people’s need.
- Next up is the configuration of the individual servers that is gonna make up the farm. Be sure to go through all the configuration options, or at least specify what pricing tier you want for each machine
- When you configure the root domain name for you Domain Controller, it is a good idea to remember the forest root domain name, as you will need it later for logging into the machines
- Same goes for the user accounts used by the SharePoint server
- When you are done with the servers it is time to configure storage and network, you don’t have a lot of options here, but make sure that you create the VHDs in the correct storage account, and you can probably do with just selecting the L1 pricing tier (locally redundant storage), if you are just building a dev or demo farm.
- The final step is to select your subscription and hosting location
- When you click create you have to be patient as the deployment of the network and machines will take 30 to 60 minutes.
Configuration for a high performant dev environment
I mostly see this new features as a tool for SharePoint developers, that don’t want to spend too much time on creating their enviroment, as well as being really useful for quickly spinning up demo/test environments. The configuration I chose to go with for my cloud dev environment is the following.
|Machine||Pricing Tier||RAM||Cores||Price/Hour (Pay-As-You-Go)||Price/Hour (MSDN)|
|Domain Controller||Basic A1||1.75||1||$0.075||$0.047|
|SQL Server||Standard A5||14||2||$2.10||$0.248|
|SharePoint Server||Standard A5||14||2||$0.30||$0.248|
With these prices you will be able to run your environment for around 276 hours, or more than 30 days if it is only online 8 hours a day, on a Visual Studio Ultimate MSDN subscription with $150 Azure Credit (MSDN subscribers don’t pay extra for SQL servers and only pay linux prices for the VMs) source. If you are not using a MSDN subscription, your price will obviously be a lot higher.
You don’t get to select what image your machines have, so the SharePoint server will be installed with Windows Server 2012 Datacenter while the Domain Controller will be installed with Windows Server 2012 R2 Datacenter.
The SQL server is running Windows Server 2012 R2 Datacenter, and have SQL Server 2014 Enterprise installed, which is the reason for the hefty price tag.
Here’s the systeminfo for the SharePoint server
Host Name: SJKPSPFARM-SP
OS Name: Microsoft Windows Server 2012 Datacenter
OS Version: 6.2.9200 N/A Build 9200
OS Manufacturer: Microsoft Corporation
OS Configuration: Member Server
OS Build Type: Multiprocessor Free
Product ID: 00184-90000-00001-AA620
Original Install Date: 7/15/2014, 6:56:05 AM
System Boot Time: 7/15/2014, 5:54:02 PM
System Manufacturer: Microsoft Corporation
System Model: Virtual Machine
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
: Intel64 Family 6 Model 45 Stepping 7 GenuineInt
el ~2200 Mhz
BIOS Version: American Megatrends Inc. 090006 , 5/23/2012
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Boot Device: \Device\HarddiskVolume3
System Locale: en-us;English (United States)
Input Locale: en-us;English (United States)
Time Zone: (UTC) Coordinated Universal Time
Total Physical Memory: 14,336 MB
Available Physical Memory: 11,197 MB
Virtual Memory: Max Size: 19,712 MB
Virtual Memory: Available: 15,297 MB
Virtual Memory: In Use: 4,415 MB
Page File Location(s): D:\pagefile.sys
Logon Server: \\SJKPSPFARM-DC
Hotfix(s): 114 Hotfix(s) Installed.
Network Card(s): 1 NIC(s) Installed.
: Microsoft Hyper-V Network Adapter
Connection Name: Ethernet 2
DHCP Enabled: Yes
DHCP Server: 220.127.116.11
Hyper-V Requirements: A hypervisor has been detected. Features required for
Hyper-V will not be displayed.
When you setup the virtual machines, you are not able to specify what disk sizes and configuration you get. But the default configuration is pretty flexible. On all machines you get 126GB for the C: drive.
On the SharePoint Server you have 1TB on a data disk F: that is not used for anything. And on the SQL server you get two disks F: and G: that are both 1TB each. The F: drive is configured as the SQL data disk, while the G: drive is used as log disk.
If you are worried that you are gonna pay for all this disk space allocated for you, that you are not gonna use, then remember that in Azure you are only billed for the amount of space that you actually use on the VHDs, all the zero-bytes are not billed. To free up unused space after deleting big files you can run the following powershell script
Optimize-Volume -DriveLetter F -ReTrim
The disk defragment tool that is configured to run once a week on the disks will do the same for you.
But if you are using your machines development they might be shutdown for long periods of time so it might be a good idea to run the ReTrim command before shutting them down.
The SharePoint Farm Configuration
The SharePoint farm is updated with Service Pack 1, so the build version are 15.0.4569.1000. But other than that the farm configuration is pretty minimal, and it will require some effort before you have anything that resemble a real SharePoint farm.
Everything is installed in the the default locations, so if you are used to something fancy here, then this is not the configuration tool for you.
Other than that you get a single application pool with a site collection with an empty site, and that is pretty much it.
One nice little touch is that the SharePoint site is accessible from the WWW per default on
So obviously the GUI farm configuration is limited, but to me it seems like a pretty good fit for creating dev/test/demo enviroments. I just played around with some open source PowerShell scripts for setting up a similar farm, and using the GUI is WAY easier and will definately help drive Azure adoptation for SharePoint devs.