Atlas Infrastructure Approach 20201015.pptx

Atlas Infra

1. 10/15/2020 V0.1 Azure Design Checkpoint Paul Snyman & Brantly Saye

2. Requirements confirmation FCS: “as-is” and business requirements EPI-USE: Atlas project workshops Design validation FCS key decisions EPI-USE: Atlas project architects Microsoft FastTrak & CSU teams (Hari, Todd, Manuel) Final designs/recommendations Final designs – Visio Blueprint documenting recommendations - Word Design Process

3. Server Team: internal IP allocation and server build Security Team: Robert (FCS) and Layer3 = FQDN, virtual IP, certificates FQDN process discovery

4. Network Security VMs Storage Backups & Disaster Recovery Authentication & SSO Integration SAP Landscape High Level Design Areas

5. KDD status On-Premise to Azure Connectivity Use ExpressRoute - decided, need to design Use of a Firewall on Azure Use Palo Alto NVA on Azure – decided, need to design Inbound connectivity policy to Azure Use On-Premise as front door to Azure – preference, need to design Outbound connectivity policy from Azure Don’t route all Azure traffic back on-premise – recommended, need to design Next steps Map end-to-end flow for Employee Express and Fiori “as is” Map the process for end-user internet access deployment/support Get Network Map document from Mark Atchison 5 Network Status

6. Status Have gotten feedback on as-is Backup processes today Have a draft Backup design ready to share Next Steps Need to present recommended Backup design to team Prepare DR design to share Compile summary of options for RPO/RTO with cost options for Key Decision Has a bearing on the VM service requests BCDR Status

7. 7