This document discusses deploying SharePoint 2013 on Microsoft Azure. It provides an overview of cloud computing models like SaaS, PaaS, and IaaS. Microsoft Azure is introduced as a cloud platform offering IaaS and PaaS. SharePoint 2013 can be deployed on Azure virtual machines within a virtual network. Key aspects covered are Azure virtual networks, virtual machines, and additional components needed for a successful SharePoint deployment on Azure like domain controllers and SQL servers.

1. SharePoint On Microsoft Azure
Martin Njalale

2. About Me
Martin Njalale
Twitter: @martinnjalale Email: mnjalale@gmail.com
Skype: martin.njalale
• Senior Software Engineer at Caytree
Partners
• Software Architect Consultant at
Ideahutch Ltd.
• Well versed with Microsoft’s stack of
technologies: Web API, ASP.Net MVC, C#,
Microsoft Azure, e.t.c.

3. Agenda
• What is Cloud computing.
• Introduction to Microsoft Azure.
• SharePoint 2013 on Microsoft Azure.

4. What is cloud computing?
This is the practice of using a network of remote
servers hosted on the Internet to store, manage, and
process data, rather than a local server on a personal
computer.

5. What is cloud computing?
SaaS (Software as a Service)
• Software is licensed on a subscription basis.
• Accessed by users using a thing client via a web browser.
• Minimal customization involved if any.
• Both software and hardware infrastructure provided with the service.
Examples:
• Office 365
• Quickbooks

6. What is cloud computing?
PaaS (Platform as a Service)
• Computing platforms and a solution stack are provided as a service.
• A consumer creates an application or service using tools and/or libraries
from the provider, and also controls software deployment and
configuration settings.
• The provider provides the networks, servers, storage and other services
required to host the consumers application.
Examples:
• Microsoft azure websites and cloud services.

7. What is cloud computing?
IaaS (Infrastructure as a Service)
• Architectural and development access to application services, storage and
application runtime..
• Customizations are allowed within a framework.
Examples:
• Microsoft Azure Virtual Machines.

8. Microsoft Azure
What is Microsoft Azure?
Microsoft Azure is Microsoft’s cloud platform that enables you to quickly
build, deploy and manage applications across a global network of Microsoft-managed
datacenters.
It offers Infrastructure as a Service (IaaS) and Platform as a Service (PaaS)

9. Microsoft Azure
Why Azure? How do I benefit?
Benefits:
• Elastic - It can quickly scale up or down to match demand so that your
deployments are efficient.
• Usage Based- Metered service, allowing you to pay only for the resources
you use to eliminate investment in underutilized capacity to meet peaks
in demand.
• Evergreen Service - Microsoft handle all maintenance and upgrades,
ensuring your organization is using the most up to date resources.
• Self-Service - Provide self-service IT infrastructure to business units and
departments quickly and simply, without involving the IT department
• Availability- it’s always up. Azure offers 99.95% financially backed SLA,
24x7 tech support and round-the-clock.

10. Microsoft Azure Services
Computer Services
• Virtual Machines
• Web sites
• Mobile services
• Cloud services
Data Services
• Storage services
• Databases
• Backup/Recovery
• Cache
Network Services
• Express Route
• Virtual Network
• Traffic Manager
• CDN
Apps
• Media services
• Service Bus
• Notification hubs
• Scheduler
• Automation
• BizTalk
• Visual Studio Online
• Active Directory
Store
• Add ons

11. SharePoint 2013 on Azure
So how is this important to SharePoint?

12. SharePoint 2013 on Azure
Microsoft Azure supports
the deployment of
SharePoint 2013 farms
with virtual machines
and virtual networks.
Cross-Premises virtual network

13. SharePoint 2013 on Azure
Azure 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 without that traffic traversing the
Internet. You define the IP address ranges your virtual machines will use.
NB: Azure Virtual Machines that are not in a virtual network cannot
communicate with each other without that traffic traversing the internet
Always create a virtual network within Azure before deploying any new
virtual machines. This allows you to group your virtual machines together
and allow you to divide and determine the ranges of IP addresses assigned to
your virtual machines.

14. SharePoint 2013 on Azure
Types of Azure Virtual Networks
There are two types of Azure Virtual Networks:
• 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.

15. SharePoint 2013 on Azure
Azure Virtual Machines
Azure allows you to create a virtual machine running on Windows Server or
any other operating system. You can access a virtual machine in Azure like
any other server, delete and recreate it whenever you want.
Azure VMs are built from virtual hard disks (VHDs) which are the same as
those used by Hyper-V and can be transferred to and from your existing
environment.
You can create multiple virtual machines and then load balance traffic from
the internet between them.

16. SharePoint 2013 on Azure
Other Relevant Azure Components
There are additional components that are necessary for a successful
deployment of SharePoint 2013 on Azure:
• Affinity Groups: these are specified when creating Azure resources such
as Virtual Networks. They let Microsoft Azure know that you wish to keep
resources located within the same Azure regional datacenter.
• Site to site VPN connections: To connect the cross-premises virtual
network in Azure to your on-premises network, you create a site-to-site
VPN connection.
• Domain Controllers: To minimize the latency of performing
authentication of intranet user credentials for access to and
administration of SharePoint farm sites and resources, you should deploy
Active Directory Domain Services (AD DS) domain controllers in the
virtual network. For redundancy, you should deploy at least two.

17. SharePoint 2013 on Azure
So how do I build SharePoint on Azure?
• Create a virtual network
• Create affinity group
• Create storage account
• Provision domain controller(s)
• Provision SQL server(s)
• Provision SharePoint Servers
• Setup accounts
• Configure SharePoint

18. SharePoint 2013 on Azure
DEMO

19. Planning
Plan your farm the same as if it was on premises
• Size your servers using the Azure server sizing chart (A1 – A8)
Plan for directory synchronization
• DirSync allows SSO for your local AD user accounts
Plan for on premises integration
• Configure VPN to internal network
• Expose LOB as services
Plan for Migration
• SharePoint content, other content?

20. Considerations
So what is the right choice for me?
On Premises On Azure (IAAS) SharePoint
Online
Control Total control Almost total
control
Restricted
LOB Integration Easy Complex Restricted
Entry Cost High (up-front) Low Low
Maintenance and
support
High Low Low
Functionality High High Limited

21. Thank You!