SharePoint Farm On Azure IAAS Prepared By : Prakhar Rastogi Premier Field engineer Microsoft India

Agenda Overview Planning for SharePoint 2013 on Azure infrastructure Services Azure Virtual Machines Azure Virtual Network The Azure scalability model Operate and maintain SharePoint farm on Azure Managing Lab Environments and automation

Overview  Cloud Services  Azure  Office 365  SharePoint online  SharePoint On Azure

Planning for SharePoint 2013 on Azure  Functions and features Determine the functions that you want the farm to provide, and identify the features required to provide the functions.  Services and service applications Determine the services and service applications that are needed for the features that you intend to use.  Farm users Determine how, how often, and when your users will use the farm functions that are provided.  Farm content Farm content types (for example, documents, pictures, videos, lists, and web articles) and volume (number of items and size) determine database capacity requirements.  Intended use The goal for deploying the farm or its intended use determine the level of planning and type of design that is needed.

Planning for SharePoint 2013 on Azure  Why SharePoint on Azure?  Determine Active Directory Domain Type  Determine SharePoint Farm Topology

Why SharePoint on Azure?  Development and test environments  Disaster recovery of on-premises SharePoint farms to Azure   Internet-facing sites   App farms to support Office 365 or on-premises environments

Azure Basics  Subscription  Location  Affinity Groups  Affinity Groups allows you to make sure that your cloud services, storage, virtual networks etc are placed “together”.  Cloud Services  Cloud Services have features such as end-points, load balancing and auto-scale.  Storage Account  Availability Sets

Azure Basics

Virtual Machine  Azure allows you to create a virtual machine running Windows Server or other operating systems. After you create a virtual machine in Azure, you can access it like any other server and delete or re-create it whenever needed. You can use a virtual machine in Azure to deploy a Windows Server 2012 R2- based server.  Azure virtual machines are built from virtual hard disks (VHDs). These VHDs are the same as the VHDs used by Hyper-V and can be transferred to and from your existing environment. Azure also allows you to create multiple virtual machines and then load balance traffic from the Internet between them

Virtual Machine Size  A1 (Shared core, 768MB Memory)  A2 (1 core, 1.75GB Memory)  A3 (2 cores, 3.5GB Memory)  A4 (4 cores, 7GB Memory)  A5 (8 cores, 14GB Memory)  A6 (4 cores, 28GB Memory)  A7 (8 cores, 56GB Memory)

Virtual Machine Component  VHD  Image  Disk  Data Disk  Temporary Disk

Virtual Networks  An Azure Virtual Network is a logical container that can host virtual machines grouped on subnets. Virtual machines on subnets in a virtual network can communicate directly with each other, just like on intranet subnets, without that traffic traversing the Internet. This is in contrast with Azure Virtual Machines that are not in a virtual network, which cannot communicate with each other without that traffic traversing the Internet.  Cross-premises virtual network A virtual network that is connected to your organization network across the Internet through a site-to-site VPN connection. Virtual machines in a cross-premises virtual network act as an extension of your organization network, providing applications and services to intranet users, Internet users, or both.  Cloud-only virtual network A virtual network that is not connected to your organization network. Virtual machines in a cloud-only virtual network typically provide applications and services to Internet users

Virtual Network Components  Site to Site VPN  Domain Controller  DNS  Affinity Groups  End Points  Availability Set

Site to Site VPN  To connect the cross-premises virtual network in Azure to your on-premises network, you create a site-to-site VPN connection. A VPN gateway device at the boundary of your on-premises network creates a secure connection to an Azure VPN gateway at the edge of your virtual network. To ensure that you can reach the virtual machines from your on-premises network, you must configure your routing infrastructure with routes for the address space of the virtual network to point to your VPN gateway device.  Azure site-to-site connections use the industry-standard Internet Security protocol (IPsec) to provide a secure connection between your VPN gateway device and an Azure VPN gateway at the boundary of your Azure virtual network. You can control network access using your on-premises security device. You can also control traffic between your data center and virtual machines running in Azure with the standard host-based Windows Firewall included with Windows Server.

Example

Operate and maintain SharePoint farm on Azure  Same as an On-Premise Farm  Monitoring  Patching/Updating  Backup/Recovery  Preparing Gold Images and Lab environments  capture-image-windows-server/ capture-image-windows-server/

Managing Lab Environments and automation  Lab Automation  create-preconfigure-windows-vms/ create-preconfigure-windows-vms/  Sample Scripts 

Additional Resources  From the MVPs: Why SharePoint on Azure?  why-sharepoint-on-azure.aspx why-sharepoint-on-azure.aspx  Deploying SharePoint 2013 with SQL Server AlwaysOn Availability Groups in Azure   Step-by-Step: Build a FREE SharePoint 2013 Dev/Test Lab in the Cloud with Windows Azure Infrastructure Services  a-free-sharepoint-2013-lab-in-the-cloud-with-windows-azure-31-days-of-servers-in- the-cloud-part-7-of-31.aspx a-free-sharepoint-2013-lab-in-the-cloud-with-windows-azure-31-days-of-servers-in- the-cloud-part-7-of-31.aspx