The document outlines a case study for migrating a large business-critical application to the Microsoft Azure cloud platform, detailing a comprehensive agenda for a collaboration event including various technical sessions. Key topics include cloud infrastructure design, Azure services troubleshooting, automation with PowerShell, and disaster recovery strategies. It also describes the specific architecture, configurations, and security protocols necessary for a global travel portal business model, highlighting the importance of high availability and load balancing across different geographical regions.

1. A case study to migrate your large business critical application to
Microsoft Azure Cloud Platform

2. Our Supporters

3. Collaborating Communities

4. 10:00 -10:45 Design & Secure Your Cloud Infrastructure – Sarvesh (Cloud Architect) and Ajay (Microsoft MVP)
10:45 – 11:00 Tea Break
11:00 – 11:45 SCCM with Azure PaaS services (CDP and CMG) - Troubleshooting Tips - Sudheesh N (Microsoft )
12:00 – 12:45 Azure Automation with PowerShell - Deepak Dhami (Microsoft MVP)
1:00 – 1:45 Lunch Break
2:00 – 2:45 Modern Management with Intune – Is it OK to move away from Group Policy to CSP– Vimal (Senior Consultant) and Anoop
(Microsoft MVP)
3:00 – 3:45 Disaster Recovery Using Azure Services - Adil (Senior Technical Support Engineer)
3:45 – 4:00 Tea Break
4:00 – 4:45 Windows 10 co management benefits and real-world experience – Rajul (Technical Consultant) and Anoop (Microsoft MVP)
Agenda

5. Sarvesh Goel (@sarveshgoyal)
•Cloud Platform Architect
•Blog – http://sarveshgoel.com/
Ajay Kakkar (@Kakkaraj)
•Microsoft MVP | Enterprise Architect
•Blog – https://insidemstech.com
Speakers

6. Scenario : Travel & Tourism
Customer Base : Global
USP : Travel Portal
Business Model : B2C & B2B
Peak Time : Festival & Holiday season
Business Need for Transition : H/W EOL
GLOBAL DESIGN

7. North America
Web Tier App Tier DB Tier
South America
Web Tier App Tier DB Tier
SQL Always On
Distributed
Availability Group
M
P
L
S
Regional Design (HA – DR)
GEO DNS
GLBS

8. Compute
DB
CPU: 2 x 12 core
Memory: 128 GB
OS: Win 2012 R2
App
CPU: 2 x 10 core
Memory: 96 GB
OS: Win 2012 R2
Web
CPU: 2 x 8 core
Memory: 64 GB
OS: Win 2012 R2
Reverse Proxy
CPU: 2 x 4 core
Memory: 32 GB
OS: Windows 2012 R2
Storage
DB
OS: 2 x 80 GB, 15K RPM SAS
Application: 2 x 160 GB, 15K RPM SAS
DB & Logs: 100 TB LUN, 15K RPM SAS
App
OS: 2 x 80 GB, 15K RPM SAS
Application: 2 x 160 GB, 15K RPM SAS
Application Cache: 2 x 256 GB SSD WI
Web
OS: 2 x 80 GB, 15K RPM SAS
Application: 2 x 160 GB, 15K RPM SAS
Reverse Proxy
OS: 2 x 80 GB, 15K RPM SAS
Network
DB
Corp Subnet: 10.10.10.x/16
Cluster: 192.168.10.x/24
App
Corp Subnet: 10.10.10.x/16
Web
Corp Subnet: 10.10.10.x/16
Reverse Proxy
Internal: 172.20.10.x/24
External: 172.30.10.x/24
SSL Offloading : Load Balancer
Security
DB
Allow: App/LDAP/DNS – DB
connectivity on specific port numbers
Block: All other connections
App
Allow: Web/DB/LDAP/DNS – App
connectivity on specific port numbers
Block: All other connections
Web
Allow: App/RPi/LDAP/DNS – Web
connectivity on specific port numbers
Block: All other connections
Reverse Proxy
Allow: External NAT/App – RP
connectivity on specific port numbers
Block: All other connections
As Is Configuration

9. • vCPU : 16
• Memory GiB : 112
• Temp storage (SSD) GiB : 224
• Max data disks : 64
• Max cached and temp storage throughput:
IOPS / MBps (cache size in GiB) : 64,000 / 512
(576)
• Max uncached disk throughput: IOPS / MBps :
51,200 / 768
• Max NICs / Expected network bandwidth
(Mbps) : 8 / 12000
Standard_DS14_v2
• vCPU : 16
• Memory GiB : 112
• Temp storage (SSD) GiB : 224
• Max data disks : 64
• Max cached and temp storage throughput:
IOPS / MBps (cache size in GiB) : 64,000 / 512
(576)
• Max uncached disk throughput: IOPS / MBps :
51,200 / 768
• Max NICs / Expected network bandwidth
(Mbps) : 8 / 12000
Standard_DS14_v2
• vCPU : 16
• Memory GiB : 128
• Temp storage (SSD) GiB : 2,807
• Max data disks : 64
• Max temp storage throughput: IOPS / MBps :
80,000 / 800
• Max uncached disk throughput: IOPS / MBps :
20,000 / 500
• Max NICs / Expected network bandwidth
(Mbps) : 8 / 16,000
Standard_L16s
To Be Configuration

10. Tools Used & How Traffic Manager works
Tool Description
Global Traffic
Manager
Geographic & Nested Traffic
Manager
Regional Traffic
Manager
Performance, pointed to
Application Gateway
Application
Gateway
SSL Offloading, Session
Affinity, WAF
Load Balancer Layer 4 load balancer

11. North
America
Workloads
South
America
Workloads
North
Europe
Workloads
West Europe
Workloads
East Asia
Workloads
West Asia
Workloads
Geo 1 - Americas Geo 2 - EUROPE Geo 3 - ASIA
Traffic Manager – Travel Portal –
Global Endpoint
E.g. http://booking.travel.com
Traffic Manager –
Regional Endpoint
Traffic Manager –
Regional EndpointTraffic Manager –
Regional Endpoint
Global – Deployment
Architecture
Application Users
Global VNET Peering or VPN Gateway

12. North America - Region
Traffic Manager – Travel Portal –
Global Endpoint
E.g. http://booking.travel.com
Geo Region –
Deployment
Architecture
Web Layer
App Layer
DB Layer
Web Layer
App Layer
DB Layer
Traffic Manager –
America Endpoint
Application Gateway
Load Balancer
South America - Region
Europe
Asia
= NSG
Application Gateway
Global VNET
Peering or VPN
Gateway

13. North America - Region
Traffic Manager – Travel Portal –
Global Endpoint
E.g. http://booking.travel.com
Regional –
Deployment
Architecture
Web Subnet
DB Subnet
Traffic Manager –
America Endpoint
Europe
Asia
Application Gateway
Web Server Web Server
App Subnet
App Server App Server
Active DB
server
Passive DB
server
Internal Load Balancer
South
America
= NSG

14. Database Subnet
Web SubnetApp Subnet
Security –
Deployment
Architecture
Traffic Manager
Application
Gateway
Symbol Description
Subnet
NSG assigned to VM
NSG assigned to subnet

15. Questions?