The document discusses moving workloads to the cloud using Microsoft Azure. It defines Azure as a set of cloud services that allow building, managing and deploying applications. It provides considerations for different cloud models like SaaS, IaaS and PaaS. It also outlines potential hurdles in moving to the cloud like network topologies, identity management and security. Finally, it discusses planning the migration and provides Azure resources for architecture guidance.
3. About me
• Twitter: @al_eardley
• LinkedIn: Alan Eardley
• Helping clients adopt Microsoft 365
• MCSE: SharePoint 2016
• MCSE: Productivity
• MCSE: Cloud
• ProSci Practitioner
• ScrumMaster
• PRINCE2 Practitioner
4. What will I cover?
• What are objectives of moving to the cloud?
• What is Azure?
• Sample scenario
• Hurdles to overcome
• Considerations
– SaaS
– IaaS
– PaaS
• Summary
10. Microsoft Azure is an ever-expanding set of cloud
services to help your organization meet your
business challenges. It’s the freedom to build,
manage, and deploy applications on a massive,
global network using your favourite tools and
frameworks.
- Microsoft
11. … as a Service
Applications
Data
Runtime
Middleware
O/S
Virtualisation
Servers
Storage
Networking
On-Premises
Applications
Data
Runtime
Middleware
O/S
Virtualisation
Servers
Storage
Networking
Infrastructure …
Applications
Data
Runtime
Middleware
O/S
Virtualisation
Servers
Storage
Networking
Platform …
Applications
Data
Runtime
Middleware
O/S
Virtualisation
Servers
Storage
Networking
Software …
12. How is it structured?
• Region
• Data centre
• Services
16. Solution objectives
New end user devices
Better security
Consolidated platform
New capabilities
Retire existing server hardware
Increased speed of delivery of enhancements
17. Current state
Windows 7 VDI
On-Premises file shares
SharePoint 2010 and SharePoint 2013
Existing data must be migrated
Continuous reporting across both platforms during migration period
18. Functionality
Document management and governance
Project scheduling and resource management
Identity management and compliance
Data warehouse for reporting
Import legacy data from on-premises application
Report on data using existing tools
Report on data using PowerBI
25. Network
On-Premises
to Azure
• VPN
• Bandwidth
Data Centre
vulnerability
• Routing to
single DC
• DC goes
down
• Speed
Global
connectivity
• Designed for
local break-
out
28. SaaS - Considerations
• Follow best practices for customisation
• APIs for access to data can be constraining
• Identity impersonation
• Licences
• Throttling
• Environments and testing
• Disaster recovery
Tunnel to Azure – 100MB
BA
Azure can scale globally – not if all traffic is routed through a single datacentre
Without the ability to access the cloud, the project stops
Different technical approaches such as cloud identity, federation and passthrough
Common issues are more related to changes in user behaviour
Like any other data centre, access needs to be controlled
Delegation of permissions works well in Azure – grant permissions to different resource groups containing logical sets of Azure resources
Azure resources have different methods for exposing endpoints
Azure SQL has firewalls to allow restriction to allowed IP addresses by default
Web based applications can accept traffic from anywhere, or be restricted to a range of IP addresses