The next step in our journey to an Azure SharePoint 2019 environment is to build Active Directory. You actually have a couple of options here in that you could integrate directly with Azure Active Directory or you can build a domain controller and create your active directory that way. Because my end state for this environment is to actually build a hybrid environment I want to build a full domain controller. This means we are going to provision a VM, install Windows Server 2016 and create an active directory.
This is a multi-part series. You can see what is coming and review other posts in the series by clicking one of the following links:
- Microsoft Azure – Prepping the Azure Environment for SharePoint 2019
- Microsoft Azure – Configure Azure Network Resources for SharePoint 2019
- Microsoft Azure – Build Storage Resources for Azure SharePoint 2019
- Microsoft Azure – Creating the Domain Controller (this post)
- Microsoft Azure – Configuring the Domain Controller Network
- Microsoft Azure – Configuring DNS and Active Directory
- Microsoft Azure – Build SharePoint Server Virtual Machine
- Microsoft Azure – Deploy SQL Server
- Microsoft Azure – Build SharePoint 2019 Template with AutoSPInstaller
- Microsoft Azure – Prepping SharePoint Servers
- Microsoft Azure – Installing SharePoint 2019
- Microsoft Azure – Add a Load Balancer for External Access
Building a SharePoint 2019 MinRole Environment in Microsoft Azure – Creating the Domain Controller
The first step is to determine the server type you want to use. Azure when creating a new Windows 2019 Datacenter VM defaults to a standard DS1 (v2) server which has a monthly cost of $72 CAD. If you have a corporate account that you can charge this to, then fill your boots and continue on. Myself, I am going to make this as minimal as possible. While the environment is just a dev environment and won’t be turned on all the time, I don’t want to burn through available credits too fast. So with that in mind, we are going to limit things a bit and create an B1ms server for the domain controller. We can get away this because the domain is going to be very small with very little load against it. If this was going to be used for anything more than dev, I would utilize a larger server.
- Click on Virtual Machines along the left-hand side and then click +Add.
- Select your subscription and the Resource Group created for this farm.
- Give your VM a name, select the region and availability options (I selected no redundancy)
- Next select the OS you wish to install (Windows Server 2019 Datacenter).
- Update the size of the VM image (B1ms as stated above)
- Next you want to put in your admin account and password as Azure will be building the OS installation for you.
- Leave the Inbound port rules to None (default)
- Next is a section called “Save Money“. Here you can indicate if you need to purchase an OS license with you server or not. If you have an available license select Yes. Then click in the box labeled Confirmation to indicate you are stating you have a license.
- Click “Next: Disks.”
- Because this is a dev environment I chose to go with standard disks instead of premium. You can change the selection at the OS disk type selection.
- We will need to add a disk as Azure only creates an OS disk. Everything else needs to go on the data disk.
- Click on Create and attach a new disk.
- Disk Type: Standard SSD
- Name: Can use the default if you want (ServerName-DataDisk-1) or change it if you wish.
- Size: 40GB (or more depending on if you are adding other resources to this server).
- Click Ok.
- Click on Create and attach a new disk.
- Click “Next: Networking”
- Here you build your network connections. Select the following options:
- Virtual network: network you created previously for this resource group (I created SP2019-net)
- Subnet: Use the default
- Public IP; Use the default
- NIC network security group: Basic
- Public inbound ports: None
- Accelerated networking: Off
- Load Balancing: No
- Click “Next: Management”
- In this section, configure your VM Management settings
- Boot Diagnostics: On
- OS Guest Diagnostics: Off
- Diagnostics Storage account: name of storage account you created for AD
- System Assigned Managed Identity: Off
- Enable auto-shutdown: Yes (unless you want it running all the time)
- Shutdown time: select the time of day you wish to shut down your VM if turned on.
- Time Zone: Select your time zone
- Notification before shutdown: No
- Click “Next: Advanced”
- Here you can add any resources (some as a service) you may require (virus scan, extensions for scripting, etc). In this case we don’t really need any so click “Next: Tags”.
- Add any tags you require for this VM.
- Click “Next: Review + Create”
- Review the settings and handle any errors (if any) the Azure wizard reports.
- Click Create and wait for deployment to complete.
- After 4-5 min the deployment should be complete. You can now view the VM by clicking “View the Resource”. Click on that button now.
Next we need to configure the server’s network settings
Thanks for reading!