Export (0) Print
Expand All

Phase 1: Configure Azure

Updated: October 8, 2014

[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]

This is the first phase of deploying SharePoint with SLQ Server AlwaysOn in Azure, which includes configuring the Azure networking infrastructure. You must complete this phase before moving on to Phase 2.

For the next phase, see Phase 2: Configure Domain Controllers.

For all of the phases of this deployment, see Deploying SharePoint with SQL Server AlwaysOn in Azure.

This deployment of SharePoint with SQL Server AlwaysOn is designed to accompany the SharePoint with SQL Server AlwaysOn Infographic and incorporate the latest recommendations.

Overview

Azure must be provisioned with these basic network components:

  • A cross-premises virtual network with one subnet

  • Three Azure cloud services

  • One Azure storage account to store VHD disk images and extra data disks

The following figure shows the configuration resulting from the successful completion of this phase.

Phase 1: The Azure Virtual Network

Before you begin

Before you begin configuring Azure components, fill in the following tables. To assist you in the procedures for configuring Azure, print this section and write down the needed information or copy this section to a document and fill it in.

For the settings of the virtual network (VNet), fill in Table V.

 

Item Description Value

1. VNet name

A name to assign to the Azure Virtual Network (example SPFarmNet).

2. VNet location

The Azure datacenter that will contain the virtual network.

3. Local network name

A name to assign to your organization network.

4. VPN device IP address

The public IPv4 address of your VPN device's interface on the Internet.

Work with your IT department to determine this address.

5. VNet address space

The address space (defined in a single private address prefix) for the virtual network.

Work with your IT department to determine this address space.

6. Final DNS servers

The fourth and fifth possible IP addresses for the address space of the subnet of the virtual network (see Table S).

Work with your IT department to determine these addresses.

Table V: Cross-premises virtual network configuration

Fill in Table S for the subnet of this solution. Give the subnet a friendly name, a single IP address space based on the Virtual Network address space, and a descriptive purpose. Work with your IT department to determine this address space from the virtual network address space.

 

Subnet name Subnet address space Purpose

1.

Table S: Subnets in the virtual network

For the two on-premises DNS servers that you want to use when initially setting up the domain controllers in your virtual network, fill in Table D. Give each DNS server a friendly name and a single IP address. This friendly name does not need to match the host name or computer name of the DNS server. Note that two blank entries are listed, but you can add more. Work with your IT department to determine this list.

 

DNS server friendly name DNS server IP address

1.

2.

Table D: On-premises DNS servers

To route packets from the cross-premises network to your organization network across the site-to-site VPN connection, you must configure the virtual network with a local network that contains a list of the address spaces (in CIDR notation) for all of the reachable locations on your organization's on-premises network. The list of address spaces that define your local network must not include or overlap with the address space used for other virtual networks or other local networks. In other words, the address spaces for configured virtual networks and local networks must be unique.

For the set of local network address spaces, fill in Table L. Note that three blank entries are listed but you will typically need more. Work with your IT department to determine this list of address spaces.

 

Local network address space

1.

2.

3.

Table L: Address prefixes for the local network

To create the virtual network with these settings, see Create a Cross-Premises Virtual Network Using Configuration Tables.

Note that after creating the Azure virtual network, the Azure Management Portal will determine the following:

  • The public IPv4 address of the Azure VPN gateway for your virtual network

  • The Internet Protocol security (IPsec) pre-shared key for the site-to-site VPN connection

To see these in the Azure Management Portal after you create the virtual network, click Networks, click the name of the virtual network, and then click the Dashboard menu option.

Next, you’ll configure the virtual network gateway to create a secure site-to-site VPN connection. See Configure the Virtual Network Gateway in the Management Portal for the next steps.

Next, create the site-to-site VPN connection between the new virtual network and an on-premises VPN device. For the details, see Configure a Virtual Network Gateway in the Management Portal.

Next, ensure that the address space of the virtual network is reachable from your on-premises network. This is usually done by adding a route corresponding to the virtual network address space to the VPN device and then advertising that route to the rest of the routing infrastructure of your organization network. Work with your IT department to determine how to do this.

Next, create the three cloud services needed for this SharePoint farm. Fill out Table C.

 

Item Purpose Cloud service name

1

Domain controllers

2

SharePoint servers

3

SQL servers

Table C: Cloud service names

Create three new Azure Cloud Services

  1. In the task bar of the Azure Management Portal, click New > Compute > Cloud Service > Quick Create.

  2. In URL, type the name from Item 1 in Table C for the cloud service for the domain controllers. This must be a unique name to Azure, so you might have to change it. When you have a unique name, update Item 1 in your Table C page with the actual name.

  3. In Region or Affinity Group, select the region corresponding to Item 3 from Table V (the region of the virtual network).

  4. Click the checkbox next to Create Cloud Service to create the cloud service.

  5. Click New > Compute > Cloud Service > Quick Create.

  6. In URL, enter the name from Item 2 in Table C for the cloud service for the SharePoint servers. This must be a unique name to Azure, so you might have to change it. When you have a unique name, update Item 2 in your Table C with the actual name.

  7. In Region or Affinity Group, select the region corresponding to Item 3 from Table V.

  8. Click the checkbox next to Create Cloud Service to create the cloud service.

  9. Click New > Compute > Cloud Service > Quick Create.

  10. In URL, enter the name from Item 3 in Table C for the cloud service for the SQL servers. This must be a unique name to Azure, so you might have to change it. When you have a unique name, update Item 3 in your Table C with the actual name.

  11. In Region or Affinity Group, select the region corresponding to Item 3 from Table V.

  12. Click the checkbox next to Create Cloud Service to create the cloud service.

Next, create a storage account for the SharePoint farm.

Create a new Azure Storage Account

  1. In the task bar of the Azure Management Portal, click New > Data Services > Storage > Quick Create.

  2. In URL, enter a name. This must be a unique name to use for the storage account URL, so you might have to change it. When you have a unique name, record it because you will need to specify this name when you create virtual machines and extra disks.

  3. In Location/Affinity Group, select the region corresponding to Item 3 from Table V (the region of the virtual network).

  4. In Replication, select Geo-Redundant.

  5. Click the check box to create the storage account.

For more information, see Create a Storage account on Azure.

Next, define the names of four availability sets. Fill out Table A.

 

Item Purpose Availability set name

1

Domain controllers

2

SQL servers

3

SharePoint application servers

4

SharePoint front-end web servers

Table A: Availability set names

You will need these names when you create the virtual machines. For more information, see Manage the availability of virtual machines.

Next Steps

For the next phase of the deployment, see Phase 2: Configure Domain Controllers.

For all of the phases of this deployment, see Deploying SharePoint with SQL Server AlwaysOn in Azure.

See Also

Community Additions

ADD
Show:
© 2014 Microsoft